EPrints Technical Mailing List Archive
Message: #06112
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
Re: [EP-tech] Antwort: Re: HTML5 and EPrints
- To: "eprints-tech@ecs.soton.ac.uk" <eprints-tech@ecs.soton.ac.uk>
- Subject: Re: [EP-tech] Antwort: Re: HTML5 and EPrints
- From: Matthew Kerwin <matthew.kerwin@qut.edu.au>
- Date: Wed, 30 Nov 2016 20:55:58 +0000
RFC 5988 is the IETF standard for Links, if anyone’s interested. It says that, besides registered tokens, extension relation types can be used but are supposed to look like a URI. That’s actually covered in the SWORDv2 profile, which says to use rel="http://purl.org/net/sword/terms/service-document" and rel="http://purl.org/net/sword/terms/deposit" However I think there’s still some value in JISC registering the SWORD 1.3 terms. The IANA registry only requires a published specification, and I think http://swordapp.org/sword-v2/sword-v2-specifications/ should be fine for that. See: https://tools.ietf.org/html/rfc5988#section-6.2.1 Cheers -- Matthew Kerwin | ITS-EIS:AS:LS | KG-SYN | QUT From: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk] On Behalf Of jens.vieler@id.uzh.ch Hey Ian,
|
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
- References:
- [EP-tech] HTML5 and EPrints
- From: jens.vieler@id.uzh.ch
- Re: [EP-tech] HTML5 and EPrints
- From: Ian Stuart <Ian.Stuart@ed.ac.uk>
- [EP-tech] Antwort: Re: HTML5 and EPrints
- From: jens.vieler@id.uzh.ch
- [EP-tech] HTML5 and EPrints
- Prev by Date: [EP-tech] Antwort: Re: HTML5 and EPrints
- Next by Date: [EP-tech] Antwort: Re: Antwort: Re: HTML5 and EPrints
- Previous by thread: [EP-tech] Antwort: Re: HTML5 and EPrints
- Next by thread: [EP-tech] Antwort: Re: Antwort: Re: HTML5 and EPrints
- Index(es):