BS EN 16425:2014
$102.76
Simple Publishing Interface
Published By | Publication Date | Number of Pages |
BSI | 2014 | 22 |
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.
PDF Catalog
PDF Pages | PDF Title |
---|---|
4 | Contents Page |
5 | Foreword |
6 | 1 Scope 2 Terms and definitions |
7 | 3 Requirements and design principles 3.1 General Figure 1 — Example SPI architectures Figure 2 — AloCom architecture |
8 | 3.2 Syntactic versus semantic interoperability 3.3 “By reference” and “by value” publishing 3.4 Flexible application |
9 | Figure 3 — The MACE harvesting architecture 3.5 Objectives 4 SPI Model 4.1 General |
10 | Figure 4 — Resource and metadata instance 4.2 Submit a resource 4.2.1 General |
11 | 4.2.2 Resource submission by value Figure 5 — By value publishing of a resource Table 1 |
12 | Table 2 4.2.3 Resource submission by reference |
13 | Figure 6 — By reference publishing of a resource Table 3 |
14 | Table 4 4.3 Delete resource Table 5 4.4 Submit metadata |
15 | Figure 7 — Publishing of a metadata instance Table 6 |
16 | Table 7 4.5 Delete metadata Table 8 4.6 Errors 4.6.1 General 4.6.1.1 Introduction 4.6.1.2 Method not supported 4.6.1.3 Invalid authorization token 4.6.1.4 Package type not supported 4.6.1.5 Content type not supported |
17 | 4.6.1.6 Deletion not allowed 4.6.1.7 Invalid identifier 4.6.1.8 Invalid source location 4.6.1.9 Schema not supported 4.6.1.10 Metadata validation failure 4.6.1.11 Resource validation failure 4.6.1.12 Resource not retrieved 4.6.1.13 Overwriting not allowed 4.6.1.14 Method failure Table 9 4.7 SPI target configurations |
18 | Table 10 4.8 Authentication |
19 | 5 Conclusion |
20 | Bibliography |