[topicmapmail] Fragmented XTM for web metadata, and some ontology?
Alexander Johannesen
alex@shelter.nu
Thu, 26 Jun 2003 13:20:44 +0200
Hi Murray,
( And sorry for the long post )
I'm trying to understand it all, but my feeble brain don't seem
to be able to grok it; let me know where you think I'm missing
the point. :)
I've been thinking of creating a simple XTM with PSI's based on DC 1.1,
where you have for the DC element "type" ;
<rdf:Property rdf:about="http://purl.org/dc/elements/1.1/type">
which has got
<rdfs:isDefinedBy rdf:resource="http://purl.org/dc/elements/1.1/"/>
for a given element that would satisfy most for a PSIs, as defined as such
for the DC "type" ;
<topic id="dc:type">
<subjectIdentity>
<subjectIndicatorRef
xlink:href="http://purl.org/dc/elements/1.1/type" />
</subjectIdentity>
</topic>
( id-attributes follow the DC recomended guideline for DC in XML )
I had some problems groking the associative DC metadata in Jan's document,
but that might be because I don't understand why
they should be expressed that way. Maybe my thinking is very
slow, but I'd like an ontology (called FXTM for now) ;
[baseNames simplified]
<topic id="fxtm">
<subjectIdentity>
<subjectIndicatorRef
xlink:href="http://purl.org/tm/psi/fxtm" />
</subjectIdentity>
<name>FXTM</name>
</topic>
<topic id="fxtm:page">
<instanceOf>
<topicRef xlink:href="#fxtm"/>
</instanceOf>
<subjectIdentity>
<subjectIndicatorRef
xlink:href="http://purl.org/tm/psi/fxtm#page" />
</subjectIdentity>
<name>A page</name>
</topic>
<topic id="fxtm:association">
<instanceOf>
<topicRef xlink:href="#fxtm"/>
</instanceOf>
<subjectIdentity>
<subjectIndicatorRef
xlink:href="http://purl.org/tm/psi/fxtm#association" />
</subjectIdentity>
<name>An association</name>
</topic>
<topic id="fxtm:link">
<instanceOf>
<topicRef xlink:href="#fxtm:association"/>
</instanceOf>
<subjectIdentity>
<subjectIndicatorRef
xlink:href="http://purl.org/tm/psi/fxtm#link" />
</subjectIdentity>
<name>A link</name>
</topic>
My thinking says that for a given page, you have the following XTM;
<!-- root node is the fragmented XTM's resource -->
<topic id="root">
<instanceOf>
<topicRef xlink:href="#fxtm:page"/>
</instanceOf>
<occurrence>
<instanceOf>
<topicRef xlink:href="#dc:title" />
</instanceOf>
<resourceData>Some title</resourceData>
</occurrence>
<occurrence>
<instanceOf>
<topicRef xlink:href="#dc:date:publish" />
</instanceOf>
<resourceData>[Some date]</resourceData>
</occurrence>
</topic>
Where the TMs for FXTM and DC are implicit part of the
namespaces used (and merged in according to the FXTM
spec?).
I don't know. Maybe I'm mixing things up too much, or
maybe I'm missing the incredible power of making the
occurrences topics instead with associations binding them, but I feel that
becomes more of an application
specific way than a general "here is the resources"
way;
<topic id="murray">
<instanceOf>
<topicRef xlink:href="#fxtm:person"/>
</instanceOf>
<name>Murray Altheim</name>
</topic>
<topic id="murrays-site">
<instanceOf>
<topicRef xlink:href="#fxtm:site"/>
</instanceOf>
<occurrence>
<instanceOf xlink:href="#dc:identifier" />
<resourceData>[Some URL]</resourceData>
</occurrence>
<occurrence>
<instanceOf xlink:href="#dc:title" />
<resourceData>Some title</resourceData>
</occurrence>
</topic>
<association>
<instanceOf>
<topicRef xlink:href="#fxtm:link"/>
</instanceOf>
<member>
<roleSpec>
<topicRef xlink:href="#fxtm:linked"/>
</roleSpec>
<topicRef xlink:href="#murray"/>
</member>
<member>
<roleSpec>
<topicRef xlink:href="#fxtm:linked-ref"/>
</roleSpec>
<topicRef xlink:href="#murrays-site"/>
</member>
<member>
<roleSpec>
<topicRef xlink:href="#fxtm:linker"/>
</roleSpec>
<topicRef xlink:href="#root"/>
</member>
</association>
Basically, what I want is a PSI set for the FXTM set
(both roles and types), and a set of PSIs for DC. The
latter is the easy part. Where should I turn for the former? Is there
anyone looking into a loose web
browsing ontology?
Kind regards,
Alexander
--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/