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

Review of Draft recommendation page

From: Young,Jeff (OR) <jyoung@oclc.org>
Date: Tue, 24 May 2011 23:58:29 -0400
Message-ID: <52E301F960B30049ADEFBCCF1CCAEF590C948358@OAEXCH4SERVER.oa.oclc.org>
To: <public-lld@w3.org>
I have an action to review the draft recommendations page:




Here are some section-by-section thoughts. In several cases the thought
was eventually addressed, so it's probably safe to ignore those. In
general, I think the section is excellent!

Recommendations (1st paragraph)

I'll try to avoid word-smithing, but I would suggest changing "libraries
can take on a leadership role around traditional library values of..."
to "libraries can leverage their traditional values of...".

Identify sets of data as possible candidates for early exposure as LD

One guideline here may be encourage developers to focus on resources
that are likely to be found in Linked Data cloud hubs. The mental block
that needs to be overcome is knowing the hubs probably don't contain
every instance needed, but developers shouldn't let that be a
show-stopper. [I see this is mentioned in the section named "Create
explicit links from ...]

For each set of data, determine the ROI...

In terms of ROI, replacing MARC bibliographic format will presumably be
more hateful than other data formats. This is implied in various places,
but this section might be less discouraging in general if the point was

Increase library participation in Semantic Web standardization

This section mentions extending standards, presumably in the sense of
library community extensions. One of the nice things about OWL, though,
is that domain-specific terms can also be mapped to other terms without
community involvement. I think this is a useful point because many
developers still seem to believe that existing vocabularies are
all-or-nothing. [I see this is mentioned in the "Directly use, or map
to,..." section.]

Develop best practices and design patterns for LLD

Assuming heterogeneity is inevitable, an OWL reasoner could be used in
combination with OWL mappings to smooth out dataset mashups.

Commit to best-practice policies for managing and preserving RDF

I'm not sure what this bullet means:

*         Extensibility of use of the namespace by smaller organizations





Jeffrey A. Young
Software Architect
OCLC Research, Mail Code 410
OCLC Online Computer Library Center, Inc.
6565 Kilgour Place
Dublin, OH 43017-3395
www.oclc.org <http://www.oclc.org> 

Voice: 614-764-4342
Voice: 800-848-5878, ext. 4342
Fax: 614-718-7477
Email: jyoung@oclc.org <mailto:jyoung@oclc.org> 

Received on Wednesday, 25 May 2011 04:07:14 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:27:44 UTC