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
Is your feature request related to a problem? Please describe.
I really appreciate the new update of the software and documentation.
It seems that the config.properties cannot be completely dropped yet. Some vocabulary annotations do not have an equivalent annotation property (extended-/importedOntologyNames/-URIs; latestVersionURI), while some others are overwritten/superseded by the ones from the config file (ontologyName; dateOfRelease).
As an example, the table of content snapshot was generated asasigning rdfs:label in the TTL and commenting ontologyName in the config.
An overview of the missing/problematic fields is given in the table below.
Metadata category
Ontology annotation property*
config.properties field(s)**
Remarks
Modification date
dcterms:modified, schema:dateModified
modified, dateOfRelease
dateOfRelease supersedes modified
Ontology name
???
ontologyName
rdfs:label does not work: requires ontologyName
Extended ontologies
???
extendedOntologyNames, extendedOntologyURIs
only in config.properties, not in TTL
Imported ontologies
owl:imports?
importedOntologyNames, importedOntologyURIs
only in config.properties, not in TTL
Latest version
???
latestVersionURI
only in config.properties, not in TTL
Serialization
???
RDFXML-/Turtle-/N3-/JSONLDSerialization
only in config.properties, not in TTL
Describe the solution you'd like
Either we find and implement suitable annotation properties, or we specify in the two guides that some annotations should be input necessarily through the config file.
I can help with the documentation.
The text was updated successfully, but these errors were encountered:
Ontology Name should be the title, if I remember correctly. And the latest version is driven (or should be) by vann:preferredNamespaceUri. I will have to have a look at the others. There is an overlap with recent issues, but I do agree these problems are pressing
Ontology Name should be the title, if I remember correctly. And the latest version is driven (or should be) by vann:preferredNamespaceUri. I will have to have a look at the others. There is an overlap with recent issues, but I do agree these problems are pressing
vann:preferredNamespaceUri is the current version (not necessarily the last one).
ontologyName is just one word (ex.: "Metadata4Ing") while the ontologyTitle is a half-sentence (ex.: "Metadata4Ing: An ontology for describing the generation of research data within a scientific activity.")
The namespace URI is the ontology URI, so it should be the one for last version (it should not change across different versions). owl:versionIRI should be the one for this version. Don't you agree?
I agree about the title. Maybe we can use the rdfs:label of the ontology.
Is your feature request related to a problem? Please describe.
I really appreciate the new update of the software and documentation.
It seems that the
config.properties
cannot be completely dropped yet. Some vocabulary annotations do not have an equivalent annotation property (extended-/importedOntologyNames/-URIs; latestVersionURI), while some others are overwritten/superseded by the ones from theconfig
file (ontologyName; dateOfRelease).As an example, the table of content snapshot was generated asasigning rdfs:label in the TTL and commenting ontologyName in the config.
An overview of the missing/problematic fields is given in the table below.
config.properties
, not in TTLconfig.properties
, not in TTLconfig.properties
, not in TTLconfig.properties
, not in TTLDescribe the solution you'd like
Either we find and implement suitable annotation properties, or we specify in the two guides that some annotations should be input necessarily through the config file.
I can help with the documentation.
The text was updated successfully, but these errors were encountered: