Bugzilla Bug 5427

Here's a list of things which have to be done to achieve APP draft 15
compliance:

 * @title attribute in app:workspace and app:collection changed to atom:title
element (section 8.1): requires work on the parser and work on the UI (title
can
now contain plain text, HTML or XHTML)

 * content-type of accept element changed (section 8.3.4): requires changes in
the logic which figures out what we can POST to a collection

 * content-type of HTTP header changed (section 9.2): requires changes in the
logic which POSTs to a collection


Also, there are new features available like the Slug header, which we don't
know
how to handle. For the moment, it is not possible to gather metadata for a
document, and dispatch this to the server.

When creating a new entry with Yulup 0.3.0, then Yulup seems to send a content
type of application/atom+xml (please see below)

POST /yanel/yulup/news-entries/?yanel.resource.viewid=atom HTTP/1.1..Host:
127.0.0.1:8080..User-A
  gent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.1) Gecko/20061208
Firefox/2.0.0.1..Accept:
  
text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=
  0.5..Accept-Language:
fr-ch,de;q=0.8,en-us;q=0.6,es;q=0.4,en;q=0.2..Accept-Encoding: gzip,deflate
  ..Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7..Keep-Alive: 300..Connection:
keep-alive..Conten
  t-Length: 349..Content-Type: application/atom+xml; charset=UTF-8..Neutron:
1.0-dev..WWW-Authentic
  ate: Neutron-Auth..Cookie: JS


but according to the spec 15 (and 16) para 9.2 it should send

application/atom+xml;type=entry

if there is no accept element within the service document or do I misunderstand
something?

Thanks

Michi