![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
> Taking the sort of paranoid approach that befits assurances of stability, > needed for people doing critical operations, I look for a well-established > range of products and for wide-spread use. Because IETF documents are used > far beyond the confines of the IETF, the term "wide-spread" needs to work > with Internet scaling, not just IETF scaling. dave - i don't know how to say this politely, so i'll just say it: the ietf is one of the least xml-friendly communities out there. i think that colors your thinking. > Until then, it is not appropriate to change the massively-stable base that > forms the encoding rules for RFCs. XML as an adjunct is fine. As a > primary form for RFCs? Not yet. err, i don't recall anyone proposing this. if you're going to argue against something, first make sure that someone proposed it, ok? /mtr
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.