OASIS XML Localisation Interchange File Format (XLIFF) TC

For the metadata module, section 5.4.5 Module Attributes omits the id attribute from the list of module attributes and there is no subsection describing the element.   I believe that this is an editorial issue, and as a resolution I propose to add ‘id’ to the list of attributes and to add this subsection:                   #.#.#.# id                   Identifier - a character string used to identify a <metadata> or <metaGroup> element.                   Value description: NMTOKEN.                   Default value: undefined                   Used in: <metadata> and <metaGroup>.                   Constraints                   The id value MUST be unique within the enclosing <metadata> and <metaGroup> elements.   Please provide any comments or dissent before Monday, March 17.

Thanks, Tom, this looks good to me, and I can implement that today. Just the id constraint should simply say that the id must be unique within the enclosing metadata element. This is I believe the general fragid principle we adopted for module ids. And when something is unique within the metadata element it is then automatically unique within any recursively nested metagroup elements so no need to mention this element in that constraint. I'd say this is not dissent just clarification on how I am going to implement the suggestion. So this should not amend the deadline for dissent you set. Cheers dF Dr. David Filip ======================= LRC CNGL LT-Web CSIS University of Limerick, Ireland telephone: +353-6120-2781 cellphone: +353-86-0222-158 facsimile: +353-6120-2734 http://www.cngl.ie/profile/?i=452 mailto: david.filip@ul.ie On Fri, Mar 14, 2014 at 5:08 AM, Tom Comerford < tom@supratext.com > wrote: For the metadata module, section 5.4.5 Module Attributes omits the id attribute from the list of module attributes and there is no subsection describing the element.   I believe that this is an editorial issue, and as a resolution I propose to add ‘id’ to the list of attributes and to add this subsection:                   #.#.#.# id                   Identifier - a character string used to identify a <metadata> or <metaGroup> element.                   Value description: NMTOKEN.                   Default value: undefined                   Used in: <metadata> and <metaGroup>.                   Constraints                   The id value MUST be unique within the enclosing <metadata> and <metaGroup> elements.   Please provide any comments or dissent before Monday, March 17.

Tom, all, This is now implemented as follows Identifier - a character string used to identify a <metadata> or <metaGroup> element. Value description: NMTOKEN Default value: undefined Used in:<metadata> and <metaGroup> Constraints The values of id attributes must be unique among all <metaGroup> and <metadata> elements within the given enclosing <metadata> element.  This will be included in the module specification and printed later today GMT The constraint follows the wording we used elsewhere in the spec, such as in core and glossary module. It makes sure that the id follows the agreed fragid principle at any given module node. Cheers dF Dr. David Filip ======================= LRC CNGL LT-Web CSIS University of Limerick, Ireland telephone: +353-6120-2781 cellphone: +353-86-0222-158 facsimile: +353-6120-2734 http://www.cngl.ie/profile/?i=452 mailto: david.filip@ul.ie On Fri, Mar 14, 2014 at 10:11 AM, Dr. David Filip < David.Filip@ul.ie > wrote: Thanks, Tom, this looks good to me, and I can implement that today. Just the id constraint should simply say that the id must be unique within the enclosing metadata element. This is I believe the general fragid principle we adopted for module ids. And when something is unique within the metadata element it is then automatically unique within any recursively nested metagroup elements so no need to mention this element in that constraint. I'd say this is not dissent just clarification on how I am going to implement the suggestion. So this should not amend the deadline for dissent you set. Cheers dF Dr. David Filip ======================= LRC CNGL LT-Web CSIS University of Limerick, Ireland telephone:  +353-6120-2781 cellphone: +353-86-0222-158 facsimile:  +353-6120-2734 http://www.cngl.ie/profile/?i=452 mailto: david.filip@ul.ie On Fri, Mar 14, 2014 at 5:08 AM, Tom Comerford < tom@supratext.com > wrote: For the metadata module, section 5.4.5 Module Attributes omits the id attribute from the list of module attributes and there is no subsection describing the element.   I believe that this is an editorial issue, and as a resolution I propose to add ‘id’ to the list of attributes and to add this subsection:                   #.#.#.# id                   Identifier - a character string used to identify a <metadata> or <metaGroup> element.                   Value description: NMTOKEN.                   Default value: undefined                   Used in: <metadata> and <metaGroup>.                   Constraints                   The id value MUST be unique within the enclosing <metadata> and <metaGroup> elements.   Please provide any comments or dissent before Monday, March 17.

This has now been printed, so that you can check it on the editor's copy pdf and svn Cheers dF Dr. David Filip ======================= LRC CNGL LT-Web CSIS University of Limerick, Ireland telephone: +353-6120-2781 cellphone: +353-86-0222-158 facsimile: +353-6120-2734 http://www.cngl.ie/profile/?i=452 mailto: david.filip@ul.ie On Fri, Mar 14, 2014 at 10:45 AM, Dr. David Filip < David.Filip@ul.ie > wrote: Tom, all, This is now implemented as follows Identifier - a character string used to identify a <metadata> or <metaGroup> element. Value description: NMTOKEN Default value: undefined Used in:<metadata> and <metaGroup> Constraints The values of id attributes must be unique among all <metaGroup> and <metadata> elements within the given enclosing <metadata> element.  This will be included in the module specification and printed later today GMT The constraint follows the wording we used elsewhere in the spec, such as in core and glossary module. It makes sure that the id follows the agreed fragid principle at any given module node. Cheers dF Dr. David Filip ======================= LRC CNGL LT-Web CSIS University of Limerick, Ireland telephone:  +353-6120-2781 cellphone: +353-86-0222-158 facsimile:  +353-6120-2734 http://www.cngl.ie/profile/?i=452 mailto: david.filip@ul.ie On Fri, Mar 14, 2014 at 10:11 AM, Dr. David Filip < David.Filip@ul.ie > wrote: Thanks, Tom, this looks good to me, and I can implement that today. Just the id constraint should simply say that the id must be unique within the enclosing metadata element. This is I believe the general fragid principle we adopted for module ids. And when something is unique within the metadata element it is then automatically unique within any recursively nested metagroup elements so no need to mention this element in that constraint. I'd say this is not dissent just clarification on how I am going to implement the suggestion. So this should not amend the deadline for dissent you set. Cheers dF Dr. David Filip ======================= LRC CNGL LT-Web CSIS University of Limerick, Ireland telephone:  +353-6120-2781 cellphone: +353-86-0222-158 facsimile:  +353-6120-2734 http://www.cngl.ie/profile/?i=452 mailto: david.filip@ul.ie On Fri, Mar 14, 2014 at 5:08 AM, Tom Comerford < tom@supratext.com > wrote: For the metadata module, section 5.4.5 Module Attributes omits the id attribute from the list of module attributes and there is no subsection describing the element.   I believe that this is an editorial issue, and as a resolution I propose to add ‘id’ to the list of attributes and to add this subsection:                   #.#.#.# id                   Identifier - a character string used to identify a <metadata> or <metaGroup> element.                   Value description: NMTOKEN.                   Default value: undefined                   Used in: <metadata> and <metaGroup>.                   Constraints                   The id value MUST be unique within the enclosing <metadata> and <metaGroup> elements.   Please provide any comments or dissent before Monday, March 17.