EPData XML Representation

From EPrints Documentation
Revision as of 12:08, 27 May 2011 by Tdb01r (talk | contribs)
Jump to: navigation, search


 Content-Type: application/vnd.eprints.data+xml; charset="utf-8"

 <?xml version='1.0' encoding='utf-8'?>
 <eprints xmlns='http://eprints.org/ep2/data/2.0'>
  <eprint id='http://yomiko.ecs.soton.ac.uk:8080/id/eprint/10'>
    <datestamp>2010-08-10 15:34:04</datestamp>
    <lastmod>2011-05-17 15:16:20</lastmod>
    <status_changed>2011-05-17 13:44:44</status_changed>
    <title>HIC HIC Koum et τοπικές hic</title>
    <abstract>" '^M
\ /^M
Aut do och Чем modi. Φακέλους et Scholl itaque αρέσει rerum tenetur हुएआदि. Similque команда voluptas или quidem schaddreg voluptatum ίδιο. Nulla animi νέα συνηθίζουν d'Loft inventore quis.^M
Expedita praesentium σημαίνει Нее rei sed et стратегические. Doloribus alias प्रा ea reiciendis Frot. Molestiae αντιλήφθηκαν μου enim. Tenetur πως отнимет во. Nihil voluptatum nobis dolorum laudantium cum Jo τι.</abstract>
    <publication>आंतरजाल ποια De impedit och आंतरजाल Чем नयेलिए nesciunt.</publicat>onn

IETF-Registration Draft

Media Type Name: application

Subtype name: vnd.eprints.data+xml

Required parameters: None

Optional parameters: charset

Same as charset parameter of application/xml as specified in RFC 3023.

Optional parameters: files

If "files=embed" the content includes file data embedded using Base64

Encoding considerations:

Same as encoding considerations of application/xml as specified in RFC 3023.

Security considerations:

In addition to those of application/xml as specified in RFC 3023, section
10; the format may contain URL-references that are retrieved and embedded in
the resulting digital object. If the EPrints recipient is configured to
allow it these URLs may be retrieved from remote systems (via HTTP) or the
recipient's file system.

Interoperability considerations: None

Published specification: http://wiki.eprints.org/EPData_XML_Representation

Applications which use this media type: EPrints http://www.eprints.org/

Additional information: Same as additional information of application/xml as
specified in RFC 3023.

Intended usage:

XML serialisation of EPrints Data (or "EPData") for the import/export of the
complete record. This is principally for internal use in the system e.g. for
ingesting the results of XSL transforms from standardised XML formats. The
mime-type is necessary to support correct content-type negotiation when
using the EPrints REST interface.

Author/Change controller:

EPrints http://www.eprints.org/

Tim Brody <tdb2@ecs.soton.ac.uk>