Re: AtomPubIssuesList for 2005/01/14

[James M Snell]

Eric Scheid wrote:
>> [1] PaceDontUseContentSrc
>
> -0 ... MUST is a problem if there isn't (yet) a public read-only IRI, so
> with no [EMAIL PROTECTED]'alternate'] the entry must have either an 
atom:summary or
> an atom:content element (right?)


Oh, one other point relating to this pace.  Using the edit link in media 
collections instead of [EMAIL PROTECTED] allows a collection URI to act as 
*both* a media collection and an entry collection simultaneously.

For instance:

1. Create an entry member

POST /collection-uri HTTP/1.1
Host: localhost
Content-Type: application/atom+xml
Content-Length: nnnn

<entry>
  <title>An entry member</title>
  ...
  <content>This is a description</content>
</entry>

2. Create an image member

POST /collection-uri HTTP/1.1
Host: localhost
Content-Type: image/png
Content-Length: nnnn
Title: A media member
Content-Description: This is a description

{binary data}

3. List the members.

GET /collection-uri
Host: localhost

<feed>
  <title>My Entry and Media Collection</title>
  ...
  <entry>
    <title>An entry member</title>
    <link href="http://example.org/public/1.html"; />
    <link rel="edit"
          type="application/atom+xml"
          href="http://example.org/members/1"; />
    ...
    <content type="text">This is a description</content>
  </entry>
  <entry>
    <title>A media member</title>
    <link href="http://example.org/public/2.png"; />
    <link rel="edit"
          type="image/png"
          href="http://example.org/members/2"; />
    <link rel="edit'
          type="application/atom+xml"
          href="http://example.org/members/2"; />
    ...
    <content type="text">This is a description</content>
  </entry>
</feed>

What's cool about this is that regardless of whether you look at it as a 
media collection or as an entry collection, it works as expected in 
either case.

- James