<trackbot> Date: 09 February 2011

<Andy> Usman: Pachube giving an overview

does someone want to take that?

data broker

variety of formats and devices, converting in real time into format that variety of technologies can deal with

buildng a massively scalable system, to that end, most effort in the back end infrastructure

<Gary> Did the agenda (and deck) get resent?

at HTTP level, not most efficent transport but most widely available

now that we have the back end in place, we are going to begin rolling more efficient transport

but the thing we are trying to do in teh M2M world is to look at both real time and historical data

to make it as easy as possible for any industry, any one to be able to access the datea

thousands of develoeprs and engineers who have build applications and share these back with the community

e.g., embedable broths

bras?

graph

share this as a widget back, includes SMS alerts, converts energy feeds into real tiime carbon footprints

all sorts of discovery processes, search for data stream,s units, tags, slide through view of the globe

huge range of applications and tools

in terms of user base, three types of users

<ahill2> Sounds like pachube is the google of numbers

on the one hand everyone is doing something, not simply consuming the data

and we can deal withindividuals, companies who use more sophisticated servcies, and even cities

city managers can patrol/control private data and make it available

third parties or citizens of the city

commercial clients include Current Costs and Cisco (uses the API for ecomap)

essentially Pachube acts as real time data broker for all sorts of applications

contextual data has more valuable than any of the data stream data

data stream might be a time series of changing numbers, but the contextual meta data helps you figure out the sensor

where by using machine tagging you can refer to external data (sensorML)

where you could actually develop your own data or refer to existing taxonomies

and we handle the obvious meta data, Geo Location, things like that

<ahill2> what about processing and aggregating this data on clients and then submitting to Pachube

you could consider this a stepping stone to semantic Web applications sensor data

<ahill2> q

Any specific Questions about either back end, how it works or anything else?

I'm passing the scribing to Andy now?

<kseiler> q

AHill: the Internet is not going to rely on centralized services

<Andy> sure

when is Pachube going to be somethingin the system?

go for it!

<Andy> thanks Christine

openSIM

your own universe to populate

<Andy> Usman: OpenSim is something I am interested . open source of secondlife server

<Andy> would like to see the same peer to peer system to pachube system

<Andy> Agree that single point of failure would be bad

<Gary> Are we going to get the deck? It would really help add context to what's being talked about

<ahill2> Andy, can you mute while typing?

<Andy> Usman: Answering a karl question on overlap, sees the overlap being that each sensor having a location etc

<ahill2> living or dead

<Andy> Usman: What additional meta data would want to be added? uncertainity is not in there but could be added

<ahill2> +1 for Karls suggestion

<Andy> Karl: Format converter aspect may be very useful to our group.

<Andy> Usman: JSON and XML formats can be converted on fly

<Andy> Usman: Data Model, environment is one author perspective

<Andy> it may or mat have description

<Andy> does have to have an id and title

<Andy> enviroment is the wrapper. and tags like flickr tags

<ahill2> Does environment=namespace?

<Andy> it will have units and id and again tags which can be arbitary or machine tags

<Andy> The data model supports the nesting of various enviroment

<Andy> Karl, Does pachube take responsibility of id management

<Andy> Environment Id is unique in the pachube system

<Andy> Environment is not equivalent to a namespace. Enviroment is a feed

<Andy> namespace comes into play with tags

<Andy> ahill: Subject of XMPP was mentioned. what does xmpp mean to pachube

<Andy> ben: responds XMPP is an interesting protocol but there isnt alot of user pull yet

<Andy> XMPP for realtime notification but pachube has achieved many of the same things via web sockets

<Andy> Many of pachube use case come from ease of startup and also lower power use cases

<Andy> ahill: what about VRPN? virtual reality peripheral network

<Andy> Popular in research labs

<kseiler> did they say they were supporting change based filtering

<Gary> (need to hang up ... something's come up)

<kseiler> interesting stuff

<ahill2> thanks guys

<kseiler> did we happen to have contacts distributed

<Andy> Cperey: Timestamping is a big parallel between each system

<kseiler> would like to have a NAVTEQ biz side followup with these folks, some useful tech for us right now

<Andy> ahill: is it just the values or also the metadata timestamped

<Andy> Ben: it is just the values now but likely changed in the future to include metadata

<Andy> Cperey: the metadata is where we will likely collaborate

<Andy> rssagent, draft minutes

<bjpirt> For reference, our API can be seen at http://api.pachube.com/v2

I think this might have been sent out to the list as well

<kseiler> i think we need to investigate their meta-data representations on tiered ownership, and history / change tracking models

+1 KSeiler

<kseiler> some good lessons learned from sensor monitoring background

No

not me either!

<kseiler> did not see it

<Andy> trackbot, end meeting

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/tages/tags/
Succeeded: s/Cpery/Cperey/
No ScribeNick specified.  Guessing ScribeNick: cperey
Inferring Scribes: cperey

WARNING: No "Topic:" lines found.

Default Present: +1.312.265.aaaa, +1.919.439.aabb, +44.750.800.aacc, +1.617.848.aadd
Present: +1.312.265.aaaa +1.919.439.aabb +44.750.800.aacc +1.617.848.aadd

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 09 Feb 2011
Guessing minutes URL: http://www.w3.org/2011/02/09-poiwg-minutes.html
People with action items: 

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