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-41) Clarify ITS Module attributes definitions


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

Yves Savourel commented on XLIFF-41:
------------------------------------

Maybe the HTML file is not reflecting the latest changes (although it is dated March-3, yesterday), but not all attributes have these two changes implemented yet.

For example:

We have: "Provenance Records Standoff Reference - the provenanceRecordsRef attribute maps to and from the [ITS] defined provenanceRecordsRef attribute." instead of "Provenance Records Standoff Reference - the provenanceRecordsRef attribute is the [ITS] defined provenanceRecordsRef attribute."

We have "Revision Organization Reference - the revOrgRef attribute exactly corresponds to the [ITS] defined revOrgRef attribute." instead of "Revision Organization Reference - the revOrgRef attribute is the [ITS] defined revOrgRef attribute."

The few first ITS attributes like localeFilterList and localeFilterType have links to the ITS LOCAL implementation, but after that it's not the case anymore. For example locQualityIssueComment has no link at all, locQualityIssueEnabled has a link to itself, so does locQualityIssueProfileRef, and so on.

The resolution for this issue looks fine, but I don't think it's implemented completely yet.


> Clarify ITS Module attributes definitions
> -----------------------------------------
>
>                 Key: XLIFF-41
>                 URL: https://issues.oasis-open.org/browse/XLIFF-41
>             Project: OASIS XML Localisation Interchange File Format (XLIFF) TC
>          Issue Type: Improvement
>          Components: ITS Module
>    Affects Versions: 2.1_csprd02
>         Environment: http://markmail.org/thread/gnic54jjpq5hyyuk
>            Reporter: David Filip
>            Assignee: David Filip
>            Priority: Minor
>              Labels: Proposed, editorial
>             Fix For: 2.1_csprd03
>
>
> In the section "5.9.12 Module Attributes" we define both ITSM and ITS
> attributes, but mostly ITS attributes.
> They usually have a definition that starts like this (using taClassRef as an
> example):
> [[
> 5.9.12.31 taClassRef
> Text Analysis Class Reference - the taClassRef attribute exactly corresponds to
> the [ITS] defined taClassRef attribute.
> ]]
> The wording "...exactly corresponds to the [ITS] defined taClassRef attribute."
> is, in my view, misleading as it does not state that
> it is the ITS attribute itself. From the text and the lack of namespace
> information, one could think the attribute is to be used
> like this: <mrk id='1' taClassRef ='...'>.
> It seems we should have a definition more like:
> [[
> Text Analysis Class Reference - the ITS taClassRef attribute
> ]]
> With a link to the attribute in the ITS specification.
> I know I have mentioned this for mtConfidence already
> (https://issues.oasis-open.org/browse/XLIFF-36) but I think this is something
> that should be addressed for all ITS attributes.



--
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]