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

Material #23

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

Material #23

GoogleCodeExporter opened this issue Mar 13, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

Description of the issue or change request

1) Device hasConstructionMaterial Material, where Material is a subclass of 
PhysicalProperty.  So far, no properties are associated with Material, mainly 
because, as with other places in DevOnt, this is basically more a placeholder 
while more elaboration is done.  This issue is about how to actually capture 
materials for the devices.  

This can/should be done by referring to definitions in a suitable external 
ontology, for example the SWEET Substance ontology: 
http://sweet.jpl.nasa.gov/1.1/substance.owl

2) Also, should Material be a subclass of ValuedPhysicalProperty, that is, to 
be able to say that a certain device has a certain material with some value 
associated, presumably a percent of that material in the composition of the 
device?

Original issue reported on code.google.com by [email protected] on 22 Jun 2010 at 11:50

@GoogleCodeExporter
Copy link
Author

The material of a device shouldn't be expressed as a percent. For marine 
devices, it will normally be used to indicate the case or housing - plastic, 
titanium, or something in between - and/or some other critical part, like a 
ceramic thermister, maybe a copper guard (used to inhibit fouling) on a CTD. 
The variation in the way this may be used doesn't make it easy to model; do we 
need to get down to this level of detail, or can we assume it will be handled 
externally (for the time being)?

Original comment by [email protected] on 17 Aug 2010 at 2:28

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