xliff-comment

Hi Bryan, all

I response to Bryan's comments I have edited the Inline Section on subflows
as follows:


[New text]
Constraints

- An inline code containing or delimiting one or more sub-flows must
have an attribute subFlows that holds a list of the identifiers of the
<unit> elements where the sub-flows are stored.
- Sub-Flows must be in the same <file> element as the <unit> element
from which they are referenced.

Processing Requirements

- Extractors should store each sub-flow in its own <unit> element.
- Extractors may order the <unit> elements of the sub-flows and the
<unit> element, from where the subflows are referenced, as they see fit.
- Other Writers must preserve the order of <unit> elements as initially
set by the Extractor.


[Old text]

*Processing Requirements*

-

The extraction tool SHOULD store each sub-flow in its own
<unit><file:///D:/!profile/Dropbox/XLIFF/!SPEC/trunk/xliff-20/xliff-core.html#unit>
element.
-

An inline code containing or delimiting one or more sub-flows MUST have
an attribute
subFlows<file:///D:/!profile/Dropbox/XLIFF/!SPEC/trunk/xliff-20/xliff-core.html#subflows>
that
holds a list of the identifiers of the
<unit><file:///D:/!profile/Dropbox/XLIFF/!SPEC/trunk/xliff-20/xliff-core.html#unit>
elements
where the sub-flows are stored.
-

The extraction tool MAY order the
<unit><file:///D:/!profile/Dropbox/XLIFF/!SPEC/trunk/xliff-20/xliff-core.html#unit>
elements
of the sub-flows and the
<unit><file:///D:/!profile/Dropbox/XLIFF/!SPEC/trunk/xliff-20/xliff-core.html#unit>
element
of their parent in any order it sees fit. User agents coming later in the
process MUST keep the
<unit><file:///D:/!profile/Dropbox/XLIFF/!SPEC/trunk/xliff-20/xliff-core.html#unit>elements
in their initial order.


Please note that this is not yet printed.
Please let me know if the edits are OK with you.

Rgds
dF


Dr. David Filip
=======================
LRC | CNGL | LT-Web | CSIS
University of Limerick, Ireland
telephone: +353-6120-2781
*cellphone: +353-86-0222-158*
facsimile: +353-6120-2734
http://www.cngl.ie/profile/?i=452
mailto: david.filip@ul.ie


On Mon, Dec 2, 2013 at 10:04 AM, Dr. David Filip <David.Filip@ul.ie> wrote:

> Thanks, Bryan, I will add a Constraint to subflows stating that subflows
> MUST not span file elements, than the subflow ids will be automatically
> unique by the current set of uniqueness constraints
> Best regards
> dF
>
> Dr. David Filip
> =======================
> LRC | CNGL | LT-Web | CSIS
> University of Limerick, Ireland
> telephone: +353-6120-2781
> *cellphone: +353-86-0222-158 <%2B353-86-0222-158>*
> facsimile: +353-6120-2734
> http://www.cngl.ie/profile/?i=452
> mailto: david.filip@ul.ie
>
>
> On Mon, Dec 2, 2013 at 3:54 AM, Schnabel, Bryan S <
> bryan.s.schnabel@tektronix.com> wrote:
>
>> Hi David,
>>
>> > Do you think that we should explicitly say
>> > that subflows are not allowed across file elements?
>>
>> Not a deal breaker, but yes, I think an explicit statement would be
>> appropriate.
>> ________________________________
>> From: Dr. David Filip [David.Filip@ul.ie]
>> Sent: Friday, November 29, 2013 8:54 AM
>> To: Schnabel, Bryan S; xliff@lists.oasis-open.org;
>> xliff-comment@lists.oasis-open.org
>> Subject: csprd02 comment #113
>>
>> Bryan, I own this comment/issue.
>> In my opinion this issue is addressed by requiring units to be unique
>> within a file.
>> Do you think that we should explicitly say that subflows are not allowed
>> across file elements?
>> Thanks
>> dF
>>
>> Dr. David Filip
>> =======================
>> LRC | CNGL | LT-Web | CSIS
>> University of Limerick, Ireland
>> telephone: +353-6120-2781
>> cellphone: +353-86-0222-158
>> facsimile: +353-6120-2734
>> http://www.cngl.ie/profile/?i=452
>> mailto: david.filip@ul.ie<mailto:david.filip@ul.ie>
>>
>>
>> --
>> This publicly archived list offers a means to provide input to the
>> OASIS XML Localisation Interchange File Format (XLIFF) TC.
>>
>> In order to verify user consent to the Feedback License terms and
>> to minimize spam in the list archive, subscription is required
>> before posting.
>>
>> Subscribe: xliff-comment-subscribe@lists.oasis-open.org
>> Unsubscribe: xliff-comment-unsubscribe@lists.oasis-open.org
>> List help: xliff-comment-help@lists.oasis-open.org
>> List archive: http://lists.oasis-open.org/archives/xliff-comment/
>> Feedback License: http://www.oasis-open.org/who/ipr/feedback_license.pdf
>> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
>> Committee:
>> http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=xliff
>> Join OASIS: http://www.oasis-open.org/join/
>>
>>
>