On Thursday 22 May 2008 08:45:33 [EMAIL PROTECTED] wrote: Hallo,
> Also it seems that you aren't, in this example, creating the resource based > on any criteria. Will there be something set in the resource later before > subscriptions are made? If not then I'm not sure what benefit there is to > creating multiple NotificationProducers when multiple subscriptions would > seem to suffice. > > Although its very likely I've missed something in your requirements :-) Ok, I'm going to provide further details: I want to use muse as a dispatcher of sensor events. On the one hand, there will be subscribers. This part is already implemented in muse. On the other hand, Sensors can advertise themselves: They provide their topic, name, description, ... which clients use for xpath filtering, later. It'll look like: <wsbn:RegisterPublisher> <wsbn:Topic dialect = “http://docs.oasis-open.org/wsn/t-1/TopicExpression/Simple”> <tsas:Measurements>mytopic</tsas:Measurements> </wsbn:Topic> <sml:SensorML> <member xlink:role="urn:ogc:def:role:OGC:sensorSystem"> <System gml:id="urn:x-ogc:object:sensor:IFGI:Temp:1"> <gml:description> ... </gml:description> <gml:name> ... </gml:name> ... </System> </member> </sml:SensorML> </wsbn:RegisterPublisher> Jan -- Jan Torben Heuer Institute for Geoinformatics [EMAIL PROTECTED] Robert-Koch-Strasse 26-28 +49 251 83-31960 48151 Münster, Germany
signature.asc
Description: This is a digitally signed message part.
