<rioxxterms:grant>
and <rioxxterms:project>
.<rioxxterms:name>
and <rioxxterms:id>
, to be used in conjunction with <rioxxterms:creator>
(updated from <rioxxterms:author>
in Version 2.0) and <rioxxterms:contributor>
.<rioxxterms:record_public_release_date>
encoded according to ISO8601/W3CDTF.<rioxxterms:ext_relation>
, used to convey external associations to related scholarly entities. Such relational associations will be scholarly entities hosted externally or outsider the direct custodianship of the repository.<rioxxterms:creator>
, <rioxxterms:contributor>
, <rioxxterms:project>
and <dc:publisher>
updated to better support persistent identifier (PID) schemes. An increased range of PID schemes recommended, to reflect growing maturity in the PID landscape.<rioxxterms:publication_date>
updated to specify encoding as per ISO8601/W3CDTF, including resources with seasonal publication dates.<rioxxterms:type>
to <dc:type>
, and updated to specify the COAR Controlled Vocabulary Resource Type Genres.<ali:free_to_read>
property.<rioxxterms:apc>
property.<rioxxterms:version_of_record>
property, superseded by updates to attribute usage within the <dc:relation>
and <rioxxterms:ext_relation>
properties.<dc:identifier>
to accommodate an HTTP(S) URI identifying the resource, resolving to a repository 'landing page' which describes the resource.<dc:relation>
, with the introduction of the following associated attributes: rel
, type
, coar_type
, coar_version
, deposit_date
, resource_exposed_date
, access_rights
, and license_ref
. <dc:relation>
to be used as principal mechanism for expressing the existence of harvestable file content, as well as other internally curated resources. To be considered in conjunction with the new property, <rioxxterms:ext_relation>
.This is an updated version of the RIOXX application profile, enhanced following the outcomes of the V4OA project.
This is the initial release of the RIOXX application profile