This is the specification of Office Open Math Markup Language, a specialized XML vocabulary for the describing the layout of mathematical equations. This solves the same problem as MathML, a long-established W3C standard and an ongoing activity in the W3C. Since the equation editing feature of Word was entirely rewritten in Word 2007, there doesn’t not seem to be the argument that an additional equation language must be introduced for the sake of legacy

It is recommended that this section be removed from OOXML and that the proposers of OOXML work within the W3C’s MathML activity, where MathML 3.0 is currently being drafted, to produce a single standard for equations that can be used later referenced by a future version of OOXML. At the very least we request that MathML be explicitly allowed as an alternative to Open Math Markup everywhere where in the schema where OOXML currently allows OMML. This way vendors and users can choose which they want to use.

- Part 4, Section 7.1

te

Proposed Disposition of DIS 29500 Comment CL-0212 (Modified: 2008-01-11) Although both Office Open XML Math and MathML provide a mechanism for storing equations/expressions as XML markup, Office Open XML was created specifically to afford for the storage of this information within the context of Office documents (for example, by providing for the use of typical document features such as revision tracking and comments within the equation/expression). As such, it is an integral part of the specification. However, we recognize the value of allowing MathML to be used for this information; accordingly, we will extend the specification to allow MathML to be utilized as a storage format, via a mechanism which allows any XML format to be used within a WordprocessingML, SpreadsheetML, or PresentationML document. This will allow use of MathML, as well as any other commonly used XML syntax (other examples are included below). The following examples illustrate how an equation is stored using both Office Open XML Math and MathML as the storage format. Given this content: The following formula computes the radius of a sphere from its volume: = 3 4 13 Office Open XML Math Using Office Open XML Math, this would be stored as follows: <w:body> <w:p> <w:r> <w:t xml:space="preserve">The following formula computes the radius of a sphere from its volume: </w:t> </w:r> <m:oMath> <w:r> <w:t>r=</w:t> </w:r> <m:sSup> <m:e> <m:d> <m:e> <w:r> <w:t>V</w:t> </w:r> <m:f> <m:num> <m:r> <m:t>3</m:t> </m:r> </m:num> <m:den> <m:r> <m:t>4</m:t> </m:r> </m:den> </m:f> </m:e> </m:d> </m:e> <m:sup> <m:f> <m:num> <m:r> <m:t>1</m:t> </m:r> </m:num> <m:den> <m:r> <m:t>3</m:t> </m:r> </m:den> </m:f> </m:sup> </m:sSup> </m:oMath> </w:p> </w:body> MathML Using MathML, this would be stored as follows. Within the Main Document Part, the contentPart element would reference the MathML in a separate part: <w:body> <w:p> <w:r> <w:t xml:space="preserve">The following formula computes the radius of a sphere from its volume: </w:t> </w:r> <w:r> <w:contentPart r:id="rId7" /> </w:r> </w:p> </w:body> That part (the Content Part targeted by the relationship with ID rId7 ) would then store the MathML: <mml:math xmlns:mml="http://www.w3.org/1998/Math/MathML"> <mml:mi>r</mml:mi> <mml:mo>=</mml:mo> <mml:msup> <mml:mrow> <mml:mfenced separators="|"> <mml:mrow> <mml:mi>V</mml:mi> <mml:mfrac> <mml:mrow> <mml:mn>3</mml:mn> </mml:mrow> <mml:mrow> <mml:mn>4</mml:mn> <mml:mi></mml:mi> </mml:mrow> </mml:mfrac> </mml:mrow> </mml:mfenced> </mml:mrow> <mml:mrow> <mml:mfrac> <mml:mrow> <mml:mn>1</mml:mn> </mml:mrow> <mml:mrow> <mml:mn>3</mml:mn> </mml:mrow> </mml:mfrac> </mml:mrow> </mml:msup> </mml:math> Within the specification, the following changes will be made: Part 1, §11.3.2, page 31, line 15: Part 1, §11.3.4, page 25, line 12: Part 1, §11.3.6, page 38, line 24: Part 1, §11.3.7, page 41, line 13: Part 1, §11.3.9, page 46, line 18: Part 1, §11.3.10, page 48, line 3: Part 1, §12.3.8, page 73, line 28: Part 1, §13.3.3, page 105, line 29: Part 1, §13.3.4, page 107, line 10: Part 1, §13.3.5, page 108, line 29: Part 1, §13.3.8, page 113, line 16: Part 1, §13.3.9, page 115, line 5: Part 1, §13.3.10, page 116, line 22: Content Part (§15.2.3a) Part 1, §15.2, after the existing §15.2.3: 15.2.3a Content Part Content Type: Any supported XML content. [Note: Some example content types are: image/svg+xml http://www.w3.org/TR/SVG11/ application/smil http://www.w3.org/TR/REC-smil/ text/xml http://www.w3.org/TR/MathML2/ end note] If no explicit MIME type exists for a specific XML format, text/xml shall be used. Consumers who read a value of text/xml should determine the contents by the root namespace of the contents of the part. Root Namespace: Various, as defined by the content type used. [Example: MathML has a root namespace of http://www.w3.org/1998/Math/MathML. end example] Source Relationship: http://schemas.openxmlformats.org/officeDocument/2006/relationships/customXml An instance of this part type can contain XML markup of a format not defined by this Office Open XML Standard. A package is permitted to contain zero or more Content parts, and each such part shall be the target of an explicit relationship from a Comments (§11.3.2), Endnotes (§11.3.4), Footer (§11.3.6), Footnotes (§11.3.7), Header (§11.3.9), or Main Document (§11.3.10) part in a WordprocessingML package; a Drawings (§12.3.8) part in a SpreadsheetML package; or a Handout Master (§13.3.3), Notes Slide (§13.3.5), Notes Master (§13.3.4), Slide (§13.3.8), Slide Layout (§13.3.9), or a Slide Master (§13.3.10) part in a PresentationML package. [Example: The following Main Document part-relationship item contains a relationship to a Content part containing SVG markup, which is stored in the ZIP item svg1.xml: <Relationships xmlns="…"> <Relationship Id="rId1" Type="http://…/customXml" Target="../customXML/svg1.xml"/> </Relationships> end example] A Content part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal ). A Content part shall not have implicit or explicit relationships to any other part defined by this Standard. Part 4, §2.3.2.23, page 199, table Child Elements: Part 4, §7.1.2.87, page 5,057, table Child Elements: contentPart (Content Part) §2.3.3.1a Part 4, §2.3.3, after the existing §2.3.3.1: 2.3.3.1a contentPart (Content Part) This element specifies a reference to XML content in a format not defined by this Office Open XML Standard. [Note: This part allows the native use of other commonly used interchange formats, such as: MathML (http://www.w3.org/TR/MathML2/) SMIL (http://www.w3.org/TR/REC-smil/) SVG (http://www.w3.org/TR/SVG11/) end note] The relationship type of the explicit relationship specified by this element shall be http://schemas.openxmlformats.org/officeDocument/2006/customXml and have a TargetMode attribute value of Internal . If an application cannot process content of the content type specified by the targeted part, then it should continue to process the file. If possible, it should also provide some indication that unknown content was not imported. [Example: Consider a WordprocessingML document which includes the following MathML markup in a part named math1.xml: <mml:math xmlns:mml="http://www.w3.org/1998/Math/MathML"> <mml:mi>r</mml:mi> <mml:mo>=</mml:mo> <mml:msup> <mml:mrow> <mml:mfenced separators="|"> <mml:mrow> <mml:mi>V</mml:mi> <mml:mfrac> <mml:mrow> <mml:mn>3</mml:mn> </mml:mrow> <mml:mrow> <mml:mn>4</mml:mn> <mml:mi></mml:mi> </mml:mrow> </mml:mfrac> </mml:mrow> </mml:mfenced> </mml:mrow> <mml:mrow> <mml:mfrac> <mml:mrow> <mml:mn>1</mml:mn> </mml:mrow> <mml:mrow> <mml:mn>3</mml:mn> </mml:mrow> </mml:mfrac> </mml:mrow> </mml:msup> </mml:math> The Main Document Part would reference this content as follows: <w:body> … <w:p> <w:r> <w:contentPart r:id="rId8" /> </w:r> </w:p> … </w:body> The contentPart element specifies that the content targeted by the relationship with an ID of rId8 is part of the WordprocessingML document. Examining the contents of the corresponding relationship part item, we can see the targets for that relationship: <Relationships … > … <Relationship Id="rId8" TargetMode="Internal" Type="http://schemas.openxmlformats.org/officeDocument/2006/relationships/customXml" Target="math1.xml" /> … </Relationships> The corresponding relationship part item shows that the file to be imported is located next to the main document and is named math1.xml . end example] Parent Elements r (§7.1.2.87); r (§2.3.2.23) Attributes Description id (Relationship to Part) Namespace: …/officeDocument/2006/relationships Specifies the relationship ID to a specified part. The specified relationship shall match the type required by the parent element: http://schemas.openxmlformats.org/officeDocument/2006/customXm l for the contentPart element http://schemas.openxmlformats.org/officeDocument/2006/relationshi ps/footer for the footerReference element http://schemas.openxmlformats.org/officeDocument/2006/relationshi ps/header for the headerReference element http://schemas.openxmlformats.org/officeDocument/2006/relationshi ps/font for the embedBold, embedBoldItalic, embedItalic, or embedRegular elements http://schemas.openxmlformats.org/officeDocument/2006/relationshi ps/printerSettings for the printerSettings element Attributes Description [Example: Consider an XML element which has the following id attribute: <… r:id="rId1" /> The markup specifies the associated relationship part with relationship ID rId1 contains the corresponding relationship information for the parent XML element. end example] The possible values for this attribute are defined by the ST_RelationshipId simple type (§7.8.2.1). The following XML Schema fragment defines the contents of this element: <complexType name="CT_Rel"> <attribute ref="r:id" use="required"/> </complexType> Part 4, §5.6.2.1, page 3,950, table Child Elements: Part 4, §5.6.2.23, page 3,971, table Child Elements: Part 4, §5.6.2.32, page 3,978, table Child Elements: contentPart (Content Part) §5.6.2.11a Part 4, §5.6.2, after the existing §5.6.2.11: 5.6.2.11a contentPart (Content Part) This element specifies a reference to XML content in a format not defined by this Office Open XML Standard. [Note: This part allows the native use of other commonly used interchange formats, such as: MathML (http://www.w3.org/TR/MathML2/) SMIL (http://www.w3.org/TR/REC-smil/) SVG (http://www.w3.org/TR/SVG11/) end note] The relationship type of the explicit relationship specified by this element shall be http://schemas.openxmlformats.org/officeDocument/2006/customXml and have a TargetMode attribute value of Internal . If an application cannot process content of the content type specified by the targeted part, then it should continue to process the file. If possible, it should also provide some indication that unknown content was not imported. [Example: Consider a SpreadsheetML document which includes the following SVG markup in a part named svg1.xml: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd"> <!–======================================================================–> <!–= Copyright 2000 World Wide Web Consortium, (Massachusetts =–> <!–= Institute of Technology, Institut National de Recherche en =–> <!–= Informatique et en Automatique, Keio University). All Rights =–> <!–= Reserved. See http://www.w3.org/Consortium/Legal/. =–> <!–======================================================================–> <!– =====================================================================–> <!– –> <!– color-datatypes-BE-01.svg –> <!– renamed for 1.1 suite to color-prop-02-f.svg –> <!– –> <!– Author : Chris Lilley, 12-Aug-2000 –> <!– 1.1 revision by Rick Graham –> <!– Revised for SVGT/B: Benoit Bezaire Jul/02/2002 –> <!– More revision CL –> <!–======================================================================–> <svg version="1.1" baseProfile="full" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" id="svg-root" width="100%" height="100%" viewBox="0 0 480 360"> <title id="test-title">color-prop-02-f.svg</title> <desc id="test-desc">Test that viewer has the basic capability to render X11colors, using any of the equivalent forms.</desc> <!–================================================================–> <!–Content of Test Case follows… ===============–> <!–================================================================–> <g id="test-body-content"> <!– groups of five colors –> <g> <circle cx="75" cy="40" r="20" fill="crimson"/> <circle cx="115" cy="40" r="20" fill="#DC143C"/> <circle cx="75" cy="80" r="20" fill="rgb(220,20,60)"/> <circle cx="115" cy="80" r="20" fill="rgb(86.274509803921568627450980392157%,7.8431372549019607843137254901961%,23.529411764705882352941176470588%)"/> </g> <g> <circle cx="200" cy="40" r="20" fill="palegreen"/> <circle cx="240" cy="40" r="20" fill="#98FB98"/> <circle cx="200" cy="80" r="20" fill="rgb(152, 251, 152)"/> <circle cx="240" cy="80" r="20" fill="rgb(59.60784313725490196078431372549%,98.431372549019607843137254901961%,59.60784313725490196078431372549%)"/> </g> <g> <circle cx="325" cy="40" r="20" fill="royalblue"/> <circle cx="365" cy="40" r="20" fill="#4169E1"/> <circle cx="325" cy="80" r="20" fill="rgb(65, 105, 225)"/> <circle cx="365" cy="80" r="20" fill="rgb(25.490196078431372549019607843137%,41.176470588235294117647058823529%,88.235294117647058823529411764706%)"/> </g> <g> <circle cx="75" cy="135" r="20" fill="firebrick"/> <circle cx="115" cy="135" r="20" fill="#B22222"/> <circle cx="75" cy="175" r="20" fill="rgb(178,34,34)"/> <circle cx="115" cy="175" r="20" fill="rgb(69.803921568627450980392156862745%,13.333333333333333333333333333333%,13.333333333333333333333333333333%)"/> </g> <g> <circle cx="200" cy="135" r="20" fill="seagreen"/> <circle cx="240" cy="135" r="20" fill="#2E8B57"/> <circle cx="200" cy="175" r="20" fill="rgb(46, 139, 87)"/> <circle cx="240" cy="175" r="20" fill="rgb(18.039215686274509803921568627451%,54.509803921568627450980392156863%,34.117647058823529411764705882353%)"/> </g> <g> <circle cx="325" cy="135" r="20" fill="mediumblue"/> <circle cx="365" cy="135" r="20" fill="#0000CD"/> <circle cx="325" cy="175" r="20" fill="rgb(0, 0, 205)"/> <circle cx="365" cy="175" r="20" fill="rgb(0%,0%,80.39215686274509803921568627451%)"/> </g> <g> <circle cx="75" cy="230" r="20" fill="indianred"/> <circle cx="115" cy="230" r="20" fill="#CD5C5C"/> <circle cx="75" cy="270" r="20" fill="rgb(205, 92, 92)"/> <circle cx="115" cy="270" r="20" fill="rgb(80.39215686274509803921568627451%,36.078431372549019607843137254902%,36.078431372549019607843137254902%)"/> </g> <g> <circle cx="200" cy="230" r="20" fill="lawngreen"/> <circle cx="240" cy="230" r="20" fill="#7CFC00"/> <circle cx="200" cy="270" r="20" fill="rgb(124, 252, 0)"/> <circle cx="240" cy="270" r="20" fill="rgb(48.627450980392156862745098039216%,98.823529411764705882352941176471%,0%)"/> </g> <g> <circle cx="325" cy="230" r="20" fill="mediumturquoise"/> <circle cx="365" cy="230" r="20" fill="#48D1CC"/> <circle cx="325" cy="270" r="20" fill="rgb(72, 209, 204)"/> <circle cx="365" cy="270" r="20" fill="rgb(28.235294117647058823529411764706%,81.960784313725490196078431372549%,80%)"/> </g> </g> <text id="revision" x="10" y="340" font-size="40" stroke="none" fill="black">$Revision: 1.6 $</text> <rect id="test-frame" x="1" y="1" width="478" height="358" fill="none" stroke="#000000"/> </svg> The SpreadsheetML Drawing part would reference this content as follows: <wsDr> <twoCellAnchor> <from> <col>3</col> <colOff>152400</colOff> <row>5</row> <rowOff>123825</rowOff> </from> <to> <col>8</col> <colOff>266700</colOff> <row>22</row> <rowOff>38100</rowOff> </to> </twoCellAnchor> <contentPart r:id="svg1"/> </wsDr> The contentPart element specifies that the SVG markup targeted by the relationship with an ID of svg1 is part of the SpreadsheetML document. Examining the contents of the corresponding relationship part item, we can see the targets for that relationship: <Relationships … > … <Relationship Id="svg1" TargetMode="Internal" Type="http://schemas.openxmlformats.org/officeDocument/2006/relationships/customXml" Target="svg1.xml" /> … </Relationships> The corresponding relationship part item shows that the file to be imported is named svg1.xml . end example] Parent Elements absoluteAnchor (§5.6.2.1); grpSp (§5.6.2.16); oneCellAnchor (§5.6.2.23); twoCellAnchor (§5.6.2.32) Attributes Description id (Relationship to Part) Namespace: …/officeDocument/2006/relationships Specifies the relationship ID to a content part. [Example: Consider an XML element which has the following id attribute: <… r:id="rId1" /> The markup specifies the associated relationship part with relationship ID rId1 contains the corresponding relationship information for the parent XML element. end example] The possible values for this attribute are defined by the ST_RelationshipId simple type (§7.8.2.1). Part 4, §4.4.1.19, page 3,029, table Child Elements: Part 4, §4.4.1.42, page 3,052, table Child Elements: contentPart (Content Part) §4.4.1.13a Part 4, §4.4.1, to a new §4.4.1.13: 4.4.1.13a contentPart (Content Part) This element specifies a reference to XML content in a format not defined by this Office Open XML Standard. [Note: This part allows the native use of other commonly used interchange formats, such as: MathML (http://www.w3.org/TR/MathML2/) SMIL (http://www.w3.org/TR/REC-smil/) SVG (http://www.w3.org/TR/SVG11/) end note] The relationship type of the explicit relationship specified by this element shall be http://schemas.openxmlformats.org/officeDocument/2006/customXml and have a TargetMode attribute value of Internal . If an application cannot process content of the content type specified by the targeted part, then it should continue to process the file. If possible, it should also provide some indication that unknown content was not imported. [Note: For better interoperability, only standard XML formats should be used. end note] [Example: Consider a PresentationML document which includes the following SMIL markup in a part named smil1.xml: <!– Copyright: Copyright 1998-2001 W3C (MIT, INRIA, Keio), All Rights Reserved. See http://www.w3.org/Consortium/Legal/. Author: Aaron Cohen (Intel) Version: February 7, 2001 Module: Animation Module Feature: animation File Name: animation-add-BE-05.smil Media Components: none Expected Behavior: Nine red rectangles numbered 1 to 9 shrink to squares over 2s as follows: at 2s #1 shrinks. at 5s #2 shrinks, 1s after #1 completes at 8s #3 shrinks. #4 shrinks when it is clicked on. #5 shrinks 1s after it is clicked on. #6 shrinks 2s after it is clicked on. #7 shrinks when the accesskey ‘1′ is pressed. #8 should be shrunk from 0s since it’s wallclock time is in the past. #9 will not shrink unless a DOM call causes it to begin. –> <smil xmlns="http://www.w3.org/2001/SMIL20/Language"> <head> <layout> <root-layout width="640" height="480" backgroundColor="white"/> <region id="whole" width="640" height="480" z-index="0"/> <region id="rect1" top="50px" left="90px" height="50px" width="30px" backgroundColor="red" z-index="1"/> <region id="rect2" top="50px" left="234px" height="50px" width="30px" backgroundColor="red" z-index="1"/> <region id="rect4" top="160px" left="90px" height="50px" width="30px" backgroundColor="transparent" z-index="1"/> <region id="rect5" top="160px" left="234px" height="50px" width="30px" backgroundColor="transparent" z-index="1"/> <region id="rect6" top="160px" left="380px" height="50px" width="30px" backgroundColor="transparent" z-index="1"/> <region id="rect7" top="270px" left="90px" height="50px" width="30px" backgroundColor="red" z-index="1"/> <region id="rect8" top="270px" left="234px" height="50px" width="30px" backgroundColor="red" z-index="1"/> <region id="rect9" top="270px" left="380px" height="50px" width="30px" backgroundColor="red" z-index="1"/> </layout> </head> <!– Copyright 1998-2001 W3C (MIT, INRIA, Keio), All Rights Reserved. See http://www.w3.org/Consortium/Legal/. –> <body> <par dur="indefinite"> <img src="../images/animation-timing-BE-05.jpg" region="whole"/> <animate id="anim1" targetElement="rect1" attributeName="height" from="50" to="25" begin="2s" dur="2s" fill="freeze"/> <animate id="anim2" targetElement="rect2" attributeName="height" from="50" to="25" begin="anim1.end+1s" dur="2s" fill="freeze"/> <brush id="brush4" color="red" region="rect4" height="50px" width="30px"/> <animate id="anim4" targetElement="brush4" attributeName="height" from="50" to="25" begin="brush4.activateEvent" dur="2s" fill="freeze"/> <brush id="brush5" color="red" region="rect5" height="50px" width="30px"/> <animate id="anim5" targetElement="brush5" attributeName="height" from="50" to="25" begin="brush5.activateEvent+1s" dur="2s" fill="freeze"/> <brush id="brush6" color="red" region="rect6" height="50px" width="30px"/> <animate id="anim6a" targetElement="brush6" attributeName="width" repeatCount="3" from="30" to="30" begin="brush6.activateEvent" dur="1s" fill="freeze"/> <animate id="anim6b" targetElement="brush6" attributeName="height" from="50" to="25" begin="anim6a.repeat(2)" dur="2s" fill="freeze"/> <animate id="anim7" targetElement="rect7" attributeName="height" from="50" to="25" begin="accesskey(1)" dur="2s" fill="freeze"/> <animate id="anim8" targetElement="rect8" attributeName="height" from="50" to="25" begin="wallclock(2000-01-01T00:00:00Z)" dur="2s" fill="freeze"/> <animate id="anim9" targetElement="rect9" attributeName="width" from="30" to="30" begin="indefinite" dur="1s" fill="freeze"/> </par> </body> </smil> A Slide Part would reference this content as follows: <p:spTree> … <p:contentPart r:id="smil01"/> … </p:spTree> The contentPart element specifies that the content targeted by the relationship with an ID of smil01 is part of the PresentationML document. Examining the contents of the corresponding relationship part item, we can see the targets for that relationship: <Relationships … > … <Relationship Id="smil01" TargetMode="Internal" Type="http://schemas.openxmlformats.org/officeDocument/2006/relationships/customXml" Target="smil1.xml" /> … </Relationships> The corresponding relationship part item shows that the SMIL content is located next to the slide and is named smil1.xml . end example] Parent Elements grpSp (§4.4.1.19); spTree (§4.4.1.42) Attributes Description id (Relationship to Part) Namespace: …/officeDocument/2006/relations Specifies the relationship ID to a content part. [Example: Consider an XML element which has the following id attribute: <… r:id="rId1" /> Attributes Description hips The markup specifies the associated relationship part with relationship ID rId1 contains the corresponding relationship information for the parent XML element. end example] The possible values for this attribute are defined by the ST_RelationshipId simple type (§7.8.2.1). To the Normative References: Andersson, O., Armstrong, P., Axelsson, H., Berjon, R., Bézaire, B., Bowler, J., et al. (2003, January 14). Scalable Vector Graphics (SVG) 1.1 Specification. Retrieved from W3C - World Wide Web Consortium: http://www.w3.org/TR/SVG/ Ausbrooks, R., Buswell, S., Carlisle, D., Dalmas, S., Devitt, S., Diaz, A., et al. (2003, October 21). Mathematical Markup Language (MathML) Version 2.0 (Second Edition). Retrieved from W3C - World Wide Web Consortium: http://www.w3.org/TR/MathML2/ Bulterman, D., Grassel, G., Jansen, J., Koivisto, A., Layaïda, N., Michel, T., et al. (2005, December 13). Synchronized Multimedia Integration Language (SMIL 2.1). Retrieved from W3C: http://www.w3.org/TR/SMIL/ To wml.xsd: contentPart will be added to the content model of EG_RunInnerContent . It will have a complex type of CT_Rel . To dml-worksheetDrawing.xsd: contentPart will be added to the content model of EG_ObjectChoices . It will have a new complex type, defined as follows: <complexType name="CT_Rel"> <attribute ref="r:id" use="required"/> </complexType> To pml-slide.xsd: contentPart will be added to the choice group within the content model of CT_GroupShape . It will have a new complex type, defined as follows: <complexType name="CT_Rel"> <attribute ref="r:id" use="required"/> </complexType> Similar Comments: CA-0077 , CL-0026 , CO-0229 , CO-0230 , DE-0087 , FI-0014 , FR-0376 , GB-0494 , GR-0013 , GR-0092 , IN-0009 , IN-0067 , IN-0078 , PT-0089 , US-0160 , UY-0007 , ZA-0017