Re: RSS Profile Comments

--- In [email protected], Geoffrey Sneddon <foolistbar@...>
wrote:
> Apologies for getting these in after the last call period has ended  
> (I'd strongly recommend allowed more than three days for interested  
> parties to review the document), but, they may as well be sent:

The vote doesn't begin until Monday, so we have a little leeway. But
given the length of the document, I don't want to spring revisions on
the board if it can be avoided.

> 2. |pubDate| has a code snippet, but gives no context to give it any  
> meaning. I assume it should refer to the above date and time section?

That's a formatting error. I've corrected it, but I'll hang on to the
draft to see if any others are necessary.
 
> 3. |hours| says, "both values to represent midnight", without  
> specifying what values represent midnight (as someone involved in  
> writing various specs, I'd prefer to spell out the blatantly obvious).

The preceding sentence states that the values are 0 and 24.

> 4. |ttl| has two consecutive sentences at the start of the "Most  
> aggregators…" paragraph with the same meaning. There is no need, and  
> as it is worded differently, it takes me a minute to look back and  
> see they mean the same thing and it isn't contradicting itself.

The second sentence makes specific the general statement in the first.

> 5. |description| says that aggregators should use the |channel| | 
> link| to resolve relative URIs, without specifying what to do if that  
> doesn't exist or is in itself relative. We should probably reference  
> RFC3986 section 5.1, with the afore mentioned element being the base  
> embedded in content.

That's already covered. The channel link can't be relative, because
it's a URL data type. The definition of URL states that it must begin
with a URI scheme.

http://www.rssboard.org/rss-profile#data-types-url
 
> 6. |enclosure| should probably state that @type and @length exist for  
> informative purposes only, and must not be treated as the  
> authoritative MIME type and file length.

I don't see anything in the spec, or in Dave Winer's use-case document
for enclosure, that says these things. Are you suggesting them as a
requirement or a recommendation?
 
> 7. |guid| could recommend something along the lines of using some  
> algorithm that will ensure that the |guid| /is/ globally unique (and  
> not just feed unique).

RSS 2.0 doesn't require global uniqueness, in spite of the name GUID.
But we do offer the Tag URI scheme as a way to create guids, which has
the added advantage of being globally unique.

Thanks for the suggestions. I know we're being harder on advice than
we've been up to this point in the drafting of the RSS Profile, but we
gotta get this thing out and start evangelizing its adoption. The
Dugger family in Arkansas conceived and birthed two children in the
time since we began the project.




 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/rss-public/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/rss-public/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:[email protected] 
    mailto:[email protected]

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/