[OASIS Issue Tracker] (XLIFF-45) wrong namespace for id in the ITS module

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/XLIFF-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=65761#comment-65761 ] 

David Filip commented on XLIFF-45:
----------------------------------

Changed locQualityIssuesRef from IDREF to IRI. This is related to https://issues.oasis-open.org/browse/XLIFF-45 as welll as https://issues.oasis-open.org/browse/XLIFF-9
The attrribute cannot be IDEREF as it is IRI in the W3C namespace
The Schematron has be changed to check IRI rather than NMTOKEN or IDREF. The IRI in locQualityIssuesRef still MUST reference within the unit. The provenanceReordsRef IRI MUST reference within the unit or it's ancestor group or file..

> wrong namespace for id in the ITS module
> ----------------------------------------
>
>                 Key: XLIFF-45
>                 URL: https://issues.oasis-open.org/browse/XLIFF-45
>             Project: OASIS XML Localisation Interchange File Format (XLIFF) TC
>          Issue Type: Bug
>          Components: ITS Module, validation artifacts
>    Affects Versions: 2.1_csprd02
>         Environment: http://markmail.org/thread/vbf6utpojxk4jdtj
>            Reporter: David Filip
>            Assignee: Soroush Saadatfar
>            Priority: Critical
>              Labels: AdoptionBlocker, Approved, material
>             Fix For: 2.1_csprd03
>
>
> The W3C its: namespace reuses xml:id on the elements it defines
> Our its.xsd introduces an its:id of the type xs:id
> I am afraid there is no such attribute in the W3C namespace because it
> actually reuses the xml:id.
> Thus, the xsd needs to change the its:id to xml:id and the prose spec needs
> to make clear in 5.9.12 and 5.9.12.4 that the module uses xml:id and not
> its:id (or even itsm:id that it had been using in csprd01). Both are of the
> xs;id type, just that we don't control the its: namespace so that we are
> not free to declare it where it didn't exist..



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