Re: [ubl-lcsc] A problem with out schema code

[Tim McGrath <tmcgrath@portcomm.com.au>]

excellent detective work, my dear watson.  you have found the deliberate 
error/trap for the unobservant. :-)

Actually,  i must take your word for this - i am still reading the XSD 
primer.

Whilst we must obviously comply with XSD, i dont think this detracts 
from the review we are undertalking.  However we will fix it in the next 
release.  We can discuss this next week.

Gregory, Arofan wrote:

>Tim:
>
>In going through the XSD spec in line of duty, I realized that we have made
>a mistake in our use of the "documentation" element. We have been using the
>"source" attribute to hold a keyword, when according to the spec it is
>supposed to hold a URN! (This URN references the source of the tagging you
>put inside the documentation element.)
>
>This is not a major problem, but we will need to fix what we are doing, as
>it is incorrect according to the XSD spec (unless I'm very much mistaken).
>We could use AppInfo, or invent some clever tagging of our own to use
>directly inside of the documentation element (which, like AppInfo, has a
>content model of "ANY").
>
>Just wanted to raise the issue, so we can make sure and fix it - it will be
>very interesting to see if any of our reviewers have a strong enough grasp
>of XSD to catch us out on this one, since parsers we're using obviously
>don't seem to enforce this bit (I'm not even sure from reading the spec that
>they should...)
>
>Cheers,
>
>Arofan
>
>
>----------------------------------------------------------------
>To subscribe or unsubscribe from this elist use the subscription
>manager: <http://lists.oasis-open.org/ob/adm.pl>
>
>.
>

-- 
regards
tim mcgrath
fremantle  western australia 6160
phone: +618 93352228  fax: +618 93352142