[XLIFF-18] Broken Language Information solution - OASIS Technical Committees Issue Tracker

XML

Word

Printable

Details

Type: Sub-task
Status: Closed
Priority: Major
Resolution: Fixed
Affects Version/s: 2.1_csprd01
Fix Version/s: 2.1_csprd02
Component/s: ITS Module, validation artifacts
Labels:
- ready-for-vote
Environment:

as resultt of applying the parent resolution

Proposal:

Hide

Reintroduce urn:oasis:names:tc:xliff:itsm:2.1 to handle this single issue

We need to discuss if the single fragid prefix can be associated with two different namespaces at the same time or if it's irrelevant. The namespace prefix of course has to be different and we should stick to itsm:

Show
Reintroduce urn:oasis:names:tc:xliff:itsm:2.1 to handle this single issue We need to discuss if the single fragid prefix can be associated with two different namespaces at the same time or if it's irrelevant. The namespace prefix of course has to be different and we should stick to itsm:
Resolution:

Hide

I will call for disent on the proposed solution in the meeting of 7th Feb 2017

Show
I will call for disent on the proposed solution in the meeting of 7th Feb 2017

Description

The W3C namespace doesn't have an attribute for Langauge Information becuase it reuses the xml:lang.
However, xml namesepace is prohibited in XLIFF inline.
Therefore the current solution breaks when falling back on the W3C module.

Attachments

Activity

People

Assignee:

Soroush Saadatfar [X] (Inactive)

Reporter:

David Filip [X] (Inactive)

Watchers:

1 Start watching this issue

Dates

Due:

06/Feb/17

Created:

02/Feb/17 4:36 PM

Updated:

02/Mar/17 4:19 PM

Resolved:

07/Feb/17 4:14 PM