OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

topicmaps-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: [xtm-wg] referents, subjectRef and subjectDescriptorRef


Dear all,

[Murray]
> Following a lengthy teleconference we figured out how to solve in syntax
> the decision in Dallas regarding 'isSubject' and 'describesSubject'.
There's
> an ongoing gummy bear competition to come up with better names for the
> two element types, <subjectRef> and <subjectDescriptorRef>, the idea being
> the names must be accurate and short.

I like the idea to abolish "referent" attributes and express referent-ness
via element names.

However I suggest even further simplification:
Currently (DTD v 1.14) <subjectRef> and <resourceRef>
seams to be duplicating each other.
they both
"provide a URI reference asserting a link to a resource "
The only difference between two elements
is that one of them is used inside <subject> element,
and means subject identifier,
and the other is used within <occurrence> element.
and means occurrence resource reference.

Note that when occurrence resource is reified,
resource itself (addressed by <resourceRef>) becomes its subject identifier
(what was expressed in earlier DTD as <subjectRef referent="isSubject">)

My suggestion is to use <resourceRef> in both places to mean "isSubject"
(This is what it turns into in any case when occurrence is reified)
In other words, use <resourceRef> within <subject> to assert
a link to a resource that is the subject of the topic.
And use <resourceRef> within <occurrence> to assert
a link to a resource that is an occurrence of the topic.

Then
1)
<resourceRef> always means referent="isSubject"
2)
<subjectRef> can stand for referent="describesSubject"
(this is to replace a longer-named <subjectDescriptorRef> )
3)
<topicRef > references an existing topic and because of topic duality
("topos" - means both a link and the described subject)
does not need "referent" semantics.
If someone wants to emphasis "referent-ness" of the link
one should use either resourceRef or subjectRef.



-------------------------- eGroups Sponsor -------------------------~-~>
eGroups eLerts
It's Easy. It's Fun. Best of All, it's Free!
http://click.egroups.com/1/9698/1/_/337252/_/974451913/
---------------------------------------------------------------------_->

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