Representing ER models (and other abstractions) in ISO Schematron
by Rick Jelliffe
I think what it quite powerful about this approach is that we can separate the information relationships from the XML serialization. Fields can be child elements, attributes, attributes of the parent, any kind of XPath, we don't care. Similarly, if two fields are related, they may use a key or containment, but we don't care. If you like you see this a technique for capturing information from a model in a form which also happens to hook into Schematron validation; but you can use the captured model for non-Schematron purposes too!
(This is an updated version of a post to XML-DEV mail list, in Nov 2006.)
Hey, that's cool!
W^L+: Thanks. Yes, if there is any demand, a mapping between DDL and Schematron would be logical to provide.