RE: [xliff-comment] Resolution for the public review comments on "Processing Requirements for XML PIs"

["Schnabel, Bryan S" <bryan.s.schnabel@tektronix.com>]

Yves,

As I said below, I agree with your technical comments. But one aspect I will need to bring up at the meeting today:

> There is no provision that address the 3 comments of the ballot
> that indicates PIs should not be allowed inside source and target
> content. Note that 2.0 does not allow extensions there currently.

At this moment if I were to add text that PIs should not be allowed inside source and target the only justification I could point to would be three comments on a ballot. This does not amount (yet) to TC consensus. One might argue that PIs are used for purposes other than extensions.

Nonetheless, personally I am in agreement with you, and my perception is that the TC would also agree (to add the " should not be allowed inside source and target " restriction).

So I will try today to formalize TC consensus in a roll call vote today.

Thanks,

Bryan

-----Original Message-----
From: Schnabel, Bryan S 
Sent: Tuesday, July 16, 2013 6:45 AM
To: 'Yves Savourel'; xliff-comment@lists.oasis-open.org
Cc: joerg@bioloom.de
Subject: RE: [xliff-comment] Resolution for the public review comments on "Processing Requirements for XML PIs"

Thanks Yves. You're right. PIs were also commented on by you and the resolution is meant to cover your comment as well. As a matter of convention we've tended to resolve internal TC comments in TC meetings, and reply to external commenters on the comment list.

I don't think David has recompiled and published new outputs yet. We can confirm in an hour at the meeting.

Thanks also for your technical comments. They make sense to me. I'll revise the section.

Thanks,

Bryan

-----Original Message-----
From: Yves Savourel [mailto:yves@opentag.com]
Sent: Monday, July 15, 2013 9:54 PM
To: Schnabel, Bryan S; xliff-comment@lists.oasis-open.org
Cc: joerg@bioloom.de
Subject: RE: [xliff-comment] Resolution for the public review comments on "Processing Requirements for XML PIs"

Hi Bryan,

> Regarding your public review comment, csprd01 15 Processing 
> Requirements for XML PIs, I implemented the result prescribed by the 
> TC ballot ...
> And noted that XML Processing Requirements within a segment could 
> cause ambiguity upon re-segmentation and may be removed on output.

Thanks for working on that item.

While comment 15 is from Jörg, comment 13 is from me and is also related to processing instructions. 

== a) First, a short note: could you point me to the latest copy of the HTML or PDF version of the editor's draft?
I do see your changes (rev 269 and 268) about PIs in the log:
https://tools.oasis-open.org/version-control/browse/wsvn/xliff/trunk/xliff-20/?op=log&rev=0&sc=0&isdir=1 but none of the HTML or PDF files in SVN seem to have those changes. The file xliff-core.pdf listed as Editor's draft in the wiki
(https://wiki.oasis-open.org/xliff/) seems to be still at revision 267 for now.

== b) As far as the resolution. From the log diffs (so I can't be sure I'm not missing something) I have two comments:

- In the new section there is a note that says: "Note: Using Processing Instructions as a means to implement a feature already specified in XLIFF core or modules is prohibited. Doing so constitutes noncompliance." While the wording is clear, it may help to have the text with a MUST or MUST NOT and be listed in the PRs items for that section, so it becomes part of the conformance clauses. Basically the same as the PR in the section about extension.
 
- There is no provision that address the 3 comments of the ballot that indicates PIs should not be allowed inside source and target content. Note that 2.0 does not allow extensions there currently.

- I believe you meant "XML Processing Instructions" not "XML Processing Requirements" in the text "XML Processing Requirements within a segment could cause ambiguity upon re-segmentation and <glossterm>may</glossterm> be removed on output." 


Cheers,
-yves




--
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/