Skip to content
This repository has been archived by the owner on Jun 15, 2018. It is now read-only.

Link/integrate with Platform ontology? #9

Open
GoogleCodeExporter opened this issue Mar 13, 2015 · 1 comment
Open

Link/integrate with Platform ontology? #9

GoogleCodeExporter opened this issue Mar 13, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

Description of the issue

Do we need/want/should integrate with the MMI Platform ontology?

In principle, I'd say, we should.  However, I'm not sure about the
structure of the platform ontology in particular regarding concepts that we
already have in DevOnt. Perhaps harmonization would be necessary, implying
updates to the platform ontology as well.

Please provide any relevant information/links below

http://marinemetadata.org/community/teams/ontplatforms

http://mmisw.org/orr/#http://mmisw.org/ont/mmi/platform

Original issue reported on code.google.com by [email protected] on 19 May 2010 at 10:49

@GoogleCodeExporter
Copy link
Author


I quickly glanced over the platform ontology using Protege 4. It does have an
Instrument class with subclasses Sensor and Sample.  Instrument's usage shows a
connection between Instrument and Platform:

Platform isBaseConnectionOf [Instrument or Platform]

See attached screenshot.

I also generated a diagram for the platform ontology:
    http://marinemetadata.org/files/mmi/platform.png  (1MB)

Thoughts?

Original comment by [email protected] on 20 May 2010 at 2:23

  • Added labels: Component-DevOnt, Component-PlatOnt
  • Removed labels: DevOnt, PlatOnt

Attachments:

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant