Comments for W3C incubator group on LLD - Draft Report for comment

Comment on Implementation challenges and barriers to adoption by Johan Oomen

Johan Oomen — Wed, 10 Aug 2011 13:35:20 +0000

“Technological changes have taken place so quickly that many in library positions today began their careers long before the World Wide Web was a reality, and these workers may not fully understand the import of these changes.” => what an extremely bold statement.

Comment on Implementation challenges and barriers to adoption by Johan Oomen

Johan Oomen — Wed, 10 Aug 2011 13:34:43 +0000

“cooperative agreements ” between whom?

Comment on Implementation challenges and barriers to adoption by Johan Oomen

Johan Oomen — Wed, 10 Aug 2011 13:34:26 +0000

Please elaborate on the “particularly libraries” statement.

Also “have greatly hindered libraries ability to create competitive information services.” => add a reference

Comment on Available Vocabularies and Datasets by Antoine Isaac

Antoine Isaac — Wed, 10 Aug 2011 13:22:10 +0000

Thanks a lot for spotting this, Adrian. We’ve updated the end of that section, see http://www.w3.org/2005/Incubator/lld/wiki/Draft_Vocabularies_Datasets_Section

We hope it’s alright!

Comment on Recommendations by Adrian

Adrian — Wed, 03 Aug 2011 11:31:02 +0000

“Use of HTTP URIs (URLs) for the identification of library elements, vocabularies and bibliographic data…”

Perhaps the term “data” should be exchanged as it is especially important to use HTTP URIs for bibliographic _resources_ and not only for the data about them.

Comment on Recommendations by Adrian

Adrian — Wed, 03 Aug 2011 07:17:16 +0000

Is it right to call OCLC Research an “independent research group”?

Comment on Recommendations by Adrian

Adrian — Wed, 03 Aug 2011 07:13:10 +0000

This paragraph contains a more differentiated view on open data than the previous paragraphs which touch the topic. As said in other comments, a general explanation of ‘Open Data’ (especially compared to ‘Linked Data’) is missing in the report.

Comment on Implementation challenges and barriers to adoption by Adrian

Adrian — Tue, 02 Aug 2011 12:22:20 +0000

The heading seems to assume that linked data necessarily means open data. This isn’t the case as you can publish data as RDF without an open license or without any license at all (as several organisations do) or as you can even do linked data in an intranet. Also, you can publish linkable data and let it be linked to and then establish a paywall around the data.

In general, the report lacks a clarification regarding the terms “Linked Data” vs. “Open Data”.

I suggest adding a paragraph or section to the report which clarifies the two terms, “open data” being about open access, open standards and open licenses in the first place and “linked data” being about a specific set of standards or best practices for publishing data on the web recommended by the W3C. An important aspect of open data is legal compatibility of data while linked data deals with technical compatibility of data.

Comment on Implementation challenges and barriers to adoption by Adrian

Adrian — Tue, 02 Aug 2011 12:08:32 +0000

I think this paragraph has to be fundamentally changed or even omitted. It implicitely argues that individual records are copyrighted. Much speaks for individual records aren’t copyrighted at all and that, thus, nobody owns any rights on them. At least in Europe you only have the related database right on collections of records.

I believe the legal status of records is quite clear (not copyrighted), at most this is a grey area. The report shouldn’t speak in favour of the view that individual records are copyrightable.

Comment on Recommendations by Ed Chamberlain

Ed Chamberlain — Fri, 29 Jul 2011 11:37:39 +0000

There are also issues of concern around attribution licenses and linked data.
Attribution only works and thus has practical value at a dataset level. Given the composite nature of RDF, any single triple could be referenced or reused by another record or service. Attribution does not work practically in this context.