An aggregated annotation MUST be listed as an aggregation

Fixes #4
Merge pull request #5 from hainesr/fix-annotation-description

An aggregated annotation MUST be listed as an aggregation
respec.js 3.2.18
Remove redundant <pre> content

(as newer respec correctly includes them even from file:///)
ROSRS service -> web service
Issue #6: Avoid polymorphic aggregates list

Values now always have to be objects
Issue #6: Always object-form in "aggregates"
Issue #3: annotation content MUST be in .ro/annotations/

.. unless it is an absolute URI or is listed under
'aggregates'
about base URI
localBiblio rather than adding biblio pr js
app: URI scheme suggests (no longer recommends) UUID :/
anchors for JSON elements
Updated FOAF reference 0.99

See also tobie/specref#114
USe full { "uri": .. } style for aggregate examples
Relax requirement for additional statements in @graph
Wf4Ever Research Object -> Research Object
editor draft URI
Fix syntax for Example 5 (Custom JSON-LD)
Clarify custom json. STRONG!
"file" -> "uri" within "aggregates"