AtomPub was designed to address the offline editing scenario.
AtomPub被设计为处理离线编辑的场景。
AtomPub is an HTTP-based protocol for creating and updating Web resources.
AtomPub是一种基于HTTP的协议，用于创建和更新Web资源。
You need to invoke the proper HTTP operation to the proper URL to use AtomPub.
您需要调用针对适当url的适当的HTTP操作来使用AtomPub。
This motivated the creation of several extensions to the AtomPub specification.
这也催生了几个AtomPub规范扩展的诞生。
The collections of these resources are accessible through Atom and can be managed using Atompub.
这些资源的集合可通过Atom进行访问，并且可以使用Atompub进行管理。
Joe Attributes the inability of AtomPub to become the "one true protocol", to browser innovations.
Joe将AtomPub不能成为“一个真正的协议”归因于浏览器的革新。
The server-side component needs to be able to communicate using AtomPub and generate an Atom feed.
服务器端组件需要能够使用AtomPub进行通信，并生成Atom 提要。
I don't need any specific tools nor do I need to know anything other than that the service is AtomPub.
我不需要任何特殊的工具或者更多的信息，仅仅只需了解这是基于AtomPub的服务。
OData.read is used to retrieve data from an OData-enabled service as an AtomPub feed or a JSON document.
开发者可以使用OData . read从支持OData的服务中获取数据，生成atompub数据或者JSON文档。
With the service document in place, the annotation service is essentially usable with the AtomPub interface.
有了服务文档之后，就可以通过AtomPub 接口使用注解服务了。
In this article we'll present an annotation server that's no more than a slightly specialized AtomPub server.
在本文中，我们将开发一个注解服务器，它仅仅是一种有点儿特殊化的AtomPub服务器。
In a post largely about the how the level of adoption that AtomPub is seeing, is far lower than the expectation.
在这篇博文里，大部分是关于AtomPub的采用程度如何远远的低于其预期。
So in the face of all those changes let's see how the some of the original motivations behind AtomPub are holding up.
面对所有这些改变让我们来看看AtomPub背后最初的动机是如何支持的。
The capabilities of browsers were limited as an "editor" and AtomPub was created to be used by thick clients and RIA's.
浏览器的功能被局限成一个“编辑器”而AtomPub为富客户端和RIA而产生。
The Atompub Working Group (within the IETF) agreed on the Atom 1.0 specification, and that it could be revised in the future.
Atompub 工作组（属于 IETF）就Atom 1.0规范达成一致意见，并在将来有可能重新修订。
Many things are awkward to model in AtomPub - really your data needs to be time based lists of things for it to be a natural fit.
很多信息用atompub来建模会显得过于笨拙。事实上，当你的数据是有时序的列表时，AtomPub是其自然的选择。
One method would be to get the entire comment feed from the AtomPub interface and simply find entries that meet the correct criteria.
一个方法是通过AtomPub接口获取完整的评论feed，然后寻找满足适当条件的条目。
Since the annotation service provides an AtomPub interface, you can define its usage using an AtomPub service document, given in Listing 2.
因为注解服务提供一个AtomPub接口，可以用一个AtomPub服务定义它的使用方法，见清单2。
The AtomClip extension in its most basic guise is just an AtomPub client, so it must be able to send AtomPub-formatted requests to the AtomPub server.
AtomClip扩展最基本的形式就是一个AtomPub客户端，因此它必须能够将atompub格式的请求发送给AtomPub服务器。
Joe writes that "There are still plenty of new protocols being developed on a seemingly daily basis, many of which could have used AtomPub, but don't."
Joe写到：“每天仍有许多新的协议在开发中，其中很多都可以用到AtomPub，但却没作出这样的选择。”
Unfortunately, AtomPub does not provide a batching mechanism, so we added batching capability to AtomServer (inspired by similar functionality in GData).
遗憾的是，AtomPub未提供批处理机制，所以我们为atomserver加进了批处理能力(灵感来自GData的类似功能)。
OData applies web technologies such as HTTP, Atom Publishing Protocol (AtomPub) and JSON to provide access to information from a variety of applications, services, and stores.
OData应用了web技术如HTTP、Atom发布协议(AtomPub)和JSON等来提供对不同应用程序，服务和存储的信息访问。
Rather than force the managers to pull two separate Feeds while correlating the data sets, as they would with conventional AtomPub, AtomServer adds the concept of an Aggregate Feed.
要求经理们拉出两个单独的Feed，并进行数据集的关联，这是常规的AtomPub做法。与此不同的是，AtomServer加入了Feed聚合的概念。
Rather than force the managers to pull two separate Feeds while correlating the data sets, as they would with conventional AtomPub, AtomServer adds the concept of an Aggregate Feed.
要求经理们拉出两个单独的Feed，并进行数据集的关联，这是常规的AtomPub做法。与此不同的是，AtomServer加入了Feed聚合的概念。
应用推荐