EN 16425:2014

• Abstract:

  This European Standard specifies the Simple Publishing Interface (SPI), an abstract protocol 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 objects 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 repositories 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 development 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 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 another 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 way that preserves these references.; The SPI model enumerates the different messages that are interchanged when publishing metadata and content.

• Status: Published
• Publication Date: 08-Jul-2014
• Withdrawal Date: 30-Jan-2015
• ICS: 35.240.30 - IT applications in information, documentation and publishing
• ICS: 35.240.99 - IT applications in other fields
• Technical Committee: CEN/TC 353 - Information and Communication Technologies for Learning, Education and Training
• Drafting Committee: CEN/TC 353 - Information and Communication Technologies for Learning, Education and Training
• Current Stage: 9060 - Closure of 2 Year Review Enquiry - Review Enquiry
• Start Date: 02-Sep-2025
• Completion Date: 02-Sep-2025
• Ref Project: SIST EN 16425:2014 - Simple Publishing Interface

Overview

EN 16425:2014 - Simple Publishing Interface (SPI) is a CEN European Standard that defines an abstract protocol for publishing digital content and the metadata that describes it into repositories while preserving the references between content and metadata. Designed originally for the education sector, SPI supports interoperability between tools that produce learning materials (authoring tools, content packagers, LMS plugins) and applications that manage learning objects and metadata (institutional repositories, educational brokers, streaming servers).

Key topics and technical requirements

• Preserve content–metadata references: SPI requires that relationships between a digital resource and its descriptive metadata are maintained during publication.
• Abstract protocol model: SPI is an abstract model (semantic interoperability) intended to be bound to concrete transport/binding technologies to achieve syntactic interoperability.
• Support for “by value” and “by reference” publishing:
  • By value: embedding resources in the publish message (useful for desktop or isolated clients).
  • By reference: providing a reference/URL so the target retrieves the resource (suitable for large files).
• Defined message classes: the model enumerates standard messages such as submit resource, delete resource, submit metadata, delete metadata, and error reporting.
• Flexible deployment: supports direct publishing to repositories and middleware architectures that transform, disaggregate, validate, or enrich content before storage.
• Authentication and error handling: SPI specifies authentication considerations and a taxonomy of errors (e.g., invalid token, validation failure, unsupported content type).
• Design principles: focuses on minimal, extensible commands and separation of data and metadata to enable reuse across varied repository types.

Applications and who should use it

• Repository implementers (institutional repositories, knowledge pools, streaming video servers) to accept standardized publish requests while preserving metadata links.
• LMS and authoring tool vendors (Moodle, Blackboard plugins, PowerPoint add-ins) to integrate one-click publishing from authoring workflows.
• Middleware and integration platforms that disaggregate content, auto-generate metadata, validate packages, or adapt to third‑party repository APIs.
• Content packagers, indexers, and harvesters to push learning objects and metadata into interoperable back-ends.
• Digital library and educational technology architects seeking practical interoperability between producers and consumers of learning resources.

Related standards and bindings

• SWORD v1.3 (Simple Web-service Offering Repository Deposit) - example binding technology.
• PENS (Package Exchange Notification Services) - example for package submission.
• PROLEARN SPI - earlier publishing specification used in design.
• Other complementary technologies mentioned: OAI‑PMH, SQI, and MACE architectures for metadata enrichment.

EN 16425:2014 is valuable for teams implementing interoperable publishing flows for learning objects and broader digital content, enabling consistent publication practices across educational and repository ecosystems.

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Vmesnik za enostavno objavljanjeSchnittstelle für einfaches PublizierenInterface de publication simpleSimple Publishing Interface35.240.30Uporabniške rešitve IT v informatiki, dokumentiranju in založništvuIT applications in information, documentation and publishingICS:Ta slovenski standard je istoveten z:EN 16425:2014SIST EN 16425:2014en,fr01-oktober-2014SIST EN 16425:2014SLOVENSKI
STANDARD
EUROPEAN STANDARD NORME EUROPÉENNE EUROPÄISCHE NORM
EN 16425
July 2014 ICS 35.240.30; 35.240.99 English Version
Simple Publishing Interface
Interface de publication simple
Schnittstelle für 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 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 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 versions.
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, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and United Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION EUROPÄISCHES KOMITEE FÜR NORMUNG
CEN-CENELEC Management Centre:
Avenue Marnix 17,
B-1000 Brussels © 2014 CEN All rights of exploitation in any form and by any means reserved worldwide for CEN national Members. Ref. No. EN 16425:2014 ESIST EN 16425:2014

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 backend 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). [ALOCOM]. 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. and 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. Interoperability 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 SIST EN 16425:2014

Figure 3 — The MACE harvesting architecture 3.5 Objectives This publishing protocol meets the following objectives: • SPI enables integrating publishing into authoring environments. This is beneficial for the author workflow, as they do not need to manually upload their learning objects using external publishing applications; • SPI provides interoperability between applications that publish and applications that manage learning objects and metadata. Doing so, the effort of integrating publishing access into an authoring application can be reused on other learning object repositories, provided that they support SPI. 4 SPI Model 4.1 General The model for SPI builds on a separation between data and metadata. The SPI model defines several classes of messages and functional units in a publishing architecture. When binding the specification to a given technology, these concepts are mapped into a concrete specification that can be implemented in a repository and for which conformance can be tested. All messages that are defined by the SPI model contain mandatory (M) and optional (O) elements. Mandatory means that a binding cannot relax this condition. A binding shall implement a mandatory attribute and shall make it mandatory as well. A binding can deal with optional elements in three ways. It can opt not to include the element, it can include the element and make it optional, or it can include the element and make it mandatory. A binding might for instance choose to not support transporting the filename attribute, or an SPI binding can offer support for the filename attribute while still allowing the source to provide a null value for this element. Depending on the choices made when implementing an SPI target, the latter can be configured in different ways and sources shall know the exact configuration of a target in order to be able to use it. As a consequence, the configuration of an SPI target shall be exposed to sources using at least one of the strategies presented in 4.7. As shown by the class diagram of Figure 4, with SPI, a resource shall have an identifier (that can either be generated by a target or a source). In addition, the resource may have a filename associated. Every resource SIST EN 16425:2014

Figure 4 — Resource and metadata instance In this model, a metadata instance shall be connected to a resource. However the resource may be hosted externally. In such a case, ingesting the resource is not part of the publishing scenario. For instance, when applying SPI to a referatory, only the messages described in 4.4 are implemented. Alternatively, resources can be published without
...