Roy Fielding: It is only when we talk about specific applications of AtomPP, such as an authoring interface to a corporate blog, that we can say anything about the anticipated state change on the server. SUCH INFORMATION DOES NOT NEED TO BE IN THE PROTOCOL SPECIFICATION.
Is that clear? Maybe someone needs to write an application guide for transparent authoring via Atom
Maybe someone should. I’ve asked.
The Atom Publishing Protocols flexibility is its real strength, but it seems like an omission if the working group declares victory without producing an additional specification / guide that actually allows blogging clients to be interoperable with blogging servers. Wasn’t that the point?
{ 6 } Comments
Isn’t this almost -embarrassing-? Protocols are APis. Heck, they’re -more- than APIs. Who would use POSIX without knowing the -semantics- — the effects — of each POSIX “utterance”?
Relax. It’s really not that bad – http://www.snellspace.com/wp/?p=625
Лучшие рецепты http://www.koptim-sami.ru/ . Пошаговые фото рецепты копчения рыбы, свиные ребрышки на барбекю, шашлык из свинины, плов со свининой.
Быстрый ответ, признак ума :)
Кондиционеры в Киеве http://ovk-complex.com.ua/. Качественные консультаии по выбору кондиционеров. Продажа и монтаж климатической техники.
Онлайн библиотека бесплатной книги LitVik.ru. http://litvik.ru/2/ – скачать книги бесплатно txt
{ 1 } Trackback
[...] Is AtomPP for or not for blogs? Rob Yates is bringing up a serious point on the work of the Atompub WG: The Atom Publishing Protocols flexibility is its real strength, but it seems like an omission if the working group declares victory without producing an additional specification / guide that actually allows blogging clients to be interoperable with blogging servers. Wasn’t that the point? [...]
Post a Comment