
schemaorg_apache_xmlbeans.system.s7F9370017BA1D190A14E19A35D3F8C33.index.xsb Maven / Gradle / Ivy
Go to download
Show more of this group Show more artifacts with this name
Show all versions of epicur Show documentation
Show all versions of epicur Show documentation
Java classes (generated with XML-Beans) for XML-Schemas xepicur and epicurlite processing.
See the official URN:NBN Resolver http://nbn-resolving.org or http://persid.org
The newest version!
?z?? ^ administrativedatatype0139type deliverytypea18etype authorizationtypedbdbtype updatestatustypeb64ctype transfertype46b7type resupplytype1ae0type urnnidtype2899type urnsnidtype40betype type55b2attrtype type1f91attrtype typef3baattrtype recordtype7751type identifiertypeb879type isversionoftype064ftype hasversiontype3da4type resourcetype7634type ispartoftype2e8etype scheme1dbeattrtype typec2d3attrtype status388battrtype roleca0fattrtype origin19bfattrtype target27aaattrtype scheme49aaattrtype schemea2e9attrtype formattypef6ebtype schemec6b0attrtype identifiertype0931type resourcetype8dd6type epicur072adoctype epicur1328elemtype
epicurelement epicurlite5dcedoctype epicurlitee4a2elemtype epicurliteelement urn:nbn:de:1111-2004033116 epicur #http://nbn-resolving.org/epicurlite
epicurlite administrative_dataType deliveryType authorizationType update_statusType transferType resupplyType
recordType identifierType isVersionOfType hasVersionType resourceType
formatType isPartOfType urn_nidType urn_snidType "nbnDe11112004033116.EpicurDocument .org.nbnResolving.epicurlite.EpicurliteDocument *nbnDe11112004033116.AdministrativeDataType nbnDe11112004033116.DeliveryType %nbnDe11112004033116.AuthorizationType $nbnDe11112004033116.UpdateStatusType nbnDe11112004033116.TransferType nbnDe11112004033116.ResupplyType nbnDe11112004033116.RecordType "nbnDe11112004033116.IdentifierType #nbnDe11112004033116.IsVersionOfType "nbnDe11112004033116.HasVersionType nbnDe11112004033116.ResourceType nbnDe11112004033116.FormatType nbnDe11112004033116.IsPartOfType nbnDe11112004033116.UrnNidType nbnDe11112004033116.UrnSnidType *org.nbnResolving.epicurlite.IdentifierType (org.nbnResolving.epicurlite.ResourceType )nbnDe11112004033116.EpicurDocument.Epicur 9org.nbnResolving.epicurlite.EpicurliteDocument.Epicurlite )nbnDe11112004033116.UpdateStatusType.Type %nbnDe11112004033116.TransferType.Type %nbnDe11112004033116.ResupplyType.Type )nbnDe11112004033116.IdentifierType.Scheme 'nbnDe11112004033116.IdentifierType.Type )nbnDe11112004033116.IdentifierType.Status 'nbnDe11112004033116.IdentifierType.Role )nbnDe11112004033116.IdentifierType.Origin )nbnDe11112004033116.IdentifierType.Target *nbnDe11112004033116.IsVersionOfType.Scheme )nbnDe11112004033116.HasVersionType.Scheme %nbnDe11112004033116.FormatType.Scheme )http://www.w3.org/2001/XMLSchema-instance schemaLocation G http://www.w3.org/2001/XMLSchema http://www.w3.org/2001/XMLSchema.xsd?
Diese Datei beinhaltet das Schema der auf XML basierenden EPICUR-Transfersyntax zur Abbildung des umfassenden URN-Workflows. Mit diesem Schema werden zwei Ziele verfolgt:
1. Die Einbindung in OAI 2.0 zum selektiven Harvesten von URN-Records durch Die Deutsche Bibliothek von einem DataProvider.
URN-Records beinhalten folgende Informationen:
- Einen neu erstellten Metadatensatz mit Informationen ueber die URN und die zugehoerige URL.
- Es wird zusaetzlich eine Metainformation ueber einen bei dem DataProvider geaenderten Record angegeben. Dieser Fall tritt ein, wenn die URL aktualisiert wurde.
- Es koennen optional hierarchische Zuordnungen (Gesamt- und Teildokument) angegeben werden und die fuer Teildokumente vergebenen URNs.
- Optional ist die Abbildung von semantischen Informationen vorgesehen wie z.B. die Angabe einer URN, die fuer eine neue Dokumentversion vergeben wurde.
2. Das Anbieten einer separaten Schnittstelle zur Implementation eines aktiven URN-Melde- und Updateprozesses an Die Deutsche Bibliothek mit folgenden
Informationen:
- URN-Erstregistrierung
- Erstmeldung einer URN fuer neue Dokumentversionen
- Erstmeldung von URNs fuer Teildkokumente
- Update einer URL
- URL-Update bei mehr als 1 registrierten URL fuer eine URN
- URL-delete
- URL-insert
Stand: Februar 2004
Version: 1.0
Autoren:
Kathrin Schroeder
?
This file contains the schema of the XML schema on the basis of the XEPICUR transfer syntax for the entire URN administration. This schema has two aims: 1. The integration into OAI 2.0 of the selective harvesting of URN records by Die Deutsche Bibliothek from a data provider. URN records contain the following information: - A created xml-based metadata record with information about a URN, its associated URL and some attributes. - Also provided is meta-information about records changed by data providers. This situation applies when a URL is updated. - Optionally hierarchical designations (for whole or partial documents) can be provided as can URNs for partial documents. - There is an option of providing semantic information such as the details of a new URN allocated for a new document version. 2. The provision of a separate technical interface for implementing an active process for reporting and updating URNs at Die Deutsche Bibliothek with the following information: - Initial URN registration - initial registration of a URN for a new version of a document - initial registration of a URN for partial documents - URL updating - URL updating where more than URL is registered against one URN - deleting URNs - inserting URLs As at: February 2004 Version: 1.0 Authors: Kathrin Schroeder
C
This file contains a XML schema for administration of URNs and their corresponding URLs.
It is based on the XEPICUR transfer syntax but is a very simplified form of it
containing only some basic information..
See: http://nbn-resolving.org/schemas/xepicur/1.0/xepicur.xsd
Version 1.0 from February 2012. Kadir Karaca Koçer, German National Library