[OASIS Issue Tracker] (XLIFF-63) Incomplete example for External Resource

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

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

David Filip commented on XLIFF-63:
----------------------------------

The proposed resolution (Complete the exmaple) has been printed as cs01 candidate dated 01 August 2017. 
http://tools.oasis-open.org/version-control/browse/wsvn/xliff/trunk/xliff-21/xliff-core-v2.1-cs01.pdf 

Hereby a Call for Dissent is made. 

If no dissent is recorded by Saturday August 11, 2017 23:59 PDT, as a comment on this issue or as an email to the XLIFF mailing list xliff@lists.oasis-open.org referencing this Issue, the currently applied disposition will be deemed approved by consensus of the TC.

> Incomplete example for External Resource
> ----------------------------------------
>
>                 Key: XLIFF-63
>                 URL: https://issues.oasis-open.org/browse/XLIFF-63
>             Project: OASIS XML Localisation Interchange File Format (XLIFF) TC
>          Issue Type: Improvement
>          Components: other
>    Affects Versions: 2.1_csprd04
>         Environment: http://markmail.org/thread/ehdiafgiyhjdjcgh
>            Reporter: Yves Savourel
>            Assignee: Tom Comerford
>            Priority: Minor
>              Labels: CFD, editorial
>             Fix For: 2.1_cs01
>
>
> In "Example 26. Extraction of External Resource at inline levels", the
> extraction example shows only the <res:resourceData> part of
> the extraction, not how the <img> is encoded in the extracted XLIFF segment.
> It would be better if that example was completed, because the examples in the
> Resource Data section are not clear either on how
> inline objects are represented.



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