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] Element simpleNote

> a. Why can't we use existing standards such as W3C ITS in XLIFF?
> If I remember correctly, we have "Reuse" as one of our XLIFF 
> 2.0 Mantras.

If we go with ITS, for a "simple note" we can use the its:locNote attribute without anything else. It goes on the element you want to annotate. We could still control which elements allow it or not using the schema. If we were to match the current locations we would allow its:locNote on <segment>, <unit>, <source> and <target>.

Two possible drawbacks:

1) An attribute value cannot have a rich content (formatting, multi paragraphs, etc.) But maybe that is not an issue with a *simple* note.

2) Since all the <source> (or <target>) elements have no common parent (they have a common grand-parent), we would not be able to assign a note to all source or all target at once by specifying it in <unit>.

On ITS overall:

I would think twice before using any XPath-based options. The main issue with this is that it pretty much forces the use of a DOM-based parser for XLIFF, which could be a problem with large documents.


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