[OASIS Issue Tracker] (LEGALRULEML-26) XSLT that post-processes the generated XSD schemas should change xs:NCName to xs:ID

From
OASIS Issues Tracker <>
Date
2016-01-05T22:24:48+00:00
ID
Thread
[OASIS Issue Tracker] (LEGALRULEML-26) XSLT that post-processes the generated XSD schemas should change xs:NCName to xs:ID
[ https://issues.oasis-open.org/browse/LEGALRULEML-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61527#comment-61527 ] 

Tara Athan commented on LEGALRULEML-26:
---------------------------------------

Note that using xs:ID on @key does not guarantee uniqueness of all key values, since @key on elements in the RuleML namespace uses CURIEs. But it is better than nothing - using this datatype would catch some validation errors regarding duplication of @key values.

> XSLT that post-processes the generated XSD schemas should change xs:NCName to xs:ID
> -----------------------------------------------------------------------------------
>
>                 Key: LEGALRULEML-26
>                 URL: https://issues.oasis-open.org/browse/LEGALRULEML-26
>             Project: OASIS LegalRuleML TC
>          Issue Type: Bug
>          Components: XSD schema, XSLT for post-processing of schemas
>         Environment: The XSLT template to change xs:NCName (used for @key on LRML elements and also @refersTo) to xs:ID is missing.
>            Reporter: Tara Athan
>            Assignee: Tara Athan
>            Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v6.2.2#6258)