Next in thread →
Next in month →
RE: [xliff] More XSD & Spec revisions
Title: Message Doug and Tony, I checked the XSDs and found them to be perfectly valid. The extension point for attributes for <tool is working fine. I guess the rest of the changes all pertained to the spec. I also checked the sample files where Tony added the example of the <mrk for protected content (see trans-unit id="_1_ski_2203"). Tony's updates were perfectly valid. But I noticed in the "Sample_AlmostEverything_1.2_strict.xlf" file a stray "f" was typed just below the comment that followed the <count-group name="_ski_43782">. It looked like it might have been a "brush-the-finger-over-the-keyboard-but-not-notice-it" mistake. The effect was that the <group element, with the "f" suddenly had PCDATA (which made it invalid). I fixed that, and also removed the "tool" attributes from the <phase elements. I attached the fixed file. If we use the attached sample file now, I think everything should be valid. Thanks, Bryan -----Original Message----- From: Doug Domeny [mailto:] Sent: Friday, May 12, 2006 11:51 AM To: 'Tony Jewtushenko'; Schnabel, Bryan S Cc: Subject: RE: [xliff] More XSD & Spec revisions Bryan, The schemas are attached. Thanks for reviewing them. It’s always good to have another pair of eyes (and XML processors) check things out. The <tool> element now has an extension point for attributes. Regards, Doug Domeny Software Analyst Ektron, Inc. +1 603 594-0249 x212 http://www.ektron.com From: Tony Jewtushenko [mailto:] Sent: Friday, May 12, 2006 2:31 PM To: Cc: ; Subject: RE: [xliff] More XSD & Spec revisions Bryan: Thanks for volunteering. I agree it's a good idea to QA the schema and samples. Please get the results with any revisions back to me by close of business Monday so I can get the ballot marerials together in time for the ballot on Tuesday. Regards, Tony -----Original Message----- From: [mailto:] Sent: 12 May 2006 13:18 To: ; Cc: Subject: RE: [xliff] More XSD & Spec revisions Hi Tony, In preparation for Monday's deadline for final revisions, and Tuesday's ballot, I'll be happy to run XML diagnostics on the revised XSDs and XLIFF sample files. I know that Doug will do excellent work, but it would probably be a good to have a second person do a final QA to ensure XML validity. If for no other reason, it will put a little mileage on the schema and samples before the ballot goes out. Doug, if you want to take me up on my offer, I'll be available to run tests today and Monday. (this will be a good time for me to fix the strict sample "almost everything," where you pointed out that the tool attribute in the phase element is deprecated.) Thanks, Bryan -----Original Message----- From: Tony Jewtushenko [mailto:] Sent: Friday, May 12, 2006 9:35 AM To: Schnabel, Bryan S; Cc: ; Subject: [xliff] More XSD & Spec revisions Asgeir has idendtified a number of other minor problems with the spec & XSD. I've noted the revisions required below, but if anyone has any further input please provide it as soon as possible. I suggest that Doug go ahead and make the necessary changes to the XSD and I'll send a revised spec later today. We'll need final revisions done by Monday. Again thanks for Asgeir for his careful review and identification of the spec and XSD. Hopefully this represents the last of the spec issues. Regards, Tony -----Original Message----- From: Asgeir Frimannsson [mailto:] Sent: 12 May 2006 01:31 To: Tony Jewtushenko Subject: More XLIFF spec corrections Hi Tony, Some further minor corrections to the XLIFF spec: 2.5.1. Adding Elements: <xliff> and <seg-source> are listed as extension points - they are not in the schema (the listed <xliff> element above also has an incorrect html anchor link) TONY> this needs to be corrected in the spec. I'm sure we added an extension point at xliff and I'm somewhat certain seg-source should also have one. 2.5.2. Adding Attributes: <xliff> and <seg-source> support non-xliff attributes in the schema, but are not listed here. (This probably relates to the issue above - a mixup when updating the spec?) In addition, <tool> is currently listed, but does not support non-xliff attributes in the schema. TONY>I'll revise the spec but tool needs to be updated in the schema. 2.5.3. Adding Attribute Values Again, alttranstype and reformat supports user defined values ('x-') in the schema, but are not listed here. TONY>I'll revise the spec Element detail for <target>: Missing description of equiv-trans and equiv-trans is not listed in optional attributes TONY>I'll revise the spec Element detail for <group>: Missing description of merged-trans and merged-trans is not listed in optional attributes TONY>I'll revise the spec Element detail for <alt-trans> No anchor on <seg-source> element in description TONY>I'll revise the spec cheers, asgeir Sample_AlmostEverything_1.2_strict.xlf
Next in thread →
Next in month →