Transforms xlink:role to data-xlink-role. Note that this should only
be used in scenarios where the corresponding HTML element in the data view
does not provide an attribute to handle the xlink:role value.
Example where to use this mapper: For the <img> element, we cannot
directly map xlink:role to any other attribute. As for images xlink:show
is fixed to embed according to CoreMedia RichText DTD 1.0, this attribute
is pretty meaningless. Thus, in custom implementations, xlink:role may
be used to store, for example, ARIA information. If this is true, you should
replace the mapping to the corresponding attribute.
Example where not to use this mapper: For the <a> element, we decided
to map the xlink:role along with the xlink:show attribute to some
target. Thus, for anchor elements, there is no need for using this mapper, as
the information is stored elsewhere.
Transforms
xlink:role
todata-xlink-role
. Note that this should only be used in scenarios where the corresponding HTML element in the data view does not provide an attribute to handle thexlink:role
value.Example where to use this mapper: For the
<img>
element, we cannot directly mapxlink:role
to any other attribute. As for imagesxlink:show
is fixed toembed
according to CoreMedia RichText DTD 1.0, this attribute is pretty meaningless. Thus, in custom implementations,xlink:role
may be used to store, for example, ARIA information. If this is true, you should replace the mapping to the corresponding attribute.Example where not to use this mapper: For the
<a>
element, we decided to map thexlink:role
along with thexlink:show
attribute to sometarget
. Thus, for anchor elements, there is no need for using this mapper, as the information is stored elsewhere.