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

Re: Vocabulary Combination


combination problems
Tim Bray <tbray@t...> wrote:
| Arjun Ray wrote:
| 
| > Correct.  The spec is silent on this, and thus useless for the general
| > problem of vocabulary combination *by syntax*.
| 
| Arjun is really getting close to troll territory here,

Speak for yourself, and use a killfile if it helps.

| but this very strong claim should not go unrefuted.  

I submit that you haven't thought enough about the problem.

| The syntactic problems of combining markup from multiple vocabularies 
| include:
| 
| 1. avoiding collisions

A non-problem.  The premise underlying this is false.  (It's the same
whopping non sequitur as in the "Motivation" section of the spec.) 

| #1 is easy, 

Yes, but not a easy as it appears.

| and namespaces solve it. 

In a silly and myopic sort of way, yes.  That's what you get with
non-sloutions to non-problems.

| That's all they've ever done, and all they've ever been claimed to do.

True, as far as the spec is concerned.  It's when people try to read more
into the spec (as the "Motivation" section would [expletive deleted] them into) that the
real problems start.

| 2. expressing syntactic restrictions on the markup from each individual 
| vocabulary

| #2 is harder, and is addressed, if not completely solved, by DTDs and 
| their successors.

Yes, the notion that names from a vocabulary can be used (in conjunction)
in some ways but not in others.  But that isn't the concern here, which is
with instance markup only.

| 3. expressing syntactic restrictions on the way the vocabularies
|     combine

Not necessary to definitions of vocabularies.  Necessary to authors for
individual documents.

| #3 is harder still, and is addressed, if not completely solved, by more
| more modern schema languages like XSD and RNG.

It's an interesting problem from the perspective of derivative schema
construction.  But the premise that a document must always be in its
entirety an instantiation of a unitary encompassing schema is false.  Or
more accurately, unnecessary. 

| 4. (maybe) expressing rules for how to extract vocabulary-specific
|     subsets of the combination.  But this is maybe getting into
|     semantic territory.
 
| #4... nope, I think that's a semantic ingegration problem.

No, the extraction procedure can be entirely generic, at the parsing
level.


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.