Aleksander Slominski wrote:


it is interesting that atom reader (in this case it seems to SharpReader) is actually rendering text content of

|<content type="application/xml">
<EndpointReference xmlns="http://www.w3.org/2005/08/addressing";>
     <Address>http://localhost:9085/wsatom/services/HelloWorld
</Address>
     </EndpointReference>
   </content>|

are atom readers supposed to do that? would it not be better to have a proper XHTML as content and store EndpointReference directly as a child inside atom:entry? after all EndpointReference is used by services and not Atom GUI apps?

If you take another look at the feed generated, I actually put text content in the summary element. Unfortunately, SharpReader seems to ignore it in favor of the content. I think that as a best practice, Atom readers should defer to the summary if the content type is anything but Text, HTML or XHTML.

second comment is very difficult (or impossible) to know that feed is actually representing "WS introspection" - should there not be there a some (optional) element inside atom:feed to indicate that feed contains (only) list of EndpointReferences?

I've been considering a profile element that can sit on the feed and entry level to indicate this sort of thing. Essentially, the profile element would be used as a key to indicate what kind of feed/entry this is.
For example,
 <feed xmlns="http://www.w3.org/2005/Atom";>
    <x:profile>http://example.com/atom/profiles/ws-inspection</x:profile>
    ...
 </feed>

One could easily imagine profile identifiers for blogs, podcasts, news, lists (ala netflix queues), etc.

- James


Reply via email to