OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

xliff message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (XLIFF-34) ITS rules mapping for ITS namespace


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

Felix Sasaki commented on XLIFF-34:
-----------------------------------

I agree with the comment, we don't need that rules. From my understanding we can then delete the following rules from its.sch:

 <!-- Rules for Allowed Characters ...
<!-- Rules for Localization Quality Issue ...
<!-- Rules for Localization Quality Rating ...
<!-- Rules for Text Analysis ...

Before doing the removal, this should be double check.

> ITS rules mapping for ITS namespace
> -----------------------------------
>
>                 Key: XLIFF-34
>                 URL: https://issues.oasis-open.org/browse/XLIFF-34
>             Project: OASIS XML Localisation Interchange File Format (XLIFF) TC
>          Issue Type: Improvement
>          Components: ITS Module, validation artifacts
>    Affects Versions: 2.1_csprd02
>         Environment: http://markmail.org/thread/iyx7bclykssmisco
>            Reporter: Yves Savourel
>            Assignee: Felix Sasaki
>              Labels: AdoptionBlocker, request_tc_discussion, work_required
>             Fix For: 2.1_csprd03
>
>
> There is a set of ITS mapping rules in
> http://docs.oasis-open.org/xliff/xliff-core/v2.1/csprd02/schemas/its.sch (in
> 5.9.2 Module
> Namespace and Validation Artifacts).
> It seems to contain mapping for data categories that are represented using the
> normal ITS namespace. For example there is: 
>         <!-- Rules for Localization Quality Issue. Note that the pointer
> attribute is only available for the local
> locQualityIssuesRef attribute, hence the mapping is also only for that attribute
> and no other Localization Quality Issue attributes.
> But this limitation is OK since a processor can work with this data category
> locally.-->
>         <its:locQualityIssueRule selector="//xlf:mrk[@type='its:generic' and
> (@its:locQualityIssueType)]"
> locQualityIssuesRefPointer="@its:locQualityIssuesRefPointer"/>
> There are other instances of this.
> Do we need those mappings? If it's in the ITS namespace, an ITS processor should
> just be able to process the <mrk> no?
> Am I missing something?



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


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]