[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: [xtm-wg] v1.14 occurrence and subject collision
In the current DTD v1.14 topic's subject can be identified in to places: 1) <snip> <!ELEMENT occurrence ( scope?, baseName*, ( subjectRef | resourceRef | resourceData )* ) > When, in an <occurrence>, you use <topicRef> instead of <resourceRef>, you're saying that whatever you're referring to shall be treated not only as an occurrence of the containing <topic>'s corresponding topic node, as the markup explicitly shows, but also as a subject descriptor of that same topic node. In the graph, the node's characteristics will be the union of the characteristics of all of the <topic>s that regard the same resource as their common subject descriptor. When one <topic> refers to another <topic> as an occurrence via a <topicRef>, the characteristics of both topics will be merged into a single topic node. </snip> and in 2) <snip> <!ELEMENT subject ( subjectRef?, ( topicRef | subjectDescriptorRef )* ) > The <subject> element provides a container for a link to a resource providing the subject of its parent <topic> element. It can contain one and only one <subjectRef> element, followed by zero or more <topicRef> or <subjectDescriptorRef> elements. </snip> I thought that we decided for clarity use the 2) solution. In any case using both of them in parallel does not make much sense. If everybody agree I would change <occurrence> structure to: <!ELEMENT occurrence ( scope?, baseName*, (resourceRef | resourceData )* ) > Thanks, Nikita. -------------------------- eGroups Sponsor -------------------------~-~> eLerts It's Easy. It's Fun. Best of All, it's Free! http://click.egroups.com/1/9699/1/_/337252/_/974437197/ ---------------------------------------------------------------------_-> To Post a message, send it to: xtm-wg@eGroups.com To Unsubscribe, send a blank message to: xtm-wg-unsubscribe@eGroups.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC