DefiningImageAccess/Standard/Eprints profile
From ImageWeb
Eprints Application Profile
| DefiningImageAccess/Standard/Eprints profile | |
|---|---|
| Link:=http://www.ukoln.ac.uk/repositories/digirep/index/Eprints_Application_Profile}} | |
| Status:=Initial Stage}} | |
| JISCProject:=True}} | |
| Focus:=Describing Digital Objects and bibliographic metadata}} | |
| [[ReferencedBy::{{{ReferencedBy}}}]]}} | |
| [[PublishedBy::{{{PublishedBy}}}]]}} | |
| [[UsedBy::{{{UsedBy}}}]]}} | |
| [[DescribedBy::{{{DescribedBy}}}]]}} | |
| [[Partner::{{{Partner}}}]]}} | |
| [[Contact::{{{Contact}}}]]}} | |
Also known as Dublin Core Application Profile for Scholarly Works.
- http://www.ukoln.ac.uk/repositories/digirep/index/Eprints_Application_Profile
- http://www.ariadne.ac.uk/issue50/allinson-et-al/
The objectives of the working group are to develop:
In the context of this work an eprint is defined to be a scientific or scholarly research text (as defined by the Budapest Open Access Initiative), for example a peer-reviewed journal article, a preprint, a working paper, a thesis, a book chapter, a report, etc. |
The profile itself is structured around FRBR-derived notions of "scholarly work - expression - manifestation - copy", with a related concept of an Agent, used with a variety of Dublin Core style relationships (affiliatedInstitution, isSupervisedBy, isFundedBy, isCreatedBy, isEditedBy, isPublishedBy). Relations between the main FRBR-derived object categories are also defined.
The XML serialization format defined for this profile looks like a variation of RDF, similar to (say) TRiX, in which a fixed XML tag set is used, and object/predicate values are all specified as attributes on an <ep:statement> element.
The specification also draws upon the DCMI abstract model, which is a framework model covering the full range of flexibility associated with what is often referred to as "qualified Dublin Core":
- http://dublincore.org/documents/abstract-model/
- http://www.ukoln.ac.uk/repositories/digirep/index/A_note_about_the_DCMI_Abstract_Model
From our point of view, this seems to exclude images; also, it's very DC centred, and our semantic aspirations might be better served by CIDOC CRM Core.
This work is of likely relevance to us, because JISC apparently wish to create a similar profile for Eprints/scholarly work images, time-based media, geospatial, eScience data (cf. Robert Muzuelfeld?). JISC have approached TASI to lead this area, and may ask us to be involved in such an activity.
Focus:=Describing Digital Objects Focus:=Bibliographic Metadata
