ubl-ndrsc — archive

[System]

Here's my understanding of the difference between xsd:appinfo and xsd:documentation, also based on the way I've seen them used in other schemas. xsd:documentation should only be used for human readable documentation. xsd:appinfo is for program readable metadata used by other applications. Usually, a separate XML namespace is defined for app-specific or vendor-specific values. For example, define the Java class name used to bind a complexType to code, used when the Java class name is different from the complexType name. Similarly, record the database table name used to store the data. Both of these are too application/tool specific for UBL's purposes. xsd:appinfo has also been used to hold Schematron constraints that go beyond the XSD's capabilities. A downstream processor would parse out the Schematron rules and apply them to doc instances. Thus, you might consider using both appinfo and documentation. Assuming that XHTML is only for humans, put it in xsd:documentation. If some of the Core Components metadata from the spreadsheet might be used by downstream processors or context engines, you might put it in xsd:appinfo using tags derived from the core components metamodel that Bill was working on. Cheers, Dave Carlson