Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Software component ontology"
(→Core properties and classes) |
(→Core properties and classes) |
||
| Line 19: | Line 19: | ||
- ''Implemented API or frameworks'' (i.e. EJB 3.0 specification, or the JDBC API). | - ''Implemented API or frameworks'' (i.e. EJB 3.0 specification, or the JDBC API). | ||
| + | |||
| + | - ''Implemented computational tasks''. | ||
- ''Hierarchically organized common features'' (i.e.: logging, persistence, parsing; Maven Repository’s tags cloud could be taxonomically organized, acting as a good starting point to formally describe software libraries in terms of functional features and areas). | - ''Hierarchically organized common features'' (i.e.: logging, persistence, parsing; Maven Repository’s tags cloud could be taxonomically organized, acting as a good starting point to formally describe software libraries in terms of functional features and areas). | ||
| + | |||
| + | |||
| + | == Reuse of existing ontologies == | ||
| + | |||
| + | A good and thorough axiomatization of the software component domain is given in the [http://cos.ontoware.org/ Core Ontology of Software/Software components/Services]. | ||
| + | |||
| + | It provides a fine granularity model, which could also support future developments of the project, i.e. formal semantic tagging of methods, classes and interfaces. | ||
| + | |||
| + | Reuse chances of the provided set of ontologies is being assessed, but it is very likely to take part. | ||
Latest revision as of 12:24, 9 May 2007
Core properties and classes
Software components shall be described through an OWL ontology.
The model is still in early inception phase. Core properties and classes shall be:
- Product development and release related metadata (i.e. same properties as those captured by Maven POM, OSGi manifest headers and/or DOAP; those schemas could be augmented).
- Reputation
- License information
- License style (capturing different licenses’ similarities could be useful).
- Activity level
- Functionalities:
- Implemented API or frameworks (i.e. EJB 3.0 specification, or the JDBC API).
- Implemented computational tasks.
- Hierarchically organized common features (i.e.: logging, persistence, parsing; Maven Repository’s tags cloud could be taxonomically organized, acting as a good starting point to formally describe software libraries in terms of functional features and areas).
Reuse of existing ontologies
A good and thorough axiomatization of the software component domain is given in the Core Ontology of Software/Software components/Services.
It provides a fine granularity model, which could also support future developments of the project, i.e. formal semantic tagging of methods, classes and interfaces.
Reuse chances of the provided set of ontologies is being assessed, but it is very likely to take part.