skip to main page content CETIS: Click here to return to the homepage
the centre for educational technology interoperability standards

skip over the long navigation bar
Home
News
Features
Events
Forums
Reference
Briefings
Press centre

Inside Cetis
what is Cetis?
Contact us
Cetis staff
Jobs at CETIS


 




Syndication
XML: Click here to get the news as an RSS XML file XML: Click here to get the news as an Atom XML file iCAL: Click here to get the events as an iCalendar file

Background
what are learning technology standards?
who's involved?
who's doing what?

CETIS Groups
what are cetis groups?
what difference can they make?
Assessment SIG
Educational Content SIG
Enterprise SIG
Metadata SIG
Life Long Learning Group
Portfolio SIG
Accessibility Group
Pedagogy Forum
Developer's forum

Subjects
Accessibility (310)
Assessment (74)
Content (283)
Metadata (195)
Pedagogy (34)
Profile (138)
Tools (197)
For Developers (569)
For Educators (344)
For Managers (339)
For Members (584)
SCORM (118)
AICC (18)
CEN (34)
DCMI (36)
EML (47)
IEEE (79)
IMS (302)
ISO (21)
OAI (24)
OKI (20)
PROMETEUS (12)
W3C (37)

Is wolf a man?

Posted on April 22 2005 by Lars Marius Garshol in reponse to From RDF to Topic Maps and back again

(Firstly: thank you for a very good summary of the RDFTM survey!)

I'd like to comment on the issue of expressing "man is a wolf" in topic maps. It is actually quite easy in topic maps: metaphorical-is-a(man : thing, wolf : metaphor).
The role types here tell you that "man" is the thing that is metaphorically a "wolf", and so you'll know that this does mean "man is a wolf" and not "wolf is a man", and you could easily make Omnigator display this as "man is a wolf" and "wolf has been used a metaphor for man".

This issue also pops up in the "Wilbert likes apple" example above. Topic maps need not only the association type "likes", but also the role types "liker" and "liked".

Replies to this post:

copyright cetis.ac.uk
Creative Commons License This work is licensed under a Creative Commons License.

syndication |publisher's statement |contact us |privacy policy

 go to start of page content