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: RE: [xliff] XLIFF and ITS mapping-ID value

Dear Felix, Yves,
Thanks for your help, your notes will be applied.


From: Felix Sasaki [felix@sasakiatcf.com]
Sent: 20 December 2015 20:41
To: Soroush.Saadatfar
Cc: xliff@lists.oasis-open.org
Subject: Re: [xliff] XLIFF and ITS mapping-ID value

HI Soroush and all,

Am 18.12.2015 um 18:14 schrieb Soroush.Saadatfar <Soroush.Saadatfar@ul.ie>:

The spec text for ID value data category of ITS is offered as follows:

"ID value

This data category provides a mechanism to build customized unique identifiers for different parts of the document. It is generally recommended to use native xml:id or id attributes for XML and HTML documents respectively.

As XLIFF 2.1 identifiers are not unique in the scope of the entire document, this data category should be avoided where possible and replaced by native XLIFF identifiers."

And I have a question with regards to the example. The current text in the wiki page mentions "exceptions for very specific context...", would you please provide a particular case? I don't think the current example on wiki is that.

There is no example because as the wiki says: „Note that the identifiers in XLIFF are not unique per document, so using the Id Value data category to specify IDs in an XLIFF document is largely useless“. So I would leave this as as, without an example about such contexts. 



From: xliff@lists.oasis-open.org [xliff@lists.oasis-open.org] on behalf of Yves Savourel [ysavourel@enlaso.com]
Sent: 19 December 2015 12:38
To: XLIFF Main List
Subject: RE: [xliff] XLIFF and ITS mapping- Elements within text

Hi Soroush,

More notes:

-- 1)

Several of the examples have "curly quotes" instead of normal ASCII double quotes to enclose attribute values.
A side effect of editing in an email probably, but they need to be correct in the spec.

-- 2)

<unit id="u1">
      <data id="d1">&lt;br/&gt;</data>
      <source>This sentence has a breakpoint<ph id="ph1" dataRef="d1"
              type="fmt" subType="xlf:lb"/>inside.

The example above has a dangling "-->" after </originalData>.

-- 3)

<unit id="u1">
      <data id="d1">&lt;u&gt;</data>
      <data id="d2">&lt;/u&gt;</data>
      <source>A paragraph where <sc id="sc1" dataRef="d1" type="fmt"
              subType="xlf:u"/>the formatted text takes more than one
      <source> The second sentence here.<ec dataRef="d2"

In the example above, the <ec/> element seems to be missing the attributes type="fmt" and subType="xlf:u".

Now, the Okapi validator gives an error on this, but I don't see in the spec any constraint that says type and subType must have the
same values in two corresponding <sc/> and <ec/>. That constraint exists only for canCopy, canDelete and canOverlap.

I don't see anywhere either that the processor should magically complement the undefined attributes in <ec/> by looking at the
corresponding <sc/>. At the same time, obviously, it would be illogical to have different values.

Are we missing yet another "implicit" constraint?


To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]