W3C home > Mailing lists > Public > public-xg-lld@w3.org > February 2011

Re: Brainstorming: Key Issues

From: Antoine Isaac <aisaac@few.vu.nl>
Date: Tue, 22 Feb 2011 22:58:51 +0100
Message-ID: <4D64319B.8060501@few.vu.nl>
To: "public-xg-lld@w3.org" <public-xg-lld@w3.org>
Adding some stuff...

> Lack of library standards and guidance in this area
> - "When ongologies/metadata schemas/vocabularies overlap, which should be used?"
> - Need for study of SKOS for authorities
> - "no community guidance on which technologies and vocabularies to use"
> Legacy data
> - Incomplete vocabularies for legacy data
> - Legacy data itself is often text, not data, and does not include relationships
> - how will the mass of legacy data be transformed?

+ Need to carefully articulate library value vocabularies (concepts, terms) with real world entities they stand for. Library entities are "proxies" for real things, which linked data has as core focus. Perhaps this needs some education of the LD community, ie, convince them that there is any value in having such proxies. And identifying appropriate mechanisms (ie. efficient in terms of data creation and consumption) to represent this (a-la skos:Concept + foaf:focus)

> Immaturity of Semantic Web at this Time
> - "There is a general sparseness of linkage in the LOD cloud."
> - Over-use or misuse of properties like OWL sameAs
> - Lack of generalized tools for creation and use of LD
> Readiness of Library Community (Education)
> - "Publishing Linked Data requires expertise which is often not available at institutions..."
> - Changing mental model from "records" to "graphs"

+ Communication/cooperation with wider cultural sector. Problems are quite similar across LAM actors.

> Applications and Management
> - (what Ross said)
> - Managing a heterogeneous metadata environment (libraries now are more homogeneous)

+ bouncing back on Ross' "Where to start?", a "Where to stop" complement: libraries should perhaps learn to rely on data produced by others and not try to produce every required data by themselves (gazetteers come to mind).

+ versioning and updates. When/how to disseminate change notifications, how data consumers should integrate them (problem of deprecation/removal of triples).

But well, this part starts looking like a very general LD issue list, not specific to libraries or even the wider cultural sector...


Received on Tuesday, 22 February 2011 21:58:34 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:35:56 UTC