numishare
numishare copied to clipboard
ewg118
validation errors in Numishare-produced NUDS
The attached, bare-bones NUDS file generated by Numishare does not validate against the current NUDS schema, suggesting that fuller records will not either. Is that likely to cause problems? Does it make sense to separately correct (e.g., via XSLT) Numishare output to be conformant?
The XSD standard is unnecessarily rigid, requiring a lot of elements to appear in a specific order. It is possible to use XPath to order elements to conform to the XSD within the XForms application, but the XPath would be inordinately complex, with no real gain since the order of elements in the XML document isn't reflected in the HTML or any other serialization. I would probably develop a Schematron schema and deprecate XSD if I had the time.
If there are specific elements that can be added in the Numishare editor that don't appear in the XSD at all, please let me know. I am working on syncing the editor to the XSD in principle (basic document structure without regard to specific element ordering)
