OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

xliff-inline message

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


Subject: Sample for metadata inline representation


Here is a second possibility for representing metadata.

This time the idea is to use a generic markup like this one described previously only for the custom metadata, while any information known in the XLIFF specification would be using a dedicated element.

Why this? Because this would allow tools to support different "modules" of metadata. For example a tool A could then support only the do-not-translate metadata, but nothing else.

Another advantage would be that since some metadata would have dedicated elements, those could have dedicated attributes, and we could have new inline extra information without having to rely on pointing to another element.

- the custom metadata would be represented the same way as in http://lists.oasis-open.org/archives/xliff-inline/201108/msg00028.html: A <mrk> element with a mandatory 'type' attribute, and optional 'idRef' attribute and possibly an optional 'id' attribute. There would be no provided values for 'type' as each one would be using the namespace-prefixed model already described.

- the do-not-translate information would be represented by two elements: <notrans> and <trans>.

- the terms would be represented by a <term> element. It would have an optional 'idRef' attribute to point to extra information.

- the comments would be represented by a <note> element. It would have either a 'idRef' attribute pointing to the data, or a 'text' attribute holding the comment. And an optional 'origin' attribute.


So this would give us something like this:

<unit id='1'>
 <segment>

  <source>It would certainly be quite a <notrans>faux pas</notrans> to start a dissertation on the origin of <term idRef='t1'>modern novel</term> without mentioning <note text='Comments about the two cited stories.' origin='author'>the <mrk type='xyz:book-title' idRef='cust1'>Epic of <mrk type='abc:proper-noun'>Gilgamesh</mrk></mrk>. </note></source>

  <target>Ce serait certainement un <notrans>faux pas</notrans> grave de commencer une thèse sur <note idRef='c2'>l'origine du <term idRef='t1'>roman moderne</term></note>, sans mentionner <note text='Comments about the two cited stories.' origin='author'>l'<mrk type='xyz:book-title' idRef='cust1'>Épopée de <mrk type='abc:proper-noun'>Gilgamesh</mrk></mrk>. </note></target>

</segment>
 <segment>

  <source><note text='Comments about the two cited stories.' origin='author'>There is also the <mrk type='xyz:book-title' idRef='cust2'>Story of <mrk type='abc:proper-noun'>Sinuhe</mrk></mrk>.</note></source>

  <target><note text='Comments about the two cited stories.' origin='author'>Il y a aussi l'<mrk type='xyz:book-title' idRef='cust2'>Histoire de <mrk type='abc:proper-noun'>Sinouhé</mrk></mrk>.</note></target>

 </segment>

 <termDefs>
  <termDef id='t1'>Info about the term 'modern novel'</termDef>
 </termDefs>

 <comments>
  <comment id='c2' origin='translator'>Translator's comments.</comment>
 </comments>

 <xyz:annotation id='cust1' type='book-title'>Some info about the Epic of Gilgamesh</xyz:annotation>
 <xyz:annotation id='cust2' type='book-title'>Some info about the Story of Sinuhe</xyz:annotation>

</unit>


Cheers,
-ys



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