AW: [topicmapmail] Re: topicmapmail digest, Vol 1 #1329 - 4
msgs
Kal Ahmed
kal@techquila.com
Tue, 20 Jul 2004 14:02:31 +0100
I couldn't have put it better myself :-)
If you find yourself doing this reification a lot you may want to also
consider if you might want to change the model to make the association
into a real "first-class" topic. For an example, you could take a look
at the way that events are modelled in my topic map of Pepys' diary
(http://www.techquila.com/blog/archives/cat_pepys_diary.html). I started
out thinking that events could be modelled simply as associations, but
for each event there turns out to be a more complex set of relationships
that it is involved in that makes it better to model an event as a
topic. I think that where you stop in this process of reification and
refinement is dependent upon the amount of detail you want to model - so
YMMV.
Cheers,
Kal
On Tue, 2004-07-20 at 13:21, schoenfeld.i@atlas.de wrote:
> Hi Richard,
>=20
> no, you cannot assign any metadata to an association. If you want to say =
more about a special association one way is to reify the association in a n=
ew topic and place the metadata there, i.e.
>=20
> <association id=3D"a-func-01.01.06.06.01">
> [...]
> </association> =20
>=20
> <topic>
> <subjectIdentity>
> <subjectIndicatorRef xlink:href=3D"#a-func-01.01.06.06.01"/>
> </subjectIdentity>
> <baseName>
> <baseNameString>[...]</baseNameString>
> </baseName>
> <occurrence>
> <instanceOf>[...]</instanceOf>
> <resourceData>enzyme converts X to Y within the process</resourceDa=
ta>
> </occurrence>
> </topic>
>=20
> This technique can be verified with the Omnigator in the way that the mem=
bers of an assoc are enhanced with a "more..." link providing a link to the=
reified topic with your additional description.
>=20
> --
> Ingo
>=20
>=20
> > -----Urspr=C3=83=C2=BCngliche Nachricht-----
> > Von: topicmapmail-admin@infoloom.com=20
> > [mailto:topicmapmail-admin@infoloom.com] Im Auftrag von=20
> > Richard Gregory
> > Gesendet: Dienstag, 20. Juli 2004 14:00
> > An: topicmapmail@infoloom.com; kal@techquila.com
> > Betreff: [topicmapmail] Re: topicmapmail digest, Vol 1 #1329 - 4 msgs
> >=20
> >=20
> > Hi Kal,
> >=20
> > In in your blog article, you mention that "using small=20
> > associations where possible gives you more flexibility in the=20
> > long run as it allows greater control over attaching metadata=20
> > to specific statements." I'm wondering about the best way to=20
> > add metadata to an association, as according to the XTM spec,=20
> > you cannot have names or occurrences within an association.=20
> >=20
> > For example, I have the association below which basically=20
> > says that within the scope of a particular organism (yeast)=20
> > an particualr enzyme is involved in a particular biological=20
> > process. If I wanted to add some extra information to this,=20
> > for example, to say that the enzyme converts X to Y within=20
> > the process (which is someting I may want to do in the=20
> > future), is there a way I could add metadat to add this=20
> > information, or would I have to refine the <roleSpec> of the=20
> > enzyme, so that instead of just saying it playes the role=20
> > "enzyme" in the association, is plays the role "converts X to=20
> > Y". If this was a topic, I could simply add an <occurrence>=20
> > with <resourceData> to include this information, but I've not=20
> > found any similar way of adding such information to an association.
> >=20
> > <association id=3D"a-func-01.01.06.06.01">
> > <instanceOf>
> > <topicRef xlink:href=3D"#at-has-function"/>
> > </instanceOf>
> > <scope>
> > <topicRef xlink:href=3D"#st-saccharomyces-cerevisiae"/>
> > </scope>
> > <member>
> > <roleSpec>
> > <topicRef xlink:href=3D"#tt-enzyme"/>
> > </roleSpec>
> > <topicRef xlink:href=3D"#t-lys4p"/>
> > </member>
> > <member>
> > <roleSpec>
> > <topicRef xlink:href=3D"#tt-function"/>
> > </roleSpec>
> > <topicRef xlink:href=3D"#t-funcat-01.01.06.06.01"/>
> > </member> =20
> > </association> =20
> >=20
> > Thanks,
> >=20
> > Richard.
> >=20
> > > ATTACHMENT part 3.2 message/rfc822
> > > Subject: Re: [topicmapmail] Topic map design guidelines?
> > > From: Kal Ahmed <kal@techquila.com>
> > > To: schoenfeld.i@atlas.de
> > > CC: topicmapmail@infoloom.com
> > > Date: Tue, 20 Jul 2004 09:15:14 +0100
> > >=20
> > > Hi Ingo,
> > >=20
> > > There are not a lot of style guides out there at the moment. I have=20
> > > started a Wiki to collect guidelines and proposals for topic map=20
> > > design patterns which you can read (and contribute to!) at=20
> > > http://www.topicmapcentral.com/
> > >=20
> > > I wrote a short blog article on my thoughts about binary vs. n-ary=20
> > > associations a while ago which you can find at=20
> > > http://www.techquila.com/blog/archives/000014.html
> > >=20
> > > Cheers,
> > >=20
> > > Kal
> > >=20
> > > On Tue, 2004-07-20 at 08:26, schoenfeld.i@atlas.de wrote:
> > > > Hi all,
> > > >=20
> > > > does anyone knows about a kind of style guide, guidelines or best=20
> > > > practices of how to design
> > > good topic maps? For example I am often unsure when to use n-ary=20
> > > associations or when to split them in binary assocs. Or when to use=20
> > > the <resourceData> element inside an occurrence instead of=20
> > > encapsulating information a separate topic with its own=20
> > topic type and=20
> > > then define an association. And so on...
> > > >=20
> > > > I know it depends on the purpose of a topic map but there=20
> > are still=20
> > > > moments of stumbling what
> > > to use in which situation. Having some generic rules would=20
> > be helpful.
> > > >=20
> > > > --
> > > > Ingo
> > > >=20
> > > > _______________________________________________
> > > > topicmapmail mailing list
> > > > topicmapmail@infoloom.com=20
> > > > http://www.infoloom.com/mailman/listinfo/topicmapmail
> > > --
> > > Kal Ahmed <kal@techquila.com>
> > > techquila
> > >=20
> > >=20
> >=20
> >=20
> >=20
> >=20
> > =09
> > =09
> > =09
> > ___________________________________________________________ALL
> > -NEW Yahoo! Messenger - sooooo many all-new ways to express=20
> > yourself http://uk.messenger.yahoo.com
> > _______________________________________________
> > topicmapmail mailing list
> > topicmapmail@infoloom.com=20
> > http://www.infoloom.com/mailman/listinfo/topic> mapmail
> >=20
> >=20
>=20
> _______________________________________________
> topicmapmail mailing list
> topicmapmail@infoloom.com
> http://www.infoloom.com/mailman/listinfo/topicmapmail
--=20
Kal Ahmed <kal@techquila.com>
techquila