RSS Mime Type Obstacle

[rcade]

I'm reading the RFCs related to MIME types and the process to apply
for one.

My read of Section 2.2.4 of RFC 2048 would exclude a joint application
for "application/rss+xml" by the RSS Advisory Board and RSS-DEV
Working Group (or any other shared type).

The section:

"2.2.4. Canonicalization and Format Requirements

"All registered media types must employ a single, canonical data
format, regardless of registration tree.

"A precise and openly available specification of the format of each
media type is required for all types registered in the IETF tree and
must at a minimum be referenced by, if it isn't actually included in,
the media type registration proposal itself."

ftp://ftp.isi.edu/in-notes/rfc2048.txt

Does anyone else have a different take on this?









Yahoo! Groups Links

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

<*> To unsubscribe from this group, send an email to:
rss-dev-unsubscribe-***@public.gmane.org

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

[Bill Kearney]

No, let's not make it any more confusing that it needs to be.

-Bill Kearney
Syndic8.com

----- Original Message -----
For what it's worth, perhaps RSS 1.0 should register for
application/rss+rdf+xml



Yahoo! Groups Links

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

<*> To unsubscribe from this group, send an email to:
rss-dev-unsubscribe-***@public.gmane.org

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

[Jon Hanna]

Post by rcade
"2.2.4. Canonicalization and Format Requirements
"All registered media types must employ a single, canonical data
format, regardless of registration tree.
"A precise and openly available specification of the format of each
media type is required for all types registered in the IETF tree and
must at a minimum be referenced by, if it isn't actually included in,
the media type registration proposal itself."
ftp://ftp.isi.edu/in-notes/rfc2048.txt
Does anyone else have a different take on this?

text/csv is registered.

text/csv isn't as simple as it appears at first glance, and there are
inconsistencies in how the edge-cases are handled by different sources.



Yahoo! Groups Links

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

<*> To unsubscribe from this group, send an email to:
rss-dev-unsubscribe-***@public.gmane.org

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

[Jon Hanna]

Post by Jon Hanna
text/csv is registered.
text/csv isn't as simple as it appears at first glance, and there are
inconsistencies in how the edge-cases are handled by different sources.

Though there is still only one description in the mime registration.
Strike my previous comment.



Yahoo! Groups Links

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

<*> To unsubscribe from this group, send an email to:
rss-dev-unsubscribe-***@public.gmane.org

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

[Ken MacLeod]

Post by rcade
I'm reading the RFCs related to MIME types and the process to apply
for one.

My read of Section 2.2.4 of RFC 2048 would exclude a joint application

Post by rcade
for "application/rss+xml" by the RSS Advisory Board and RSS-DEV
Working Group (or any other shared type).
Does anyone else have a different take on this?

Circumstantial exception. Documenting current behavior.

Write an RFC for the registration that clearly defines the interoperable
behavior of agents that exchange formats of the "application/rss+xml" type.
Note that they are all derived from the original format.

Many RFCs that define a complete format include a MIME registration as part
of the RFC. Other MIME registrations are simply boilerplate that point to
an external format for the purpose of registering the MIME type. A combined
RSS MIME registration would have one or two sections on defining the
interoperable behavior of an RSS formatted document, and include the
registration info.

I don't think the RFC should attempt to "restate" the formats (with a nod
here to Mark N. for the original RSS MIME registration draft). Simply point
to the existing documents. They've been stable long enough to be referenced
regardless of their lack of standards organization. A MIME registration of
this type will likely only be considered an "Informational" RFC anyway.

-- Ken


[Non-text portions of this message have been removed]




Yahoo! Groups Links

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

<*> To unsubscribe from this group, send an email to:
rss-dev-unsubscribe-***@public.gmane.org

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