SWORD ‘itself’ is the profile of APP. Essentially 2 strands: The profile The test implementations Advocacy/dissemination
Didn’t want to reinvent the wheel Looked at a range of existing standards
ATOMPUB came out as best fit Used for publishing blog posts
Thorny issue of package support MIME Multipurpose Internet Mail Extensions (MIME) is an Internet standard that extends the format of e-mail to support: * Text in character sets other than ASCII * Non-text attachments * Message bodies with multiple parts * Header information in non-ASCII character sets Not enough information to dscribe compund types and their content So, SWORD extends atomPub to understand and accept packages – significant part of the profile
Some issues with X-On-Behalf-Of and looking at this now I may be a cataloguer or repository metadata expert submitting on behalf of an author
Auto- discovery – link rel=“sword” href=[service doc url] Nested Service Desc: No of collections in server system can become v large such that APP service doc becomes too large. So SWORD adds sword:service as a child of app:collection APP doc to allow nesting
This is how 1.2 differs from 1.3
Web architecture based with standard GET and POST Make a request to GET a service doc The service doc explains the service in terms of its collections and what file types and packages it can accept, developer extensions etc. HTTP response details whether the deposit has been successful
Number of clients – some SWORD funded, some other JISC and wider projects.
Drop down for SWORD demo repos or can test your own Can be implemented via any website Can have own repositories list and own look and feel – radio buttons Highlight the on behalf of
Service details highlight – version, developer functions, max upload size Info about the collections - Open and Geography collection What they accept
FeedForward is a desktop application that keeps you on top of your personal information environment, enabling you to scan, organise, remix, and republish entries from your feeds to everything from Twitter to bibliographic databases
JISC had strong ideas on this. Devise a model for supporting SWORD including developing a website knowledge base and enhanced documentation including a technical primer for SWORD implementers. Develop additional SWORD usage and implementation case studies e.g. based on Microsoft uptake Hold SWORD promotional event with show-and-tells, demonstrations, and technical workshops
Develop a ‘SWORD enabled’ repositories registry prototype and populate for use in promoting SWORD uptake.