 |
|
|
Not to preach to the choir, it is because we lose the distinction of tag
sprinkling vs application. That's been a hole in the fabric ever since we
lost the tight coupling to formal schema definitions. It isn't that both
options aren't viable. It helps to distinguish them and point out that
free-hand sprinkling (making up tags just in time) has downsides, and that
if one finds they have to document the tags/elements, there are several
levels of optional rigor. Then it is a matter of choosing among those
formally (given some rule or policy) even if the policy is "pick one, we'll
try it, if we like it, we'll keep it, if not, go to plan b".
See Idiocracy. Rule by consensus isn't all that hot. :-)
len
From: Deborah Aleyne Lapeyre [mailto:dalapeyre@m...]
And since the definition of "tagging" is usually
"applying markup to the date", why not?
|
|
| |
These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.
| |
| |
|
|
|
