Attribute Naming

[Wanicki, Martin]

Thinking further about things, I put forward for debate the notion of
a standard bucket of attribute names that different notification formats 
draw on to build their specs.


A spec for names being something like ...

Name			Meaning
=========================
Originator  		The Human originator of a notification
Originator-Agent	The Software application that originated/produced
the notification
Protocol-Name		The name of the protocol this notification belongs
to
Protocol-Version	The version of the protocol this notification
conforms to
Timeout			The Suggested lifetime of the message, in minutes
...etc



and then individual spec could be made up of any of the elements in the
naming spec


this, I think would make the building of spec easier and at the same time
making interoperability
between clients easier

thoughts ?

Martin