-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/10/2013 11:26 AM, Yusuke DOI wrote: > Peter, > > (2013-11-11 0:43), Peter Waher wrote: > >> XML has many features that are very nice: Plugability and >> versioning using namespaces, validation (schema), swearch (xpath) >> and transformations/conversions (xslt). > > I don't think it's beneficial to start JSON vs. XMPP discussion > here. If we want to hand logs to JSON-based systems, this doesn't > mean we should use JSON as-is. For example, we can still use > JSON-ish XML instead. In the case, if we use complex namespace and > XML-ish versioning, XML-JSON binding may become broken. > > What I would like to clarify is use cases.
fortunately I don't think we need to go down that dragon strewn path as we can now just put xmpp-ftw or stanza.io into the mix. > >>> 'logging' is a too broad word I think. What framework/logging >>> facilities in your mind? >> >> I was thinking of network/admin logging, for instance like or >> based on Syslog semantics (also IETF). Could be used to log >> events of interest to system administrators, network architects, >> etc. Can also be used to find problems or learn how IoT networks >> based on XMPP work. > > Then, I guess netconf/netmod(YANG) and SNMP will be a first > choices. FYI, as IoT-related disucussion there are proposal on > CoAP-based management interface (not adopted by IETF yet). > > http://www.ietf.org/mail-archive/web/core/current/msg05102.html > The realm of logging appears to be broadly divided into two camps; the folks who live in the structured realm of SNMP type log generation and the others who sling text and/or JSON at a receiving entity. I am mainly interested in using XMPP as a transport so am not to worried about maintaining a strict XML structure but I can see how that would be beneficial to have. This means we would need to identify a core set of elements as MUST with the rest being optional. - -- bear xmpp agitator; ops curmudgeon; generalist http://bear.im/about http://bear.im/pubkey.txt 0A93 9BA7 8203 FCBC 58A9 E8B5 9D1E 0661 8EE5 B4D8 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSf8CyAAoJEJ0eBmGO5bTYCCIQAKLDIEmx/3WPLj7Cine3zr80 qUbUewnsaD5BcyItNQmpitDfeo/5ufZLqTcLx77LZnOTtxrN5IRDzcrQyuMHJw+h e1bypi6lRBfnwTK9myWhiHumI6rpT2j02RaLyuElSJ2CwjxOsVA21VxhoEhPjEya J2CL9nTIiB2e4moUmAxeceo71xUGjwDkEfv2zwfuuNfIyriXdWlfPO/J4O/Aw4Zx HUiyvaOt3TDOuN9pFMAHONYplraoBlSUjrCvyRyVvCONPKjD3xiR5CoM5iX84AAi Z408AU/Suh6z083faXSVsuE7GdcsOs5Q7cHmo0RCttnFyoMXoT8K9LTE6/Y495i/ x36Qh33vkjb48pSyS01w+ex64UQWujlwMY2SmLbBasDdB9lSWOLeDpPnqCfS0lkK 4l6sCfzm+HwK/BAlI+UqDVNTCGkp2CEpUc9JpyR9il5bvq/uIHFsu4q4iqrq4UR0 u3V3FfZ0rG+VxNHqXaJqbsajwuSA1pwXdhrn4NQqQtgANPD94t0VBT5odhF0Ovyv KH2V9qfx9ojIY821p/Fv5pPURhUYut6OFABOSVOZL1lR0LTlgbv8/j9XaI/K6vP1 52SGRfYtXcWRFw2J8JCXVmm7TtiF8zWGZLJqF6KkPsT5zG1fUoVkgaqiao+nehSG 0HbohQYYa/5MMqwpCYXH =j1Uc -----END PGP SIGNATURE-----
