OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

xliff-comment message

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

Subject: RE: [xliff-comment] XLIFF 1.2 Errata: datatype

Hi Asgeir,

You've been a steady and reliable resource for the XLIFF Technical
Committee to draw upon for quite a while, and we are grateful for any
input you have.  I hope nobody has given you reason to think otherwise.

Our strategy for responding to your very useful comments is to give the
TC members a bit of time to consider the issue, discuss it on the
xliff-tc list if necessary, determine the urgency of your comment (to
what degree does it cause a substantive change), and then to make a
decision about what action to take.

As you know, some of the issues you've raised have been so important
that we've halted the process, and reverted back to Committee Draft.
And some of the issues we've deemed small enough that they can be put on
the 2.0 list, but not cause us to restart.

As for the comment you made earlier today, and this comment, we are in
the process of determining what action to take.  Pending the discussion
on the xliff-tc list, we will consider your comments and get back to you
with a response on this list (xliff-comment).

So even though, as you yourself have characterized these as "primarily
small issues that needs to be addressed in the move to 2.0," they are
none-the-less very valuable, and appreciated by the TC.

Again, thank you Asgeir for your continued help at making our standard
better.  As you say, "no standard is perfect," but your comments help us
to improve ours.



-----Original Message-----
From: Asgeir Frimannsson [mailto:asgeirf@gmail.com] 
Sent: Tuesday, October 30, 2007 4:22 PM
To: xliff-comment@lists.oasis-open.org
Subject: [xliff-comment] XLIFF 1.2 Errata: datatype

Hi all,

First of all, as discussed on the xliff-tc list, I'm not trying to
delay or restart the process of getting XLIFF 1.2 accepted as an oasis
standard. However, no standard is perfect, and it's important to
document any errors or glitches. So yes, these are primarily small
issues that needs to be addressed in the move to 2.0, but should
perhaps be included in a later errata document or implementation

Now to the issue:

In the specification, the 'datatype' attribute is specified with a
default value of 'Empty string'. This should be 'undefined'.

Consequences: The 'empty string' default value will cause XSD
validation to fail.


Asgeir Frimannsson
PhD Candidate
School of Software Engineering and Data Communications
Queensland University of Technology
126 Margaret Street, Level 3
Brisbane QLD 4001, Australia

Phone: (+61) 7 3138 9332 Mob: (+61) 405 412 696
Email: asgeirf@gmail.com

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

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