Subject: Re: [xliff-comment] RE: csprd02 comment #113
The extraction tool SHOULD store each sub-flow in its own
The extraction tool MAY order the
<unit> elements of the sub-flows and the
<unit> element of their parent in any order it sees fit. User agents coming later in the process MUST keep the
<unit>elements in their initial order.
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 constraintsBest regardsdFOn Mon, Dec 2, 2013 at 3:54 AM, Schnabel, Bryan S <email@example.com> wrote:
Not a deal breaker, but yes, I think an explicit statement would be appropriate.
> Do you think that we should explicitly say
> that subflows are not allowed across file elements?
From: Dr. David Filip [David.Filip@ul.ie]
Sent: Friday, November 29, 2013 8:54 AM
To: Schnabel, Bryan S; firstname.lastname@example.org; email@example.com
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?
Dr. David Filip
LRC | CNGL | LT-Web | CSIS
University of Limerick, Ireland
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
List help: firstname.lastname@example.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
Join OASIS: http://www.oasis-open.org/join/