2011-01-26: Moving the content of this document into a new document, DraftReport.See DraftReport
- 1 LLD XG Final Report
- 1.1 Benefits of LD for libraries
- 1.2 State of the art use cases and requirements
- 1.2.1 Bibliographic data cluster (Gordon, Martin)
- 1.2.2 Authority data cluster (Jeff, Alex)
- 1.2.3 Vocabulary alignment cluster (Antoine, Marcia, Michael)
- 1.2.4 Archives and heterogeneous data cluster (Karen, Emmanuelle)
- 1.2.5 Citations cluster (Ed, Kai)
- 1.2.6 Digital objects cluster (Mark, Jodi, Asaf)
- 1.2.7 Collections cluster (Gordon, Karen)
- 1.3 Available data
- 1.4 Recommendations
- 2 Appendix
LLD XG Final Report
Benefits of LD for libraries
Introduction explaining what are the expected benefits for libraries (and other GLAM institutions). What are the opportunities for stakeholders, both for libraries (e.g. for scenarios like collaborative cataloging) and for the rest of the world. Possibly recommending to do more strategic work, targeting managers (this specific item may be in #Recommendations)
State of the art use cases and requirements
Three pages each for describing the following clusters.
Bibliographic data cluster (Gordon, Martin)
Authority data cluster (Jeff, Alex)
Vocabulary alignment cluster (Antoine, Marcia, Michael)
Archives and heterogeneous data cluster (Karen, Emmanuelle)
Citations cluster (Ed, Kai)
Digital objects cluster (Mark, Jodi, Asaf)
Collections cluster (Gordon, Karen)
Datasets, metadata elements sets, and value vocabularies: see our definition.
List here existing and in use vocabularies, in development vocabularies, and missing vocabularies.
Topics to be included here (with transclusion) :
Placeholder for an effort to identify relevant datasets on CKAN
NOTE: These recommendations are PLACEHOLDERS -- very early drafts that have not yet been submitted for discussion by the group. The point is to suggest a style and granularity for the recommendations section. Note that the charter suggests that the LLD deliverable "describe relevant technology pieces, including vocabularies and ontologies (e.g., SKOS), with the intended goal to identify extension or interoperability requirements, and help determine what other standards may be needed."
- LLdata should be produced using the FR's as domain model. However, the correct use of FR concepts requires expertise and resources that may not always be available, especially when converting legacy data. Best practices are needed for clarifying when and how FR models should be applied.
- Status and relationship between multiple extant expressions of FRBR (e.g., by IFLA, RDA, SWAP, FRBRoo, Talis...) should be clarified.
- Need to address reusability outside of libraries and mixing of FRBR and non-FRBR data
- The LLD XG identifies missing vocabs for XXX (to be completed). The Lib. community should carry on future work to complete the coverage of vocabs.
- Recomendations for producers of vocabularies: namespaces persistence, use of a metadata registry, links with other vocabs.
Topics to be included here (with transclusion) :
- Best practices are needed on how to reuse legacy Ids in a LD context (this is a minor concern for the group for the moment. Let's see how it evolves with use cases).
- The XG recommends to consider URI patterns when designing URIs for Linked Data. Best practices needed, not specific to Libraries.
- Best practices are needed for the conversion from MARC to RDF. The XG identifies possible approches and recommends future work.
- The XG identifies an issue regarding names vs. RWO when it comes to authority data. The XG identifies possible approaches for modelling this. Possibly recommends future work.
- There is a need for a mechanism for constraints and validation (application profiles). The XG identifies possible approaches and recommends future work.
- Best practices are needed for IT architecture & infrastructure. Not specific to libraries, but targeted use case are more useful than generic ones (imho).
- The community should start sharing feedback on successful - and unsuccessful - implementation stories. Suggest/identify a group or mechanism which can help facilitate this?
- Cross-linking of vocabs is a key feature of LLdata. The XG identifies different approaches (1-to-1, Hub-Spoke, etc.).
General education and outreach
- The XG recommends that someone (?) writes a linked data primer for libraries
- The XG recommends that Liaison between std bodies (which ones?) (incl. W3C) is established
- The XG recommends future work for outreach to GLAM community (from particular groups?) (about Linked Data, or also about other issues?)
- Qualifications for a "next generation librarian" educated in the concept of linked data (including problems and opportunities) and the roles libraries can play.
- Recommendations on future work to further identify these qualifications and/or gather related education material
Put use cases here, one per page.