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

Re: Vocabulary Combination

Arjun Ray wrote:
> Paul Prescod <paul@p...> wrote:
> | Arjun Ray wrote:
> |> "It can't be done" is an acceptable answer, btw.
> | 
> | There is no global rule about the semantics of embedded namespaces. 
> Semantics ("what names mean") wasn't the issue.  If you mean that there is
> no global rule about the generic semantics of embedding syntax (using the
> namespaces device) then I agree.  That was, after all, my question. :-)

Right. You asked a question and I provided an answer.

> | Any rule that handled the book/html case would fall apart in the face of 
> The general problem is the same.

Not really. One is a code/literal problem. The other is a "reuse these 
semantics" problem. They are quite different which is why there is no 
general semantics for embedding namespaces.

> | Nevertheless, they have found widespread use as a trigger for 
> | specific processors, like XSLT engines.
> Actually, they have found widespread use for DWIMming. 

It isn't DWIMming. XSLT is very precise about how to interpret 
"extension elements" versus "literal result elements" versus "built-in 
elements". WSDL is also very precise. RDF is also very precise. They 
just don't all use the same rules. They ascribe their own semantics to 
the syntactic convention of "foreign namespaces".

> ... The asymmetry in
> John's first stab at a procedure is an example.   The real concern there
> was "knowing" when to leave out #PCDATA.

If BookML were formally defined then the formal definition should tell 
you how to handle PCDATA in the extraction of the implicit XHTML 
document. People are even working on languages specific to that 
extraction problem. But the simple answer is you cannot tell how to 
segment namespaced fragments just by relying on the semantics defined in 
the Namespaces specification. You must also rely on the rule defined by 
your vocabulary.

Actually, it gets worse. If you are presented with an XML document and 
no external type metadata, there is no way to know which namespace to 
use as the one that defines the fragmentation semantics.

  Paul Prescod


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.
First Name
Last Name
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.