Better explanation of @ux-source-priority

["Julio Vazquez" <jvazquez@vasont.com>]

http://docs.oasis-open.org/dita/dita/v1.3/csprd01/part1-base/langRef/base/resourceid.html

 

While the allowed values are listed, there really is not explanation of what those values represent or how a processor should interpret them. While map-only, topic-only, map-takes-priority and topic-takes-priority seem intuitive, it makes you wonder why they exist because it appears as if those values have the same meaning. Topic-and-map has no intuitive meaning in this context and appears to mean that the values on both topic and map should be combined to supply the information a help system might need to retrieve the topic.

 

Julio J. Vazquez

Senior Content Analyst

Vasont Systems

A TransPerfect Company 

Skype: tpt_jvazquez

 

www.vasont.com

The information in this email is confidential and intended for those to whom it is addressed.