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

Re: Motivations for namespaces (sorry)

• To: "Thomas B. Passin" <tpassin@c...>
• Subject: Re: Motivations for namespaces (sorry)
• From: "Chiusano Joseph" <chiusano_joseph@b...>
• Date: Wed, 09 Jul 2003 10:50:08 -0400
• Cc: xml-dev@l...
• Organization: BAH
• References: <3.0.6.32.20030709091454.00dd8150@p...> <16140.3589.719083.55307@m...> <004a01c34620$76de16f0$6401a8c0@tbp1>

<Quote>
The namespace tells immediately which schema is in play.  Annotation
elements (this is XML Schema, so it has them) could be used, but they do
not always exist.  Without namespaces, it would be nearly impossible to
find out where things came from.  You would have to build an index by
reading all the schema imports (assuming no name conflicts), and refer
to the index whenever you wanted to look up information about an
element.

But with namespaces, you know at once.  This is much better, and is one
of the reasons that I recommended that we use namespaces in this task.
</Quote>

+1

Joe Chiusano
Booz | Allen | Hamilton

"Thomas B. Passin" wrote:
> 
> [David Megginson]
> > So far, we don't know, because most of this discussion is
> > hypothetical.  XML is scarcely used at all for widespread publication
> > of documents or data -- most XML projects are in-house or inside a
> > small set of exchange partners.  The few examples of widespread XML,
> > like RSS and the Linux Documentation Project, are narrowly confined to
> > a specific vocabulary.
> >
> 
> I have been involved with a schema for a standard that makes use of about
> five other standards by importing their schemas.  We are using a different
> namespace for importing each of them.  These other standards are being
> developed by  unrelated organizations.  Each one is complicated in its own
> right.  Each one is developed using a different conceptual model and a
> different concept of operations.
> 
> It often happens that one needs to look up some particular structure to find
> out more about it.  So one needs to know where it came from.  This is
> especially important for
> elements that contain an ungodly number of enumerated choices, which is the
> case in this work.
> 
> The namespace tells immediately which schema is in play.  Annotation
> elements (this is XML Schema, so it has them) could be used, but they do not
> always exist.  Without namespaces, it would be nearly impossible to find out
> where things came from.  You would have to build an index by reading all the
> schema imports (assuming no name conflicts), and refer to the index whenever
> you wanted to look up information about an element.
> 
> But with namespaces, you know at once.  This is much better, and is one of
> the reasons that I recommended that we use namespaces in this task.
> 
> Cheers,
> 
> Tom P
> 
> -----------------------------------------------------------------
> 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://lists.xml.org/ob/adm.pl>

begin:vcard 
n:Chiusano;Joseph
tel;work:(703) 902-6923
x-mozilla-html:FALSE
url:www.bah.com
org:Booz | Allen | Hamilton;IT Digital Strategies Team
adr:;;8283 Greensboro Drive;McLean;VA;22012;
version:2.1
email;internet:chiusano_joseph@b...
title:Senior Consultant
fn:Joseph M. Chiusano
end:vcard

• References:
  • Motivations for namespaces (sorry)
    • From: Gustaf Liljegren <gustaf.liljegren@b...>
  • re: Motivations for namespaces (sorry)
    • From: David Megginson <david@m...>
  • Re: Motivations for namespaces (sorry)
    • From: "Thomas B. Passin" <tpassin@c...>

• Prev by Date: Re: XSLT vs. CSS (Re: Indexing)
• Next by Date: RE: XSLT vs. CSS (Re: Indexing)
• Previous by thread: Re: Motivations for namespaces (sorry)
• Next by thread: Re: Motivations for namespaces (sorry)
• Index(es):
  • Date
  • Thread