[topicmapmail] Classification of occurrences using keywords

[Jason Cupp]

You're right, I tried to get it working with omnigator and it wouldn't work.
But using an association does, creates a nice two-way link from a keyword to
it's source:

<topic id="Automobiles">
  <basename>
    <baseNameString>Automobiles</baseNameString>
  </baseName>
</topic>

<topic id="windscreen">
  <basename>
    <baseNameString>Windscreen</baseNameString>
  </baseName>
</topic>

<topic id="is-described-with">
  <instanceOf>
    <topicRef xlink:href="#metadata"/>
  </instanceOf>
  <basename>
    <baseNameString>is described with</baseNameString>
  </baseName>
</topic>

<association>
   <instanceOf>
     <topicRef xlink:href="#is-described-with"/>
   </instanceOf>

  <member>
    <roleSpec>
      <topicRef xlink:href="#keyword"/>
    </roleSpec>
    <topicRef xlink:href="#windscreen"/>
  </member>
  
  <member>
    <roleSpec>
      <topicRef xlink:href="#source"/>
    </roleSpec>
    <topicRef xlink:href="#Automobiles"/>
  </member>
</association>


> -----Original Message-----
> From: Murray Altheim [mailto:m.altheim@open.ac.uk]
> Sent: Monday, November 11, 2002 9:52 AM
> To: Jason Cupp
> Cc: topicmapmail@infoloom.com
> Subject: Re: [topicmapmail] Classification of occurrences 
> using keywords
> 
> 
> Jason Cupp wrote:
> 
> > You could create topics for the keywords and link them with 
> <resourceRef>s.
> > (Not sure if resourceRefs are suppose to link to topics) 
> This would create
> > the possibility for future merging and allow you to browse 
> by keyword in a
> > navigator...
> 
> 
> If you do this you probably would want to scope the keyword 
> topic's base
> names so that they aren't accidentally merged. <resourceRef> links are
> 
> used to point something considered as an actual resource, so in your 
> 
> example, the topic *element* would be considered as a 
> resource. While not
> strictly incorrect, it's pretty confusing; you could put an ID on the
> <resourceData> element and point to that instead, since it's 
> the content
> of the <resourceData> that is the resource, not the <topic> wrapper.
> 
> You also probably don't want to require custom topic map processing
> functionality. Pointing to an XML element within an XTM document and
> expecting to obtain its DOM Text node as a resource is probably not
> asking too much.
> 
> 
> Murray
> 
> ......................................................................
> Murray Altheim                  <http://kmi.open.ac.uk/people/murray/>
> Knowledge Media Institute
> The Open University, Milton Keynes, Bucks, MK7 6AA, UK
> 
>             If you're the first person in a new territory,
>             you're likely to get shot at.
>                                                      -- ma
> 
>