Is there somewhere an ontology for ontologies? What would it need?
intended domain
collateral domains
specialization of (some ontology)
generalization of (some ontology)
synonyms (in other ontologies)
antonyms (in other ontologies)
type of (ontological) structures
structure (of this ontology)
main features
based on (foundation ontologies)
classes
taxonomy
links to (other ontologies)
representational units
composite representations
terms
concepts
sounds like
btw @MitziLaszlo, can we add a Linked Data or Linked Data for Solid category?
That seems to be used just to point to different ontologies instead of describing more general differences between them, unless Iâm missing something?
An ontology of ontologies would be useful to describe ontologies so they could be found on a pod according to what they do and how theyâre related, also maybe some measures of their adoption.
âA DCAT profile is a specification for a data catalog that adds additional constraints to DCAT. A data catalog that conforms to the profile also conforms to DCAT.â
Hello,
I donât know of an ontology of ontologies per se, but as @Smag0 pointed out, a lot of the features you describe may be achieved using a combination of well-known ontologies:
"A general issue is determined by the fact that Schema.org and DCAT-AP address different use cases. More precisely, the main purpose of Schema.org is to enhance discovery and indexing of online resources via search engines. As such, it is addressing more general objectives compared with DCAT-AP, that is instead meant to model in detail information on datasets and data catalogues.
One of the main consequences is that some information that is relevant in DCAT-AP it is not modelled in Schema.org with specific terms. This results in a relevant amount of (a) âmissingâ and (b) âmany-to-oneâ mappings - i.e., different metadata elements of DCAT-AP are mapped to the same element in Schema.org."
Unfortunately with DCAT they appear to be developing yet another âstandardâ. It isnât RDF and Iâm not sure it is even JSON-LD.
From my reading it seems to be either a subset of JSON-LD or is a non RDF compliant form of JSON-LD which will make it difficult to work with using tools and libraries that are built for RDF.
It isnât clear, but it may be that theyâve designed it so that they can consume RDF compatible JSON-LD, but not the other way around. Kind of parasitic.
Perhaps someone who understands the technicalities better than me can correct or confirm.
Hopefully I am wrong and your link does make it clear that DCAT is an RDF ontology.
I think my question is whether they are using it to describe RDF resources or not because the description of its use doesnât mention RDF, only JSON and JSON-LD, and describes how much of the JSON-LD is optional which Iâm taking as meaning it is not RDF compliant.
However, for your purposes you can still use DCAT in RDF resources.
So maybe it is more that they are using an RDF ontology to define their non RDF compliant schema?