Closed cpfaff closed 8 years ago
This is the first commit: a1891513cf44676199052f121c41405e94aeb25d
@naouelkaram I have a question. Currently we have the following structure:
Thing
Location
Continent
List of continents ...
Country
List of countries ...
I would rather like to be more general so that it is possible to just list all locations just in a flat list. And then describe that there is a type and then have there under location type Continent Country and whatever else will come. How to best do that.
@naouelkaram Sorry I saved the comment before it was finished.
Well that would directly go into very much detail and complexity. I just want to discuss what we really need and what the best solution is to represent it in the owl file. If we want to simply just list what concepts we have then the structure above is fine. If we want something that is extendable (which would be cool) then I would add a more generic structure that allows to learn from new annotations. How would this look like? In a tool that guides through the annotation process we ask the user to specify a location name and then to classify it. The classification represents a location type and the name well is a location name. Currently this is not possible with the schema that we have.
I am just playing around. Now we have the structure:
Thing
Location
List of location names here ...
Location Type
Country
Continent
And we have an object property that says hasType. That would for example allow: Lets say we are tagging search objects to fetch all search objects that are tagged with a specifiy location from the list. Or we can ask get me all search objects that are tagged with a country.
Or at least we can do that if the locations are linked with the property to the types. Could you assist with that @naouelkaram
This is the first issue for the owl vocabulary. I will start to add more concepts to the location to form the backbone. I will create new issues with descriptions that will involve you @naouelkaram if wee need support for more complex stuff.