Altova Mailing List Archives


Re: Namespaces and Schemes

From: "Thomas B. Passin" <tpassin@----.--->
To: xml-dev@-----.---.---
Date: 11/12/2000 6:06:00 AM
I haven't seen your example, but it sounds like a job for
Schematron.

Tom Passin

Sean B. Palmer asked -

...
>those names. However, I am developing a system (well a
processor for a
> document framework; see the RDF IG lists) whereby the
namespace of a
> document and its scheme are very closely binded, and I
*need* some means of
> tying them together before I can go on to the next step:
which is
> recognising parsing and separating self describing rules
etc.
>
> This is a messy problem, and I realise this sort of thing
usually start big
> arguements, but I just want to find the "easiest" solution
for my particular
> program. The problems I am facing at the moment are:-
> 1. DTDs can't be mixed on the level that I am trying to
achieve this
> 2. XML Schemas can't be validated on this level
> 3. RDF Schemas don't have anything to do with the
structure I need
> If you still haven't got a clue as to what I am hinting at
here, look
> through the RDF IG archives for my SDF example, and tell
me how on earth I
> am supposed to validate it (let's just say it mixes a
*lot* of different
> vocabularies).

Disclaimer

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.