1
0
So what should happen when the client de-references the resource in the sword:state-description element? To remain in keeping with SWORD, its recommended that this is an Atom Entry document with particular emphasis on the atom:title and atom:summary elements to convey the appropriate information. The advantage of this is that due to the extensible nature of Atom, if it becomes apparent that this state description could benefit from including further information this will be trivial to include.
2
2
Nonetheless, this is a diversion of the Atom standard, and alternative suggestions and simplifications are requested from the community. One alternative, for example, is simply for us to define our own format for transmitting this information.
Sick of obtaining low numbers of useless visitors to your website? Well i wish to share with you a fresh underground tactic which makes me personally $900 daily on 100% AUTOPILOT. I possibly could be here all day and going into detail but why dont you simply check their site out? There is a great video that explains everything. So if your seriously interested in making quick cash this is the site for you. Auto Traffic Avalanche
concur… if you hadn’t dathered already
Irrespective of the Atom-or-not-Atom question, I think an option should exist to use content negotiation to retrieve human-readable vs machine-readable versions of the same information.
As for the format being an Atom entry, if Atom provides practical value then fine, if not then I’d inclined to suggest content-negotiated HTML/RDF/JSON.