You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 15, 2018. It is now read-only.
Description of the issue
EnvironmentalToleranceLimit: other possible cases:
* RF tolerance (e.g. from Argos transmitters) - creates noisy data
* Noise tolerance - probably not the correct term - may prevent a device from communicating but it may still record internally
* Magnetic field tolerance
* Distance from receiver - is this an EnvironmentalTolerance or an OperationalRestriction?
Please provide any relevant information/links below
http://marinemetadata.org/community/teams/ontdevices/agendas/am20100622
Original issue reported on code.google.com by [email protected] on 22 Jun 2010 at 5:00
The text was updated successfully, but these errors were encountered:
Nan: I have made several changes per our telecon on June 22 2010, including the
new subclasses SprayTolerance and SubmersionTolerance. Please see
http://marinemetadata.org/community/teams/ontdevices/devont for the updated OWL
and diagram. If you get a change, can you please see how to incorporate these
other cases (presumably as subclasses of EnvironmentalToleranceLimit) or
alternatively elaborate a bit on these new cases? Thanks.
Original issue reported on code.google.com by
[email protected]
on 22 Jun 2010 at 5:00The text was updated successfully, but these errors were encountered: