Commit 55fe5655 authored by Mark Jordan's avatar Mark Jordan
Browse files

Updated README.

parent 7a753560
......@@ -47,19 +47,6 @@ BagItLD provide a simple RDF syntax that is compatible with the structure of bag
## Implementation
#### BagItLD statements and ordinary BagIt tags can coexist
Since BagItLD statements respect the conventions of bag-info.txt tags, they can coexist peacefully with ordinary tags in the same bag-info.txt file.
```
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]
Internal-Sender-Identifier: bag_03
Source-Organization: Simon Fraser University Library
Contact-Email: mjordan@sfu.ca
```
#### Bags are blank nodes
The Bag is a blank RDF node and is understood to be the subject of the RDF statement. If it is the object of an RDF statement, it must be referenced using `[]` (we use SPARQL's `[]` to refernce blank nodes; we can't use `_:b` because of colon has structural significance within bag-info.txt).
......@@ -79,6 +66,20 @@ In this example, the 'dc' suffix constrains 'Title', 'Date', and 'Subject' to th
Why "suffixes" and not "prefixes"? Because we can't use a colon to separate a namespace from a property as we do with XML namespaces (the colon is reserved by the BagIt specification), we use the `@` symbol. Following the convention established by email addresses, where the username precedes the `@` and the domain follows it is pure syntactic sugar.
#### BagItLD statements and ordinary BagIt tags can coexist
Since BagItLD statements respect the conventions of bag-info.txt tags, they can coexist peacefully with ordinary tags in the same bag-info.txt file.
```
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]
Internal-Sender-Identifier: bag_03
Source-Organization: Simon Fraser University Library
Contact-Email: mjordan@sfu.ca
```
## Serialization
To test BagItLD against other RDF syntaxes, we can serialze the statements we have been using as examples above into a variety of popular syntaxes.
......
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