See also: IRC log
<trackbot> Date: 11 May 2010
<Holger> ScribeNick: Payam
Holger is leaving CSIRO and also the group (sorry to hear that Holger you are leaving the group and best wishes with your new postion)
Laurent will take over as the new chair
Holger and Simon have sent the slides to Payam (action point from last week)
Kerry has updated the wiki regarding not submitting the member submission; please have a look (all)
<laurent_lefort_cs> Payam introduces all the classes from the figure
Payam explained the operation/survival model
I can't hear
<kerry> i can't hear amit either
<krzysztof_j> same for me
Michael suggests chaging survival temperature range to survial environmental range
<krzysztof_j> agree with kerry
Kerry suggests the proposed attributes could be a part of device model
Kerry: how this model and the properties should be related to the current ontology?
Michael: some attributes such as maintanence schedule, processing/memory capacities are related to system level
do we need to split them up to cdevice related and system related attributes
Kerry: Survival ranges, they could be system properties not device?
<krzysztof_j> (if we put them to the system and not the device, do we all agree on what a system is? we had long disucssions about that at the ISWC 09 meeting)
<laurent_lefort_cs> Laurent: looking at http://www.w3.org/2005/Incubator/ssn/wiki/Key_Sensor_Concepts
Payam: some of the attributes in particualr, transmission range, battery life, operating range are part of devide model and the rest could be represented at the system level
<laurent_lefort_cs> ... we have a PowerSupply block where we could attach some
Kerry: the arrow, are those properties?
<michael> too many property names was what was decided for the accuracy modelling, so we just used one.
Kerry: whether each of the arrows refer to a property name; then we have too many property names
Krzysztof; adding properties in the system level not device level
Krzysztof: what is the reasonof adding all the properties in the device level?
Michael: we want to capture a wider range of concepts/things- then in this case sensor is not just a device
<krzysztof_j> of the sensor if it is a physical device
Payam: all the properties could be labelled as hasConstraints
<krzysztof_j> (are they all datattype properties?)
<michael> nice point
Cory: some of the represented concepts have inter-dependence
transmission range and battery life for example
Michael: battery life time can be calculated using other parameters; but we could have a static attribute as battery capacity
<scribe> ACTION: Payam, to update the operation/survival model [recorded in http://www.w3.org/2010/05/11-ssn-minutes.html#action01]
<trackbot> Sorry, couldn't find user - Payam,
<scribe> ACTION: Payam to update the operation/survival model [recorded in http://www.w3.org/2010/05/11-ssn-minutes.html#action02]
<trackbot> Created ACTION-24 - Update the operation/survival model [on Payam Barnaghi - due 2010-05-18].
summery of required updates on the model: tranmission, power, battery life will be a part of device level model
other properties will be a part of the system model; properties will be called as hasConstraint#
temperature survival range will be changed to environemtal surviaval range; and power survival range will be dropped
Michael discusses modelling of concepts related to deployments and system/device/deployment information.
how to link the current ontology defintions and to platforms
and relating that to MMI ontology
Kerry: to keep our focus on
sensor and device; relating our concepts to platforms but not
... we can import MMI ontology if we want to have a platform description in the ontology
Michael: we need to explain this in the document; this would be a part of the final report, but not the ontology
Amit: agrees to keep the work focused, but providing explanation how the ontology can be extended; i.e. by linking it to MMI ontology to explain the platforms
Michael we need to pick up this subject again when Luis is in the telco
Michael, wether to be aligned with MMI ontology- from deployment to platform - or from system to ... to platform
Michael: other aspects such as manufacture, model, etc. we can use MMI ontology for defining this concepts
<scribe> ACTION: Holger/Michael to send an email to Luis to discuss the issues [recorded in http://www.w3.org/2010/05/11-ssn-minutes.html#action03]
<trackbot> Sorry, couldn't find user - Holger/Michael
<scribe> ACTION: Holger, Michael to send an email to Luis to discuss the issues [recorded in http://www.w3.org/2010/05/11-ssn-minutes.html#action04]
<trackbot> Sorry, couldn't find user - Holger,
<scribe> ACTION: Holger ,Michael to send an email to Luis to discuss the issues [recorded in http://www.w3.org/2010/05/11-ssn-minutes.html#action05]
<trackbot> Created ACTION-25 - ,Michael to send an email to Luis to discuss the issues [on Holger Neuhaus - due 2010-05-18].
Kerry: 1st international semantic
sensor web conference cfp
... has submitted a proposal to
3rd internationl semantic sensor network conference
sorry workshop ISWC
This is scribe.perl Revision: 1.135 of Date: 2009/03/02 03:52:20 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/2nd international/1st international/ Found ScribeNick: Payam Inferring Scribes: Payam WARNING: No "Topic:" lines found. Default Present: Holger, david, michael, Payam, dongmei, +1.716.688.aacc, laurent_lefort_cs, +61.4.097.8.aadd, krzysztof_j, +1.937.775.aaee, Arthur Present: Holger david michael Payam dongmei +1.716.688.aacc laurent_lefort_cs +61.4.097.8.aadd krzysztof_j +1.937.775.aaee Arthur Found Date: 11 May 2010 Guessing minutes URL: http://www.w3.org/2010/05/11-ssn-minutes.html People with action items: holger michael payam WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. WARNING: No "Topic: ..." lines found! Resulting HTML may have an empty (invalid) <ol>...</ol>. Explanation: "Topic: ..." lines are used to indicate the start of new discussion topics or agenda items, such as: <dbooth> Topic: Review of Amy's report[End of scribe.perl diagnostic output]