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… Read More »
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… Read More »
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… Read More »
The SWORDV3 project has been funded by Jisc with two key aims for the next generation of the SWORD Protocol: To bring SWORD up-to-date with the developments in the repository sphere in the last 5 years, with alignment to new protocols and new use-cases such as data publishing and complex objects. To establish community and… Read More »
A new copy of the proposed SWORD v2 specification has been posted based on recent feedback from the Technical Advisory Panel: https://sword.cottagelabs.com/sword-v2/sword-v2-specifications/ The main changes that were made are as follows: 1/ Changed all relevant instances of URI to IRI. 2/ Provided a better introduction with text from the business case/technical approach document. 3/ Corrected… Read More »