[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xliff] RE: [xliff-comment] Public Comment
Thanks again for the report Jonah, But, shouldn't this be: <xsd:element name="source" type="xlf:ElemType_source"/> <xsd:element name="target" type="xlf:ElemType_target" minOccurs="0"/> <xsd:choice minOccurs="0" maxOccurs="unbounded"> <xsd:element name="context-group" type="xlf:ElemType_context-group"/> <xsd:element name="count-group" type="xlf:ElemType_count-group"/> <xsd:element name="prop-group" type="xlf:ElemType_prop-group"/> <xsd:element name="note" type="xlf:ElemType_note"/> <xsd:element name="alt-trans" type="xlf:ElemType_alt-trans"/> </xsd:choice> <xsd:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> Leaving <xsd:any namespace="##other"> outside of the <choice> to follow the spec listing it as the last optional item. -yves ________________________________ From: Jonah Petri [mailto:jpetri@apple.com] Sent: Wednesday, May 19, 2004 12:49 PM To: Yves Savourel Cc: bryan.s.schnabel@exgate.tek.com; xliff@lists.oasis-open.org Subject: Re: [xliff] RE: [xliff-comment] Public Comment Thanks for posting the new schema. I found another problem. Your specification for <trans-unit> says: Contents: One <source> element, followed by Zero or one <target> element, followed by Zero, one or more <context-group>, <count-group>, <prop-group>, <note>, <alt-trans> elements, ***in any order***, followed by Zero, one or more non-XLIFF elements. Your schema doesn't allow for arbitrary ordering of the context-group, count-group, prop-group, note, and alt-trans elements. In the XSD: <xsd:complexType name="ElemType_trans-unit"> <xsd:sequence> <xsd:element name="source" type="xlf:ElemType_source"/> <xsd:element name="target" type="xlf:ElemType_target" minOccurs="0"/> <xsd:element name="context-group" type="xlf:ElemType_context-group" minOccurs="0" maxOccurs="unbounded"/> <xsd:element name="count-group" type="xlf:ElemType_count-group" minOccurs="0" maxOccurs="unbounded"/> <xsd:element name="prop-group" type="xlf:ElemType_prop-group" minOccurs="0" maxOccurs="unbounded"/> <xsd:element name="note" type="xlf:ElemType_note" minOccurs="0" maxOccurs="unbounded"/> <xsd:element name="alt-trans" type="xlf:ElemType_alt-trans" minOccurs="0" maxOccurs="unbounded"/> <xsd:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xsd:sequence> Change to: <xsd:complexType name="ElemType_trans-unit"> <xsd:sequence> <xsd:element name="source" type="xlf:ElemType_source"/> <xsd:element name="target" type="xlf:ElemType_target" minOccurs="0"> <xsd:choice minOccurs="0" maxOccurs="unbounded"> <xsd:element name="context-group" type="xlf:ElemType_context-group" /> <xsd:element name="count-group" type="xlf:ElemType_count-group" /> <xsd:element name="prop-group" type="xlf:ElemType_prop-group" /> <xsd:element name="note" type="xlf:ElemType_note" /> <xsd:element name="alt-trans" type="xlf:ElemType_alt-trans" /> <xsd:any namespace="##other" processContents="lax"/> </xsd:choice> </xsd:sequence> -Jonah On May 19, 2004, at 9:35 AM, Yves Savourel wrote: The fixed (and overdue) XSD addressing this issue should be posted sometime today. Thank again, -yves -----Original Message----- From: bryan.s.schnabel@exgate.tek.com [mailto:bryan.s.schnabel@exgate.tek.com] Sent: Wednesday, May 19, 2004 10:27 AM To: jpetri@apple.com Cc: xliff@lists.oasis-open.org Subject: [xliff] RE: [xliff-comment] Public Comment Yes, I agree with your solution. This is the solution we came to in March. http://lists.oasis-open.org/archives/xliff/200403/msg00010.html The second part is to remove the occurrence indicators of each child element. Thank you for your observation. Bryan Schnabel -----Original Message----- From: comment-form@oasis-open.org [mailto:comment-form@oasis-open.org] Sent: Wednesday, May 19, 2004 8:40 AM To: xliff-comment@lists.oasis-open.org Subject: [xliff-comment] Public Comment Comment from: jpetri@apple.com Your XMLSchema for XLIFF is badly broken. The 'ElemType_header' complex-type has an xsd:choice grouping in it, containing 'glossary', 'reference', 'count-group', 'prop-group', and 'tool' elements. A choice group allows exactly 1 of the contained elements to appear, but your standard clearly says that 0, 1 or more of these elements may appear. You need to add minOccurs="0" and maxOccurs="unbounded" as attributes to the xsd:choice for XLIFF documents to validate correctly. To unsubscribe from this list, send a post to xliff-comment-unsubscribe@lists.oasis-open.org, or visit http://www.oasis-open.org/mlmanage/. To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/xliff/members/leave_workgroup.p hp.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]