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-57) Unhelpful comments in the ITS module


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

David Filip commented on XLIFF-57:
----------------------------------

Yves, the warnings are probably too obvious for someone who already implemented ITS 2.0.
But here and elsewhere I am trying to assist the "naïve" ITS implementer who approaches the ITS from the XLIFF perspective.
I am unable to bring any new arguments to the table and it seems to me you aren't either.
So just to summarize for the last time:
The PR says (in each of the 3 cases), the annotatorsRef is not REQUIRED if the annotation is in scope of another annotatorsRef for that datacat.
Since the ITS tool reference is obligatory in those three cases and no one else but the creator of the annotation can tell if the annotatorsRef resolves with the intended value, I am absolutely certain this is a very helpful warning for people who haven't done ITS before.. And I am open to improving the wording if someone has a proposal...
The issue is actually broader than removing or keeping these three warnings. Felix and you want to have maximum done by pointing to the W3C Recommendation, but IMHO we are not doing a good job if we force the implementer to go back to the W3C spec too often or at all.  
What we have in the spec now is a kind of compromise (mostly driven by who originally wrote the provisions for each of the datacats) as doing it one way or the other would take a huge rehaul of the whole module spec.. and I hope we don't want that.
Therefore, I wouldn't waste any more time and effort on that and simply resolve this and other issues of this kind (you logged a few but they are not in the JIRA yet) simply by ballots..

> Unhelpful comments in the ITS module
> ------------------------------------
>
>                 Key: XLIFF-57
>                 URL: https://issues.oasis-open.org/browse/XLIFF-57
>             Project: OASIS XML Localisation Interchange File Format (XLIFF) TC
>          Issue Type: Bug
>          Components: ITS Module
>    Affects Versions: 2.1_csprd04
>         Environment: http://markmail.org/thread/e5uzazha44zfxm6f
>            Reporter: Yves Savourel
>            Assignee: Tom Comerford
>            Priority: Minor
>              Labels: editorial, request_tc_discussion, work_required
>             Fix For: 2.1_cs01
>
>
> In
> http://docs.oasis-open.org/xliff/xliff-core/v2.1/csprd04/xliff-core-v2.1-csprd04.html
> there are 3 warnings starting with "This
> annotation can be syntactically in scope of a relevant."
> I believe the wording is confusing and does not really help the implementers and
> removing the text would improve the specification.
> As noted here in
> https://lists.oasis-open.org/archives/xliff/201705/msg00170.html this was issue
> https://issues.oasis-open.org/browse/XLIFF-53 that was closed temporarily to
> move forward.



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