Quoting Jakob Voss <jakob.voss_at_GBV.DE>:
>> The sticky point I see is your idea of "URL of catalog": what does
>> this mean? What if you have multiple "catalogs" that serve different
>> purposes? Which is more important the URL of the catalog? Or the
>> library homepage (foaf:homepage)?
>
> If most existing library registries have an "URL-of-OPAC" field and if
> I assume that the people that collected all the data have something
> common in mind, I can simply map this to RDF. If someone complains that
> a concept like "URL of catalog" is too fuzzy than welcome him to
> reality or let him stay alone in unicorn-land. The fuzzyness comes from
> how our reality is (or how we structure our reality). The naive view of
> some Semantic Web enthusiasts about clearly defined concepts makes me
> laugh.
Presumably this isn't an either/or situation. Many libraries have
multiple catalogs, and many have searchable resources that aren't in a
catalog, per se. It seems that any library would want to choose its
preferred starting point or points for users, which may be the
library home page, may be a web page for a federated search, etc. What
is needed is a good vocabulary to describe what the link means...
catalog, home page, online resources, etc. etc. That's an ontology
that would need to be created (and would by necessity have some
fuzziness that matches the fuzziness of the services themselves). It
may also be useful to include URLs of key information points (library
location, library hours, library maps).
kc
--
Karen Coyle
kcoyle@kcoyle.net http://kcoyle.net
ph: 1-510-540-7596
m: 1-510-435-8234
skype: kcoylenet
Received on Wed Dec 09 2009 - 11:31:45 EST