OASIS XML Localisation Interchange File Format (XLIFF) TC

  • 1.  Eelement names

    Posted 12-11-2013 12:50
    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


  • 2.  RE: [xliff] Eelement names

    Posted 12-11-2013 15:10
    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


  • 3.  RE: [xliff] Eelement names

    Posted 12-11-2013 15:22
    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


  • 4.  RE: [xliff] Eelement names

    Posted 12-11-2013 15:37
    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


  • 5.  RE: [xliff] Eelement names

    Posted 12-11-2013 16:22
    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


Related Content