See also: IRC log
<trackbot> Date: 19 May 2010
<Holger> ScribeNick: krp
Holger: sent email; Luis not on call
Holger: not heard from Payam on
... has anyone heard anything from Payam regarding the operating model?
Holger: MMI are aware of the
alignment issues; work is in progress
... how are deployments being handled? Attached to platform or instrument?
... how are sub-deployments being handled in relation to a new deployment?
Which wiki page is this, Holger?
<krzysztof_j> ack, in this case it is a process
Holger: is deployment a state... a lifetime of a system
krp: Is deployment an event.. a process that happens to the installation
<krzysztof_j> yes, i would think so
<krzysztof_j> entity:sensor participatesIn process:deployment
Can you re-deploy the same system instance?
Holger: the deployment is putting the sensors in the field, not the time the sensor is in the field
krzysztof_j: and the configuration of the sensors for that environment
Holger: three options: the act of
putting the system in the field
... the time the system is in the field
... the configuration of the system for that environment
indeed - does it matter
kelsey: we need to remember that many sensor are not static. Data from them moves in space and time.
In the wider framework of: http://www.w3.org/2005/Incubator/ssn/wiki/Key_Sensor_Concepts
Holger: would it make sense to have an act of deployment, which is a process? Construction and deconstruction
<kelsey> installed = commissioned and uninstalled = decomissioned?
yes, that's clear terminology
Arthur: should be some way to represent that the sensor is deployed in one place, and then another
<michael> I can - but you'll have to catch me up on the bits I just missed
What is the intention of the diagram on the wiki from MMI?
in relation to whether it's the event of deployment
or is it trying to solve being able to resolve when and where an observation was made
Right.. so what we care about is where the *measurement* was made..
scribe: but we're talking about devices and systems
Holger: we next need to look at time
michael: dolce has the idea of moving through space and time... so is a location fixed in both time and space?
krzysztof_j: entities participating over the lifetime
<krzysztof_j> locations are participants in the lifetime/deployment of the sensor
how is a lifetime scoped? would a given system have more than one? (lifetime ~=deployment?)
so lifetime/deployment is scoped as between commissioning and decommissioning?
arthur and holger: lifetime is perhaps misleading, but can define deployment in terms of (de)commissioning
kelsey: what is the relationship between the system lifetime and that of the constituent devices
do we have to decide if we can model both cases?
<michael> agreed, those are options our model should allow
right, to whatever granularity is appropriate
Yes, many thanks!
<krzysztof_j> YES, thanks holger!
<kelsey> Thank you Holger and best wishes in your new pursuits!
michael: thanks to Holger for his work chairing the group
<krzysztof_j> bye bye
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) Found ScribeNick: krp Inferring Scribes: krp Default Present: Holger, david, Arthur, krzysztof_j, krp, michael Present: Holger david Arthur krzysztof_j krp michael Regrets: Cory Luis Found Date: 19 May 2010 Guessing minutes URL: http://www.w3.org/2010/05/19-ssn-minutes.html People with action items:[End of scribe.perl diagnostic output]