Re: Discovery of APP service documents

[James M Snell <jasnell@xxxxxxxxx>]

This isn't for feed discovery.  It's for service document discovery when
the choice comes down between an Atom service document or a legacy RSD
document.

- James

Brian Smith wrote:
> Joe Cheng wrote:
>> <link rel="service" class="preferred" 
>> type="application/atomsvc+xml" href="..." />
>>
>> If anyone has feedback about this approach, I would love to 
>> hear it. Hopefully as time goes by and Atom implementations 
>> catch up in features and real-world experience, we can switch 
>> to Atom as the default.
> 
> It seems simpler to just re-use the mechanism that Microsoft suggested
> for feed auto-discovery: the server orders the <link> elements from best
> to worst, best first. This is easy to understand and also implies a
> convenient limitation: only one service document can be considered
> "active" at one time. That is, if there are multiple service documents,
> they should be considered alternatives to each other.
> 
> Anyway, could you provide a fuller example of your proposed mechanism?
> There could be many feeds associated with a particular blog entry:
> 
> * a feed for the entire blog (the most common type)
> * a feed for the particular entry, to keep track of modifications to
> just that entry
> * a feed for comments for this particular entry
> * a feed for all the comments for the whole weblog
> * a feed for trackbacks
> * a feed that combines comments, trackbacks, and/or modifications to the
> entry.
> 
> The immediate problem I am trying to solve is "Which
> workspace/collection should I post my comments to?"
> 
> Regards,
> Brian
> 
>