Open jonquet opened 1 week ago
Our internal model for properties is too light. It does not contains domain and range that are among the miniml info we need to have about a property.
For instance: https://data.agroportal.lirmm.fr/ontologies/C3POPARAM/properties/http%3A%2F%2Fwww.elzeard.co%2Fontologies%2Fc3po%2Fparameter%23maxValue?display=all
Ultimatly, implementing this means adding a "properties" attrtibute to the model of Property that will allow us to see all the properties of a property exaclty like we see all the ones from a class e.g., https://data.agroportal.lirmm.fr/ontologies/C3POPARAM/classes/http%3A%2F%2Fwww.elzeard.co%2Fontologies%2Fc3po%2Fparameter%23Length?display=all&apikey=2ae6878b-a599-4cee-8224-e8efaf6f610e And among all those properties (that in most cases will show up in the UI in the Raw data section) some need to be "mapped" to our common model, including domain and range.
In our mapped properties I propose to encode this rdfs:domain adn rdfs:range properties.
Related to https://github.com/ontoportal-lirmm/bioportal_web_ui/issues/708 fro the UI
Our internal model for properties is too light. It does not contains domain and range that are among the miniml info we need to have about a property.
For instance: https://data.agroportal.lirmm.fr/ontologies/C3POPARAM/properties/http%3A%2F%2Fwww.elzeard.co%2Fontologies%2Fc3po%2Fparameter%23maxValue?display=all
Ultimatly, implementing this means adding a "properties" attrtibute to the model of Property that will allow us to see all the properties of a property exaclty like we see all the ones from a class e.g., https://data.agroportal.lirmm.fr/ontologies/C3POPARAM/classes/http%3A%2F%2Fwww.elzeard.co%2Fontologies%2Fc3po%2Fparameter%23Length?display=all&apikey=2ae6878b-a599-4cee-8224-e8efaf6f610e And among all those properties (that in most cases will show up in the UI in the Raw data section) some need to be "mapped" to our common model, including domain and range.
In our mapped properties I propose to encode this rdfs:domain adn rdfs:range properties.