If you’re looking to store localization data and propagate it through your localization pipeline allowing tools to interoperate then you may want to use the XLIFF 2.0 object model. The XLIFF 2.0 object model implements the OASIS Standard for the XLIFF 2.0 specification as defined at http://docs.oasis-open.org/xliff/xliff-core/v2.0/xliff-core-v2.0.html.
If the XLIFF 2.0 file contains comment marked span with other types of references the validator will detect and error.
Other note references that are not supported:
1) #n1 : <mrk id="1" type="comment" ref="#n1"
2) #f=f2/u=u1/n=n1 : <mrk id="1" type="comment" ref="#f=f2/u=u1/n=n1"
This note references are valid and can be found in the XLIFF 2.0 documentation. Also validating with the Okapi-Lynx validator (http://okapi-lynx.appspot.com/validation) does not detect any errors.
The library should support different types of note references.
The only accepted note reference type for comment marked span elements is:
This is the only accepted reference: #n=n1
If the XLIFF 2.0 file contains comment marked span with other types of references the validator will detect and error.
Other note references that are not supported: 1) #n1 :
<mrk id="1" type="comment" ref="#n1"
2) #f=f2/u=u1/n=n1 :<mrk id="1" type="comment" ref="#f=f2/u=u1/n=n1"
This note references are valid and can be found in the XLIFF 2.0 documentation. Also validating with the Okapi-Lynx validator (http://okapi-lynx.appspot.com/validation) does not detect any errors.
The library should support different types of note references.