19:42:19 RRSAgent has joined #ssn 19:42:19 logging to http://www.w3.org/2009/08/12-ssn-irc 19:42:28 Zakim has joined #ssn 19:42:36 zakim, this will be INC_SSN 19:42:36 ok, Holger; I see INC_SSN()4:00PM scheduled to start in 18 minutes 19:43:07 Meeting: SSN XG 12-August-2009 19:43:20 Chair: Holger 19:44:38 Regrets: AmitS, Krzysztof, Victor, Kerry 19:44:45 agenda+ Roll call 19:44:52 agenda+ Scribe list 19:45:03 agenda+ Discussion about Observation/Phenomenon structure in the SSN Ontology 19:45:11 agenda+ Refine/prioritise use cases: how to do that and when to start 19:45:17 agenda+ AOB 19:47:14 agenda? 19:51:49 INC_SSN()4:00PM has now started 19:51:56 +Holger 19:54:46 zakim, whi's on the phone? 19:54:46 I don't understand your question, Holger. 19:54:51 zakim, who's on the phone? 19:54:51 On the phone I see Holger 19:55:23 Danh_DERI has joined #ssn 19:55:34 +??P1 19:56:48 +giorgi 19:59:00 Arthur has joined #ssn 19:59:53 +[IPcaller] 20:00:14 + +1.206.662.aaaa 20:00:42 Zakim, [IPcaller] is me 20:00:42 +Arthur; got it 20:00:54 krp has joined #ssn 20:01:07 michael has joined #ssn 20:01:53 +krp 20:02:04 cory has joined #ssn 20:02:31 +??P6 20:02:46 zakim, ??P6 is me 20:02:46 +michael; got it 20:02:49 + +1.202.408.aabb 20:03:14 + +1.650.450.aacc 20:04:09 JohnGraybeal has joined #ssn 20:04:55 +Prateek 20:05:03 bermudez has joined #ssn 20:05:23 zakim, Prateek is me 20:05:23 +cory; got it 20:05:57 zakim, who's on the phone? 20:05:57 On the phone I see Holger, ??P1, giorgi, Arthur, +1.206.662.aaaa, krp, michael, +1.202.408.aabb, +1.650.450.aacc, cory 20:06:09 Payam has joined #SSN 20:07:08 agenda? 20:07:35 Rodrigo has joined #ssn 20:08:27 kelsey has joined #ssn 20:11:47 ScribeNick: kelsey 20:12:00 + +34.98.439.aadd 20:12:50 Holger: meeting minutes will rotate via the scribe list 20:13:19 Action: Holger to edit wiki to reflect scribe list 20:13:22 Zakim, +34-98.439.aadd is me 20:13:22 sorry, Rodrigo, I do not recognize a party named '+34-98.439.aadd' 20:13:30 Zakim, +34.98.439.aadd is me 20:13:30 +Rodrigo; got it 20:14:29 +q 20:15:19 ack payam 20:15:53 +q 20:15:57 zakim, who's making noise? 20:16:07 Holger, listening for 10 seconds I heard sound from the following: ??P1 (100%), giorgi (80%), Arthur (4%) 20:16:36 ack michael 20:16:53 zakim, mute ??P1 20:16:53 ??P1 should now be muted 20:17:18 zakim, unmute ??P1 20:17:18 ??P1 should no longer be muted 20:17:22 +q 20:17:34 zakim, who's making noise? 20:17:45 Holger, listening for 10 seconds I heard sound from the following: giorgi (56%), michael (60%) 20:18:05 zakim, mute giorgi 20:18:05 giorgi should now be muted 20:18:26 ack krp 20:18:55 +q 20:19:09 zakim, who's making noise? 20:19:28 Holger, listening for 16 seconds I heard sound from the following: Arthur (9%), krp (2%), michael (63%) 20:20:05 +q 20:20:18 ack michael 20:21:03 ack krp 20:21:04 +q 20:21:23 +q 20:21:54 Holger: need to have *some* representation of O&M in the ssn ontology 20:21:54 ack JohnGraybeal 20:22:16 +q 20:22:32 +q 20:23:06 ack bermudez 20:23:28 JohnGraybeal: this group should not be focused on describing data sets (though device data will need to be described) 20:24:27 ack cory 20:24:54 +q 20:25:07 ack krp 20:26:12 ack Payam 20:26:21 cory: perceived sensor web enablement was the focus, should in part focus on sensors 20:26:33 +q 20:26:52 payam: device vs. phenomena - not interested in device, rather what is being measured 20:26:57 ack michael 20:27:23 -michael 20:27:54 +[IPcaller] 20:28:15 sorry lost connection 20:28:31 zakim, [IPcaller] is me 20:28:31 +michael; got it 20:29:42 zakim, who's making noise? 20:29:54 Holger, listening for 10 seconds I heard sound from the following: Arthur (11%), michael (21%) 20:29:59 +q 20:30:37 +q 20:30:42 zakim, who's making noise? 20:30:49 michael: ssn's may be used for phenomena measurement, but also sensor capabilities - hence the need to characterize sensors 20:30:55 Holger, listening for 13 seconds I heard sound from the following: Arthur (77%) 20:31:05 zakim, mute me 20:31:05 Arthur should now be muted 20:31:26 ack Payam 20:31:58 +q 20:32:13 ack michael 20:32:38 +q 20:32:52 payam: Quality of information relative to the device - this is part of observation of measurement or device description? 20:32:58 +q 20:33:26 ack krp 20:33:36 michael: observation & measurement should reference back to the sensor to avoid redundancy in info reporting 20:34:13 +q 20:34:37 ack cory 20:34:47 krp: need to have link between the data and the sensor 20:35:37 ack bermudez 20:35:43 cory: Quality is described in the SensorML spec (e.g. values generated from sensor should not be trusted if temperature falls outside specific bounds), this *could be* sensor specific and not observation 20:36:08 ack Payam 20:36:18 bermudez: SoS points to link in SensorML doc 20:36:36 +q 20:36:43 +q 20:37:24 ack michael 20:37:30 payam: How does the observation association relate to the temporal transience of the sensor (e.g.what if the sensor device changes quality over time) 20:37:44 Can someone point me to our statement of intent to annotate SWE data using a data ontology? 20:38:20 +q 20:39:07 ack cory 20:39:38 ack Payam 20:39:48 +q 20:39:51 zakim, unmute me 20:39:51 Arthur should no longer be muted 20:40:14 michael: attach sensor historical information in observation vs. time tag in observation used to correlate with device managed history 20:40:21 ack Arthur 20:41:17 +q 20:41:25 +q 20:41:42 Payam: what if sensor is no longer available? Accuracy lookup may be lost 20:41:54 ack Payam 20:42:17 Arthur: UID and sensor quality can be sent 20:42:44 ack: JohnGraybeal 20:42:50 ack JohnGraybeal 20:42:58 Payam: this suggest an archiving approach 20:43:15 Yes, much of this sounds an implementation detail - if the resource representing the sensor doesn't persist I'm not sure there's much we can do about that in the ontology 20:43:54 JohnGraybeal: ontology should focus on device (and data, if desired) description - not system design 20:44:32 (sorry, meant that if the sensor doesn't persist that doesn't mean the resource representing it doesn't persist) 20:44:38 agreed we can't 'solve' semantic sensor networks, just build an ontology - but do need some use cases 20:44:45 Holger: target of this discussion is do we need O&M (description of data) in the device ontology 20:45:16 agree with michael - let the use cases drive this 20:45:29 I would have said do we need an O&M ontology, not does it need to be *in* the device ontology 20:45:54 we can just import odoe or similar and start there 20:46:02 I think that a valid point on email was that there isn't much to/in the O&M model 20:47:13 Holger: Linkage of O&M in the ontology will be discussed in the ontology working group 20:48:13 Holger: what approach should be used for identification/selection of use case drivers? 20:48:33 what happened to Simon's use cases? 20:50:49 Action: Holger will follow up with Simon re use cases 20:51:21 +q 20:51:45 ack JohnGraybeal 20:52:32 JohnGraybeal: can use cases successfully drive development? 20:55:09 Are the use cases for ontology validation? Or for analysis to develop the ontology from? Is the question how rigorous or complete the coverage of the use cases needs to be such that they're useful to us? 20:56:03 JohnGraybeal: team could id key ontology requirements (or existing use cases) vs. taking the time required to develop reasonable use cases 20:56:12 (so yes, as John just said) 20:56:49 Yes, those are the right questions krp. 20:57:50 I would be willing to build a "what do you want the ontology for" page to answer the question... 20:58:06 ... (the question of what the priority uses should be) 20:58:14 Action: All to send desired ontology capabilities to the mailing list 21:00:03 good idea 21:01:00 Action: JohnGraybeal will create a page on the wiki with brief description of use cases (what the ontology should be used for), send here rather than the mailing list 21:01:27 put on the wiki directly, send it to the mailing list or send directly to John 21:01:48 Thanks, bye. 21:01:50 - +1.202.408.aabb 21:01:53 - +1.650.450.aacc 21:01:55 -michael 21:01:55 -??P1 21:01:57 -giorgi 21:01:59 -Arthur 21:02:01 - +1.206.662.aaaa 21:02:01 -Rodrigo 21:02:06 -krp 21:02:15 Arthur has left #ssn 21:02:34 -Holger 21:02:57 zakim, bye 21:02:57 leaving. As of this point the attendees were Holger, giorgi, +1.206.662.aaaa, Arthur, krp, michael, +1.202.408.aabb, +1.650.450.aacc, cory, Rodrigo 21:02:57 Zakim has left #ssn 21:02:59 rrsagent, make log public 21:03:09 rrsagent, draft minutes 21:03:09 I have made the request to generate http://www.w3.org/2009/08/12-ssn-minutes.html Holger 21:03:46 rrsagent, bye 21:03:46 I see 4 open action items saved in http://www.w3.org/2009/08/12-ssn-actions.rdf : 21:03:46 ACTION: Holger to edit wiki to reflect scribe list [1] 21:03:46 recorded in http://www.w3.org/2009/08/12-ssn-irc#T20-13-19 21:03:46 ACTION: Holger will follow up with Simon re use cases [2] 21:03:46 recorded in http://www.w3.org/2009/08/12-ssn-irc#T20-50-49 21:03:46 ACTION: All to send desired ontology capabilities to the mailing list [3] 21:03:46 recorded in http://www.w3.org/2009/08/12-ssn-irc#T20-58-14 21:03:46 ACTION: JohnGraybeal will create a page on the wiki with brief description of use cases (what the ontology should be used for), send here rather than the mailing list [4] 21:03:46 recorded in http://www.w3.org/2009/08/12-ssn-irc#T21-01-00