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"
(New page: '''Software components''' shall be described through an '''OWL ontology.''' Core properties and classes shall be: - Product development and release related metadata (i.e. same properties...) |
|||
Line 1: | Line 1: | ||
+ | == Core properties and classes == | ||
+ | |||
'''Software components''' shall be described through an '''OWL ontology.''' | '''Software components''' shall be described through an '''OWL ontology.''' | ||
Revision as of 06:25, 28 April 2007
Core properties and classes
Software components shall be described through an OWL ontology.
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).
- 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).