[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: Separate data from rules ... is the XML Schema 1.1 <as
Michael Kay wrote > I don't think the split between > structural rules and business rules equates at all closely to the split > between grammar and predicates. I agree. But I would say that the demarcation between what constraints to put in XSD (whether in the grammar or in assertions) or RELAX NG and in a subsequent Schematron schema (or in derived XSD schemas) should reflect or align with the institutional arrangements of schema ownership, responsibility and maintenance. At one extreme, if a code list (e.g. a product code list or country code list) is maintained by another organization, then it may be that the XSD schema should not enumerate the values but just give the regex pattern they conform to (e.g. [A-Z]{2-3} ) with the external code list validated by the separate Schematron schema. Or, it may be that the purpose of the schema is to collect as many different constraints as possible in order to be the prime documentation for developers,regularly updated and maintained. In that case, an enumeration would be appropriate. Cheers Rick Jelliffe
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] |
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|