A. Pagaltzis wrote:

Atom is not a weblog aggregation format.

It can be used in that capacity, and certainly is the finest
choice for that, but that is only one possible use case, and
applications using Atom should not be bent around it.

Putting the EndpointReference in the content is the right thing
to do. Intermediaries and generic Atom stores can trivially pass
it around and/or extract it and delegate it to attached
format-specific processors correctly.

+1

The namespace of the entries’ contents would be a bit of hint,
no?

Yes, but it would still be helpful to not have to parse the content in order to see what's in there. In this case the content media type is not much help given that there is not a specific media type for WS-Addressing Endpoint References

should there not be there a some (optional) element inside
atom:feed to indicate that feed contains (only) list of
EndpointReferences?

An extension that allows one to define something like that sounds
like a useful thing to have. (James?)

The right term for this would probably be “role”. Or maybe
“profile”, in the sense that it’s a constrained use of a more
generic format.

+1. this is something I've been thinking about and could likely have something drafted up in the come couple of weeks.

- James


Reply via email to