Commit db10a631 authored by Mark Jordan's avatar Mark Jordan
Browse files

Updated README.

parent d7eba0aa
......@@ -38,7 +38,7 @@ but allows other arbitrary tags to exist within bag-info.txt provided they confo
Linked Data structures share a three-part "subject", "predicate", "object" pattern. The contents of bag-info.txt are "are intended primarily for human readability".
```
bagitldprefix@dc: http://purl.org/dc/elements/1.1/
bagitldsuffix@dc: http://purl.org/dc/elements/1.1/
Title@dc: I am a title
Date@dc: 2017-06-20
Subject@dc: [Testing stuff, Linked Data]
......@@ -53,6 +53,17 @@ BagItLD provide a simple RDF syntax that is compatible with the structure of bag
The Bag is a blank node and is assumed to be the subject of the RDF statement. If it is the object of an RDF statement, it must be referenced using `[]` (we use the SPARQL `[]` to refernce blank nodes; we can't use `_:b` because of colon has structural meaning within bag-info.txt).
BagiItLD provides shorthand for RDF vocabularies through "suffixes". Suffixes associate a vocabulary with a suffix that is used within the tags in the same bag-info.txt file, much like XML namespace declarations associate namespace prefixes with namespace URIs. Suffixing is accomplished by tags that start with "bagitldsuffix@" and end in a locally defined suffix. The value of a bagitldsuffix tag is the namespace to be represented by the suffix. The suffix then can be used in the tags as shorthand for properties from the vocabulary in the form `property@suffix`.
```
bagitldsuffix@dc: http://purl.org/dc/elements/1.1/
Title@dc: I am a title
Date@dc: 2017-06-20
Subject@dc: [Testing stuff, Linked Data]
```
In this example, the 'dc' suffix constrains 'Title', 'Date', and 'Subject' to the 'http://purl.org/dc/elements/1.1/` vocabulary.
## Serialization
### RDF/XML
......@@ -62,6 +73,13 @@ The Bag is a blank node and is assumed to be the subject of the RDF statement. I
### N-Triples
_: <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://www.openarchives.org/ore/terms/Aggregation> .
_: <http://purl.org/dc/terms/title> "I am a title" .
_: <http://purl.org/dc/terms/date> 2017-06-20 .
_: <http://purl.org/dc/terms/subject> "Testing stuff" .
_: <http://purl.org/dc/terms/subject> "Linked Data" .
### JSON-LD
## Alternatives
......@@ -83,7 +101,7 @@ Why not put Turtle data (for example) in an optional tag file as described in se
Possible answers: bag-info.txt is optional, but it is widely used and most implementations probably assume it to be present. While it is possible to specify the requirement for additional tagfiles using a [BagIt Profile](https://github.com/ruebot/bagit-profiles), the presence of an additional tagfile conforming to a specific Linked Data structure would be purely optional. Which is fine.
BagItLD is quite human readable, despite its use of namespaces/prefixes. At least as humanly readable as other Linked Data structures.
BagItLD is quite human readable, despite its use of namespaces/suffixes. At least as humanly readable as other Linked Data structures.
......@@ -93,4 +111,4 @@ BagItLD is quite human readable, despite its use of namespaces/prefixes. At leas
To the extent possible under law, Mark Jordan has waived all copyright and related or neighboring rights to this work. This work is published from: Canada.
https://git.lib.sfu.ca/mjordan/bagitld/edit/master/README.md
\ No newline at end of file
https://git.lib.sfu.ca/mjordan/bagitld/edit/master/README.md
Supports Markdown
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