Re: [xliff-comment] XLIFF 2.1 csprd01: Enforcing <target> existence based on segment state

[David Filip <david.filip@adaptcentre.ie>]

Jano, thanks for reporting this

I have created the issue

https://issues.oasis-open.org/browse/XLIFF-11

Please follow the disposition of your comment on the above URL, we will strive to resolve and apply this comment resolution by early December 2016.

Could you please specify in reply to this on which validation platform(s) the example file validated?

Please follow up in this thread in case you don't agree with the disposition or if you wish to otherwise comment on the disposition

Cheers and thanks

dF

Cheers and thanks

dF

Dr. David Filip

===========

OASIS XLIFF OMOS TC Chair

OASIS XLIFF TC Secretary, Editor, Liaison Officer

Spokes Research Fellow

ADAPT Centre

KDEG, Trinity College Dublin

Mobile: +420-777-218-122

On Wed, Nov 16, 2016 at 10:01 AM, Ján Husarčík <jan.husarcik@gmail.com> wrote:

Hello,

file

<?xml version="1.0" encoding="utf-8"?>
<xliff xmlns:mda="urn:oasis:names:tc:xliff:metadata:2.0"
    xmlns="urn:oasis:names:tc:xliff:document:2.0" srcLang="en-US" trgLang="fr-FR" version="2.0">
    <file id="1">
        <group id="content">
            <unit id="1">
                <segment state="final">
                    <source>1</source>
                </segment>
            </unit>
        </group>
    </file>
</xliff>

is reported as valid with state="final", while the <target> is not present.

Could you please consider enforcing existence of <target> (even if it's empty) for segment states different from default?

If you decide to do so, could you please update processing requirements in http://docs.oasis-open.org/xliff/xliff-core/v2.1/csprd01/xliff-core-v2.1-csprd01.html#contentmodification accordingly, and reference them (at least) in http://docs.oasis-open.org/xliff/xliff-core/v2.1/csprd01/xliff-core-v2.1-csprd01.html#state and http://docs.oasis-open.org/xliff/xliff-core/v2.1/csprd01/xliff-core-v2.1-csprd01.html#target

Thanks,
Jan