Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: How to define a "anywhere" node in my XSD

From: Peter Flynn <peter.nosp@-.--------.-->
To: NULL
Date: 9/2/2006 4:36:00 PM

Stefan Ram wrote:
> Peter Flynn <peter.nosp@m...> writes:
>>>>>> I would like to specify in my XSD that the "Documentation" element can
>>>>>> be added everywhere in the XML document. A bit like the
>>>>>> xs:documentation node.
>> Yes, this is why it's unlikely to happen. Sadly the use of XML for 
>> dealing with real-life text documents was sidelined in the mad rush
>> to use XML for handling data, for which it is not always suited.
> 
>   I do not know XSD, but I guess that the above can already be
>   done today, by explicitly allowing this element for every
>   element (repeatedly for each element).

Oh yes (see earlier posts). The nice thing about Exceptions was that
they only had to be specified on the earliest ancestor element type,
and were then inherited to all descendants automatically. But they
are a DTD solution, not an XSD solution.

The solution, of course, is to use schema modelling software like
Relax/NG, as you imply.

///Peter

>   So the only problem of the OP might be that this has to be
>   repeated, but this can be eliminated by generating the XSD
>   from a program or using a preprocessor. I mean, who still
>   writes his XSD manually, today? (seriously; I don't know,
>   because I have no experience with XSD.)
> 
>   One even might consider to write a tool that translates an
>   SGML-DTD to the best XSD-approximation, which would include
>   this capability.
> 


transparent
Print
Mail
Like It
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.

.
.

transparent

transparent