[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 Doug, I'll take a look at the examples and create a schema that we can use. I think the example is a few years old. We may, or may not want to edit the prefix and local part of the namespace in our example. I'll dig into this. Thanks, Bryan -----Original Message----- From: Doug Domeny [mailto:ddomeny@ektron.com] Sent: Tuesday, October 24, 2006 5:45 AM To: 'Asgeir Frimannsson'; 'Tony Jewtushenko'; xliff-comment@lists.oasis-open.org; Schnabel, Bryan S Subject: RE: [xliff-comment] Section 2.5.4 Validating Documents with Extensions - needs revision Tony, I'm fine with changing the 'strict' schema to use "lax" instead of "skip", but then we should probably provide the schema for the tek namespace in the example. Bryan, is there a schema or could you create one for the tek namespace used in the example? I'm also fine with leaving both using "skip". Regards, Doug Domeny Software Analyst Ektron, Inc. +1 603 594-0249 x212 http://www.ektron.com -----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 Extensions - needs revision Tony, Doug, all, Referring to spec revision 20061023 (http://www.oasis-open.org/archives/xliff/200610/msg00022.html): "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 Declaration). 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. cheers, asgeir -- 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 Committee: http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=xliff
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]