<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
At the moment, I'm looking for exactly this -- pointers to existing
actual practices. I'll note that the Feedburner approach
(<a class="moz-txt-link-freetext" href="http://www.burningdoor.com/eric/archives/000759.html">http://www.burningdoor.com/eric/archives/000759.html</a>) is different
from James Snell's link rel="license" extension for Atom. Is one or
the other in actual use?<br>
<br>
Chris Messina wrote:
<blockquote
cite="mid1bc4603e0603221351v45b5abd4q37173a0091ce2125@mail.gmail.com"
type="cite">
<pre wrap="">Feedburner already allows you to embed a license in your feed. We
should document their approach.
I think feeds already allow you to embed a license generally:
<a class="moz-txt-link-freetext" href="http://www-128.ibm.com/developerworks/xml/library/x-extatom2.html">http://www-128.ibm.com/developerworks/xml/library/x-extatom2.html</a>
<a class="moz-txt-link-freetext" href="http://ietfreport.isoc.org/idref/draft-snell-atompub-feed-license/">http://ietfreport.isoc.org/idref/draft-snell-atompub-feed-license/</a>
One other idea to consider for hAtom at least would be embedding a
license using the object tag -- this way you could simply refer to the
external license permalink and not replicate all the extra data (which
seems to me one of the shortcomings of the current licensing
implementation).
<a class="moz-txt-link-freetext" href="http://microformats.org/discuss/mail/microformats-discuss/2006-February/003147.html">http://microformats.org/discuss/mail/microformats-discuss/2006-February/003147.html</a>
Anyway, I might be missing the point of your question -- what are you
looking for?
Chris
On 3/22/06, John Panzer <a class="moz-txt-link-rfc2396E" href="mailto:jpanzer@aol.net"><jpanzer@aol.net></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I'm starting a discussion about feed licencing which might be of
interest to members of this mailing list, and which will hopefully help
form the technical extensions that AOL adopts to deal with feed
licencing issues. I'm soliciting input from the community.
This may apply to hAtom (to the extent that hAtom ends up being used as
a substitute for XML based feed data) and of course data within RSS or
Atom feeds may have RelLicence elements.
Link:
<a class="moz-txt-link-freetext" href="http://journals.aol.com/panzerjohn/abstractioneer/entries/1281">http://journals.aol.com/panzerjohn/abstractioneer/entries/1281</a>
This is the initial discussion, painfully abstracted to avoid the
complicated stuff. I'm trying at this point to see which of these
starting assumptions are themselves problematic before going further.
Thanks,
--
John Panzer
System Architect
<a class="moz-txt-link-freetext" href="http://journals.aol.com/panzerjohn/abstractioneer">http://journals.aol.com/panzerjohn/abstractioneer</a>
_______________________________________________
microformats-discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:microformats-discuss@microformats.org">microformats-discuss@microformats.org</a>
<a class="moz-txt-link-freetext" href="http://microformats.org/mailman/listinfo/microformats-discuss">http://microformats.org/mailman/listinfo/microformats-discuss</a>
</pre>
</blockquote>
<pre wrap=""><!---->_______________________________________________
microformats-discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:microformats-discuss@microformats.org">microformats-discuss@microformats.org</a>
<a class="moz-txt-link-freetext" href="http://microformats.org/mailman/listinfo/microformats-discuss">http://microformats.org/mailman/listinfo/microformats-discuss</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
John Panzer
System Architect, AOL
<a class="moz-txt-link-freetext" href="http://abstractioneer.org">http://abstractioneer.org</a>
</pre>
</body>
</html>