Thursday, January 19, 2012

Names in RDA

Help get the NACO/LC Authority File ready for RDA.
The Acceptable Headings Implementation Task Group has been established by the Program for Cooperative Cataloging to develop an implementation plan for preparing the LC/NACO authority file for RDA. The work of this group is largely based on the report of an earlier PCC Task Group; this group recommended a series of mechanical operations designed to make as many of the records in the LC/NACO authority file as useful as possible under RDA without individual review. The present group is exploring each of the changes suggested by the first group in detail, and fitting each into a proposed schedule.

The group has created a Facebook page as one means for communication between the group and the larger community:!/pages/PCC-Acceptable-Headings-Implementation-Task-Group/232585923488557 We invite comments on our work, but ask that comments follow the guidelines found in the “Info" section of this page. THE INFO SECTION describes the Group's activities, including the broad areas in which the group is interested in receiving comments and those areas not in the Group's charge in which the group is not interested in receiving comments.

The group has already drafted several documents. These documents may be found at the Group's download site (and they are also available from the Facebook page):
  • a document describing a phased implementation of the suggested changes
  • a discussion of the issues involved in the handling of subfield $c in personal names
  • a discussion of the suppression (or otherwise) of 4XX fields for AACR2 forms of name
The Group is in the midst of drafting a series of documents describing the stages in which this work should be performed, and the details involved in the work. These documents will also be posted to the Group's download site, and notices of the postings placed on the Facebook page. The Group is actively soliciting volunteers interested in assisting the Group in its work. These tasks will include the review of long lists of changed headings for correctness.

Tuesday, January 17, 2012

Open Data Access

English: Open Data stickersImage via WikipediaMake your open data even more open with CORS (Cross Origin Request Security).
Currently, client-side scripts (e.g., JavaScript) are prevented from accessing much of the Web of Linked Data due to "same origin" restrictions implemented in all major Web browsers.

While enabling such access is important for all data, it is especially important for Linked Open Data and related services; without this, our data simply is not open to all clients.

If you have public data which doesn't use require cookie or session based authentication to see, then please consider opening it up for universal JavaScript/browser access.

.data TLD

Stephen Woldram, of Wolfram|Alpha and Mathematica, has proposed a top level domain .data.
But what would be the point? For me, it’s about highlighting the exposure of data on the internet—and providing added impetus for organizations to expose data in a way that can efficiently be found and accessed.

In building Wolfram|Alpha, we’ve absorbed an immense amount of data, across a huge number of domains. But—perhaps surprisingly—almost none of it has come in any direct way from the visible internet. Instead, it’s mostly from a complicated patchwork of data files and feeds and database dumps.

But wouldn’t it be nice if there was some standard way to get access to whatever structured data any organization wants to expose?