[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [xliff] Element names
Here are the 12 places that need to be fixed in the spec, per Yves' comments. I assume these are all editorial so I've entered issue 149 and assigned it to DavidF. David, if you prefer, we can co-assign it to Joachim and me as owners of metadata and glossary (please just let us know)
----------------------------
(1) Please change the example in 4.7.3.1.2 Term Annotation from
<gls:glossentry id="g1" ref="#m1">
<gls:term>doppelgänger</gls:term>
<gls:definition source="dictionary.com">A ghostly double or counterpart of a living person.</gls:definition>
</gls:glossentry>
to
<gls:glossEntry id="g1" ref="#m1">
<gls:term>doppelgänger</gls:term>
<gls:definition source="dictionary.com">A ghostly double or counterpart of a living person.</gls:definition>
</gls:glossEntry>
(2) Please change the Contains section in 5.2.4.2 glossary from:
One or more <glossentry> elements.
to
One or more <glossEntry> elements.
(3) Please change the Identifier section in 5.2.5.1 id from:
Identifier - a character string used to identify a <glossentry> or <translation> element.
to
Identifier - a character string used to identify a <glossEntry> or <translation> element.
(4) Please change the Example in 5.2.6 Example from:
<gls:glossentry ref="#m1">
<gls:term source="publicTermbase">TAB key</gls:term>
<gls:translation id="1" source="myTermbase">Tabstopptaste</gls:translation>
<gls:translation ref="#m2" source="myTermbase">TAB-TASTE</gls:translation>
<gls:definition source="publicTermbase">A keyboard key that is traditionally used to insert tab characters into a document.</gls:definition>
</gls:glossentry>
to
<gls:glossEntry ref="#m1">
<gls:term source="publicTermbase">TAB key</gls:term>
<gls:translation id="1" source="myTermbase">Tabstopptaste</gls:translation>
<gls:translation ref="#m2" source="myTermbase">TAB-TASTE</gls:translation>
<gls:definition source="publicTermbase">A keyboard key that is traditionally used to insert tab characters into a document.</gls:definition>
</gls:glossEntry>
(5) Please change the 5.2.7 XML Schema examples from:
<xs:element name="glossary">
<xs:complexType mixed="false">
<xs:sequence>
<xs:element minOccurs="1" maxOccurs="unbounded" ref="gls:glossentry" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="glossentry">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="1" maxOccurs="1" ref="gls:term"/>
<xs:element minOccurs="0" maxOccurs="unbounded" ref="gls:translation" />
<xs:element minOccurs="0" maxOccurs="1" ref="gls:definition" />
<xs:any maxOccurs="unbounded" minOccurs="0" namespace="##other" processContents="skip"/>
</xs:sequence>
<xs:attribute name="id" use="optional" type="xs:NMTOKEN"/>
<xs:anyAttribute namespace="##any" processContents="skip"/>
</xs:complexType>
</xs:element>
to
<xs:element name="glossary">
<xs:complexType mixed="false">
<xs:sequence>
<xs:element minOccurs="1" maxOccurs="unbounded" ref="gls:glossEntry" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="glossEntry">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="1" maxOccurs="1" ref="gls:term"/>
<xs:element minOccurs="0" maxOccurs="unbounded" ref="gls:translation" />
<xs:element minOccurs="0" maxOccurs="1" ref="gls:definition" />
<xs:any maxOccurs="unbounded" minOccurs="0" namespace="##other" processContents="skip"/>
</xs:sequence>
<xs:attribute name="id" use="optional" type="xs:NMTOKEN"/>
<xs:anyAttribute namespace="##any" processContents="skip"/>
</xs:complexType>
</xs:element>
(6) Please change the 5.1.6 Example: from:
<mda:metagroup>
<!-- One or more of mda:metagroup or mda:meta -->
</mda:metagroup>
</mda:metadata>
to
<mda:metaGroup>
<!-- One or more of mda:metagroup or mda:meta -->
</mda:metaGroup>
</mda:metadata>
(7) Please change 5.4.4.1 Tree Structure from:
<_metadata>
|
+---<metaGroup> +
|
+---At least one of (<metagroup> or <meta>)
|
+---<meta>
to
<_metadata>
|
+---<metaGroup> +
|
+---At least one of (<metaGroup> or <meta>)
|
+---<meta>
(8) Please change 5.4.4.2 metadata from
Contains:
- One or more <metagroup> elements
to
Contains:
- One or more <metaGroup> elements
(9) Please change the example in 5.4.4.2 metadata from
<mda:metadata>
<mda:metagroup category="row_xml_attribute">
<mda:meta type="style">head</mda:meta>
</mda:metagroup>
</mda:metadata>
</group>
<group name="row">
<unit id="u3" name="cell">
<segment>
<source>Patrick K.</source>
</segment>
</unit>
<unit id="u4" name="cell">
<segment>
<source>Right Wing</source>
</segment>
</unit>
</group>
<group name="row">
<unit id="u5" name="cell">
<segment>
<source>Bryan B.</source>
</segment>
</unit>
<unit id="u6" name="cell">
<segment>
<source>Left Wing</source>
</segment>
</unit>
</group>
</group>
<mda:metadata>
<mda:metagroup category="document_xml_attribute">
<mda:meta type="version">3</mda:meta>
<mda:meta type="phase">draft</mda:meta>
</mda:metagroup>
</mda:metadata>
to
<mda:metadata>
<mda:metaGroup category="row_xml_attribute">
<mda:meta type="style">head</mda:meta>
</mda:metaGroup>
</mda:metadata>
</group>
<group name="row">
<unit id="u3" name="cell">
<segment>
<source>Patrick K.</source>
</segment>
</unit>
<unit id="u4" name="cell">
<segment>
<source>Right Wing</source>
</segment>
</unit>
</group>
<group name="row">
<unit id="u5" name="cell">
<segment>
<source>Bryan B.</source>
</segment>
</unit>
<unit id="u6" name="cell">
<segment>
<source>Left Wing</source>
</segment>
</unit>
</group>
</group>
<mda:metadata>
<mda:metaGroup category="document_xml_attribute">
<mda:meta type="version">3</mda:meta>
<mda:meta type="phase">draft</mda:meta>
</mda:metaGroup>
</mda:metadata>
(10) Please change 5.4.5.1 category from:
category - indicates a category for metadata contained in the enclosing <metagroup> element.
Value description: Text.
Default value: undefined.
Used in: <metagroup>.
to
category - indicates a category for metadata contained in the enclosing <metaGroup> element.
Value description: Text.
Default value: undefined.
Used in: <metaGroup>.
(11) Please change 5.4.5.3 appliesTo from
Indicates the element to which the content of the metagroup applies.
Value description: source, target, or ignorable.
Default value: undefined.
Used in: <metagroup>.
to
Indicates the element to which the content of the metaGroup applies.
Value description: source, target, or ignorable.
Default value: undefined.
Used in: <metaGroup>.
(12) Please change 5.4.6 Example: from:
<mda:metadata>
<mda:metagroup>
<!-- One or more of mda:metagroup or mda:meta -->
</mda:metagroup>
</mda:metadata>
to
<mda:metadata>
<mda:metaGroup>
<!-- One or more of mda:metagroup or mda:meta -->
</mda:metaGroup>
</mda:metadata>
(13) Please change 5.4.7 XML Schema from:
<xs:element name="metadata">
<xs:complexType mixed="false">
<xs:sequence>
<xs:element minOccurs="1" maxOccurs="unbounded" ref="mda:metagroup" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="metagroup">
<xs:complexType>
<xs:sequence>
<xs:choice minOccurs="1" maxOccurs="unbounded">
<xs:element ref="mda:metagroup"/>
<xs:element ref="mda:meta"/>
</xs:choice>
</xs:sequence>
<xs:attribute name="category" use="optional"/>
<xs:attribute name="appliesTo" use="optional" type="xlf:appliesTo"/>
</xs:complexType>
</xs:element>
to
<xs:element name="metadata">
<xs:complexType mixed="false">
<xs:sequence>
<xs:element minOccurs="1" maxOccurs="unbounded" ref="mda:metaGroup" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="metaGroup">
<xs:complexType>
<xs:sequence>
<xs:choice minOccurs="1" maxOccurs="unbounded">
<xs:element ref="mda:metagroup"/>
<xs:element ref="mda:meta"/>
</xs:choice>
</xs:sequence>
<xs:attribute name="category" use="optional"/>
<xs:attribute name="appliesTo" use="optional" type="xlf:appliesTo"/>
</xs:complexType>
</xs:element>
----------------------------
-----Original Message-----
From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf Of Yves Savourel
Sent: Wednesday, December 11, 2013 8:21 AM
To: xliff@lists.oasis-open.org
Subject: RE: [xliff] Eelement names
Good point Tom.
It looks like the specification is inconsistent: we use both glossEntry and glossentry and also both metaGroup and metagroup in text and examples.
Thanks,
-ys
-----Original Message-----
From: Schnabel, Bryan S [mailto:bryan.s.schnabel@tektronix.com]
Sent: Wednesday, December 11, 2013 8:37 AM
To: Tom Comerford; Yves Savourel; xliff@lists.oasis-open.org
Subject: RE: [xliff] Eelement names
Thanks for the clarification Tom. This should be treated as a non-issue (tracker-wise), and once the schemas are archived in SVN it will be a fixed issue (schema to specification-wise).
________________________________________
From: xliff@lists.oasis-open.org [xliff@lists.oasis-open.org] on behalf of Tom Comerford [tom@supratext.com]
Sent: Wednesday, December 11, 2013 7:22 AM
To: Schnabel, Bryan S; 'Yves Savourel'; xliff@lists.oasis-open.org
Subject: RE: [xliff] Eelement names
For the record, both glossEntry and metaGroup are in the spec, but I haven't yet updated the schema files. Working on the assumption that (a) the spec takes precedence and (b) the name changes in the spec have already been approved, I can update the schema files later today.
-----Original Message-----
From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf Of Schnabel, Bryan S
Sent: Wednesday, December 11, 2013 10:10 AM
To: Yves Savourel; xliff@lists.oasis-open.org
Subject: RE: [xliff] Eelement names
I second Yves' proposal to change <metagroup> to <metaGroup>, and <glossentry> to <glossEntry>.
Please communicate any dissent by Friday.
I will add this to the tracker as an editorial improvement in the category that our OASIS admin indicated is allowed post-PR comment period, and as an editorial fix, I will add DavidF as owner.
Thanks,
Bryan
________________________________________
From: xliff@lists.oasis-open.org [xliff@lists.oasis-open.org] on behalf of Yves Savourel [ysavourel@enlaso.com]
Sent: Wednesday, December 11, 2013 4:50 AM
To: xliff@lists.oasis-open.org
Subject: [xliff] Eelement names
Hi everyone,
While <metadata> all lowercase is fine (because it's an actual word), based on our naming convention <mda:metagroup> should be <mda:metaGroup>, like <res:resourceData> for example.
(I also wonder why we didn't simply use <mda:group> as it's in a different namespace...
Or why we use <mda:meta> instead of <mda:data>... but never mind).
In the same vein:
<gls:glossentry> should be <gls:glossEntry> (or better: <gls:entry>).
At this point I don't really care if we change or not any of those, but keep in mind that is the last chance to get them right and consistent (if we think they are wrong).
Cheers,
-yves
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]