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

Re: Musing over Namespaces

  • From: "Steve Baty" <steve@r...>
  • To: <xml-dev@i...>
  • Date: Wed, 15 Dec 1999 11:57:40 +1100

xpath register namespace
>I was thinking more along the line of English dictionary which
>allows multiple entries per word.  Each entry is qualified with
>some XPath-subset.  Company-specific entries should be possible
>if qualified with some proprietary information.

Don,

Although I agree to a certain extent that xml tags could conform to a
dictionary-style approach to registration, is there any real benefit to this
approach when each definition for a particular element requires additional
information such as "some XPath-subset" and "some proprietary information".

Why not just reference the namespace in the registered definition?

On a slightly different note, if I were to register an element such as
"purchase" which had child elements "card_type", "product_id" and "price"
how would I differentiate these child elements from somebody else's elements
of the same name? If each element in the registry had a namespace
declaration I could follow the thread of the element def'ns fairly easily.

The main problem I see in the registry approach, albeit
registry-as-dictionary, is that there would need to be some way to
differentiate between "my" "purchase" element, and the one that, say, a
stockbroker might use to define a request for shares "purchase".

The way I see it, what you are proposing would look something like:
purchase: i) element, sun microsystems, attributes:approved (true|false),
child elements (payment_type,delivery_address,...)
ii) attribute, foo_bar corp, element:transaction;

etc

Now, how might I, looking at this defn, determine who's defn of
"payment_type" I should go and look up? Perhaps instead of a dictionary
we're really talking thesaurus!?

I suppose the point is: if you need to include company-specific and XPath
information into the definition in the registry in order to identify which
element we're "really" talking about, why not use namespaces?

=========================
Steve Baty
Technical Designer
Red Square Productions
http://www.redsquare.com.au
steve@r...
Ph: +612 9519 4599
Fax: +612 9519 4699






xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To unsubscribe, mailto:majordomo@i... the following message;
unsubscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)



PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
 

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.


Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.