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] Re csprd01 comment 028 - Action To Be Taken.

Hi Ryan,


Just a few notes:


-   I believe it would be ref=”s1” instead of ref=”#s1” as the value of ref would presumably not be a URI but a reference to an ID.

-   appliesTo=”source | target” is not valid per the current definition. I’m not sure we want to get into having lists of elements. If there is no appliesTo and the reference points to a <segment> then it can be said to apply to both source and target.




From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf Of Ryan King
Sent: Thursday, June 27, 2013 10:08 PM
To: xliff@lists.oasis-open.org
Subject: [xliff] Re csprd01 comment 028 - Action To Be Taken.


Hi David, Fredrik, All,


In keeping with other emails today on the subject of re-segmentation and tree structure, I would like to put forth a solution for csprod01 comment 02, relating to the improvement of data referencing in modules, and propose using appliesTo and ref attributes to do this. This should hopefully help solve the issue of removing modules and potentially <notes> out of <segment>.



  <segment id=”s1”>…</segment>

<ignorable id=”i1”>…</ignorable>

  <segment id=”s2”>…</segment>



  <note id=”n1” appliesTo=”source | target” ref=”#s1”>…</note>

  <note id=”n2” appliesTo=”source | target” ref=”#s2”>…</note>



  <match ref=”#s1”>…</match>

  <match ref=”#s2”>…</match>



  <glossentry ref=”#s1”>…</glossentry>

  <glossentry ref=”#s2”>…</glossentry>



  <metagroup appliesTo=”source | target” ref=”#s1”>…</metagroup>

  <metagroup appliesTo=”source | target” ref=”#s2”>…</metagroup>

  <metagroup appliesTo=”ignorable” ref=”#i1”>…</metagroup>


<!-- changeTrack already defines referencing using this method, we would just rename nid to ref -->


  <revisions appliesTo=”source | target” ref=#s1></revisions>

  <revisions appliesTo=”source | target” ref=#s2></revisions>

  <revisions appliesTo=”note” ref=#n1></revisions>

  <revisions appliesTo=”note” ref=#n2></revisions>



  <rule ref=”#s1”>…</rules>

  <rule ref=”#s1”>…</rules>



Alternatively, <mrk> could be used to annotate a substring to refer to <notes> and <glossentry>:



  <segment id=”s1”>

    <source><mrk id=”m1” type=”comment” ref=#n1”>Hello</mrk> World</source>


  <segment id=”s2”>

    <source>Good-bye <mrk id=”m1” type=”term” ref=”#g1”>World</mrk></source>




  <note id="n1">A greeting</note>



  <glossentry id=”g1”>…</glossentry>






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