[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.
|
Due to discussions on segmentation and referencing in today’s TC Conference call, I retract this proposal. I will add 2.a to the Change Track proposal and replace
this one with a new proposal on referencing based on the <mrk> element. Ryan From: Ryan King
Sorry for the churn on this one. I remembered after hitting send that the appliesTo attribute on the change track module can refer to any valid XLIFF element, so updating 2.a, the proposal
is now: 1. Add a
ref attribute to the following:
2. Rename nid to ref for <ctr:changeTrack> a.
Add a processing requirement that when referring to an element with multiple child elements of the same type, containing an id, the ref attribute is required. 3. Add an appliesTo attribute to <mda:metagroup> with the possible values of source, target, or ignorable. From: Ryan King
One addition (2.a below) to the proposal on referencing between notes/modules and segments, due to comment 035 regarding the change track module: “[2] No processing restrictions are given
for the nid attribute. It is strange that for example appliesTo could specify "note", but nid could be absent. In this case, it would not be clear what note the revision refers to.” The new proposal: 1. Add a
ref attribute to the following:
2. Rename nid to ref for <ctr:changeTrack> a.
Add a processing requirement that when referring to a <unit> with multiple <segment> elements, or a <notes> with multiple <note> elements, the ref attribute is required. 3. Add an appliesTo attribute to <mda:metagroup> with the possible values of source, target, or ignorable. From:
xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org]
On Behalf Of Ryan King In short, then, I propose that we do the following to improve the referencing between notes/modules and segments, optimistically assuming that we remove notes/modules from <segment>
for re-segmentation purposes: Thanks for your consideration, Ryan From:
xliff@lists.oasis-open.org on behalf of Ryan King Thanks Yves. Your first comment makes sense. For your second comment, what I meant by appliesTo=”source | target” was appliesTo=”source” OR appliesTo=”target”.
My short-hand annotation was confusing, I see. I’ve pasted the proposal below with those two fixes. Hopefully, that makes better sense now. <unit> <segment id=”s1”>…</segment> <ignorable id=”i1”>…</ignorable> <segment id=”s2”>…</segment> </unit> <notes> <note id=”n1” appliesTo=”source” ref=”s1”>…</note> <note id=”n2” appliesTo=”target” ref=”s2”>…</note> </notes> <mtc:matches> <match ref=”s1”>…</match> <match ref=”s2”>…</match> </mtc:matches> <gls:glossary> <glossentry ref=”s1”>…</glossentry> <glossentry ref=”s2”>…</glossentry> </gls:glossary> <mda:metadata> <metagroup appliesTo=”source” ref=”s1”>…</metagroup> <metagroup appliesTo=”target” ref=”s2”>…</metagroup> <metagroup appliesTo=”ignorable” ref=”i1”>…</metagroup> </mda:metadata> <!-- changeTrack already defines referencing using this method, we would just rename nid to ref --> <ctr:changeTrack> <revisions appliesTo=”source” ref=”s1”></revisions> <revisions appliesTo=”target” ref=”s2”></revisions> <revisions appliesTo=”note” ref=”n1”></revisions> <revisions appliesTo=”note” ref=”n2”></revisions> </ctr:changeTrack> <val:validation> <rule ref=”s1”>…</rules> <rule ref=”s1”>…</rules> </val:validation> Alternatively, <mrk> could be used to annotate a substring to refer to <notes> and <glossentry>: <unit> <segment id=”s1”> <source><mrk id=”m1” type=”comment” ref=#n1”>Hello</mrk> World</source> </segment> <segment id=”s2”> <source>Good-bye <mrk id=”m1” type=”term” ref=”#g1”>World</mrk></source> </segment> </unit> <notes> <note id="n1">A greeting</note> </notes> <gls:glossary> <glossentry id=”g1”>…</glossentry> </gls:glossary> From:
xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org]
On Behalf Of Yves Savourel 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. -ys From:
xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org]
On Behalf Of Ryan King 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>. <unit> <segment id=”s1”>…</segment> <ignorable id=”i1”>…</ignorable> <segment id=”s2”>…</segment> </unit> <notes> <note id=”n1” appliesTo=”source | target” ref=”#s1”>…</note> <note id=”n2” appliesTo=”source | target” ref=”#s2”>…</note> </notes> <mtc:matches> <match ref=”#s1”>…</match> <match ref=”#s2”>…</match> </mtc:matches> <gls:glossary> <glossentry ref=”#s1”>…</glossentry> <glossentry ref=”#s2”>…</glossentry> </gls:glossary> <mda:metadata> <metagroup appliesTo=”source | target” ref=”#s1”>…</metagroup> <metagroup appliesTo=”source | target” ref=”#s2”>…</metagroup> <metagroup appliesTo=”ignorable” ref=”#i1”>…</metagroup> </mda:metadata> <!-- changeTrack already defines referencing using this method, we would just rename nid to ref --> <ctr:changeTrack> <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> </ctr:changeTrack> <val:validation> <rule ref=”#s1”>…</rules> <rule ref=”#s1”>…</rules> </val:validation> Alternatively, <mrk> could be used to annotate a substring to refer to <notes> and <glossentry>: <unit> <segment id=”s1”> <source><mrk id=”m1” type=”comment” ref=#n1”>Hello</mrk> World</source> </segment> <segment id=”s2”> <source>Good-bye <mrk id=”m1” type=”term” ref=”#g1”>World</mrk></source> </segment> </unit> <notes> <note id="n1">A greeting</note> </notes> <gls:glossary> <glossentry id=”g1”>…</glossentry> </gls:glossary> Thanks, Ryan |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]