Hi Fabio, Monica,
I have been running various tests on all my Akoma Ntoso code for the past two days now - it seems I've got a rather lot now. Without a workable car, I have plenty of time on Saturday. (I'm not sure if I should use a smiley face or a sad face).
In my testing, I have come across one issue that relates to the schema:
If you remember, earlier the @id notation used dashes as separators. Tom Bruce pointed out that there are some numbers that contain dashes in the U.S. Code. That's why we went to the underscore separator. Well, I have come across the dashed values. When I generate the @eId I get values such as sec_31-2. It turns out that this is disalloewed as an xs:NMTOKEN does not permit dashes.
I think that it is important that the dash be preserved in the numeric part of the number. It is required for use by the resolver and its existence is the reason we use the more awkward underscore separator in the first place.
My testing continues...
Regards,
Grant
____________________________________________________________________
Grant Vergottini
Xcential Group, LLC.
email:
grant.vergottini@xcential.com
phone: 858.361.6738