Hi, I really think we have made some progress on this one. So cool Peter! :-) Just want to add a small thing: I have some logging like this already on my clients, and when the information is not that important I sometime piggy back the event log into one message stanza. So what I really would like to do is, to be able to have multiple <log> tags.
So maybe like this: <message from='[email protected]/device' to='[email protected]' type='normal' xml:lang='en'> <log> <event xmlns='urn:xmpp:eventlog' message='Something happened.' timestamp='2013-11-10T15:52:23Z’ /> <event xmlns='urn:xmpp:eventlog' message='Something else happened.' timestamp='2013-11-10T15:54:23Z’ /> </log> </message> Is it totally crazy? Coming back to the naming.. Now here is a log, consisting of multiple events.. Of course I would only do this If the logged events are not that important and needed to be near real-time. :-) -Just my 50 cent /Steffen On 12 Nov 2013, at 16:30, Peter Waher <[email protected]> wrote: > Hello > > I’ve updated the event logging proposal following the discussion with Dave. > I’ve made the message and stackTrace attributes into child elements instead, > better suited for multi-line text. I’ve also added some more security > considerations and reference to the publish/subscribe pattern. > > I’ve attached the latest versions. > > Best regards. > Peter Waher > > > > <eventlogging.html><eventlogging.xml><eventlogging.xsd>
smime.p7s
Description: S/MIME cryptographic signature
