[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xliff] ID value type
During our meeting, yesterday, we discussed making the id consistently a string rather than a NMTOKEN in a few cases and a string in others. I suggested that the id was being used as a reference. As such, we may want to keep it a NMTOKEN so that its reference can be a REFID. I also said I would check on this. In the 1.1 spec, in section 2.4, Inline Elements, the following bullet point appears. "* Use the xid attribute of the <bx/>, <ex/> and <x/> elements to relate a <trans-unit> or <bin-unit> that contains the content of that replaced code." The xid attribute is defined as follows: "Extern Reference identifier - The xid attribute is used to link an inline element to a different <trans-unit> or <bin-unit> element. For example, to link the text within a code to a corresponding translation unit." "Value description: The value of the referenced id. "Default value: Undefined. "Used in: <bpt>, <ept>, <it>, <ph>, <g>, <x/>, <bx/>, <ex/>, <sub>." However, our posted schema represents the xid attribute, in all instances, thusly: <xsd:attribute name="xid" type="xsd:string" use="optional" /> Changing the schema to be consistent, either using NMTOKEN and REFID or XSD:STRING for both would work.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]