Am 18.04.2011 um 07:16 schrieb ac:
Yes I can create a dictionary like
<dic>
<word>
<instance xml:lang="en" gender="m">Mr</instance>
<instance xml:lang="en" gender="f">Mrs</instance>
<instance xml:lang="fr" gender="m">M.</instance>
<instance xml:lang="fr" gender="f">Mme</instance>
...
</word>
</dic>
but, given the proper namespace declarations, I could also have it as
<dic>
<word en:instance="Mr" en-f:instance="Mrs" fr:instance="M."
fr-f:instance="Mme" ... />
...
</dic>
IMO this is a good example why the perceived verbosity of some XML is a good
thing. Regarding flexibility and future maintenance the first version has clear
advantages: It requires almost no effort to add more languages, or more genders
(if needed) or other attributes to the dictionary if needed, while the second
version needs rules how to create new namespace names (and an expanded name for
each) and requires updates to the validation schema for each change.
I would rank maintainability if XML sources far higher than the number of
nodes. Regarding performance of XSLT processors I don’t think there is a
difference if the correct keys are defined.
- Michael
--
_______________________________________________________________
Michael Müller-Hillebrand: Dokumentation Technology
Adobe Certified Expert, FrameMaker
Consulting and Training, FrameScript, XML/XSL, Unicode
Blog [de]: http://cap-studio.de/
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--