U.S. TC46 TAG comments / Date: 2010-04-20 / Document:ISO/DIS 24616
1 / 2 / (3) / 4 / 5 / (6) / (7)
MB1
/ Clause No./
Subclause No./
Annex
(e.g. 3.1) / Paragraph/
Figure/Table/Note
(e.g. Table 1) / Type of com-ment2 / Comment (justification for change) by the MB / Proposed change by the MB / Secretariat observations
on each comment submitted
AT / ge, te / Comment 1: The standard aims at reaching “ a better convergence between heterogenous standardization activities” (see Introduction), references important metamodels like the TMF metamodel, ISO 12620 and DCR data categories, but does not mention terminology management at all. At least non-nested, simple structured term entries could be mapped onto MLIF (term onto SegC, langSet onto MonoC, termEntry onto MultiC). / Argue in a more holistic way and include terminology references (Introduction, Scope, etc.) and examples (Annex). / This is not the purpose for this specification to represent terminology, however, you are right: simple structured terms could be easily map onto MLIF.
AT / ge, te / Comment 2: It is not explicitly clarified if the objective of the present standard is to define a XML-based framework or a generic framework where XML is only one possible representation among others. In 5.1 it is stated that “MLIF provides a generic structure …“. However, components and data categories are not expressed consistently (mostly in XML style) and named “Elements” in Annex G.
If the standard is meant to be generic, it should distinguish neatly throughout the whole document between the components of the metamodel graph vs. the exemplary XML representation of these components (e.g. HistoC component vs. <HistoC> element) and generic ISO TC 37 DCR data categories vs. XML instances of data categories (e.g. /sourcetype/ vs. <sourceType>). / Make a clear statement at the beginning of the standard and express components and data category names accordingly and in a consistent way. / The specification defines an XML based framework. Nowadays, there is nothing else.
AT / ge / Comment 3: There is a lack of consistency in spelling throughout the document (“standardisation” vs. “standardization” or “A recursive component allowing any level of segmentation for textual information.” in 4.2 vs. “the person responsible for the creation of the content.” in 5.9) and punctuation, for example, the use of periods in running text and tables (“Represents a collection of data containg global information and several multilingual units.” in 4.2 with period vs. “Indicates the format from which MLIF data have been generated from an MLIF compliant application” in 5.4 without period). / Use spelling and punctuation in a consistent way. / You are right. We have harmonized the text, based on your comments.
AT / Introduction / P 2 / ed / Comment 4: Spelling error and inconsistent spelling (Multi Lingual Information Framework. See title of the standard) / Multilingual information framework / done
AT / Introduction / P 3 / ed / Comment 5: Inconsistent spelling (standardisation vs. standardization?). See comment 3 / done
AT / 2 / P 4 / te / Comment 6: ISO 12620 has been updated recently (ISO 12620:2009). Problem: The current ISO 12620 does not contain specific data categories any more. These data categories has been moved to a web-based service (ISOcat) to be part of the ISO TC 37 Data Category Registry. So if specific data categories and the corresponding definition are cited, the DCR should be referenced. / ISOcat - ISO TC 37 Data Category Registry, / 12620:2009 is refered and is mentionned inside this specification, please see the new section-2
AT / 2 / P 6 / te / Comment 7: Update ISO 8601. / ISO 8601:2004 (or newer version if available) / ok, done.
AT / 3.2 / P 1 / te / Comment 8: Include video games. / textual versions of the dialog in films, television programs, video games, etc. / ok
AT / 3.3 / Title / ed / Comment 9: Inconsistent spelling (Synchronisation vs. Synchronization?). See comment 3. / ok
AT / 4 / Title / ed / Comment 10: Inconsistent spelling (Metamodel) / MLIF metamodel / ok
AT / 4.2 / 1st – 7th bullet / te / Comment 11: <MLDC>, <GI>, <GroupC>, etc. See comment 2. / see comment 2
AT / 4.2 / 5th bullet / ed / Comment 12: Inconsistent spelling (Part vs. part?). See comment 3. / ok
AT / 4.2 / 7th bullet / ed / Comment 13: Inconsistent spelling (A recursive vs. a recursive?) and punctuaction (period or not?). See comment 3. / ok
AT / 4.2 / Figure / ed / Comment 14: Inconsistent use of period. The titles of figure 2 (5.2) and figure 3 (Annex B.4) end with a period. / MLIF metamodel. / ok
AT / 5.2 / Figure / ed / Comment 15: Spelling error (Data Categories). Graph and text are too small. / data categories. / no, the graph is not too small. This is the usual size.
AT / 5.3 / 1st,, 2nd bullet / ed / Comment 16: Set off attributes using italics in running text. / xml:lang must be … xml:id must be … / fixed
AT / 5.3 / 2nd bullet / ed / Comment 17: Spelling error (must me) / must be / thanks, fixed
AT / 5.4 / All / te / Comment 18: For names of data categories see comment 2. A set of data categories is listed, but some of these data categories (creationDate, creationIdentifier, creationTool, formatVersion) seem not to be standard ISOcat data categories (in TDG 11 - Multilingual Information Management). If so, shouldn´t they be public for referencing? / ok
AT / 5.4 / 1st – 8th bullet / ed / Comment 19: Missing trailing spaces after brackets / e.g. … Specifies / ok
AT / 5.4 / 3rd, 4th, 7th bullet / te / Comment 20: ISO 12620:1999 (3 times). See comment 6. / [ISOcat - ISO TC 37 Data Category Registry] / ok
AT / 5.4 / 3rd, 4th, 5th, 6th, 7th bullet / ed / Comment 21: Inconsistent punctuation (periods or not?). See comment 3. / ok
AT / 5.4 / 8th bullet / ed / Comment 22: Spelling error (inficate) / indicate / ok
AT / 5.5 / te / Comment 23: For names of data categories see comment 2. For standard data categories see comment 18. / ok
AT / 5.5 / 1st bullet / ed / Comment 24: Wrong word (Specific) / (Group type) Specifies / ok
AT / 5.6 / te / Comment 25: For names of data categories see comment 2. For standard data categories see comment 18. / ok
AT / 5.6 / 1st bullet / ed / Comment 26: Inconsistent spelling (A hierarchical vs. a hierarchical?) and punctuation (period or not?). See comment 3. / ok
AT / 5.7 / 1st, 2nd bullet / te / Comment 27: For names of data categories see comment 2. For standard data categories see comment 18. / ok
AT / 5.7 / 1st bullet / ed / Comment 28: Spelling error (translaiton) and inconsistent punctuation (period or not?). See comment 3. / translation / ok
AT / 5.7 / 3rd, 4th bullet / ed / Comment 29: Missing space and inconsistent punctuation (period or not?). See comment 3. / e.g. att.lang Provides / ok
AT / 5.7 / Table / ed / Comment 30: Inconsistent use in tables throughout the document (see also Annex G.4) of minuscule/capital letters at the beginning of sentences or fragments / ok
AT / 5.7 / Row href / ed / Comment 31: Inconsistent punctuation (period or not?). See comment 3. / ok
AT / 5.7 / Row type / ed / Comment 32: Inconsistent punctuation (period or not?). See comment 3. / ok
AT / 5.8 / 1st – 7th bullet / te / Comment 33: For names of data categories see comment 2. For standard data categories see comment 18. / ok
AT / 5.8 / 1st bullet / ed / Comment 34: Spelling error (translaiton) and inconsistent punctuation (period or not?). See comment 3. / translation / ok
AT / 5.8 / 7th, 8th bullet / ed / Comment 35: Missing space / e.g. att.linguistic Linguistic / ok
AT / 5.8 / Table 1, row Pos / ed / Comment 36: Inconsistent spelling (Pos vs. pos?, indicates vs. Indicates?) and punctuation (period or not?). See comment 3. / ok
AT / 5.8 / Table 1, row Lemma / ed / Comment 37: Inconsistent spelling (Lemma vs. lemma?) and punctuation (period or not?). See comment 3. / ok
AT / 5.8 / Table 1, row mfeature / ed / Comment 38: Inconsistent spelling (this vs. This?) and punctuation (period or not?). See comment 3. / ok
AT / 5.8 / 9th bullet / ed / Comment 39: Missing space and inconsistent punctuation (period or not?). See comment 3. / att.xlink Provides / ok
AT / 5.8 / Table 2, row href / ed / Comment 40: Inconsistent punctuation (period or not?). See comment 3. / ok
AT / 5.8 / Table 2, row type / ed / Comment 41: Inconsistent punctuation (period or not?). See comment 3. / ok
AT / 5.9 / P 1 / ed / Comment 42: Inconsistent writing of MLIF metamodel components / ok
AT / 5.9 / P 2 / ed / Comment 43: Inconsistent writing of MLIF metamodel component (HistoryComponent) / HistoC component / ok
AT / 5.9 / P 2, all bullets / te / Comment 44: For names of data categories see comment 2. For standard data categories see comment 18. / ok
AT / 5.9 / P 2, all bullets / ed / Comment 45: Inconsistent punctuation (period or not?). See comment 3. / ok
AT / 5.10 / P 2, all bullets / te / Comment 46: For names of data categories see comment 2. For standard data categories see comment 18. / ok
AT / 5.10 / P 2 / te / Comment 47: <SegC>. See comment 2. / see comment 2
AT / 5.10 / P 3 / ed / Comment 48: Delete leading space at the beginning of the first sentence. Grammatical error (permits) / <g> … permit / ok
AT / 5.11 / Title / ed / Comment 49: Inconsistent spelling (localisation vs. localization?). See comment 3. / ok
AT / 5.11 / All bullets / te / Comment 50: For names of data categories see comment 2. For standard data categories see comment 18. / ok
AT / 5.11 / 1st bullet / ed / Comment 51: Spelling error (translaiton) and inconsistent punctuation (period or not?). See comment 3. / translation / ok
AT / 5.12 / Title / ed / Comment 52: Inconsistent spelling (internationalisation vs. internationalization). See comment 3. / ok
AT / 5.12 / 1st bullet / te / Comment 53: For names of data categories see comment 2. For standard data categories see comment 18. / ok
AT / 5.12 / 1st bullet / ed / Comment 54: Missing space / … The translate / ok
AT / 5.13 / Title / ed / Comment 55: Inconsistent spelling (synchronisation vs. synchronization). See comment 3. / ok
AT / 5.13 / All bullets / te / Comment 56: For names of data categories see comment 2. For standard data categories see comment 18. / ok
AT / 5.13 / All bullets / ed / Comment 57: Missing space / e.g. … The duration / ok
AT / 6 / P 2 / ed / Comment 58: The abbreviation “TM” for “Translation Memory” is already introduced in the Introduction clause. / localization and TM resources / ok
AT / 6 / P 3 / ed / Comment 59: Formatting error (…) / part of speech, etc., but … section, etc.). / ok
AT / Annex A / P 3 / te / Comment 60: A current version of Trados Workbench should be used. / SDL Translator's Workbench 8 is as follows: / ok
AT / Annex A / P 3 (Code) / te / Comment 61: Use a current version of Trados Workbench (exemplary build version). / creationtoolversion=”Edition 8 Build 863” / done
AT / Annex A / P 5 (Step-1) / ed / Comment 62: Inconsistent punctuation (period or not?). See comment 3. / ok
AT / Annex B.2 / P 1, 1st, 2nd, 4th, 5th, 6th bullet / te / Comment 63: <MLDC> component , <GI> component, etc. See comment 2. / ok
AT / Annex B.2 / P 1, 3rd bullet / ed / Comment 64: Incorrect use of brackets (<MLIF>) and inconsistent punctuation (period or not?). See comment 3. / MLIF metamodel / ok
AT / Annex B.2 / P 2 / ed / Comment 65: Missing colon / core data categories as follows: / ok
AT / Annex B.2 / P 2, 1st bullet / ed / Comment 66: Inconsistent spelling (the creationtool vs. The creationTool?) and punctuaction (period or not?). See comment 3. Set off the attribute using italics in running text. / creationtool attribute / no. "creationtool" is the TMX name and "creationTool" is the MLIF name
AT / Annex B.2 / P 2, 1st bullet / te / Comment 67: <creationTool>. See comment 2. “creationTool” is defined as a data category, but this data category seems not to be a standard ISOcat data category (in TDG 11 - Multilingual Information Management). If so, shouldn´t it be public for referencing? See comment 18. / ok
AT / Annex B.2 / P 2, 2nd bullet / ed / Comment 68: Inconsistent spelling (the creationDate vs. The creationDate?) and punctuaction (period or not?). See comment 3. Set off the attribute using italics in running text. / creationdate attribute / see comment 66
AT / Annex B.2 / P 2, 2nd bullet / te / Comment 69: <creationDate>. See comment 2. “creationDate” is defined as a data category, but this data category seems not to be a standard ISOcat data category (in TDG 11 - Multilingual Information Management). If so, shouldn´t it be public for referencing? See comment 18. / ok
AT / Annex B.2 / P 2, 3rd bullet / ed / Comment 70: Inconsistent spelling (the tuid vs. The tuid?) and punctuaction (period or not?). See comment 3. Set off the attribute using italics in running text. / tuid attribute / ok
AT / Annex B.2 / P 2, 3rd bullet / te / Comment 71: <creationIdentifier>. See comment 2. “creationIdentifier” is defined as a data category, but this data category seems not to be a standard ISOcat data category (in TDG 11 - Multilingual Information Management). If so, shouldn´t it be public for referencing? See comment 18. / ok
AT / Annex B.2 / P 2, 4th bullet / ed / Comment 72: Inconsistent spelling (the <pop> vs. The <pop>?) and punctuation (period or not?). See comment 3. Spelling error (ISOCat) / ISOcat / ok
AT / Annex B.3 / P 1 / te / Comment 73: If working drafts of standards are cited, it should be done with all standards (e.g. development of XLIFF 2.0). / ok
AT / Annex B.4 / P 1 / ed / Comment 74: The terms used in the explainatory text of figure 3 should be consistent with the terms used in corresponding the figure (or viceversa). Also, it would help to have the reference numbers in the text assigned to the corresponding arrows in the figure. Figure and text are too small. / a MLIF document (3) … relevant linguistic content. / ok
AT / Annex C.2 / P 1 / te / Comment 75: For names of data categories see comment 2. For standard data categories see comment 18. / ok
AT / Annex C.2 / P 1 / te / Comment 76: <MonoC>, <GI>. See comment 2. / ok
AT / Annex C.2 / P 2, 1st bullet / te, ed / Comment 77: <MLDC>. See comment 2. Inconsistent punctuation (period or not?). See comment 3. / ok
AT / Annex C.2 / P 2, 2nd bullet / te, ed / Comment 78: <GI>. See comment 2. Inconsistent punctuation (period or not?). See comment 3. / ok
AT / Annex C.2 / P 2, 3rd bullet / ed / Comment 79: Inconsistent punctuation (period or not?). See comment 3. / ok
AT / Annex C.2 / P 2, 4th bullet / ed, te / Comment 80: Inconsistent spelling (the <phase> vs. The <phase>?) and punctuation (period or not?). See comment 2. <HistoC>. See comment 3. / ok
AT / Annex C.2 / P 2, 5th bullet / te, ed / Comment 81: <MultiC>. See comment 2. Inconsistent punctuation (period or not?). See comment 3. / ok
AT / Annex C.2 / P 2, 6th bullet / te / Comment 82: <MonoC>, <SegC>. See comment 2. / ok
AT / Annex C.2 / P 2, 6th bullet / te / Comment 83: <translationRole>, <sourceLanguage>. See comment 2. “translationRole” is defined as a data category, but this data category seems not to be a standard ISOcat data category (in the whole public workspace and in TDG 11 - Multilingual Information Management). If so, shouldn´t it be public for referencing? See comment 18. Inconsistent use of brackets (here translationRole and sourceLanguage without brackets). / ok
AT / Annex C.2 / P 2, 7th bullet / te / Comment 84: <MonoC>, <SegC>. See comment 2. / ok
AT / Annex C.2 / P 2, 7th bullet / te / Comment 85: <translationRole>, <targetLanguage>. See comment 2. “translationRole” is defined as a data category, but this data category seems not to be a standard ISOcat data category (in the whole public workspace and in TDG 11 - Multilingual Information Management). If so, shouldn´t it be public for referencing? See comment 18. / ok
AT / Annex C.2 / P 2, 8th bullet / te, ed / Comment 86: <MultiC>. See comment 2. Inconsistent punctuation (period or not?). See comment 3. / ok
AT / Annex C.2 / P 2, 8th bullet / te / Comment 87: <translationStatus>, <alternateTranslation>. See comment 2. At least “translationStatus” (“alternateTranslation”?) is defined as a data category, but this data category seems not to be a standard ISOcat data category (in the whole public workspace and in TDG 11 - Multilingual Information Management). If so, shouldn´t it be public for referencing? See comment 18. / ok
AT / Annex C.2 / P 3, 1st bullet / ed / Comment 88: Inconsistent spelling (the tool vs. The tool?) and punctuation (period or not?). See comment 3. Set off the attribute using italics in running text. / tool attribute / ok
AT / Annex C.2 / P 3, 1st bullet / te / Comment 89: <creationTool>. See comment 2. “creationTool” is defined as a data category, but this data category seems not to be a standard ISOcat data category (in TDG 11 - Multilingual Information Management). If so, shouldn´t it be public for referencing? See comment 18. / ok
AT / Annex C.3 / P 1 / te / Comment 90: Update XLIFF version. / The current version of XLIFF is 1.2 (1 February 2008). / ok
AT / Annex C.3 / Code / te / Comment 91: Change XLIFF version (5 times). / 1.2 / ok
AT / Annex D.2 / P 1 / ed / Comment 92: Inconsistent spelling (synchronisation vs. synchronization?). See comment 3. / ok
AT / Annex D.3 / P 2, 1st bullet / te, ed / Comment 93: <MonoC>. See comment 2. Inconsistent punctuation (period or not?). See comment 3. / ok
AT / Annex D.3 / P 2, 2nd bullet / te, ed / Comment 94: <SegC>. See comment 2. Inconsistent punctuation (period or not?). See comment 3. / ok
AT / Annex D.3 / P 3 / ed / Comment 95: Delete “a” in “based on the a <switch> constructs” / the <switch> constructs / ok
AT / Annex D.4 / P 1, 3rd bullet / ed / Comment 96: Spelling error (tevelement) / <tev> element / fixed now
AT / Annex D.4 / P 2, all bullets / ed / Comment 97: Perhaps it would be better to use a more specific description for the three attributes instead of "dur maps onto …" and set them off using italics in running text. / - The dur attribute maps onto
- The begin attribute
- The next attribute / ok
AT / Annex D.4 / P 2, all bullets / ed / Comment 98: Inconsistent punctuation (period or not?). See comment 3. / ok
AT / Annex E.1 / P 3 / ed / Comment 99: Use capital letters for file formats (see ISO 12639:2004). / TIFF, BMP / ok
AT / Annex E.2 / Fragment-3 / ed / Comment 100: Spelling error (xlink) / XLink / ok
AT / Annex E.2 / Fragment-3 / ed / Comment 101: Wrong word (bloc) / block / ok
AT / Annex E.3.1 / P 1 / ed / Comment 102: Wrong word (This) and missing period (or colon). / The … format. / ok
AT / Annex E.4 / Code / ed / Comment 103: There are some empty code lines. They should be deleted. / ok
AT / Annex G.2.1 – G. 2.6 / First row / ed / Comment 104: Inconsistent punctuation (period or not?). See comment 3. / ok
AT / Annex G.2.7 / First row / ed / Comment 105: Inconsistent spelling (internationalisation vs. internationalization?). See comment 3. / ok
AT / Annex G.2.9 / First row / ed / Comment 106: Inconsistent spelling (localisation vs. localization?). See comment 3. / ok
AT / Annex G.2.9 – G.2.10 / Row Note / ed / Comment 107: Inconsistent punctuation (period or not?). See comment 3. / ok
AT / Annex G.2.11 / First row / ed / Comment 108: Inconsistent spelling (Meta vs. meta?). See comment 3 / ok
AT / Annex G.3.2 – G.3.3 / First row / ed / Comment 109: Inconsistent punctuation (period or not?). See comment 3. / ok
AT / Annex G.3.4 / Row pos, lemma, mfeature / ed / Comment 110: Inconsistent spelling (indicates) and punctuaction (period or not?). See comment 3. / ok
AT / Annex G.3.6 / First row, href, Note, type, Values are: / ed / Comment 111: Inconsistent punctuation (period or not?). See comment 3. / ok
AT / Annex G.3.6 / Row Values are: / ed / Comment 112: Spelling error (trasversal) / transversal / ok
AT / Annex G.4 / All titles / te / Comment 113: For names of data categories see comment 2. For standard data categories see comment 18. / ok
AT / Annex G.4.1 / Row Note / ed / Comment 114: Formatting error (…) / etc. / done
AT / Annex G.4.3 / Row Note / ed / Comment 115: Formatting error (…) / etc. / done
AT / Annex G.4.5 / First row / ed / Comment 116: Inconsistent spelling (Part vs.part?). See comment 3. / ok
AT / Annex G.4.7 / First row / ed / Comment 117: Inconsistent spelling (A recursive vs. a recursive?) and punctuation (period or not?). See comment 3. / ok
AT / Annex G.4.8 / First row / ed / Comment 118: Inconsistent punctuation (period or not?). See comment 3. / ok
AT / Annex G.4.10 / First row / te / Comment 119: For names of data categories see comment 2. / ok
AT / Annex G.4.13 / First row / ed / Comment 120: Inconsistent spelling (A hierarchical vs. a hierarchical?) and punctuation (period or not?). See comment 3. / ok
AT / Annex G.4.18 / First row / ed / Comment 121: Inconsistent punctuation (period or not?). See comment 3. / ok
AT / Annex G.4.20 / First row / ed / Comment 122: Inconsistent spelling (The duration vs. the duration?) and punctuation (period or not?). See comment 3. / ok
AT / Annex G.4.21 / Row Note / te / Comment 123: The cell contains a comment/question, not a specification. / ok
AT / Annex G.4.22 / First row / te / Comment 124: For names of data categories see comment 2. / ok
AT / Annex G.4.23 / First row / ed / Comment 125: Inconsistent punctuation (period or not?). See comment 3. / ok
AT / Annex G.4.26 / First row / ed / Comment 126: Wrong word (Specific) / Specifies / ok
AT / Annex G.4.27 / Row Note / ed / Comment 127: Inconsistent punctuation (period or not?). See comment 3. / ok
AT / Annex G.4.32 / First row / ed, te / Comment 128: Inconsistent spelling (A complete vs. a complete) and punctuation (period or not?). See comment 3. Update ISO reference. See comment 6. / [ISOcat – ISO TC 37 Data Category Registry] / ok
AT / Annex G.4.33 / First row / ed / Comment 129: Inconsistent punctuation (period or not?). See comment 3. / ok
AT / Annex G.4.34 / First row / ed, te / Comment 130: Inconsistent spelling (In a translation vs. in a translation?) and punctuation (period or not?). See comment 3. Update ISO reference. See comment 6. / [ISOcat – ISO TC 37 Data Category Registry] / ok
AT / Annex G.4.35 / First row / ed, te / Comment 131: Inconsistent spelling (In multilingual vs. in multilingual?) and punctuation (period or not). See comment 3. Update ISO reference. See comment 6. / [ISOcat – ISO TC 37 Data Category Registry] / ok
AT / Annex G.4.35 / Row Note / ed, te / Comment 132: Update ISO reference. See comment 6. / [ISOcat – ISO TC 37 Data Category Registry] / ok
AT / Annex G.4.36 / First row / ed, te / Comment 133: Inconsistent spelling (In a translation vs. in a translation?) and punctuation (period or not?). See comment 3. Update ISO reference. See comment 6. / [ISOcat – ISO TC 37 Data Category Registry] / ok
AT / Annex G.4.37 / First row / ed / Comment 134: Inconsistent punctuation (period or not?). See comment 3. / ok
AT / Annex G.4.39 / First row / ed / Comment 135: Spelling error (translaiton) and inconsistent punctuation (period or not?). See comment 3. / translation / ok
AT / Annex G.4.41 / First row / ed / Comment 136: Inconsistent punctuation (period or not?). See comment 3. / ok
CA / Annex D / All / Te / The normative detailed specification should form part of the main body of the standard / Move to the main body / Annex-D is informative. It is an example on how to represent smilText into MLIF, so, as such, this section cannot be moved into the main body.
CA / Annex D / All / Te / Annex D -- the most important part of the standard -- is very difficult to read.
The specifications are expressed in ODD format which is not appropriate for this standard. We can (sort of) read it because we have used ODD before. But who else has? Although ODD is compliant with TEI, it is an unfamiliar format for most readers and is not used as a production vocabulary by the users of this standard (developers of language resources). It also cannot be used for validation purposes. We need a standard grammar, such as DTD, XML Schema, or RelaxNG. ODD is a suitable format for authoring the text of the standard but it is not a suitable format for delivering the normative specification. There are aspects of the ODD organization which are arbitrary, such as the definition of model classes. Model classes are efficient to avoid duplication of content in the ODD authoring format but they are irrelevant to MLIF. The use of such classes requires the reader to jump all over the place in Annex G just to get a complete understanding of MLIF.