OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: [xml-dev] More on namespaces...

[ Lists Home | Date Index | Thread Index ]

"Seairth Jacobs" <seairth@seairth.com> wrote:

| 1) Suppose you have a vocabulary that states that only <B> may be within
| <A>.  Now suppose you have another vocabulary with element <C>.  If one 
| were to do <ns1:A><ns1:B/><ns2:C/></ns1:A>, would the document still be 
| valid according to the first vocabulary?

I don't think this is a well-formed question.  It confuses documents with
document types.  The schema for a vocabulary defines a document type; how
a document type *applies* to any particular document is a separate issue.
Must this document type always apply point-by-point to the entirety of the

If you say yes, then the answer is no, this document is not valid, because
by construction it has "foreign" material that the schema for vocabulary
ns1 does not account for.

If you say no, then the answer is yes, the document is valid in the sense
that it has a partition which meets all required constraints of the ns1

| 3) In one of the original posts of the recent thread, there was a sample
| document:

Which was taken from an article advocating namespaces:


From the passage in that article introducing this very sample document:

: So let's set up a scenario: suppose XML.com wanted to start publishing 
: reviews of XML books. We'd want to mark the info up with XML, of course, 
: but we'd also like to use HTML to help beautify the display. Here's a 
: tiny sample of what we might do:

I thought there was a basis for "document views", but the author of the
article has since questioned this interpretation, so what the example is
really supposed to be illustrating must be something else.

| I am wondering if the real problem here is the way in which the 
| vocabularies are being mixed.  [...] I guess the point is...  in the
| original XML above, are we really trying to figure out how to separate 
| the vocabularies successfully, 

Apparently, this is "not useful", according to the author.

| or are we really seeing a case where the design is bad to start with?

Depends on what the design is intended to achieve, no?

| 4) Should a vocabulary be able to dictate how other vocabularies can be 
| used with it? 

No.  That way lies madness. 


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS