[Home] [By Thread] [By Date] [Recent Entries]

  • From: "Radu Cernuta" <radu.cernuta@g...>
  • To: "Jeff Lowery" <jlowery@m...>
  • Date: Tue, 6 Feb 2007 23:43:43 +0100

<?xml version="1.0"?>
<grammar xmlns="http://relaxng.org/ns/structure/1.0">
    <start>
        <ref name="rootElement"></ref>
    </start>
   
    <define name="rootElement">
        <element>
            <anyName>
                <except>
                    <name>interestingElement1</name>
                    <name>interestingElement2</name>
                    ....
                </except>                   
            </anyName>
            <ref name="children"></ref>
        </element>
    </define>
....

Life is made of choices. Sometimes you just got to cut the knot.

Of course, you can also cut is differently and move to XML Schema, where you don't have the flexibility of the <exclude> for namespaces, but you can rely on xsi:schemaLocation attributes in the instance documents(and on the users that to place them there correctly) or on schemas placed so that they can be found using the namespace URI.

Greetings,
Radu Cernuta

2007/2/6, Jeff Lowery <jlowery@m...>:

<?xml version="1.0"?>
<grammar xmlns="http://relaxng.org/ns/structure/1.0">
    <start>
        <ref name="rootElement"></ref>
    </start>
   
    <define name="rootElement">
        <element>
            <anyName>
                <except>
                    <nsName ns="http://interestingElements.com"></nsName>
                </except>                   
            </anyName>
            <ref name="children"></ref>
        </element>
    </define>

…

 

Aside from this example, how would this approach work for interesting elements that are in the same namespace as the base schema?

 

 




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member