XCRI 1.2 Updates

From Xcri

Editor’s NoteThis is just an initial draft pulling together various other bits of documentation, and needs more work

[edit] About

Editor’s NoteMaybe move some of the names to the acknowledgements section, and add in contributors from the forum etc

Editors:

Mark Stubbs (m.stubbs@mmu.ac.uk)
Scott Wilson (scott.bradley.wilson@gmail.com)
Alan Paull (alan@alanpaull.co.uk)

Authors:

Simon Grant
Alan Paull (alan@alanpaull.co.uk)
Ben Ryan (mail@benryan.co.uk)
Mark Stubbs (m.stubbs@mmu.ac.uk)
Scott Wilson (scott.bradley.wilson@gmail.com)

[edit] Status

This is currently a working draft of version 1.2.

[edit] Patents

This specification is subject to a royalty free patent policy.

There are no known patents covering any of this work. If you think that part of this work may be subject to an existing or pending patent, please email the editors.

[edit] Copyright and License

This work is (c) 2005-2010 XCRI.org, and licensed under a Creative Commons Attribution 3.0 Licence. All contributions MUST be licensed under the same conditions. This is to ensure that the specification work can be transferred to an appropriate standardisation body.

[edit] Inspiration and acknowledgements

We would like to thank the many UK institutions and lifelong learning networks that have contributed to its development through their work on implementation. We also thank JISC for supporting the development of this specification.

[edit] Introduction

The delta update or delta harvesting pattern involves a data collector receiving or taking updated data only, in contrast to whole data sets. This method can be implemented in a wide variety of ways, including the use of static files and dynamic system-to-system procedures either by pushing the updates or pulling them. It relies on the provider implementing a minimum level of auditing information that can be referenced by the data aggregator. The main structures in XCRI-CAP contain a recstatus attribute that satisfies the minimum requirement.

[edit] Pull model

A potential method is shown in the following diagrams. This method pulls the updates from the provider’s system, so that control of timing rests with the data collector, which is assumed to be a separate organisation for the purposes of this example.

[edit] Overview of the interaction between data collecting organisation and provider

Overview of the interaction between data collecting organisation and
provider {width=”974” height=”290”}

[edit] Provider updates local system

Provider updates local
system {width=”454” height=”309”}

[edit] Data collecting organisation gets update

Data collector pulls
update {width=”643” height=”701”}

\ For further discussion: It is likely that more extensive logging, including date:time might be needed to enable delta harvesting.

[edit] The recstatus attribute

*URI: *

The optional recstatus attribute provides a mechanism for indicating whether the resource to which it refers has changed. The enumerated value of the attribute indicates the nature of the change:

= Added
= Updated
= Deleted

This attribute MUST contain only one of “1”, “2” or “3” with no leading or trailing whitespace.

An element that has this attribute MUST include an identifier element that supplies a persistent, unique value so that the recipient of the xml can maintain state for itself.

[edit] Example

     http://xcri.org/example/courses/1
     ...

[edit] Usage

Recstatus may be used in the Course and Provider elements of an XCRI document.

Retrieved from “http://localhost/XCRI_1.2_Updates”

Views

Personal tools

Search

Toolbox

This page was last modified 12:38, 27 March 2012.
This page has been accessed 4,929 times.
Content is available under Attribution 3.0.
Privacy policy
About Xcri
Disclaimers