Take into account lessons learned from SWIB18

[acka47]

Although, we won't change a lot from the original SWIB workshop, there are some things to be improved. We collect those here:

• [x] Use Zotero API as example for JSON API instead of GitHub (#1)
• [x] Add Rob Pike quote? (see annotation)
• [ ] ~Use other "fix context example" as rdf:value should be @value in JSOn-LD (see SWIB18 slides 68f~

[acka47]

Re.

Use other "fix context example" as rdf:value should be @value in JSOn-LD

I was wrong thinking that @value and rdf:value have something to do with each other more than their label. rdf:value is rarely used. In Bibframe identifiers are made entities so that they can be made members of a class by using rdf:typeon them, e.g.:

<http://id.loc.gov/resources/works/c000000033> bf:identifiedBy [
  a <http://id.loc.gov/ontologies/bibframe/Local> ;
  rdf:value "33" .

This is a different thing than a typed value/literal e.g.:

<http://id.loc.gov/resources/works/c000000033> bf:identifiedBy "33"^^<http://www.w3.org/2001/XMLSchema#integer> .

And @value in JSON-LD is only used for typed literals so it would be wrong to use it on Bibframe identifiers.

I am sceptical that it could be called good practice how Bibframe is doing this. rdf:value doesn't seem to be used much in the wild. However, regardingthe workshop, everything is fine and we do not need to change anything. Thus, closing this issue