• Save
ResourceSync - NISO Update Jan 2014
 

ResourceSync - NISO Update Jan 2014

on

  • 696 views

 

Statistics

Views

Total Views
696
Views on SlideShare
322
Embed Views
374

Actions

Likes
0
Downloads
0
Comments
0

12 Embeds 374

http://feedly.com 179
http://www.niso.org 95
http://www.infodocket.com 65
http://www.newsblur.com 14
http://www.feedspot.com 5
http://www.inoreader.com 4
http://127.0.0.1 3
http://digg.com 3
http://reader.aol.com 2
http://newsblur.com 2
https://www.commafeed.com 1
http://www.hanrss.com 1
More...

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • However, there are significant use cases that require low latency and high accuracy in reflecting a remote server's changing content.

ResourceSync - NISO Update Jan 2014 ResourceSync - NISO Update Jan 2014 Presentation Transcript

  • ResourceSync Nettie Lagace ALA Midwinter NISO Update – January 26, 2014
  • General Description Consideration: • • Source (server) A has resources that change over time: they get created, modified, deleted Destination (servers) X Y and Z leverage (some) resources of Source A Problem: • Destinations want to keep in step with the resource changes at Source A: resource synchronization Goal: • Design an approach for resource synchronization aligned with the Web Architecture that has a fair chance of adoption by different communities. The approach must scale better than recurrent HTTP HEAD/GET on resources
  • General Description • Range of easy to implement capabilities • Modular: provides flexibility and enables a broad range of use cases • Supported by server to enable remote systems to remain more tightly in step with its evolving resources. • Describes how a server can advertise the capabilities it supports. – Remote systems can inspect this information to determine how best to remain aligned with the evolving data. • Each capability provides a different synchronization functionality: – list of the server's resources – recently changed resources: created, updated, deleted – Implemented on document formats introduced by Sitemap protocol
  • ResourceSync Partnership • NISO • Open Archives Initiative • JISC • Funded by the Alfred P. Sloan Foundation 4
  • Working Group Core • Herbert Van de Sompel, LANL • Martin Klein, LANL • Robert Sanderson, LANL • Simeon Warner, Cornell University • Bernhard Haslhofer, University of Vienna • Michael L. Nelson, Old Dominion University • Carl Lagoze, University of Michigan • Graham Klyne, University of Oxford • Peter Murray, Lyrasis Technical • Shlomo Sanders, Ex Libris • Richard Jones, Paul Walk, Stuart Lewis, JISC • Kevin Ford, Library of Congress • Jeff Young, OCLC • David Rosenthal, LOCKSS • Christian Sadilek, RedHat
  • Recent steps • August 2013 - Release of ResourceSync framework Core specification, Version 0.9.1; public draft of ResourceSync Archives specification released • September 2013 - Core specification on its way to become an ANSI standard • November 2013 - Internal draft of ResourceSync Notification specification • January 2014 - Public draft of ResourceSync Notification specification • Q1 2014 - Core specification becomes ANSI/NISO standard 6
  • Thank you! Questions?