SWORDWe will be running a SWORDV3 Workshop at Open Repositories 2018 (June 4-7, in Bozeman, Montana). Currently, we are scheduled for 9-12pm on Monday 4th.
The workshop will go through the technical specification in detail, followed by a discussion on Community and sustainability plans for the future.
Hope to see you there!
The final draft of the SWORD V3 Technical Specification has been released for comment. You can find them in the SWORD V3 of this website along with guidance for reading the documents and other supporting materials.
To comment, please contact us to get onto the stakeholders list – details can be found here.
Happy New Year, hope you all had a great Christmas.
Over December and the first half of January, we’ve been working through the comments and our email discussions to produce a new iteration of the specification for review. It’s still by no means a finished work, so there’s plenty more scope for alterations, additions and removals!
The new version is here: https://docs.google.com/document/d/1eQL1Guv0ihfxPJIIceLJk4l22cRpGbXTsNVSNqcEdOM/edit
The following summarises the changes that we’ve made:
There’s a fair bit to look at, so I’ll leave that to sit with you for a week or so, and for you to add any comments you like to the doc, and then as before we’ll pick some key topics for discussion on this list.
To avoid any confusion, I have now disabled commenting on the old version. Most comments on the old version were resolved, and I’ve carried forward any comments which are still relevant.
All the best,
Richard
A SWORD Community Discussion document has been released for comment. You can find them in the SWORD V3 section of this website along previously released technical documentation.
To comment, please contact us to get onto the stakeholders list – details can be found an earlier previous post. We aim to start developing some firmer community recommendations in the new year.
The first drafts of the SWORD V3 Technical Specification have been released for comment. You can find them in the SWORD V3 of this website along with guidance for reading the documents and other supporting materials.
To comment, please contact us to get onto the stakeholders list – details can be found in the previous post. We aim to start work on a revised spec, taking into account your feedback, bythe end of the year.
The SWORDV3 project has been funded by Jisc with two key aims for the next generation of the SWORD Protocol:
in September, the project was formally announced at PASIG 2017 in Oxford and the RDA 10th Plenary in Montreal. We are looking for expressions of interest in becoming involved as stakeholders in the project: to make suggestions, review activities and meet as required over the coming months. In particular, we are interested in making contact with people who may wish to develop SWORD V3 libraries for their preferred platforms or languages since we aim to provide some support for such activities during the project. Please contact one of the project team if you are interested in participating, and indicate if you are interested in the technical or community aspects of the project (or both!).
The key members of the project team are:
On the technical side, we are creating a document that brings together the change requests and new use cases that have collected since the release of SWORDV2, culled from the github site, message posts and preliminary discussions with some stakeholders earlier this year. This has also suggested a way forward that breaks with SWORD’s AtomPub roots in order to provide a more up-to-date and flexible protocol. We will circulate this to stakeholders soon.
On the community side, we will circulate a similar document outlining possible models for developing the SWORD community in the future. This is a much more open set of choices since the SWORD user-base has expanded considerably since its first conception, and we are open to further suggestions! The final arrangements must be aligned with community wishes in order to be an effective sustainable solution.
Neil Jefferies (neil.jefferies[at]bodleian.ox.ac.uk) @NeilSJefferies
Dom Fripp (dom.fripp[at]jisc.ac.uk) @Domicus
Richard Jones (richard[at]cottagelabs.com) @cottagelabs