The standard HTML rendering of a vocabulary element is for RDF afficionados only.
For example
http://cor.esipfed.org/ont/?iri=http://www.w3.org/ns/sosa/Sensor
just lists the immediate properties, using the URIs or literals, or blank-node IDs.
Almost N3.
I realise you won't want to get too far into prettifying this, but maybe one step along the path could make COR/ORR end-user friendly enough.
Ideas:
- Show the Concise Bounded Description (https://www.w3.org/Submission/CBD/) so it doesn't stop at the blank node IDs
- For those properties that have an rdfs:label known to the COR/ORR, show the label in preference to the term URI (maybe show the term URI in a smaller font underneath or alongside)
- The 'standard' RDF vocabularies should be known to COR/ORR, so the rdfs:label for http://www.w3.org/2000/01/rdf-schema#label should be 'built-in' - also OWL, VOAF, DC, dcterms, FOAF, VoID, DCAT, ORG, probably all the OMV vocabs
The standard HTML rendering of a vocabulary element is for RDF afficionados only.
For example
http://cor.esipfed.org/ont/?iri=http://www.w3.org/ns/sosa/Sensor
just lists the immediate properties, using the URIs or literals, or blank-node IDs.
Almost N3.
I realise you won't want to get too far into prettifying this, but maybe one step along the path could make COR/ORR end-user friendly enough.
Ideas: