1、Oktober 2014DEUTSCHE NORM DIN-Normenausschuss Informationstechnik und Anwendungen (NIA)Preisgruppe 12DIN Deutsches Institut fr Normung e. V. Jede Art der Vervielfltigung, auch auszugsweise, nur mit Genehmigung des DIN Deutsches Institut fr Normung e. V., Berlin, gestattet.ICS 35.240.30; 35.240.99!%7
2、#“2205900www.din.deDDIN EN 16425Schnittstelle fr einfaches Publizieren (Simple Publishing Interface SPI);Englische Fassung EN 16425:2014Simple Publishing Interface;English version EN 16425:2014Interface de publication simple;Version anglaise EN 16425:2014Alleinverkauf der Normen durch Beuth Verlag G
3、mbH, 10772 Berlin www.beuth.deGesamtumfang 22 SeitenDIN EN 16425:2014-10 2 Nationales Vorwort Dieses Dokument (EN 16425:2014) wurde vom Technischen Komitee CEN/TC 353 Informations- und Kommunikationstechnologien fr Lernen, Ausbildung und Weiterbildung“ erarbeitet, dessen Sekretariat vom UNI (Italien
4、) gehalten wird. Das Prsidium des DIN hat mit seinem Beschluss 1/2004 festgelegt, dass von dem in den Regeln der europischen Normungsarbeit von CEN/CENELEC verankerten Grundsatz, wonach Europische Normen in den drei offiziellen Sprachen Deutsch, Englisch und Franzsisch verffentlicht werden, in begrn
5、deten Ausnahmefllen abgewichen und auf die deutsche Sprachfassung verzichtet werden kann. Die Genehmigung dafr hat die DIN-Geschftsleitung entsprechend den festgelegten Kriterien fr die vor-liegende Norm auf Antrag des DIN-Normenausschusses Informationstechnik (NIA) erteilt. DIN EN 16425 spezifizier
6、t eine Schnittstelle fr einfaches Publizieren (en: Simple Publishing Interface SPI). Dabei handelt es sich um ein Protokoll fr das Publizieren von digitalen Objekten oder deren Metadaten in Repositorien fr Lernobjekte. Das Protokoll dient dazu, den Transfer von Metadaten und Inhalt von den Produzent
7、en dieser Lernmaterialien zu Anwendungen, welche Lernobjekte und Metadaten verwalten, zu erleichtern. Dieses Dokument enthlt die Anforderungen (en: requirements) fr das Simple Publishing Interface“ (SPI), ein Protokoll fr die Aufbewahrung von Bildungsmaterialen in einem Repository. Dieses Protokoll
8、ermglicht den Transfer von Metadaten und Inhalten von Tools, die Lernmaterialien produzieren, zu Anwendungen (en: applications), die stndig Lernobjekte und Metadaten verwalten, aber es ist auch anwendbar fr die Verffentlichung einer greren Auswahl von digitalen Objekten. DIN EN 16425:2014-10 3 Natio
9、naler Anhang NA (informativ) Begriffe Die Benennungen der Begriffe sind identisch mit den Benennungen in der Englischen Fassung. 2.1 Quelle (en: source) System, das eine Anfrage (en: request) fr eine Verffentlichung (en: publication) ausgibt. Alternativ kann dieses System auch als Anfrager (en: requ
10、ester) bezeichnet werden. 2.2 Ziel (en: target) System, zu dem Anfragen (en: requests) fr eine Verffentlichung (en: publication) gesendet werden. Dies kann eine Komponente eines Repository oder einer mittleren Softwareebene (en: middle layer) sein. Solch eine Komponente einer mittleren Softwareebene
11、 kann mehrere Aufgaben erfllen. Sie kann Metadaten zu einer Ressource anfgen, kleinere, mehr granulare Komponenten disaggregieren und verffentlichen oder zum Beispiel als Adapter zur Verffentlichungs-API (en: application programming interface) von anderer Software (en: third party) agieren. Anmerkun
12、g 1 zum Begriff: Die Begriffe client“ und server“ sind nicht benutzt, um Missverstndnisse zu vermeiden hinsichtlich eines Interface, das nur in client/server Anwendungen (en: applications) anwendbar ist. Darber hinaus sehen die Szenarien, in denen die API benutzt wird, auch eine Quelle (en: source),
13、 die auf einem Server luft (z. B. Verffentlichen innerhalb eines LMS). Im Folgenden werden in diesem Dokument die Begriffe resource“, digital content“, learning object“ und educational material“ benutzt. DIN EN 16425:2014-10 4 Leerseite EUROPEAN STANDARD NORME EUROPENNE EUROPISCHE NORM EN 16425 July
14、 2014 ICS 35.240.30; 35.240.99 English Version Simple Publishing Interface Interface de publication simple Schnittstelle fr einfaches Publizieren (Simple Publishing Interface SPI) This European Standard was approved by CEN on 22 May 2014. CEN members are bound to comply with the CEN/CENELEC Internal
15、 Regulations which stipulate the conditions for giving this European Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical references concerning such national standards may be obtained on application to the CEN-CENELEC Management Centre or to any CEN
16、 member. This European Standard exists in three official versions (English, French, German). A version in any other language made by translation under the responsibility of a CEN member into its own language and notified to the CEN-CENELEC Management Centre has the same status as the official versio
17、ns. CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Po
18、land, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and United Kingdom. EUROPEAN COMMITTEE FOR STANDARDIZATION COMIT EUROPEN DE NORMALISATION EUROPISCHES KOMITEE FR NORMUNG CEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels 2014 CEN All rights of exploitatio
19、n in any form and by any means reserved worldwide for CEN national Members. Ref. No. EN 16425:2014 E EN 16425:2014 (E) 2 Contents Page Foreword 3 1 Scope 4 2 Terms and definitions .4 3 Requirements and design principles .5 3.1 General 5 3.2 Syntactic versus semantic interoperability 6 3.3 “By refere
20、nce” and “by value” publishing 6 3.4 Flexible application6 3.5 Objectives .7 4 SPI Model 7 4.1 General 7 4.2 Submit a resource8 4.2.1 General 8 4.2.2 Resource submission by value 9 4.2.3 Resource submission by reference 10 4.3 Delete resource . 12 4.4 Submit metadata . 12 4.5 Delete metadata 14 4.6
21、Errors . 14 4.6.1 General . 14 4.6.1.1 Introduction . 14 4.6.1.2 Method not supported 14 4.6.1.3 Invalid authorization token . 14 4.6.1.4 Package type not supported 14 4.6.1.5 Content type not supported . 14 4.6.1.6 Deletion not allowed . 15 4.6.1.7 Invalid identifier . 15 4.6.1.8 Invalid source loc
22、ation . 15 4.6.1.9 Schema not supported . 15 4.6.1.10 Metadata validation failure . 15 4.6.1.11 Resource validation failure 15 4.6.1.12 Resource not retrieved . 15 4.6.1.13 Overwriting not allowed . 15 4.6.1.14 Method failure 15 4.7 SPI target configurations . 15 4.8 Authentication . 16 5 Conclusion
23、 17 Bibliography . 18 DIN EN 16425:2014-10 EN 16425:2014 (E) 3 Foreword This document (EN 16425:2014) has been prepared by Technical Committee CEN/TC 353 “Information and Communication Technologies for Learning, Education and Training”, the secretariat of which is held by UNI. This European Standard
24、 shall be given the status of a national standard, either by publication of an identical text or by endorsement, at the latest by January 2015, and conflicting national standards shall be withdrawn at the latest by January 2015. Attention is drawn to the possibility that some of the elements of this
25、 document may be the subject of patent rights. CEN and/or CENELEC shall not be held responsible for identifying any or all such patent rights. This document contains the requirements for the Simple Publishing Interface (SPI), a protocol for storing educational materials in a repository. This protoco
26、l facilitates the transfer of metadata and content from tools that produce learning materials to applications that persistently manage learning objects and metadata, but is also applicable to the publication of a wider range of digital objects. According to the CEN/CENELEC Internal Regulations, the
27、national standards organizations of the following countries are bound to implement this European Standard: Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia,
28、 Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom. DIN EN 16425:2014-10 EN 16425:2014 (E) 4 1 Scope This European Standard specifies the Simple Publishing Interface (SPI), an abstract protocol
29、for publishing digital content and/or the metadata that describes it into repositories in a way that preserves the references between the two. This protocol is designed to facilitate the transfer of learning materials from tools that produce learning materials to applications that manage learning ob
30、jects and metadata. It is also applicable to the publication of a wider range of digital objects. The objectives behind SPI are to develop practical approaches towards interoperability between repositories for learning and applications that produce or consume educational materials. Examples of repos
31、itories for learning include educational brokers, knowledge pools, institutional repositories, streaming video servers, etc. Examples of applications that produce these educational materials are query and indexation tools, authoring tools, presentation programs, content packagers, etc. Whilst the de
32、velopment of the SPI specification draws exclusively on examples from the education sector, it is recognised that the underlying requirement to publish content and metadata into repositories crosses multiple application domains. This abstract model has been designed to be implemented using existing
33、specifications such as v1.3 Simple Web-service Offering Repository Deposit (SWORD) profile SWORD, Package Exchange Notification Services PENS and the publishing specification that was developed in the ProLearn Network of Excellence PROLEARN SPI. The intent of this work is thus not to create yet anot
34、her specification but to create a model that can be bound to existing technologies in order to make sure that these technologies are used in a way that takes into account requirements specific to the learning domain, where it is necessary to publish both content and metadata that references it in a
35、way that preserves these references. The SPI model enumerates the different messages that are interchanged when publishing metadata and content. 2 Terms and definitions For the purposes of this document, the following terms and definitions apply and are used to distinguish the requester from the sys
36、tem that publishes an entity (a metadata instance or a learning object): 2.1 source system that issues a publication request. Alternatively, this system can be labelled as requester 2.2 target system to which publication requests are sent. This can be a repository component or a middle layer compone
37、nt. Such a middle layer component can fulfil several tasks. It can generate and attach metadata to a resource, disaggregate and publish more granular components or act for instance as an adapter to a third party publishing API (application programming interface) NOTE The terms “client” and “server”
38、have not been used in order to avoid any bias towards an interface that is only applicable in client/server applications. Moreover, the scenarios in which the API is used also envisage a source running on a server (e.g., publishing from within an LMS). In the remainder of this document, the terms “r
39、esource”, “digital content”, “learning object” and “educational material” are used interchangeably. DIN EN 16425:2014-10 EN 16425:2014 (E) 5 3 Requirements and design principles 3.1 General In this clause, some of the requirements for a publishing API are identified. These requirements stem from dif
40、ferent repository architectures where learning resources and metadata instances need to be communicated across system boundaries. SPI enables applications to upload learning resources or metadata to a repository. For example, Figure 1 illustrates how an authoring tool (e.g., OpenOffice) could use SP
41、I to upload a resource directly into a repository. A Learning Management System (LMS) (e.g., Moodle, Blackboard) could enable teachers to publish their materials transparently into a repository. By doing so, materials are simultaneously made available to students and published into a repository wher
42、e they can be reused. Figure 1 Example SPI architectures SPI also enables flexible architectures where a middleware component gathers learning resources or metadata through an SPI interface (from authoring tools or harvesters), applies value adding operations on these, and then stores them into a ba
43、ckend repository. Examples of such operations are disaggregation of material into small reusable components, automatic generation of metadata and validation or translation services. Figure 2 AloCom architecture Such architecture has been implemented in the context of the AloCom project (Figure 2). A
44、LOCOM. This architecture contains a plug-in for MS PowerPoint, a source that can publish to a middle layer application, which is the target of this publishing operation. Next, the AloCom middleware disaggregates the material into small reusable components such as diagrams, individual slides, etc. an
45、d automatically generates metadata for each component. Each individual component is then published by the middleware component into a specialised AloCom repository where individual components are available for reuse. The AloCom middleware acts as a source and the AloCom repository as target. Interop
46、erability in both publishing steps is important. First, as several applications (not only MS PowerPoint) require publishing access to the middle layer application, the publishing process from within end-user DIN EN 16425:2014-10 EN 16425:2014 (E) 6 applications needs standardization. Secondly, the m
47、iddle layer application shall be interoperable with other repositories, to promote interchangeability of components. 3.2 Syntactic versus semantic interoperability The design of the SPI API is based on the design principles of the simple query interface (SQI) SQI. As such a simple set of commands th
48、at is extensible and flexible have been defined. By analogy with SQI, this protocol makes the following distinction between semantic and syntactic interoperability: syntactic interoperability is the ability of applications to deal with the structure and format of data. For instance, a language such
49、as XML Schema Description (XSD) ensures the syntactic interoperability of XML documents as it allows for the parsing and validation of these documents; semantic interoperability refers to the ability of two parties to agree on the meaning of data or methods. When exchanging data, semantic interoperability is achieved when data are interpreted the same way by all the applications involved. This European Standard tackles semantic interoperability for SPI. Without a binding (e.g., a REST binding) this speci
