I read the specification, and frankly won't try to claim that I have a good grasp of all the ideas; I think there is a 
lot more I'm not picking up yet but it's already very interesting to me.

But from what I can understand so far, a framework like this that allows and facilitates information dissemination is 
something that we have been looking for a while now, and find it extremely useful, especially in the area of sensor, 
environment and physical automation data management. We do some portion of this here and there today, but not in as well
 define and generic as in this document. I really like how clean the design is (pls keep it that way).

I have actually more question at this point then comments, and some of them are:
- I'm really glad to see in the spec Event and Message is clearly laid out as separate entities, I think that is a 
crucial point
- Have you consider intercept-able runtime binding of subscribers and publishers on a message-by-message level? 
  Something like Spring for data dissemination, if you know what I mean. For example, at runtime it would be very useful
 a for a trusted third party component to inject itself between two entities for the purposes of A) monitoring, B) data 
modification or annotation (like external context data), C) value added services
- Maybe this is in your plans for phase II, but have you looked into how identifications of both publishers and 
subscribers would work? Would there be trust levels that subscriptions can be based on, for example I only want to hear 
from people that is compliance to some corporate policy
- What about fine grain security. We have similar environment where we need to provide "vocabulary" level security. For 
example, a "visibility" mask based on your access control would define how others would really see your publication and 
who can subscribe to it. This is important to us if we were to use this beyond a company's four walls.
- I see this protocol as something that would really benefit M2M since nothing in that area that would provide this 
level of binding and data exchange semantics.
- Is there a way to link one event to always pull in another to form a larger event at subscription time?
- Will subscribers be notified when the vocabulary of the publication changed? Maybe a "system" publisher that anyone 
can subscribe (with right access) to for monitoring these changes?
- Have you consider how to pay binary payload? base64 or XpOinter or others?

What is the timeline for prototyping this, I would be very interested to find out more.

Thanks.

Regards,
  Sam Rehman <samuelson.rehman@oracle.com>
  Director of Development, Sensor Based Services
  Oracle Corp.