A
Andy Chambers
Hi All,
Is there a way to define an empty named pattern? Here's the use-case.
I'm trying to use relax-ng to specify an extendable schema.
Basically, people should be able to tack on whatever they like to a
core set of elements/attributes provided their extensions are in a
different namespace.
It would be nice if I could split it up into
core.rnc
ext-1.rnc
ext-2.rnc
so that a final schema could be made from just doing
include "core.rnc"
include "ext-2.rnc"
which would allow elements/attributes from ext-2 but not ext-1.
I thought I could do this by adding the named pattern "extension" to
each element defined in core.rnc. ext-1 etc could then redefine
extension accordingly.
If there's a better a way to accomplish similar goals, I'd be
interested in hearing them too.
Cheers,
Andy
Is there a way to define an empty named pattern? Here's the use-case.
I'm trying to use relax-ng to specify an extendable schema.
Basically, people should be able to tack on whatever they like to a
core set of elements/attributes provided their extensions are in a
different namespace.
It would be nice if I could split it up into
core.rnc
ext-1.rnc
ext-2.rnc
so that a final schema could be made from just doing
include "core.rnc"
include "ext-2.rnc"
which would allow elements/attributes from ext-2 but not ext-1.
I thought I could do this by adding the named pattern "extension" to
each element defined in core.rnc. ext-1 etc could then redefine
extension accordingly.
If there's a better a way to accomplish similar goals, I'd be
interested in hearing them too.
Cheers,
Andy