Defect Report on DSRL

it is recommended that the prefix used be declared in a namespace declaration that is declared as an attribute of the dsrl:from element.

optional dsrl:parent element can be used to record XML Stylesheet Langauge Transformation (XSLT) patterns

NOTE: This precedence rule allows the XSLT error recovery rule for matching paths using the last template defined to be applied when processing DSRL using XSLT.

No two dsrl:attribute-map elements within a given dsrl:element-map can have the same value for their dsrl:from element.

If an attribute has been declared to be an additional attribute by the addition of an additional="true" attribute to a dsrl:name element the attribute map shall contain a dsrl:default-value element.

users of ISO/IEC 19757-2 can create a mapping rule

Mapping of enity names can

the renaming of entities may only be possible using a preprocess stage such as that described in Annex B

references to entities declared in a DSRL map can be processed by converting them to an XML document type definition

The specification says that the text must be converted to an XML entity declaration, but gives no indication how that is to be done.

There is no definition of the namespace context of the inserted text, or whether the markup (which the specification text, but not the schema) says must be CDATA-quoted, must be unquoted when making the entity)

If I have

<dsrl:from>zzz</dsrl:from>
<dsrl:replacement-text
   xmlns:a="a"><!CDATA[<a:b/>]]></dsrl:replacement-text>

<dsrl:replacement-text
   xmlns:a="a"><a:b/></dsrl:replacement-text>

<foo>
<one xmlns:a="one">&zzz;</one>
<two xmlns:a="two">&zzz;</two>
</foo>

presumably two eleemnts with local name b are added, but are they in namespace "a", "one" or "two"? If the entity mechanism is to be implemented by converting the entity to the (namespace unaware) XML entity mechanism then presumably the namespace bindings in the dsrl file are ignored and whatever local context is in the target file is used, but this appears to be unspecified. It would be consistent with the rest of dsrl if the namespace context from the dsrl file were used, which could be achieved by forcing the namespace context into the XML entity definition so

<!ENTITY zzz '<a:b xmlns:a="a"/>'>

<!ENTITY zzz '<a:b/>'>

Applications that do not support entity-mapping conformance shall support entity-definition conformance. This means that as well as being able to support all the compulsory components of a dsrl:maps element they shall also support the optional dsrl:define-entity methodology for defining entity declarations to be used in the result document of a DSRL map.