Skip to content
Snippets Groups Projects
Commit 26f3b4b0 authored by PTSEFTON's avatar PTSEFTON
Browse files

edits

parent 7d77abc6
Branches
No related merge requests found
No preview for this file type
......@@ -185,41 +185,35 @@ For example, using this [sample from the bagit-ro tool]
There is a section that lists aggregated files:
"aggregates": [
{ "uri": "../data/numbers.csv",
"mediatype": "text/csv"
},
>"aggregates": [
>
> { "uri": "../data/numbers.csv",
> "mediatype": "text/csv"
> },
And a separate place to describe *annotations* on those files:
"annotations": [
{ "about": "../data/numbers.csv",
"content": "annotations/numbers.jsonld",
"createdBy": {
"name": "Stian Soiland-Reyes",
"orcid": "http://orcid.org/0000-0001-9842-9718"
}
}
>"annotations": [
>
>{ "about": "../data/numbers.csv",
> "content": "annotations/numbers.jsonld",
> "createdBy": {
> "name": "Stian Soiland-Reyes",
> "orcid": "http://orcid.org/0000-0001-9842-9718"
> }
>}
With the actual description of the numbers.csv file residing in `annotations/numbers.jsonld`.
{ "@context": { "@vocab": "http://purl.org/dc/terms/", "dcmi": "http://purl.org/dc/dcmitype/Dataset"},
"@id": "../../data/numbers.csv",
"@type": "dcmi:Dataset",
"title": "CSV files of beverage consumption",
"description": "A CSV file listing the number of cups/mugs consumed per person."
}
The
The PAV ontology used by has several
>{ "@context": { "@vocab": "http://purl.org/dc/terms/", "dcmi": "http://purl.org/dc/dcmitype/Dataset"},
> "@id": "../../data/numbers.csv",
> "@type": "dcmi:Dataset",
> "title": "CSV files of beverage consumption",
> "description": "A CSV file listing the number of cups/mugs consumed per person."
>}
Our experience in implementing systems tells us that it very likely that in real
life
- The ontology they use based on PROV is all about nuanced kinds of authorship
- The PAV ontology they use based on PROV is all about nuanced kinds of authorship
that we don't think implementers will get right
- Uses lots of little files
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment