Re: topicmapmail digest, Vol 1 #1329 - 4 msgs

Hi Kal,

In in your blog article, you mention that "using small associations where 
possible gives you more
flexibility in the long run as it allows greater control over attaching 
metadata to specific
statements." I'm wondering about the best way to add metadata to an 
association, as according to
the XTM spec, you cannot have names or occurrences within an association. 

For example, I have the association below which basically says that within the 
scope of a
particular organism (yeast) an particualr enzyme is involved in a particular 
biological process.
If I wanted to add some extra information to this, for example, to say that the 
enzyme converts X
to Y within the process (which is someting I may want to do in the future), is 
there a way I could
add metadat to add this information, or would I have to refine the <roleSpec> 
of the enzyme, so
that instead of just saying it playes the role "enzyme" in the association, is 
plays the role
"converts X to Y". If this was a topic, I could simply add an <occurrence> with 
<resourceData> to
include this information, but I've not found any similar way of adding such 
information to an
association.

<association id="a-func-01.01.06.06.01">
        <instanceOf>
            <topicRef xlink:href="#at-has-function"/>
        </instanceOf>
        <scope>
            <topicRef xlink:href="#st-saccharomyces-cerevisiae"/>
        </scope>
        <member>
            <roleSpec>
                <topicRef xlink:href="#tt-enzyme"/>
            </roleSpec>
            <topicRef xlink:href="#t-lys4p"/>
        </member>
        <member>
            <roleSpec>
                <topicRef xlink:href="#tt-function"/>
            </roleSpec>
            <topicRef xlink:href="#t-funcat-01.01.06.06.01"/>
        </member>        
    </association>     

Thanks,

Richard.

> ATTACHMENT part 3.2 message/rfc822 
> Subject: Re: [topicmapmail] Topic map design guidelines?
> From: Kal Ahmed <kal-5x+ggncFKvmB+jHODAdFcQ@xxxxxxxxxxxxxxxx>
> To: schoenfeld.i-cEVuhUXcnyw@xxxxxxxxxxxxxxxx
> CC: topicmapmail-Zo64W7twoUFWk0Htik3J/w@xxxxxxxxxxxxxxxx
> Date: Tue, 20 Jul 2004 09:15:14 +0100
> 
> Hi Ingo,
> 
> There are not a lot of style guides out there at the moment. I have
> started a Wiki to collect guidelines and proposals for topic map design
> patterns which you can read (and contribute to!) at
> http://www.topicmapcentral.com/
> 
> I wrote a short blog article on my thoughts about binary vs. n-ary
> associations a while ago which you can find at
> http://www.techquila.com/blog/archives/000014.html
> 
> Cheers,
> 
> Kal
> 
> On Tue, 2004-07-20 at 08:26, schoenfeld.i-cEVuhUXcnyw@xxxxxxxxxxxxxxxx wrote:
> > Hi all,
> > 
> > does anyone knows about a kind of style guide, guidelines or best practices 
> > of how to design
> good topic maps? For example I am often unsure when to use n-ary associations 
> or when to split
> them in binary assocs. Or when to use the <resourceData> element inside an 
> occurrence instead of
> encapsulating information a separate topic with its own topic type and then 
> define an
> association. And so on...
> > 
> > I know it depends on the purpose of a topic map but there are still moments 
> > of stumbling what
> to use in which situation. Having some generic rules would be helpful.
> > 
> > --
> >   Ingo
> > 
> > _______________________________________________
> > topicmapmail mailing list
> > topicmapmail-Zo64W7twoUFWk0Htik3J/w@xxxxxxxxxxxxxxxx
> > http://www.infoloom.com/mailman/listinfo/topicmapmail
> -- 
> Kal Ahmed <kal-5x+ggncFKvmB+jHODAdFcQ@xxxxxxxxxxxxxxxx>
> techquila
> 
> 




        
        
                
___________________________________________________________ALL-NEW Yahoo! 
Messenger - sooooo many all-new ways to express yourself 
http://uk.messenger.yahoo.com