I don't see what functionality would be restricted by defining that hubs couldn't change content that they don't maintain as part of the protocol.  If I'm missing something, please enlighten me.

    I have always been of the opinion that the "message content" is every attribute of that content.  If someone who is not me changes anything that is in that feed, they are changing the message content.  Some content may be intended for machines instead of humans, but the fact that I took the time to add a <foo:bar/> tag to my item may have very important meaning to someone/thing reading it.

    Except as necessary to support the propagation of content to subscribers (e.g. removing items so that only deltas are published, adding atom:source tags for aggregation, etc.), I can find no reasonable case for the hub making modifications to the feed.

On 10/19/2009 4:19 PM, Alexis Richardson wrote:
I'm sorry I expressed that terribly.  

I think some hubs will change some metadata or their functionality will be very restricted.  But that's ok - the message content and identifying source is what matters?



On Tue, Oct 20, 2009 at 12:15 AM, Jay Rossiter <[email protected]> wrote:

    "it" would be the hub.  When the hub sends updates to its subscribers, the data that it sends should be identical to what it received in the feed, with the exceptions of what is required to handle the protocol.  Unknown or invalid tags... everything contained within the item/feed being handled.

    In short, the hub should never change anything that it is not specifically responsible for maintaining.

--

Jay Rossiter | Software Engineer/System Administrator
Pioneering RSS Advertising Solutions

[email protected] | Phone: 503.896.6187 | Fax: 503.235.2216
Website: www.pheedo.com | RSS: www.pheedo.info/index.xml

Reply via email to