Issue #3 tracks issues having to do with the software used for the wine-ontology.
Editors
One obvious choice would be protege. It seems to read the dbpedia ontology pretty well. IMO it's kinda hard to navigate that tool, and it lacks a graphical interface. There is also the webprotege online tool which seems a bit easier to use and share; multiple users can be added to it. However, it does not import
existing schemas like the desktop client does, this makes it more difficult to implement.
Servers
Another possibility is to more explicitly divide the t-box and a-box components of the project, and use schema.org as a starting point for the t-box (ontology). In this case, we would more directly program the ontology, and then use a fork of the schema.org to build a collaborative site for other people to buy into the ontology. We'd develop the a-box portion sort of separately, though we could probably use the same fork for that. Schema.Org Winery is about the only part of schema.org that currently has any wine related activity. If we went that route, alot of the schema development would probably be taking bits an pieces from dbpedia, and I'm not sure how useful that is
Issue #3 tracks issues having to do with the software used for the wine-ontology.
Editors
One obvious choice would be protege. It seems to read the dbpedia ontology pretty well. IMO it's kinda hard to navigate that tool, and it lacks a graphical interface. There is also the webprotege online tool which seems a bit easier to use and share; multiple users can be added to it. However, it does not import existing schemas like the desktop client does, this makes it more difficult to implement.
Servers
Another possibility is to more explicitly divide the t-box and a-box components of the project, and use schema.org as a starting point for the t-box (ontology). In this case, we would more directly program the ontology, and then use a fork of the schema.org to build a collaborative site for other people to buy into the ontology. We'd develop the a-box portion sort of separately, though we could probably use the same fork for that. Schema.Org Winery is about the only part of schema.org that currently has any wine related activity. If we went that route, alot of the schema development would probably be taking bits an pieces from dbpedia, and I'm not sure how useful that is