/ "Eric van der Vlist" <[EMAIL PROTECTED]> was heard to say: | Another option is to add these attributes through a XSLT transformation or | a regular expression! | | After all, RNG schemas are also XML documents (in their XML syntax) or | text documents (in their compact syntax) and they have the flexibility | that these formats give them. | | My RNG schemas tend to live and evolve a lot thanks to XSLT...
The DocBook grammars are built this way too. Not to solve this
particular problem, but to make it convenient to add attribute
co-constrants and Schematron rules.
For example:
ctrl:other-attribute [ name="db.biblio.class.attribute"
enum-name="db.biblio.class-enum.attribute"
other-name="db.biblio.class-other.attributes" ]
Sets up the patterns for the "class" attribute on bibliography elements
where class has to be an enumerated value and, if the value is "other"
otherclass must be specified. (If it is not other, otherclass may not
be specified.)
And:
ctrl:exclude [ from="db.formal.blocks" exclude="db.formal.blocks" ]
Adds Schematron rules to db.formal.blocks to exclude db.formal.blocks.
All in all, very handy.
| Finally, as John has just mentioned, is that worth making changes to RNG
| to solve something that is solved by NVDL?
Are there NVDL-aware validators out there now?
Be seeing you,
norm
--
Norman Walsh <[EMAIL PROTECTED]> | Everything should be made as simple as
http://nwalsh.com/ | possible, but no simpler.
pgpVbnXhNb1FM.pgp
Description: PGP signature
