Thanks for everyone for their useful help yesterday.
I am deferring the RDFa parts, and instead will concentrate on making
page-level RDF descriptions that may be useful for data links for the
outside world. (The HTML pages are now full of ids, hproduct
microformats class, HTML rel, and dublin Core, which may be some use.)
So new plan is concentrate on simple RDF indexes on topical lines first.
That seems rather less pioneering. Here is an example.
For the medicines, I am first making abstract LSIDs for all the WHO ATC
codes in our system (no representation retrievable). Then there will be
a atc.rdf document with items like the following:
<rdf:Description rdf:about="urn:lsid:www.pbs.gov.au:atc-code:P01" >
<rdfs:label>P01</rdfs:label>
<foaf:isPrimaryTopicOf
rdf:resource="http://www.pbs.gov.au/html/consumer/search/results?atc-code=A01A#pbs-search-results"/>
<foaf:page
rdf:resource="http://www.whocc.no/atcddd/indexdatabase/index.php?query=A01A"/>
<rdfs:seeAlso
rdf:resource="http://dbpedia.openlinksw.com:8890/page/ATC_code_A01A"/>
</rdf:Description>
Now the foaf:isPrimaryTopicOf is fine.
And the rdfs:seeAlso is fine there.
But the foaf:page has me feckless and fretting. It is the closest I can
get for a semantic WHO URI. I really want to say "What that page is
about is what this page is about", ie that topic belonging to the LSID I
am using is an alias for the topic in that page.
I am tempted to use rdfs:sameAs but that seems to be used when the two
pages are identical rather than two topics being the same. (Actually,
rdfs:sameAs gets used sometimes semantically and sometimes for pages.)
What is best practice here please? I suppose I could also use
foaf:isPrimaryTopicOf too: is it ettiquette to say that some external
page is actually about a local identifier?
Cheers
Rick Jelliffe
