Skip to content
This repository was archived by the owner on Aug 2, 2018. It is now read-only.

Improve introduction#12

Open
shsdev wants to merge 2 commits into
DILCISBoard:masterfrom
shsdev:master
Open

Improve introduction#12
shsdev wants to merge 2 commits into
DILCISBoard:masterfrom
shsdev:master

Conversation

@shsdev

@shsdev shsdev commented Jul 4, 2018

Copy link
Copy Markdown
Collaborator

Addressing issue #11

The last "ultimate goal" is a repetition of the first bullet point (removed).

Addressed "interoperability between systems/repositories" instead of "interoperability between information packages".

General proof-reading added.

shsdev added 2 commits July 4, 2018 11:32
The last "ultimate goal" is a repetition of the first bullet point (removed).

Addressed "interoperability between systems/repositories" instead of "interoperability between information packages".
General proof-reading of the introduction.
One correction at the end also relates to:
DILCISBoard#12
Comment thread introduction/index.md
This document introduces the concept of a Common Specification for Information Packages. It aims to serve three main purposes:

1. Establish a common understanding of the requirements which need to be met in order to achieve interoperability of Information Packages;
1. Establish a common understanding about the requirements which need to be met in order to achieve interoperability between repositories and other information systems with respect to the use of Information Packages;

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This changes the focus of the introduction from IP interoperability to system interoperability. Isn't it too limiting?

@shsdev shsdev Jul 4, 2018

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The idea behind the proposed change is that "interoperability" it is actually about (repository) systems being able to handle the information packages.
In this sense, interoperability is not a characteristic of the information package, but the use of E-ARK compliant information packages is a means to achieve system interoperability.
Regarding the CS defining a common base for SIP, AIP, and DIP the purpose is also to make conversions - from SIP to AIP or from AIP(s) to DIP - more efficient. Here it is about interoperability between the systems or modules for SIP creation, storage, or access.

@kuldaraas kuldaraas added the help wanted Extra attention is needed label Jul 11, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

help wanted Extra attention is needed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants