Skip to content

Update kernel.md #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Update kernel.md #1

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a5b2f58
Update kernel.md
May 12, 2019
db11578
Update kernel.md
May 12, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
38 changes: 20 additions & 18 deletions kernel.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,28 +16,30 @@ References reviewed:
* PID Kernel WG RDA <https://www.rd-alliance.org/groups/pid-kernel-information-wg> Though focused on PIDs there seems some value in considering this kernel and its potential use with digital objects.
* DID or Decentralized Identifiers <https://w3c-ccg.github.io/did-spec/> is about self sovereign digital identifiers. So again more focused on PIDs but now in a decentralized manner. Still, again this seems to have enough connection to digital objects to merit review.
* Schema.org type DigitalDocument <https://schema.org/DigitalDocument> is looking for something than be associated with a digital object as opposed to a data set or catalog.
* DCAT-2 <https://w3c.github.io/dxwg/dcat/> This section needs attention. Can we leverage DCAT to describe a DO/byte stream as opposed to a data set or catalog as differentiated in the above text.
* DCAT-2 <https://w3c.github.io/dxwg/dcat/> This section needs attention. Can we leverage DCAT to describe a DO/byte stream as opposed to a data set or catalog as differentiated in the above text. DCAT distinguishes between the conceptual resource (Dataset, DataService, ...) and its digital representation. Different sets of properties are used to describe each

Note: No attempt has been made to order these across the rows... that needs to be done

| FDP (resource) | PID | DID | schema.org | DCAT-2 |
| FDP (resource) | PID | DID | schema.org | [DCAT-2](https://w3c.github.io/dxwg/dcat/) |
| --------------------- | ------------------------ | ------------------------ | ------------------------------- | ------ |
| name | pid | id | schema:DigitalDocument | |
| path | KernelInformationProfile | publicKey | schema:name | |
| title | digitalObjectType | authentication | schema:URL | |
| description | digitalObjectLocation | services | schema:about | |
| format | digitalObjectPolicy | service:id | schema:description | |
| mediatype | etag | services:type | schema:encodingFormat | |
| encoding | dateModified | services:serviceEndpoint | schema:fileSize | |
| bytes | dateCreated | | schema:identifier <br />(via PropVal, see below) | |
| hash | version | | schema:isBasedOn | |
| schema | wasDerivedFrom | | schema:license | |
| sources | specialixationOF | | schema:dateModified | |
| license | wasRevisionOF | | schema:dateCreated | |
| | hasPrimarySource | | xyz:Type (domain typing) | |
| | wasQuotedFrom | | | |
| | alternatOF | | | |

| name | pid | id | schema:DigitalDocument | dcat:Dataset |
| path | KernelInformationProfile | publicKey | schema:name | dct:identifier |
| title | digitalObjectType | authentication | schema:URL | dct:title |
| description | digitalObjectLocation | services | schema:about | dct:description |
| format | digitalObjectPolicy | service:id | schema:description | dcat:distribution/dcat:downloadURL|
| mediatype | etag | services:type | schema:encodingFormat | dcat:distribution/dcat:accessURL |
| encoding | dateModified | services:serviceEndpoint | schema:fileSize | dct:conformsTo |
| bytes | dateCreated | | schema:identifier <br />(via PropVal, see below) | dcat:distribution/dct:conformsTo |
| hash | version | | schema:isBasedOn | dcat:distribution/dcat:byteSize |
| schema | wasDerivedFrom | | schema:license | dct:type |
| sources | specialixationOF | | schema:dateModified | dcat:distribution/dcat:mediaType |
| license | wasRevisionOF | | schema:dateCreated | dct:issued|
| | hasPrimarySource | | xyz:Type (domain typing) | dct:modified |
| | wasQuotedFrom | | | dct:relation |
| | alternateOf | | | dcat:qualifiedRelation |
| | | | | dcat:keyword |
| | | | | dcat:theme |
| | | | | dcat:keyword |


This is an example of the current schema:DigitalDocument package we are generating
Expand Down