[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Xml internationalization design

• To: liam@w...
• Subject: Re: Xml internationalization design
• From: "tom tom" <tomxsllist@h...>
• Date: Tue, 09 May 2006 09:50:16 +0100
• Bcc:
• Cc: xml-dev@l...
• In-reply-to: <20060508173416.GE13492@w...>

>(1) if you need to select or manipulate all the titles as a group
>(3) if you need to know when all the titles have finished, e.g for
>     formatting purposes (this is very close to (1) in practice)

the data is being processed with XSLT 2 hence I can use xsl:for-each-group 
to acheive this in the rare cases where it happens. I think your other 
points balance each other out for our purposes - ie it is closer to how we 
think about the data but it makes generic software harder.

thanks for your help.



>From: Liam Quin <liam@w...>
>To: tom tom <tomxsllist@h...>
>CC: xml-dev@l...
>Subject: Re:  Xml internationalization design
>Date: Mon, 8 May 2006 13:34:16 -0400
>
>On Mon, May 08, 2006 at 11:31:27AM +0100, tom tom wrote:
>[...]
> > The latter will lead to much less verbose XML but the titles tags aren't
> > wrapped up in a single extensible parent. I would be very grateful if
> > someone could point me to somewhere which advises on best practice here.
>
>It depends... :-)
>Your approach is a good one in either case.  Reasons for a wrapper
>might include
>(1) if you need to select or manipulate all the titles as a group
>(2) if you have multiple sets of titles that must be distinguished
>(3) if you need to know when all the titles have finished, e.g for
>     formatting purposes (this is very close to (1) in practice)
>(4) if it is closer to the way you think about the information
>(5) if it helps you write generic software to process the data.
>
>Consider an author element, where the order of first/last name might
>be different in Japan, or where the author might be spelt differently,
>     <author lang="en">St. Paul</author>
>     <author lang="it">S Paulo</author>
>or whatever.  But you might have a document with two adjacent
>author elements, and in that case you'll certainly need a wrapper
>of some kind -- same with two adjacent paragraph elements.
>
>Liam
>
>--
>Liam Quin, W3C XML Activity Lead, http://www.w3.org/People/Quin/
>http://www.holoweb.net/~liam/
>
>-----------------------------------------------------------------
>The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
>initiative of OASIS <http://www.oasis-open.org>
>
>The list archives are at http://lists.xml.org/archives/xml-dev/
>
>To subscribe or unsubscribe from this list use the subscription
>manager: <http://www.oasis-open.org/mlmanage/index.php>
>

_________________________________________________________________
Be the first to hear what's new at MSN - sign up to our free newsletters! 
http://www.msn.co.uk/newsletters

• Follow-Ups:
  • Improving XML desing?
    • From: <juanrgonzaleza@c...>

• References:
  • Re: Xml internationalization design
    • From: Liam Quin <liam@w...>

• Prev by Date: Re: Java NVDL implementation
• Next by Date: Improving XML desing?
• Previous by thread: Re: Xml internationalization design
• Next by thread: Improving XML desing?
• Index(es):
  • Date
  • Thread