This pull request introduces a rewrite of the spec. It now defines 2 big chapters: an ontology, which is kept simple and is now hosted at https://w3id.org/tree, and 4 application profile building blocks.
Clients can choose to implement any individual building block. The four building blocks are related to:
Discovery
Traversing a tree:Node’s tree:hasChildRelation for more specific information
Search forms to e.g. use a search form for geospatial tiles cfr. OpenStreetMap tiles
Describe Provenance and Summaries of existing tree:Nodes containing actual data
A big change in the spec is that a tree:Node is now explicitly designed to be 1 page. Furthermore, the new spec does not limit itself to only trees. However, every tree:Node a client is currently visiting just has a Tree-like view to go on to a next page, having a tree:ChildRelation to something else.
The README.md has been adapted accordingly and a simplistic vocabulary overview is added as a png.
I’ll merge this one into master as the version in this branch is more stable than the version on master at this moment. Still issues and TODOs open though.
This pull request introduces a rewrite of the spec. It now defines 2 big chapters: an ontology, which is kept simple and is now hosted at
https://w3id.org/tree
, and 4 application profile building blocks.Clients can choose to implement any individual building block. The four building blocks are related to:
tree:Node
’stree:hasChildRelation
for more specific informationA big change in the spec is that a tree:Node is now explicitly designed to be 1 page. Furthermore, the new spec does not limit itself to only trees. However, every tree:Node a client is currently visiting just has a Tree-like view to go on to a next page, having a tree:ChildRelation to something else.
The README.md has been adapted accordingly and a simplistic vocabulary overview is added as a png.