Lists Home |
Date Index |
- From: "Ogievetsky, Nikita" <firstname.lastname@example.org>
- To: "'email@example.com'" <firstname.lastname@example.org>
- Date: Thu, 4 Feb 1999 12:32:27 -0500
I thought of namespace prefixes as aliases. If parser is capable
to resolve alias <=> alias definition than it should not matter which
alias one uses to define the same namespace?
Ronald Bourret wrote:
>> Imagine A, B, C, D and E and all users of some XML data. A and B exchange
>> data and agree to use A's namespace and that "<an:t>title</an:t>" is a
>> book title (among other things).
>> Elsewhere, C and D also exchange data and agree to use D's namespace and
>> that "<dn:t>title</dn:t>" is a book title.
>> 1. E comes along and wants to create data and exchange data with A, B, C
>> and D. What does E use? If E creates a new NS "<en:t>title</en:t>"
>> A, B, C and D have to update there procedures to cater for this?
>E should use <an:t> to exchange data with A and B and <dn:t> to exchange
>data with C and D. If E creates their own DTD, then everybody who wants to
>exchange data with E needs to update their software, which is unlikely to
>make E very popular. A much better solution is to get everybody (A-E) to
>agree on a single set of tags in the first place.
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)