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


Help: OASIS Mailing Lists Help | MarkMail Help

xliff message

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

Subject: RE: [xliff-comment] Section 2.5.4 Validating Documents with Extensions - needs revision

Hi Bryan: 

If it's not complicated then I think it's worth waiting an extra few hours.
If you can send it out by your end of day today I will roll it into a spec
package tomorrow morning and put together a ballot for it immediately.

Thanks for your work on this.


-----Original Message-----
From: bryan.s.schnabel@exgate.tek.com
Sent: 24 October 2006 17:58
To: tony.jewtushenko@productinnovator.com; ddomeny@ektron.com;
asgeirf@gmail.com; xliff-comment@lists.oasis-open.org
Subject: RE: [xliff-comment] Section 2.5.4 Validating Documents with
Extensions - needs revision

Hi Tony,

> Bryan: would it be difficult or too time 
> consuming to make the change as
> Doug describes?

This would not be too difficult.  But given the fact that I'm on West
Coast US time, and that I will need to work it into my schedule today, I
cannot promise that I would get it done in time for you to roll it into
a 1.2 spec package, and send it out in time for most of our TC to review
it today (i.e., most of our group would *hopefully* be relaxing at home
by the time it gets to be afternoon here in Oregon).

I will work on this today and get it to you as soon as I can.  If you'd
rather not wait, and feel you should send out the final revision without
my sample schema, that's completely understandable, and supported by me.



-----Original Message-----
From: Tony Jewtushenko [mailto:tony.jewtushenko@productinnovator.com] 
Sent: Tuesday, October 24, 2006 6:21 AM
To: 'Doug Domeny'; 'Asgeir Frimannsson';
xliff-comment@lists.oasis-open.org; Schnabel, Bryan S
Subject: RE: [xliff-comment] Section 2.5.4 Validating Documents with
Extensions - needs revision

Doug and all:
At the risk of further delay in the spec, I would prefer using lax for
strict schema in order to validate the non-XLIFF content structure
than to validate it is well formed.  But it is not a deal breaker for me
I would vote to approve the spec & xsd as is (with a couple of small
revisions that I've already made and am ready to send out).

Bryan: would it be difficult or too time consuming to make the change as
Doug describes?  If yes, I'll send out the final revision later today
set up a ballot.  If you provide me with the revisions I can roll them
the 1.2 spec package and send it out for review & balloting immediately.


-----Original Message-----
From: Doug Domeny [mailto:ddomeny@ektron.com] 
Sent: 24 October 2006 13:45
To: 'Asgeir Frimannsson'; 'Tony Jewtushenko';
xliff-comment@lists.oasis-open.org; bryan.s.schnabel@exgate.tek.com
Subject: RE: [xliff-comment] Section 2.5.4 Validating Documents with
Extensions - needs revision


I'm fine with changing the 'strict' schema to use "lax" instead of
but then we should probably provide the schema for the tek namespace in

Bryan, is there a schema or could you create one for the tek namespace
in the example?

I'm also fine with leaving both using "skip".

Doug Domeny
Software Analyst
Ektron, Inc.
+1 603 594-0249 x212
-----Original Message-----
From: Asgeir Frimannsson [mailto:asgeirf@gmail.com] 
Sent: Tuesday, October 24, 2006 1:15 AM
To: Tony Jewtushenko; Doug Domeny; xliff-comment@lists.oasis-open.org
Subject: [xliff-comment] Section 2.5.4 Validating Documents with
- needs revision

Tony, Doug, all,

Referring to spec revision 20061023

"The only change made to the spec was to add a note indicating that
external schema's would not be validated by the Transitional XSD."

Both the transitional AND strict schemas were changed to use
processContents='skip'. I just noticed that this unfortunately also
invalidates section 2.5.4. (Validating Documents with Extensions) of
the specification:

"In order to validate an XLIFF document that contains non-XLIFF parts,
you can use the schema validation mechanism: In addition to the
namespace declarations, add the schemaLocation attribute of the XML
Schema-instance namespace to define what schemas to use to validate
the document (XLIFF and the non-XLIFF namespaces)."

Also note the reference to section 2.5.4 from section 3.1. (XML

If the spec is being updated again as a result of this, also notice
the small insignificant layout-mistake in section 3.1:
 "The same example as above would then look like this:<?xml
version="1.0"?>"  - the xml declaration should be part of the
following example, and not this paragraph.


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: a.frimannsson@qut.edu.au

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]