Do/should we have a committee with more than one people who has the authority to release new spec? I think it is important for us. David. <div class="gmail_quote">2012/10/28 Laszlo Papp <<a href="mailto:lpapp@kde.org" target="_blank">lpapp@kde.org</a>> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Frank, Are there any blockers (feature, time, consideration and so forth) why this proposal got stuck and did not get any decision: neither approval, nor denial? I have just come across this service plan while chatting today about an addition to attica on irc: <a href="http://www.freedesktop.org/wiki/Specifications/open-collaboration-services-1.7#CLOUD" target="_blank">http://www.freedesktop.org/wiki/Specifications/open-collaboration-services-1.7#CLOUD</a> Is it a blocker for 1.7 or why cannot we proceed with releasing the unreleased work we have? Thank you in advance. Laszlo <div class="HOEnZb"><div class="h5"> On Mon, Aug 27, 2012 at 6:45 AM, Laszlo Papp <<a href="mailto:lpapp@kde.org">lpapp@kde.org</a>> wrote: > Hi David, > >> Just reviewed the JSON draft, very clear. >> The differences between xml and json: >> 1. move the xml prop to json item. >> example: <person details="summary"></person> --> { details: >> "summary"} > > > Correct. > >> >> 2. remove the 'meta' node in xml > > > Correct. > >> >> I'm going to modify my nodejs-ocs implementation following this. >> >> >> One question, about both the xml and json draft: >> icon/video in 'content' is an array, >> >> but preview/homepages in 'content' is list one by one by adding >> appendix(1, 2..10) > > > Correct. Unfortunately, there is this foobarX inside OCS v1 around. We have > been planning to address that issue in OCS v2. > > Thank you for your feedback. > > Laszlo </div></div></blockquote></div>