Re: ProtocolDataModel issues

[Ezra Cooper <ezra@xxxxxxxxxxxx>]

Here are some kinds of resources that I'd be interested in modeling in 
Atom:

  * Non-entry resources (images, etc.)
  * Templates
      - template body
      - name
      - target filename
  * Authors (Principals)
  * Categories
  * Weblog-level configuration

Can we agree on at least a few weblog-level configuration fields that 
would be useful to be treated by the protocol? Such as title, 
description, HTML URL, maybe timezone... At the very least, having a 
URL for the blog entity provides a convenient place to do the 
"introspection" that you wouldn't want to expose on the public web 
pages; it could include service.* links to all the other editable 
resources.

In the case of templates, I assume we all need a body and a name--but 
there's a lot of variation in determining what templates get used for 
what target pages.

+1 to using MIME types to label the template language.

The WebDAV ACL model looks interesting. At first blush it seems 
cumbersome, but having a ready-to-go spec for that functionality is 
attractive.

In regard to ProtocolDataModel, what is intended by the items "Index 
Page" and "Post Page"? Are the outward-facing blog pages meant to be 
treated by the protocol? What operations would they permit?

On Sep 13, 2004, at 12:29 PM, Greg Stein wrote:

> > > I'm also a little puzzled by, e.g. Post Page:  "A formatted display 
> > > of
> > > a single entry.".  -  the model part is the Entry, surely the
> > > presentation should be dealt with separately?
>
> A URL points to a resource. Every resource should have a listing in our
> data model. In this case, a post page is a typical item in a blog 
> setup,
> so I think it is important to have in the model. There are also
> relationships that are defined between that page and others in a blog.

But what is a "Post Page"? How is it different from an Entry and what 
is it useful for within the model?

Ezra