- From: A.Nikolov <a.nikolov@open.ac.uk>
- Date: Tue, 24 Aug 2010 11:11:59 +0100
- To: "'public-xg-ssn@w3.org'" <public-xg-ssn@w3.org>
- Message-ID: <2915005DADAFCB4899898B66C031AE9F5B6FDF60AB@SALCEYCMS1.open.ac.uk>
Dear all, Attached are a draft of possible "how to" issues which might be good to explain (ACTION-43 from the previous teleconference) and a new version of the accelerometer example aligned with the new version of the ontology. Concerning the "how to" questions, there are still some issues not quite clear to me: - What is Process supposed to be used for? Do we have an example of a sensor linked to a process? - Some names may possibly appear confusing. - Property. Although it is clear what it means in the context of sensors, it just looks similar to rdfs:Property (and not always distinguishable in ontology editors). Also the word "property" is used in MeasurementProperty, OperatingProperty, and SurvivalProperty. Maybe Quality can be used instead? - Some property names are a bit confusing: e.g., measurementPropertyCondition, hasOperatingCondition, hasSurvivalCondition hint that their range is Condition. Maybe, these can be hasMeasurementProperty, hasOperatingProperty, hasSurvivalProperty? - Minor comment: can there be mutual dependencies between MeasurementCapability, OperatingRange, and SurvivalRange? If yes, how can those be represented? - observationResultTime and qualityOfObservation still have domains specified. Should those be defined as allValuesFrom restrictions at the class level? Best, Andriy -- The Open University is incorporated by Royal Charter (RC 000391), an exempt charity in England & Wales and a charity registered in Scotland (SC 038302).
Attachments
- application/msword attachment: HowTos.doc
- application/x-zip-compressed attachment: SSNSensorKitchenExample-protege.zip
Received on Tuesday, 24 August 2010 10:12:36 UTC