ubl-ndrsc — archive

[bill burcham]

If I understand you, then for instance, if a user needed to eliminate zip code from an Address (assuming that Zip code was "required") then that user is going to suddenly be using ur-schemas for all the doc-types that use Address. This is the "cascade" effect we talked about in Barcelona. I don't have a solution to this problem -- I just want to be sure we're all aware of it. For those who haven't read the example: it defines an ur-schema with a few types, one of which, CountryCode has a Code element. The "UBL" schema is derived from that one (by _restriction_) and makes some of the elements required (they're all optional in the ur-schema by definition). I then define a "third-party" schema that derives from the ur-schema and changes CountryCode so as to replace the Code element with an element called "NewElement". Two instances are provided: a vanilla UBL one and a "third-party" one. In my original message (the one Matt just replied to) I provided an example of the ur-proposal as I understood it -- and it required xsi:type everywhere. Matt: will you please correct my example and post it back to the list.