Uploaded image for project: 'OASIS XML Localisation Interchange File Format (XLIFF) TC'
  1. OASIS XML Localisation Interchange File Format (XLIFF) TC
  2. XLIFF-11

Enforce <target> existence based on segment state

          Details

          • Proposal:
            Hide

            Discuss by 29th Nov if this can be added as PR or as a Warning/Note
            Consider Advanced Validation impact.

            Show
            Discuss by 29th Nov if this can be added as PR or as a Warning/Note Consider Advanced Validation impact.
          • Resolution:
            Hide

            Consensus 17th January 2017:
            Implement state dependency in core sch
            Describe the behavior in advanced validation prose [dF]
            Look into specifics of <target> elements that are children of <ignorable> rather than <segment>
            Target will not be enforced in case of <ignorable> parents which even don't have state

            Show
            Consensus 17th January 2017: Implement state dependency in core sch Describe the behavior in advanced validation prose [dF] Look into specifics of <target> elements that are children of <ignorable> rather than <segment> Target will not be enforced in case of <ignorable> parents which even don't have state

            Description

            FROM:
            Ján Husarčík <jan.husarcik@gmail.com>

            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

              Attachments

                Activity

                  People

                  • Assignee:
                    soroush.saadatfar Soroush Saadatfar [X] (Inactive)
                    Reporter:
                    DavidFilip David Filip
                  • Watchers:
                    2 Start watching this issue

                    Dates

                    • Due:
                      Created:
                      Updated:
                      Resolved: