EPData XML Representation

From EPrints Documentation
Revision as of 11:56, 27 May 2011 by Tdb01r (talk | contribs) (Created page with 'Media Type Name: application Subtype name: vnd.eprints.data+xml Required parameters: None Optional parameters: charset Same as charset parameter of application/xml as spec…')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

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.


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>

Retrieved from ‘https://wiki.eprints.org/w/index.php?title=EPData_XML_Representation&oldid=9869’