Rogers,

Thanks for taking a look. Some comments.

Rogers Cadenhead wrote:
> [snip]
> Our original spec said that it could be used with RSS
> 1.0, RSS 2.0 and Atom, but the Atom guidance was
> removed to get out of your way as your spec is being
> drafted.
> 

After going through and reviewing the WHATWG and RSS Board work last
night, I am strongly leaning in favor of moving this draft forward as an
Informational RFC rather than on the Standards Track.  The difference
between the two is that an Informational RFC is not a normative
specification.  This will give us a bit more leeway to include
information about RSS and pointers over to the WHATWG work.  The bottom
line is that, if the RSS Board is willing, the stuff you've done could
likely be folded into this document.

> I will put a couple of proposals on the wiki this
> morning.
> 

I see PaceRestrictRelValuesForAutodiscovery and
PaceRestrictTypeValuesForAutodiscovery.  I will comment on these separately.

> Regarding your current draft, a couple of editorial
> suggestions:
> 
> 1.
> 
> Are the "most relevant rules" part of Sections 3.2 and
> "most relevant differences" part of 3.3 necessary?
> It's helpful information, but it documents behavior
> that's covered by the HTML and XHTML specs, so it
> seems redundant and makes your spec longer than it
> needs to be.
> 

Well... on the one hand it is redundant; on the other it is helpful,
particularly in an informational document whose purpose is to describe
the best way of implementing autodiscovery.  However, I definitely think
the format could be reworked a bit.

> 2.
> 
> The href attribute's section is out of order
> alphabetically. For easier reference, I'd order
> sections 4.1 through 4.3 as href, rel and type rather
> than rel, type, href.
> 

Noted

> 3.
> 
> Your introduction to autodiscovery doesn't describe
> the most common and popular implementation of the
> technique.
> 

Yeah, this document was originally authored before that use case really
started to emerge.  I'll definitely add something about it to the intro
but I may not use your suggested words verbatim (I specifically want to
avoid mention of specific vendors).

- James

Reply via email to