You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 text was updated successfully, but these errors were encountered:
These are great proposals. I think I've always wanted to prettify this, and maybe SWEET and/or ESIP will prove a motivator for more resources to help get it done.
I'd add to the suggestion list that this view be treated as more of a first-class object, describing everything about the concept that can be readily captured (history and other provenance, highlighting significant changes, usage by mappings, etc.).
Right - CBD+ is a specific graph for each URI.
Therefore it has its own URI, but also may the end destination of a default redirect of the URI for the node.
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:
The text was updated successfully, but these errors were encountered: