https://microformats.org/wiki/api.php?action=feedcontributions&feedformat=atom&user=JoshuaKinbergMicroformats Wiki - User contributions [en]2026-05-05T02:47:18ZUser contributionsMediaWiki 1.38.4https://microformats.org/wiki/index.php?title=events/2006-03-13-sxsw-microformats&diff=5268events/2006-03-13-sxsw-microformats2006-02-28T02:45:42Z<p>JoshuaKinberg: /* Attending */</p>
<hr />
<div><h1> Microformats panel at SXSW Interactive 2006 </h1><br />
<br />
One of several microformats [[events]].<br />
<br />
During the [http://2006.sxsw.com/ SXSWi 2006] conference, there will be a [http://2006.sxsw.com/interactive/programming/panels/?action=show&id=IAP060038 Microformats panel] where microformats implementers will demonstrate and discuss microformats support in their tools and/or websites.<br />
<br />
Presenters, please see To Do section.<br />
<br />
__TOC__<br />
== Session Details ==<br />
<br />
* What: Microformats: Evolving the Web<br />
* Who (confirmed presenters): Tantek Çelik, Mark Norman Francis, Chris Messina<br />
* When: Monday, March 13th, 11:30 am - 12:30 pm<br />
* Where: Room 17AB, Austin Convention Center, Austin, TX<br />
<br />
== Attending ==<br />
Please add your name here if you are attending SXSW Interactive (whether you are speaking or not), alphabetically sorted by last name.<br />
* Tantek Çelik<br />
* Mark Norman Francis<br />
* Eran Globen<br />
* Ryan King<br />
* Chris Messina<br />
* Eric Meyer<br />
* Matt Mullenweg<br />
* [http://suda.co.uk Brian Suda]<br />
* [http://FireAnt.tv Joshua Kinberg]<br />
* ...<br />
<br />
== To Do ==<br />
Please check the to do list to see if you can help out.<br />
* '''ASAP: Anybody with who can help''' add [[hcalendar|hCalendar]] and [[hcard|hCard]] markup to the SXSW speakers and schedule/panels pages. Email the result to SXSW webmasters so they can update the pages. Host the marked up version on your own site in the meantime, and for redundancy's sake.<br />
** Need [[hcalendar|hCalendar]] markup for the events and [[hcard|hCard]] markup wherever speakers are listed with details/info/photo (feel free to put you name next to one to claim it and start working on it).<br />
*** [http://2006.sxsw.com/interactive/programming/panels/ 2006 Interactive Panel Schedule]<br />
*** [http://2006.sxsw.com/interactive/programming/opening_remarks/ SXSWi opening remarks]<br />
*** [http://2006.sxsw.com/interactive/programming/keynotes/ SXSWi keynotes]<br />
*** [http://2006.sxsw.com/interactive/tradeshow/ SXSWi trade show]<br />
*** [http://2006.sxsw.com/interactive/web_awards/ SXSWi web awards]<br />
*** [http://2006.sxsw.com/interactive/evening_events/ SXSWi evening events]<br />
*** [http://2006.sxsw.com/interactive/media_partners/ SXSWi media partners]<br />
*** [http://2006.sxsw.com/interactive/programming/daystage/ SXSWi day stage] - no schedule yet, but expect to see the content there soon.<br />
*** (get list of schedule related pages and put URLs here, prioritize SXSW Interactive, but also include SXSW Film and Music URLs as well)<br />
** Need hCards on (feel free to put you name next to one to claim it and start working on it) <br />
*** [http://2006.sxsw.com/interactive/programming/speakers/ SXSWi speakers]<br />
*** [http://2006.sxsw.com/interactive/tradeshow/exhibitor_list/ SXSWi tradeshow exhibitor list]<br />
*** [http://2006.sxsw.com/interactive/press/ SXSWi press info]<br />
*** [http://2006.sxsw.com/interactive/dewey_award/ SXSWi dewey award]<br />
*** (get list of speakers/panelist/location/travel related pages and put URLs here)<br />
** Need to send to SXSW folks so they can look at the diffs and update their pages <br />
*** (move URLs here when marked up with hCard and hCalendar, and append link to marked up version as well. feel free to review these, and add your name next to the one you've reviewed along with assessment, looks good or fails X2V etc. and any other notes re: gotchas/bugs etc.)<br />
* All demonstrations/discussion presentations should confirm that demonstrations are done, ready, practiced, and timed to complete within 5-10 minutes. Link to them from here as soon as possible (even drafts) so we can all review and see where everyone is at.<br />
** Tantek Çelik: working on slides, demo script for hCard and hCalendar import to Apple Address Book and Apple iCal calendaring application.<br />
** Chris Messina (Flock demo): working on it...<br />
** Mark Norman Francis (Yahoo UK! demo): ...<br />
** demo slot 4<br />
** demo slot 5<br />
<br />
== Short Summary ==<br />
<br />
This is simply a direct quote from http://2006.sxsw.com/interactive/programming/panels/?action=show&id=IAP060038 typos, misspellings, and UTF-8 gotchas all.<br />
<br />
Microformats: Evolving The Web<br />
<br />
Room 17AB<br />
<br />
Monday, March 13th<br />
<br />
11:30 am - 12:30 pm<br />
<br />
Microformats are simple semantic XHTML extensions for expressing numerous common concepts (people, events, etc.) on today's Web. Panelists will demonstrate and discuss microformats support in their websites.<br />
<br />
Moderator: Tantek ‚elik Chief Technologist, Technorati<br />
<br />
* Tantek ‚elik Chief Technologist, Technorati<br />
* Chris Messina Dir of Experience & Open Source Ambassador, Flock<br />
<br />
<br />
== Demonstration and Discussion Tips ==<br />
<br />
Note about the demonstrations. All demonstrations MUST:<br />
* '''Use or produce content published in one or more microformats'''. I suppose that should be obvious. ;)<br />
* '''Be completed in 5-10 minutes''' from start to finish, ''including'' setup time. We are working under strict time constraints, and thus I must cut-off demonstrations at the 10 minute mark so that we have time for the remaining demonstrations. If your demonstration stalls or appears to not work, we will move onto the next demo and if we have time, may come back, so be sure you have practiced your demo and are sure it will work (you can assume presence of a network, but being able to also run locally is a good thing). If you can keep your demo to 5 minutes and allow for a few minutes of quick audience Q&A that would be ideal.<br />
* '''Demonstrate end user benefit.''' Showing the code that makes it behind the scenes and discussing the microformats used briefly is good, but strictly ''secondary'' to showing something working with actual microformat content.<br />
<br />
== Proposed Demonstrations ==<br />
<br />
I have deliberately kept a few of the demonstration/discussion slots open for new/latecomers/implementers to be able to demonstrate their cool microformat implementations. If you have a useful and dazzling microformat implementation that you can successfully explain and demonstrate in 5-10 minutes please add your name, and brief explanation of what you plan to demonstrate, and we'll see if we can fit folks in. Some of the criteria to help decide will include:<br />
* Does the demo run *today*? (2006-02-26)<br />
* Does it demonstrate a microformat not currently being demonstrated by the other demos? E.g. one or more of:<br />
** [[hatom|hAtom]]<br />
** [[hlisting-proposal|hListing]]<br />
** [[hresume|hResume]]<br />
** [[hreview|hReview]] (perhaps [http://judysbook.com Judy's Book])<br />
** [[xfolk|xFolk]]<br />
<br />
Proposed demos:<br />
<br />
* Name, Company, title/summary, URL to working demo/download<br />
* ...<br />
* ...<br />
* ...<br />
* ...<br />
* ...<br />
<br />
<br />
== Longer Session Description ==<br />
<br />
I am working on this here, and will submit to SXSW to update on the page for the session: http://2006.sxsw.com/interactive/programming/panels/?action=show&id=IAP060038 <br />
<br />
- Tantek<br />
<br />
Microformats: Evolving The Web<br />
<br />
Room 17AB<br />
<br />
Monday, March 13th<br />
<br />
11:30 am - 12:30 pm<br />
<br />
Microformats are simple semantic XHTML extensions for expressing numerous common concepts (people, events, etc.) on today's Web. Panelists will demonstrate and discuss microformats support in their websites and tools.<br />
<br />
Moderator: Tantek Çelik, Chief Technologist, Technorati<br />
<br />
* Tantek Çelik Chief Technologist, Technorati<br />
* Mark Norman Francis, Yahoo UK!<br />
* Chris Messina Dir of Experience & Open Source Ambassador, Flock<br />
<br />
== Earlier Description ==<br />
<br />
Title: Microformats: Evolving the Web<br />
<br />
Summary: <br />
<br />
As the web design, development, IA, and blogging communities have adopted more and more valid semantic (X)HTML, two key realizations have emerged: there is a need to express common information building blocks on pages such as people, addresses, events, reviews etc., and (X)HTML lacks the built-in semantics to do so.<br />
<br />
Microformats are a set of simple open data formats that provide an evolutionary approach to easily expressing such common building blocks on today's Web. In contrast to dedicated XML schemas, microformats for events or contact info are familar XHTML with semantic class names, making them trivial to embed in existing content, style with CSS, and interoperate with desktop applications.</div>JoshuaKinberghttps://microformats.org/wiki/index.php?title=media-info-examples&diff=4253media-info-examples2006-01-04T10:09:55Z<p>JoshuaKinberg: /* Music */</p>
<hr />
<div>= Media Info Examples =<br />
<br />
== Contributors ==<br />
<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* [http://joshkinberg.com/blog/ Joshua Kinberg]<br />
<br />
== Introduction ==<br />
<br />
Examples of what people actually publish on the Web when discussing, linking to, referring to media. This is focused predominantly on time based media such as audio and video, but may consider aspects of static media as well such as still images.<br />
<br />
== Emphasis on Practical, Simple, and Minimal ==<br />
<br />
Since all previous known attempts at this problem area have ended up quite complex and over-designed, this attempt will place simplicity and minimalism first and foremost.<br />
<br />
Thus for now, this document is deliberately restricted to examples that are:<br />
* ''Actual'' examples in practice on the Web with URLs to the originals (note, all *-examples pages should be like this, but previous attempts at documenting media info examples have mostly ignored this requirement, and thus it is necessary to be explicit).<br />
* Representative of ''very common'' publishing behavior on the Web. This focus on common, representative examples is essential. If possible, include an estimate of the number of similar examples. E.g. ~10k.<br />
* Simple and minimalist. As simple as possible. Go read [http://microformats.org/wiki/microformats#the_microformats_principles the microformats principles] right now before proceeding any further.<br />
<br />
Any examples added which do not conform to these requirements will be deleted.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Examples ==<br />
<br />
=== Audio ===<br />
==== Speech ====<br />
Publication of audio speeches on blogs is often called "podcasting". In essence though, it is simply audio speech publishing.<br />
<br />
* [http://www.microformats.org/blog/2005/09/30/web-essentials-audio/ Microformats: Web Essentials Audio]<br />
** Appears to be composed of:<br />
*** title/summary of the recording<br />
*** clickable hyperlink to the recording (MP3)<br />
** Contextual:<br />
*** (primary) speaker is indicated in nearby text<br />
==== Music ====<br />
* ...<br />
<br />
=== Video ===<br />
Publication of video on blogs often goes by "videoblogging", "vlogging", "VODcasting", or "video podcasting". The typical process involves publishing a direct link to the video file within the blog entry. The blog entry can, but does not have to, include an embedded video player.<br />
<br />
* [http://FreeVlog.org FreeVlog]: the most popular tutorial on the web describing the videoblogging process by combining free tools and services (Blogger, OurMedia/Internet Archive, FeedBurner).<br />
** According to this process, a videoblog entry contains:<br />
*** Direct link to the video file<br />
*** Clickable thumbnail image/screen capture of the video<br />
*** Contextual information about the video (title, description, etc) is usually contained in the surrounding blog entry<br />
<br />
* [http://joshkinberg.com/popupmaker Video Pop Up Maker]<br />
** This example based on the process taught at [http://FreeVlog.org FreeVlog] generates code to create a dynamic pop up window with embedded video player. The reasons for this are enumerated [http://www.unmediated.org/archives/2005/10/easily_create_p.php here]<br />
<br />
== Next Steps ==<br />
# Add more real-world, simple, minimal examples.<br />
# Research and organize existing/previous [[media-info-formats]], with a focus on formats for publishing '''common''', '''user-visible''' media information.<br />
# Start [[media-info-brainstorming]] based on examples.<br />
<br />
== See Also ==<br />
* [[media-metadata-examples]] - previous attempt which is a bit of a deep-dive mess, and includes formats which should be in a separate page. Probably useful as both a source of research.</div>JoshuaKinberghttps://microformats.org/wiki/index.php?title=media-info-examples&diff=3874media-info-examples2006-01-04T09:54:29Z<p>JoshuaKinberg: /* Video */</p>
<hr />
<div>= Media Info Examples =<br />
<br />
== Contributors ==<br />
<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* [http://joshkinberg.com/blog/ Joshua Kinberg]<br />
<br />
== Introduction ==<br />
<br />
Examples of what people actually publish on the Web when discussing, linking to, referring to media. This is focused predominantly on time based media such as audio and video, but may consider aspects of static media as well such as still images.<br />
<br />
== Emphasis on Practical, Simple, and Minimal ==<br />
<br />
Since all previous known attempts at this problem area have ended up quite complex and over-designed, this attempt will place simplicity and minimalism first and foremost.<br />
<br />
Thus for now, this document is deliberately restricted to examples that are:<br />
* ''Actual'' examples in practice on the Web with URLs to the originals (note, all *-examples pages should be like this, but previous attempts at documenting media info examples have mostly ignored this requirement, and thus it is necessary to be explicit).<br />
* Representative of ''very common'' publishing behavior on the Web. This focus on common, representative examples is essential. If possible, include an estimate of the number of similar examples. E.g. ~10k.<br />
* Simple and minimalist. As simple as possible. Go read [http://microformats.org/wiki/microformats#the_microformats_principles the microformats principles] right now before proceeding any further.<br />
<br />
Any examples added which do not conform to these requirements will be deleted.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Examples ==<br />
<br />
=== Audio ===<br />
==== Speech ====<br />
Publication of audio speeches on blogs is often called "podcasting". In essence though, it is simply audio speech publishing.<br />
<br />
* [http://www.microformats.org/blog/2005/09/30/web-essentials-audio/ Microformats: Web Essentials Audio]<br />
** Appears to be composed of:<br />
*** title/summary of the recording<br />
*** clickable hyperlink to the recording (MP3)<br />
** Contextual:<br />
*** (primary) speaker is indicated in nearby text<br />
=== Music ===<br />
* ...<br />
<br />
=== Video ===<br />
Publication of video on blogs often goes by "videoblogging", "vlogging", "VODcasting", or "video podcasting". The typical process involves publishing a direct link to the video file within the blog entry. The blog entry can, but does not have to, include an embedded video player.<br />
<br />
* [http://FreeVlog.org FreeVlog]: the most popular tutorial on the web describing the videoblogging process by combining free tools and services (Blogger, OurMedia/Internet Archive, FeedBurner).<br />
** According to this process, a videoblog entry contains:<br />
*** Direct link to the video file<br />
*** Clickable thumbnail image/screen capture of the video<br />
*** Contextual information about the video (title, description, etc) is usually contained in the surrounding blog entry<br />
<br />
* [http://joshkinberg.com/popupmaker Video Pop Up Maker]<br />
** This example based on the process taught at [http://FreeVlog.org FreeVlog] generates code to create a dynamic pop up window with embedded video player. The reasons for this are enumerated [http://www.unmediated.org/archives/2005/10/easily_create_p.php here]<br />
<br />
== Next Steps ==<br />
# Add more real-world, simple, minimal examples.<br />
# Research and organize existing/previous [[media-info-formats]], with a focus on formats for publishing '''common''', '''user-visible''' media information.<br />
# Start [[media-info-brainstorming]] based on examples.<br />
<br />
== See Also ==<br />
* [[media-metadata-examples]] - previous attempt which is a bit of a deep-dive mess, and includes formats which should be in a separate page. Probably useful as both a source of research.</div>JoshuaKinberghttps://microformats.org/wiki/index.php?title=media-info-examples&diff=3873media-info-examples2006-01-04T09:06:36Z<p>JoshuaKinberg: /* Video */</p>
<hr />
<div>= Media Info Examples =<br />
<br />
== Contributors ==<br />
<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* [http://joshkinberg.com/blog/ Joshua Kinberg]<br />
<br />
== Introduction ==<br />
<br />
Examples of what people actually publish on the Web when discussing, linking to, referring to media. This is focused predominantly on time based media such as audio and video, but may consider aspects of static media as well such as still images.<br />
<br />
== Emphasis on Practical, Simple, and Minimal ==<br />
<br />
Since all previous known attempts at this problem area have ended up quite complex and over-designed, this attempt will place simplicity and minimalism first and foremost.<br />
<br />
Thus for now, this document is deliberately restricted to examples that are:<br />
* ''Actual'' examples in practice on the Web with URLs to the originals (note, all *-examples pages should be like this, but previous attempts at documenting media info examples have mostly ignored this requirement, and thus it is necessary to be explicit).<br />
* Representative of ''very common'' publishing behavior on the Web. This focus on common, representative examples is essential. If possible, include an estimate of the number of similar examples. E.g. ~10k.<br />
* Simple and minimalist. As simple as possible. Go read [http://microformats.org/wiki/microformats#the_microformats_principles the microformats principles] right now before proceeding any further.<br />
<br />
Any examples added which do not conform to these requirements will be deleted.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Examples ==<br />
<br />
=== Audio ===<br />
==== Speech ====<br />
Publication of audio speeches on blogs is often called "podcasting". In essence though, it is simply audio speech publishing.<br />
<br />
* [http://www.microformats.org/blog/2005/09/30/web-essentials-audio/ Microformats: Web Essentials Audio]<br />
** Appears to be composed of:<br />
*** title/summary of the recording<br />
*** clickable hyperlink to the recording (MP3)<br />
** Contextual:<br />
*** (primary) speaker is indicated in nearby text<br />
=== Music ===<br />
* ...<br />
<br />
=== Video ===<br />
Publication of video on blogs often goes by "videoblogging", "vlogging", "VODcasting", or "video podcasting". The typical process involves publishing a direct link to the video file within the blog entry. The blog entry can but does not have to include an embedded video player.<br />
<br />
* [http://FreeVlog.org FreeVlog]: the most popular tutorial on the web describing the videoblogging process by combining free tools and services (Blogger, OurMedia/Internet Archive, FeedBurner).<br />
** According to this process, a videoblog entry contains:<br />
*** Direct link to the video file<br />
*** Clickable thumbnail image/screen capture of the video<br />
*** Contextual information about the video (title, description, etc) is usually contained in the surrounding blog entry<br />
<br />
* [http://joshkinberg.com/popupmaker Video Pop Up Maker]<br />
** This example based on the process taught at [http://FreeVlog.org FreeVlog] generates code to create a dynamic pop up window with embedded video player. The reasons for this are enumerated [http://www.unmediated.org/archives/2005/10/easily_create_p.php here]<br />
<br />
== Next Steps ==<br />
# Add more real-world, simple, minimal examples.<br />
# Research and organize existing/previous [[media-info-formats]], with a focus on formats for publishing '''common''', '''user-visible''' media information.<br />
# Start [[media-info-brainstorming]] based on examples.<br />
<br />
== See Also ==<br />
* [[media-metadata-examples]] - previous attempt which is a bit of a deep-dive mess, and includes formats which should be in a separate page. Probably useful as both a source of research.</div>JoshuaKinberghttps://microformats.org/wiki/index.php?title=media-info-examples&diff=3872media-info-examples2006-01-04T09:01:09Z<p>JoshuaKinberg: /* Contributors */</p>
<hr />
<div>= Media Info Examples =<br />
<br />
== Contributors ==<br />
<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
* [http://joshkinberg.com/blog/ Joshua Kinberg]<br />
<br />
== Introduction ==<br />
<br />
Examples of what people actually publish on the Web when discussing, linking to, referring to media. This is focused predominantly on time based media such as audio and video, but may consider aspects of static media as well such as still images.<br />
<br />
== Emphasis on Practical, Simple, and Minimal ==<br />
<br />
Since all previous known attempts at this problem area have ended up quite complex and over-designed, this attempt will place simplicity and minimalism first and foremost.<br />
<br />
Thus for now, this document is deliberately restricted to examples that are:<br />
* ''Actual'' examples in practice on the Web with URLs to the originals (note, all *-examples pages should be like this, but previous attempts at documenting media info examples have mostly ignored this requirement, and thus it is necessary to be explicit).<br />
* Representative of ''very common'' publishing behavior on the Web. This focus on common, representative examples is essential. If possible, include an estimate of the number of similar examples. E.g. ~10k.<br />
* Simple and minimalist. As simple as possible. Go read [http://microformats.org/wiki/microformats#the_microformats_principles the microformats principles] right now before proceeding any further.<br />
<br />
Any examples added which do not conform to these requirements will be deleted.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Examples ==<br />
<br />
=== Audio ===<br />
==== Speech ====<br />
Publication of audio speeches on blogs is often called "podcasting". In essence though, it is simply audio speech publishing.<br />
<br />
* [http://www.microformats.org/blog/2005/09/30/web-essentials-audio/ Microformats: Web Essentials Audio]<br />
** Appears to be composed of:<br />
*** title/summary of the recording<br />
*** clickable hyperlink to the recording (MP3)<br />
** Contextual:<br />
*** (primary) speaker is indicated in nearby text<br />
=== Music ===<br />
* ...<br />
<br />
=== Video ===<br />
Publication of video on blogs often goes by "videoblogging", "vlogging", "VODcasting", or "video podcasting". The typical process involves publishing a direct link to the video file within the blog entry. The blog entry can but does not have to include an embedded video player.<br />
<br />
* [http://FreeVlog.org FreeVlog]: the most popular tutorial on the web describing the videoblogging process by combining free tools and services (Blogger, OurMedia/Internet Archive, FeedBurner).<br />
** According to this process, a videoblog entry contains:<br />
*** Direct link to the video file<br />
*** Clickable thumbnail image/screen capture of the video<br />
*** Contextual information about the video (title, description, etc) is usually contained in the surrounding blog entry<br />
<br />
* [http://joshkinberg.com/popupmaker Video Pop Up Maker]<br />
** This example based on the process taught at [http://FreeVlog.org FreeVlog] generates code to create a dynamic pop up window with embedded video player. The reasons for this are enumerated [http://www.unmediated.org/archives/2005/10/easily_create_p.php here]<br />
<br />
* Some video publishing services, such as [http://youtube.com YouTube] and [http://video.google.com Google Video], convert uploaded videos to Flash Video format (FLV) and attempt to obscure direct download links, only publishing videos using embedded Flash players.<br />
** [http://triciawang.blogspot.com/2005/12/circle-circus-ends-at-school-161-i.html Here] is an example of YouTube's embedded Flash player in a blog entry<br />
** [http://www.youtube.com/watch.php?v=laSF2KalgBk Here] is an example of YouTube embedded Flash player on the YouTube website<br />
** [http://video.google.com/videoplay?docid=-5721216010568488162 Here] is an example of Google Video embedded Flash player on the Google Video website<br />
** [http://www.joshkinberg.com/blog/archives/2005/11/greased_google.php Here] are a couple Greasemonkey scripts intended to create direct download links for videos hosted on YouTube and Google Video<br />
<br />
== Next Steps ==<br />
# Add more real-world, simple, minimal examples.<br />
# Research and organize existing/previous [[media-info-formats]], with a focus on formats for publishing '''common''', '''user-visible''' media information.<br />
# Start [[media-info-brainstorming]] based on examples.<br />
<br />
== See Also ==<br />
* [[media-metadata-examples]] - previous attempt which is a bit of a deep-dive mess, and includes formats which should be in a separate page. Probably useful as both a source of research.</div>JoshuaKinberghttps://microformats.org/wiki/index.php?title=media-info-examples&diff=3871media-info-examples2006-01-04T08:49:00Z<p>JoshuaKinberg: /* Video */</p>
<hr />
<div>= Media Info Examples =<br />
<br />
== Contributors ==<br />
<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
<br />
== Introduction ==<br />
<br />
Examples of what people actually publish on the Web when discussing, linking to, referring to media. This is focused predominantly on time based media such as audio and video, but may consider aspects of static media as well such as still images.<br />
<br />
== Emphasis on Practical, Simple, and Minimal ==<br />
<br />
Since all previous known attempts at this problem area have ended up quite complex and over-designed, this attempt will place simplicity and minimalism first and foremost.<br />
<br />
Thus for now, this document is deliberately restricted to examples that are:<br />
* ''Actual'' examples in practice on the Web with URLs to the originals (note, all *-examples pages should be like this, but previous attempts at documenting media info examples have mostly ignored this requirement, and thus it is necessary to be explicit).<br />
* Representative of ''very common'' publishing behavior on the Web. This focus on common, representative examples is essential. If possible, include an estimate of the number of similar examples. E.g. ~10k.<br />
* Simple and minimalist. As simple as possible. Go read [http://microformats.org/wiki/microformats#the_microformats_principles the microformats principles] right now before proceeding any further.<br />
<br />
Any examples added which do not conform to these requirements will be deleted.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Examples ==<br />
<br />
=== Audio ===<br />
==== Speech ====<br />
Publication of audio speeches on blogs is often called "podcasting". In essence though, it is simply audio speech publishing.<br />
<br />
* [http://www.microformats.org/blog/2005/09/30/web-essentials-audio/ Microformats: Web Essentials Audio]<br />
** Appears to be composed of:<br />
*** title/summary of the recording<br />
*** clickable hyperlink to the recording (MP3)<br />
** Contextual:<br />
*** (primary) speaker is indicated in nearby text<br />
=== Music ===<br />
* ...<br />
<br />
=== Video ===<br />
Publication of video on blogs often goes by "videoblogging", "vlogging", "VODcasting", or "video podcasting". The typical process involves publishing a direct link to the video file within the blog entry. The blog entry can but does not have to include an embedded video player.<br />
<br />
* [http://FreeVlog.org FreeVlog]: the most popular tutorial on the web describing the videoblogging process by combining free tools and services (Blogger, OurMedia/Internet Archive, FeedBurner).<br />
** According to this process, a videoblog entry contains:<br />
*** Direct link to the video file<br />
*** Clickable thumbnail image/screen capture of the video<br />
*** Contextual information about the video (title, description, etc) is usually contained in the surrounding blog entry<br />
<br />
* [http://joshkinberg.com/popupmaker Video Pop Up Maker]<br />
** This example based on the process taught at [http://FreeVlog.org FreeVlog] generates code to create a dynamic pop up window with embedded video player. The reasons for this are enumerated [http://www.unmediated.org/archives/2005/10/easily_create_p.php here]<br />
<br />
* Some video publishing services, such as [http://youtube.com YouTube] and [http://video.google.com Google Video], convert uploaded videos to Flash Video format (FLV) and attempt to obscure direct download links, only publishing videos using embedded Flash players.<br />
** [http://triciawang.blogspot.com/2005/12/circle-circus-ends-at-school-161-i.html Here] is an example of YouTube's embedded Flash player in a blog entry<br />
** [http://www.youtube.com/watch.php?v=laSF2KalgBk Here] is an example of YouTube embedded Flash player on the YouTube website<br />
** [http://video.google.com/videoplay?docid=-5721216010568488162 Here] is an example of Google Video embedded Flash player on the Google Video website<br />
** [http://www.joshkinberg.com/blog/archives/2005/11/greased_google.php Here] are a couple Greasemonkey scripts intended to create direct download links for videos hosted on YouTube and Google Video<br />
<br />
== Next Steps ==<br />
# Add more real-world, simple, minimal examples.<br />
# Research and organize existing/previous [[media-info-formats]], with a focus on formats for publishing '''common''', '''user-visible''' media information.<br />
# Start [[media-info-brainstorming]] based on examples.<br />
<br />
== See Also ==<br />
* [[media-metadata-examples]] - previous attempt which is a bit of a deep-dive mess, and includes formats which should be in a separate page. Probably useful as both a source of research.</div>JoshuaKinberghttps://microformats.org/wiki/index.php?title=media-info-examples&diff=3870media-info-examples2006-01-04T08:47:20Z<p>JoshuaKinberg: /* Video */</p>
<hr />
<div>= Media Info Examples =<br />
<br />
== Contributors ==<br />
<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
<br />
== Introduction ==<br />
<br />
Examples of what people actually publish on the Web when discussing, linking to, referring to media. This is focused predominantly on time based media such as audio and video, but may consider aspects of static media as well such as still images.<br />
<br />
== Emphasis on Practical, Simple, and Minimal ==<br />
<br />
Since all previous known attempts at this problem area have ended up quite complex and over-designed, this attempt will place simplicity and minimalism first and foremost.<br />
<br />
Thus for now, this document is deliberately restricted to examples that are:<br />
* ''Actual'' examples in practice on the Web with URLs to the originals (note, all *-examples pages should be like this, but previous attempts at documenting media info examples have mostly ignored this requirement, and thus it is necessary to be explicit).<br />
* Representative of ''very common'' publishing behavior on the Web. This focus on common, representative examples is essential. If possible, include an estimate of the number of similar examples. E.g. ~10k.<br />
* Simple and minimalist. As simple as possible. Go read [http://microformats.org/wiki/microformats#the_microformats_principles the microformats principles] right now before proceeding any further.<br />
<br />
Any examples added which do not conform to these requirements will be deleted.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Examples ==<br />
<br />
=== Audio ===<br />
==== Speech ====<br />
Publication of audio speeches on blogs is often called "podcasting". In essence though, it is simply audio speech publishing.<br />
<br />
* [http://www.microformats.org/blog/2005/09/30/web-essentials-audio/ Microformats: Web Essentials Audio]<br />
** Appears to be composed of:<br />
*** title/summary of the recording<br />
*** clickable hyperlink to the recording (MP3)<br />
** Contextual:<br />
*** (primary) speaker is indicated in nearby text<br />
=== Music ===<br />
* ...<br />
<br />
=== Video ===<br />
Publication of video on blogs often goes by "videoblogging", "vlogging", "VODcasting", or "video podcasting". The typical process involves publishing a direct link to the video file within the blog entry. The blog entry can but does not have to include an embedded video player.<br />
<br />
* [http://FreeVlog.org FreeVlog]: the most popular tutorial on the web describing the videoblogging process by combining free tools and services (Blogger, OurMedia/Internet Archive, FeedBurner).<br />
** According to this process, a videoblog entry contains:<br />
*** Direct link to the video file<br />
*** Clickable thumbnail image/screen capture of the video<br />
<br />
* [http://joshkinberg.com/popupmaker Video Pop Up Maker]<br />
** This example based on the process taught at [http://FreeVlog.org FreeVlog] generates code to create a dynamic pop up window with embedded video player. The reasons for this are enumerated [http://www.unmediated.org/archives/2005/10/easily_create_p.php here]<br />
<br />
* Some video publishing services, such as [http://youtube.com YouTube] and [http://video.google.com Google Video], convert uploaded videos to Flash Video format (FLV) and attempt to obscure direct download links, only publishing videos using embedded Flash players.<br />
** [http://triciawang.blogspot.com/2005/12/circle-circus-ends-at-school-161-i.html Here] is an example of YouTube's embedded Flash player in a blog entry<br />
** [http://www.youtube.com/watch.php?v=laSF2KalgBk Here] is an example of YouTube embedded Flash player on the YouTube website<br />
** [http://video.google.com/videoplay?docid=-5721216010568488162 Here] is an example of Google Video embedded Flash player on the Google Video website<br />
** [http://www.joshkinberg.com/blog/archives/2005/11/greased_google.php Here] are a couple Greasemonkey scripts intended to create direct download links for videos hosted on YouTube and Google Video<br />
<br />
== Next Steps ==<br />
# Add more real-world, simple, minimal examples.<br />
# Research and organize existing/previous [[media-info-formats]], with a focus on formats for publishing '''common''', '''user-visible''' media information.<br />
# Start [[media-info-brainstorming]] based on examples.<br />
<br />
== See Also ==<br />
* [[media-metadata-examples]] - previous attempt which is a bit of a deep-dive mess, and includes formats which should be in a separate page. Probably useful as both a source of research.</div>JoshuaKinberghttps://microformats.org/wiki/index.php?title=media-info-examples&diff=3869media-info-examples2006-01-04T07:05:11Z<p>JoshuaKinberg: /* Examples */</p>
<hr />
<div>= Media Info Examples =<br />
<br />
== Contributors ==<br />
<br />
* [http://tantek.com/log/ Tantek Çelik]<br />
<br />
== Introduction ==<br />
<br />
Examples of what people actually publish on the Web when discussing, linking to, referring to media. This is focused predominantly on time based media such as audio and video, but may consider aspects of static media as well such as still images.<br />
<br />
== Emphasis on Practical, Simple, and Minimal ==<br />
<br />
Since all previous known attempts at this problem area have ended up quite complex and over-designed, this attempt will place simplicity and minimalism first and foremost.<br />
<br />
Thus for now, this document is deliberately restricted to examples that are:<br />
* ''Actual'' examples in practice on the Web with URLs to the originals (note, all *-examples pages should be like this, but previous attempts at documenting media info examples have mostly ignored this requirement, and thus it is necessary to be explicit).<br />
* Representative of ''very common'' publishing behavior on the Web. This focus on common, representative examples is essential. If possible, include an estimate of the number of similar examples. E.g. ~10k.<br />
* Simple and minimalist. As simple as possible. Go read [http://microformats.org/wiki/microformats#the_microformats_principles the microformats principles] right now before proceeding any further.<br />
<br />
Any examples added which do not conform to these requirements will be deleted.<br />
<br />
== Table of Contents ==<br />
<br />
__TOC__<br />
<br />
== Examples ==<br />
<br />
=== Audio ===<br />
==== Speech ====<br />
Publication of audio speeches on blogs is often called "podcasting". In essence though, it is simply audio speech publishing.<br />
<br />
* [http://www.microformats.org/blog/2005/09/30/web-essentials-audio/ Microformats: Web Essentials Audio]<br />
** Appears to be composed of:<br />
*** title/summary of the recording<br />
*** clickable hyperlink to the recording (MP3)<br />
** Contextual:<br />
*** (primary) speaker is indicated in nearby text<br />
=== Music ===<br />
* ...<br />
<br />
=== Video ===<br />
Publication of video on blogs often goes by "videoblogging", "vlogging", "VODcasting", or "video podcasting". The typical process involves publishing a direct link to the video file within the blog entry. The blog entry can but does not have to include an embedded video player.<br />
<br />
* [http://FreeVlog.org FreeVlog]: the most popular tutorial on the web describing the vidoeblogging process by combining free tools and services (Blogger, OurMedia/Internet Archive, FeedBurner).<br />
** According to this process, a vidoeblog entry contains:<br />
*** Direct link to the video file<br />
*** Clickable thumbnail image/screen capture of the video<br />
<br />
* [http://joshkinberg.com/popupmaker Video Pop Up Maker]<br />
** This example based on the process taught at [http://FreeVlog.org FreeVlog] generates code to create a dynamic pop up window with embedded video player. The reasons for this are enumerated [http://www.unmediated.org/archives/2005/10/easily_create_p.php here]<br />
<br />
== Next Steps ==<br />
# Add more real-world, simple, minimal examples.<br />
# Research and organize existing/previous [[media-info-formats]], with a focus on formats for publishing '''common''', '''user-visible''' media information.<br />
# Start [[media-info-brainstorming]] based on examples.<br />
<br />
== See Also ==<br />
* [[media-metadata-examples]] - previous attempt which is a bit of a deep-dive mess, and includes formats which should be in a separate page. Probably useful as both a source of research.</div>JoshuaKinberghttps://microformats.org/wiki/index.php?title=rel-enclosure&diff=2711rel-enclosure2005-10-14T22:55:55Z<p>JoshuaKinberg: /* Multiple Enclosures */</p>
<hr />
<div>= rel="enclosure" =<br />
<br />
relEnclosure is a simple, open, format for indicating files to cache which is embeddable in (X)HTML, Atom, RSS, and arbitrary XML. relEnclosure is an [[elemental-microformat|elemental microformat]], one of several [[microformats|microformat]] open standards.<br />
<br />
__TOC__<br />
<br />
== Draft Specification 2005-06-21 ==<br />
=== Author ===<br />
[http://epeus.blogspot.com Kevin Marks], [http://technorati.com Technorati, Inc.]<br />
<br />
=== Copyright ===<br />
{{MicroFormatCopyrightStatement2004}}<br />
<br />
=== Patents ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Abstract ==<br />
<br />
relEnclosure is one of several microformats. By adding <code>rel="enclosure"</code> to a hyperlink, a page indicates that the destination of that hyperlink is intended to be downloaded and cached. E.g. with the following hyperlink:<br />
<br />
<pre><nowiki><br />
<a href="http://homepage.mac.com/kevinmarks/wwdc2005.mov" rel="enclosure">WWDC 2005 Keynote with chapters</a><br />
</nowiki></pre><br />
<br />
the author indicates that the movie should be downloaded.<br />
<br />
== Multiple Enclosures ==<br />
Multiple such rel="enclosure" hyperlinks indicate that several media items should be downloaded.<br />
<br />
'''Question:''' What if there are several alternative formats, such as high- and low-bandwidth recordings? Since <link rel="alternate" href="..."> is already defined in XHTML for that purpose, so how should it interact with this new rel tag?<br />
<br />
'''Response:''' rel="alternate" is defined in the HTML spec:<br />
<br />
<blockquote>Designates substitute versions for the document in which the link occurs.</blockquote><br />
<br />
In the case of enclosure links "alternate" is not suited, because the media file is not a substitute version of the document in which the link occurs - it is a substitute version of another link on the document in which the link occurs.<br />
<br />
'''Proposal:''' Multiple instances of the same enclosure (i.e. same video with different formats, size/resolution, bitrates, etc) could be grouped in a class="enclosure" block with multiple rel="enclosure" links. This would be analogous to <media:group> in [http://video.yahoo.com/mrss MRSS]<br />
<br />
== XMDP profile ==<br />
<pre><nowiki><br />
<dl class="profile"><br />
<dt id="rel">rel</dt><br />
<dd><p><br />
<a rel="help" href="http://www.w3.org/TR/html401/struct/links.html#adef-rel"><br />
HTML4 definition of the 'rel' attribute.</a> <br />
Here is an additional value.</p><br />
<dl><br />
<dt id="enclosure"> enclosure </dt><br />
<dd>Indicates that the referred resource is intended to be downloaded and cached</dd><br />
</dl><br />
</dd><br />
</dl><br />
</nowiki></pre><br />
<br />
== Implementations ==<br />
This section is '''informative'''.<br />
<br />
The following implementations have been developed which either generate or parse rel-enclosure links. If you have a rel-enclosure implementation, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.<br />
<br />
* [http://odeo.com ODEO] [http://odeo.com/blog/2005/07/adding-microformats-to-odeo.html publishes] rel-enclosure links for user podcast MP3s.<br />
* [http://joshkinberg.com/popupmaker/ Video Pop-Up Link Maker]: generates code for rel-enclosure links for videobloggers. Also generates javascript to launch a pop-up window with the video embedded.<br />
<br />
== References ==<br />
=== Normative References ===<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
<br />
=== Informative References ===<br />
* http://www.ietf.org/internet-drafts/draft-ietf-atompub-format-09.txt: <br />
** 4.2.7.2 The "rel" Attribute<br />
4. The value "enclosure" signifies that the IRI in the value of the<br />
href attribute identifies a related resource which is potentially<br />
large in size and might require special handling. For atom:link<br />
elements with rel="enclosure", the length attribute SHOULD be<br />
provided.</div>JoshuaKinberghttps://microformats.org/wiki/index.php?title=rel-enclosure&diff=2163rel-enclosure2005-10-14T22:54:59Z<p>JoshuaKinberg: /* Multiple Enclosures */</p>
<hr />
<div>= rel="enclosure" =<br />
<br />
relEnclosure is a simple, open, format for indicating files to cache which is embeddable in (X)HTML, Atom, RSS, and arbitrary XML. relEnclosure is an [[elemental-microformat|elemental microformat]], one of several [[microformats|microformat]] open standards.<br />
<br />
__TOC__<br />
<br />
== Draft Specification 2005-06-21 ==<br />
=== Author ===<br />
[http://epeus.blogspot.com Kevin Marks], [http://technorati.com Technorati, Inc.]<br />
<br />
=== Copyright ===<br />
{{MicroFormatCopyrightStatement2004}}<br />
<br />
=== Patents ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Abstract ==<br />
<br />
relEnclosure is one of several microformats. By adding <code>rel="enclosure"</code> to a hyperlink, a page indicates that the destination of that hyperlink is intended to be downloaded and cached. E.g. with the following hyperlink:<br />
<br />
<pre><nowiki><br />
<a href="http://homepage.mac.com/kevinmarks/wwdc2005.mov" rel="enclosure">WWDC 2005 Keynote with chapters</a><br />
</nowiki></pre><br />
<br />
the author indicates that the movie should be downloaded.<br />
<br />
== Multiple Enclosures ==<br />
Multiple such rel="enclosure" hyperlinks indicate that several media items should be downloaded.<br />
<br />
'''Question:''' What if there are several alternative formats, such as high- and low-bandwidth recordings? Since <link rel="alternate" href="..."> is already defined in XHTML for that purpose, so how should it interact with this new rel tag?<br />
<br />
'''Response:''' "Alternate" is defined in the HTML spec:<br />
<br />
"Designates substitute versions for the document in which the link occurs."<br />
<br />
In the case of enclosure links "alternate" is not suited, because the media file is not a substitute version of the document in which the link occurs - it is a substitute version of another link on the document in which the link occurs.<br />
<br />
'''Proposal:''' Multiple instances of the same enclosure (i.e. same video with different formats, size/resolution, bitrates, etc) could be grouped in a class="enclosure" block with multiple rel="enclosure" links. This would be analogous to <media:group> in [http://video.yahoo.com/mrss MRSS]<br />
<br />
== XMDP profile ==<br />
<pre><nowiki><br />
<dl class="profile"><br />
<dt id="rel">rel</dt><br />
<dd><p><br />
<a rel="help" href="http://www.w3.org/TR/html401/struct/links.html#adef-rel"><br />
HTML4 definition of the 'rel' attribute.</a> <br />
Here is an additional value.</p><br />
<dl><br />
<dt id="enclosure"> enclosure </dt><br />
<dd>Indicates that the referred resource is intended to be downloaded and cached</dd><br />
</dl><br />
</dd><br />
</dl><br />
</nowiki></pre><br />
<br />
== Implementations ==<br />
This section is '''informative'''.<br />
<br />
The following implementations have been developed which either generate or parse rel-enclosure links. If you have a rel-enclosure implementation, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.<br />
<br />
* [http://odeo.com ODEO] [http://odeo.com/blog/2005/07/adding-microformats-to-odeo.html publishes] rel-enclosure links for user podcast MP3s.<br />
* [http://joshkinberg.com/popupmaker/ Video Pop-Up Link Maker]: generates code for rel-enclosure links for videobloggers. Also generates javascript to launch a pop-up window with the video embedded.<br />
<br />
== References ==<br />
=== Normative References ===<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
<br />
=== Informative References ===<br />
* http://www.ietf.org/internet-drafts/draft-ietf-atompub-format-09.txt: <br />
** 4.2.7.2 The "rel" Attribute<br />
4. The value "enclosure" signifies that the IRI in the value of the<br />
href attribute identifies a related resource which is potentially<br />
large in size and might require special handling. For atom:link<br />
elements with rel="enclosure", the length attribute SHOULD be<br />
provided.</div>JoshuaKinberghttps://microformats.org/wiki/index.php?title=rel-enclosure&diff=2162rel-enclosure2005-10-14T22:44:25Z<p>JoshuaKinberg: /* Multiple Enclosures */</p>
<hr />
<div>= rel="enclosure" =<br />
<br />
relEnclosure is a simple, open, format for indicating files to cache which is embeddable in (X)HTML, Atom, RSS, and arbitrary XML. relEnclosure is an [[elemental-microformat|elemental microformat]], one of several [[microformats|microformat]] open standards.<br />
<br />
__TOC__<br />
<br />
== Draft Specification 2005-06-21 ==<br />
=== Author ===<br />
[http://epeus.blogspot.com Kevin Marks], [http://technorati.com Technorati, Inc.]<br />
<br />
=== Copyright ===<br />
{{MicroFormatCopyrightStatement2004}}<br />
<br />
=== Patents ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Abstract ==<br />
<br />
relEnclosure is one of several microformats. By adding <code>rel="enclosure"</code> to a hyperlink, a page indicates that the destination of that hyperlink is intended to be downloaded and cached. E.g. with the following hyperlink:<br />
<br />
<pre><nowiki><br />
<a href="http://homepage.mac.com/kevinmarks/wwdc2005.mov" rel="enclosure">WWDC 2005 Keynote with chapters</a><br />
</nowiki></pre><br />
<br />
the author indicates that the movie should be downloaded.<br />
<br />
== Multiple Enclosures ==<br />
Multiple such rel="enclosure" hyperlinks indicate that several media items should be downloaded.<br />
<br />
'''Question:''' What if there are several alternative formats, such as high- and low-bandwidth recordings? Since <link rel="alternate" href="..."> is already defined in XHTML for that purpose, so how should it interact with this new rel tag?<br />
<br />
'''Proposal:''' Multiple instances of the same enclosure (i.e. same video with different formats, size/resolution, bitrates, etc) could be grouped in a class="enclosure" block with multiple rel="enclosure" links. This would be analogous to <media:group> in [http://video.yahoo.com/mrss MRSS]<br />
<br />
== XMDP profile ==<br />
<pre><nowiki><br />
<dl class="profile"><br />
<dt id="rel">rel</dt><br />
<dd><p><br />
<a rel="help" href="http://www.w3.org/TR/html401/struct/links.html#adef-rel"><br />
HTML4 definition of the 'rel' attribute.</a> <br />
Here is an additional value.</p><br />
<dl><br />
<dt id="enclosure"> enclosure </dt><br />
<dd>Indicates that the referred resource is intended to be downloaded and cached</dd><br />
</dl><br />
</dd><br />
</dl><br />
</nowiki></pre><br />
<br />
== Implementations ==<br />
This section is '''informative'''.<br />
<br />
The following implementations have been developed which either generate or parse rel-enclosure links. If you have a rel-enclosure implementation, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.<br />
<br />
* [http://odeo.com ODEO] [http://odeo.com/blog/2005/07/adding-microformats-to-odeo.html publishes] rel-enclosure links for user podcast MP3s.<br />
* [http://joshkinberg.com/popupmaker/ Video Pop-Up Link Maker]: generates code for rel-enclosure links for videobloggers. Also generates javascript to launch a pop-up window with the video embedded.<br />
<br />
== References ==<br />
=== Normative References ===<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
<br />
=== Informative References ===<br />
* http://www.ietf.org/internet-drafts/draft-ietf-atompub-format-09.txt: <br />
** 4.2.7.2 The "rel" Attribute<br />
4. The value "enclosure" signifies that the IRI in the value of the<br />
href attribute identifies a related resource which is potentially<br />
large in size and might require special handling. For atom:link<br />
elements with rel="enclosure", the length attribute SHOULD be<br />
provided.</div>JoshuaKinberghttps://microformats.org/wiki/index.php?title=rel-enclosure&diff=2161rel-enclosure2005-10-14T22:43:58Z<p>JoshuaKinberg: /* Multiple Enclosures */</p>
<hr />
<div>= rel="enclosure" =<br />
<br />
relEnclosure is a simple, open, format for indicating files to cache which is embeddable in (X)HTML, Atom, RSS, and arbitrary XML. relEnclosure is an [[elemental-microformat|elemental microformat]], one of several [[microformats|microformat]] open standards.<br />
<br />
__TOC__<br />
<br />
== Draft Specification 2005-06-21 ==<br />
=== Author ===<br />
[http://epeus.blogspot.com Kevin Marks], [http://technorati.com Technorati, Inc.]<br />
<br />
=== Copyright ===<br />
{{MicroFormatCopyrightStatement2004}}<br />
<br />
=== Patents ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Abstract ==<br />
<br />
relEnclosure is one of several microformats. By adding <code>rel="enclosure"</code> to a hyperlink, a page indicates that the destination of that hyperlink is intended to be downloaded and cached. E.g. with the following hyperlink:<br />
<br />
<pre><nowiki><br />
<a href="http://homepage.mac.com/kevinmarks/wwdc2005.mov" rel="enclosure">WWDC 2005 Keynote with chapters</a><br />
</nowiki></pre><br />
<br />
the author indicates that the movie should be downloaded.<br />
<br />
== Multiple Enclosures ==<br />
Multiple such rel="enclosure" hyperlinks indicate that several media items should be downloaded.<br />
<br />
'''Question:''' What if there are several alternative formats, such as high- and low-bandwidth recordings? Since <link rel="alternate" href="..."> is already defined in XHTML for that purpose, so how should it interact with this new rel tag?<br />
<br />
'''Proposal:''' Multiple instances of the same enclosure (i.e. same video with different formats, size/resolution, bitrates, etc) could be grouped in a class="enclosure" block with multiple rel="enclosure" links. This would be analogous to <media:group> in [http://video.yahoo.com/mrss MRSS] - [[user:JoshuaKinberg|JoshuaKinberg]] at 14 Oct. 2005, 6:37pm EST<br />
<br />
== XMDP profile ==<br />
<pre><nowiki><br />
<dl class="profile"><br />
<dt id="rel">rel</dt><br />
<dd><p><br />
<a rel="help" href="http://www.w3.org/TR/html401/struct/links.html#adef-rel"><br />
HTML4 definition of the 'rel' attribute.</a> <br />
Here is an additional value.</p><br />
<dl><br />
<dt id="enclosure"> enclosure </dt><br />
<dd>Indicates that the referred resource is intended to be downloaded and cached</dd><br />
</dl><br />
</dd><br />
</dl><br />
</nowiki></pre><br />
<br />
== Implementations ==<br />
This section is '''informative'''.<br />
<br />
The following implementations have been developed which either generate or parse rel-enclosure links. If you have a rel-enclosure implementation, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.<br />
<br />
* [http://odeo.com ODEO] [http://odeo.com/blog/2005/07/adding-microformats-to-odeo.html publishes] rel-enclosure links for user podcast MP3s.<br />
* [http://joshkinberg.com/popupmaker/ Video Pop-Up Link Maker]: generates code for rel-enclosure links for videobloggers. Also generates javascript to launch a pop-up window with the video embedded.<br />
<br />
== References ==<br />
=== Normative References ===<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
<br />
=== Informative References ===<br />
* http://www.ietf.org/internet-drafts/draft-ietf-atompub-format-09.txt: <br />
** 4.2.7.2 The "rel" Attribute<br />
4. The value "enclosure" signifies that the IRI in the value of the<br />
href attribute identifies a related resource which is potentially<br />
large in size and might require special handling. For atom:link<br />
elements with rel="enclosure", the length attribute SHOULD be<br />
provided.</div>JoshuaKinberghttps://microformats.org/wiki/index.php?title=rel-enclosure&diff=2160rel-enclosure2005-10-14T22:43:36Z<p>JoshuaKinberg: /* Implementations */</p>
<hr />
<div>= rel="enclosure" =<br />
<br />
relEnclosure is a simple, open, format for indicating files to cache which is embeddable in (X)HTML, Atom, RSS, and arbitrary XML. relEnclosure is an [[elemental-microformat|elemental microformat]], one of several [[microformats|microformat]] open standards.<br />
<br />
__TOC__<br />
<br />
== Draft Specification 2005-06-21 ==<br />
=== Author ===<br />
[http://epeus.blogspot.com Kevin Marks], [http://technorati.com Technorati, Inc.]<br />
<br />
=== Copyright ===<br />
{{MicroFormatCopyrightStatement2004}}<br />
<br />
=== Patents ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Abstract ==<br />
<br />
relEnclosure is one of several microformats. By adding <code>rel="enclosure"</code> to a hyperlink, a page indicates that the destination of that hyperlink is intended to be downloaded and cached. E.g. with the following hyperlink:<br />
<br />
<pre><nowiki><br />
<a href="http://homepage.mac.com/kevinmarks/wwdc2005.mov" rel="enclosure">WWDC 2005 Keynote with chapters</a><br />
</nowiki></pre><br />
<br />
the author indicates that the movie should be downloaded.<br />
<br />
== Multiple Enclosures ==<br />
Multiple such rel="enclosure" hyperlinks indicate that several media items should be downloaded.<br />
<br />
'''Question:''' What if there are several alternative formats, such as high- and low-bandwidth recordings? Since <link rel="alternate" href="..."> is already defined in XHTML for that purpose, so how should it interact with this new rel tag?<br />
<br />
'''Proposal:''' Multiple instances of the same enclosure (i.e. same video with different formats, size/resolution, bitrates, etc) could be grouped in a class="enclosure" block with multiple rel="enclosure" links. This would be analogous to <media:group> in [http://video.yahoo.com/mrss MRSS]<br />
<br />
- [[user:JoshuaKinberg|JoshuaKinberg]] at 14 Oct. 2005, 6:37pm EST<br />
<br />
== XMDP profile ==<br />
<pre><nowiki><br />
<dl class="profile"><br />
<dt id="rel">rel</dt><br />
<dd><p><br />
<a rel="help" href="http://www.w3.org/TR/html401/struct/links.html#adef-rel"><br />
HTML4 definition of the 'rel' attribute.</a> <br />
Here is an additional value.</p><br />
<dl><br />
<dt id="enclosure"> enclosure </dt><br />
<dd>Indicates that the referred resource is intended to be downloaded and cached</dd><br />
</dl><br />
</dd><br />
</dl><br />
</nowiki></pre><br />
<br />
== Implementations ==<br />
This section is '''informative'''.<br />
<br />
The following implementations have been developed which either generate or parse rel-enclosure links. If you have a rel-enclosure implementation, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.<br />
<br />
* [http://odeo.com ODEO] [http://odeo.com/blog/2005/07/adding-microformats-to-odeo.html publishes] rel-enclosure links for user podcast MP3s.<br />
* [http://joshkinberg.com/popupmaker/ Video Pop-Up Link Maker]: generates code for rel-enclosure links for videobloggers. Also generates javascript to launch a pop-up window with the video embedded.<br />
<br />
== References ==<br />
=== Normative References ===<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
<br />
=== Informative References ===<br />
* http://www.ietf.org/internet-drafts/draft-ietf-atompub-format-09.txt: <br />
** 4.2.7.2 The "rel" Attribute<br />
4. The value "enclosure" signifies that the IRI in the value of the<br />
href attribute identifies a related resource which is potentially<br />
large in size and might require special handling. For atom:link<br />
elements with rel="enclosure", the length attribute SHOULD be<br />
provided.</div>JoshuaKinberghttps://microformats.org/wiki/index.php?title=rel-enclosure&diff=2159rel-enclosure2005-10-14T22:42:06Z<p>JoshuaKinberg: /* Implementations */</p>
<hr />
<div>= rel="enclosure" =<br />
<br />
relEnclosure is a simple, open, format for indicating files to cache which is embeddable in (X)HTML, Atom, RSS, and arbitrary XML. relEnclosure is an [[elemental-microformat|elemental microformat]], one of several [[microformats|microformat]] open standards.<br />
<br />
__TOC__<br />
<br />
== Draft Specification 2005-06-21 ==<br />
=== Author ===<br />
[http://epeus.blogspot.com Kevin Marks], [http://technorati.com Technorati, Inc.]<br />
<br />
=== Copyright ===<br />
{{MicroFormatCopyrightStatement2004}}<br />
<br />
=== Patents ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Abstract ==<br />
<br />
relEnclosure is one of several microformats. By adding <code>rel="enclosure"</code> to a hyperlink, a page indicates that the destination of that hyperlink is intended to be downloaded and cached. E.g. with the following hyperlink:<br />
<br />
<pre><nowiki><br />
<a href="http://homepage.mac.com/kevinmarks/wwdc2005.mov" rel="enclosure">WWDC 2005 Keynote with chapters</a><br />
</nowiki></pre><br />
<br />
the author indicates that the movie should be downloaded.<br />
<br />
== Multiple Enclosures ==<br />
Multiple such rel="enclosure" hyperlinks indicate that several media items should be downloaded.<br />
<br />
'''Question:''' What if there are several alternative formats, such as high- and low-bandwidth recordings? Since <link rel="alternate" href="..."> is already defined in XHTML for that purpose, so how should it interact with this new rel tag?<br />
<br />
'''Proposal:''' Multiple instances of the same enclosure (i.e. same video with different formats, size/resolution, bitrates, etc) could be grouped in a class="enclosure" block with multiple rel="enclosure" links. This would be analogous to <media:group> in [http://video.yahoo.com/mrss MRSS]<br />
<br />
- [[user:JoshuaKinberg|JoshuaKinberg]] at 14 Oct. 2005, 6:37pm EST<br />
<br />
== XMDP profile ==<br />
<pre><nowiki><br />
<dl class="profile"><br />
<dt id="rel">rel</dt><br />
<dd><p><br />
<a rel="help" href="http://www.w3.org/TR/html401/struct/links.html#adef-rel"><br />
HTML4 definition of the 'rel' attribute.</a> <br />
Here is an additional value.</p><br />
<dl><br />
<dt id="enclosure"> enclosure </dt><br />
<dd>Indicates that the referred resource is intended to be downloaded and cached</dd><br />
</dl><br />
</dd><br />
</dl><br />
</nowiki></pre><br />
<br />
== Implementations ==<br />
This section is '''informative'''.<br />
<br />
The following implementations have been developed which either generate or parse rel-enclosure links. If you have a rel-enclosure implementation, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.<br />
<br />
* [http://odeo.com ODEO] [http://odeo.com/blog/2005/07/adding-microformats-to-odeo.html publishes] rel-enclosure links for user podcast MP3s.<br />
* [http://joshkinberg.com/popupmaker/ Video Pop-Up Link Maker]: generates code for rel-enclosure links for videobloggers. Also generates javascript to launch a pop-up window with the video embedded.<br />
<br />
- [[user:JoshuaKinberg|JoshuaKinberg]] at 14 Oct. 2005, 6:41pm EST<br />
<br />
== References ==<br />
=== Normative References ===<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
<br />
=== Informative References ===<br />
* http://www.ietf.org/internet-drafts/draft-ietf-atompub-format-09.txt: <br />
** 4.2.7.2 The "rel" Attribute<br />
4. The value "enclosure" signifies that the IRI in the value of the<br />
href attribute identifies a related resource which is potentially<br />
large in size and might require special handling. For atom:link<br />
elements with rel="enclosure", the length attribute SHOULD be<br />
provided.</div>JoshuaKinberghttps://microformats.org/wiki/index.php?title=rel-enclosure&diff=2158rel-enclosure2005-10-14T22:39:26Z<p>JoshuaKinberg: /* Multiple Enclosures */</p>
<hr />
<div>= rel="enclosure" =<br />
<br />
relEnclosure is a simple, open, format for indicating files to cache which is embeddable in (X)HTML, Atom, RSS, and arbitrary XML. relEnclosure is an [[elemental-microformat|elemental microformat]], one of several [[microformats|microformat]] open standards.<br />
<br />
__TOC__<br />
<br />
== Draft Specification 2005-06-21 ==<br />
=== Author ===<br />
[http://epeus.blogspot.com Kevin Marks], [http://technorati.com Technorati, Inc.]<br />
<br />
=== Copyright ===<br />
{{MicroFormatCopyrightStatement2004}}<br />
<br />
=== Patents ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Abstract ==<br />
<br />
relEnclosure is one of several microformats. By adding <code>rel="enclosure"</code> to a hyperlink, a page indicates that the destination of that hyperlink is intended to be downloaded and cached. E.g. with the following hyperlink:<br />
<br />
<pre><nowiki><br />
<a href="http://homepage.mac.com/kevinmarks/wwdc2005.mov" rel="enclosure">WWDC 2005 Keynote with chapters</a><br />
</nowiki></pre><br />
<br />
the author indicates that the movie should be downloaded.<br />
<br />
== Multiple Enclosures ==<br />
Multiple such rel="enclosure" hyperlinks indicate that several media items should be downloaded.<br />
<br />
'''Question:''' What if there are several alternative formats, such as high- and low-bandwidth recordings? Since <link rel="alternate" href="..."> is already defined in XHTML for that purpose, so how should it interact with this new rel tag?<br />
<br />
'''Proposal:''' Multiple instances of the same enclosure (i.e. same video with different formats, size/resolution, bitrates, etc) could be grouped in a class="enclosure" block with multiple rel="enclosure" links. This would be analogous to <media:group> in [http://video.yahoo.com/mrss MRSS]<br />
<br />
- [[user:JoshuaKinberg|JoshuaKinberg]] at 14 Oct. 2005, 6:37pm EST<br />
<br />
== XMDP profile ==<br />
<pre><nowiki><br />
<dl class="profile"><br />
<dt id="rel">rel</dt><br />
<dd><p><br />
<a rel="help" href="http://www.w3.org/TR/html401/struct/links.html#adef-rel"><br />
HTML4 definition of the 'rel' attribute.</a> <br />
Here is an additional value.</p><br />
<dl><br />
<dt id="enclosure"> enclosure </dt><br />
<dd>Indicates that the referred resource is intended to be downloaded and cached</dd><br />
</dl><br />
</dd><br />
</dl><br />
</nowiki></pre><br />
<br />
== Implementations ==<br />
This section is '''informative'''.<br />
<br />
The following implementations have been developed which either generate or parse rel-enclosure links. If you have a rel-enclosure implementation, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.<br />
<br />
* [http://odeo.com ODEO] [http://odeo.com/blog/2005/07/adding-microformats-to-odeo.html publishes] rel-enclosure links for user podcast MP3s.<br />
<br />
== References ==<br />
=== Normative References ===<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
<br />
=== Informative References ===<br />
* http://www.ietf.org/internet-drafts/draft-ietf-atompub-format-09.txt: <br />
** 4.2.7.2 The "rel" Attribute<br />
4. The value "enclosure" signifies that the IRI in the value of the<br />
href attribute identifies a related resource which is potentially<br />
large in size and might require special handling. For atom:link<br />
elements with rel="enclosure", the length attribute SHOULD be<br />
provided.</div>JoshuaKinberghttps://microformats.org/wiki/index.php?title=rel-enclosure&diff=2157rel-enclosure2005-10-14T22:38:34Z<p>JoshuaKinberg: /* Multiple Enclosures */</p>
<hr />
<div>= rel="enclosure" =<br />
<br />
relEnclosure is a simple, open, format for indicating files to cache which is embeddable in (X)HTML, Atom, RSS, and arbitrary XML. relEnclosure is an [[elemental-microformat|elemental microformat]], one of several [[microformats|microformat]] open standards.<br />
<br />
__TOC__<br />
<br />
== Draft Specification 2005-06-21 ==<br />
=== Author ===<br />
[http://epeus.blogspot.com Kevin Marks], [http://technorati.com Technorati, Inc.]<br />
<br />
=== Copyright ===<br />
{{MicroFormatCopyrightStatement2004}}<br />
<br />
=== Patents ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Abstract ==<br />
<br />
relEnclosure is one of several microformats. By adding <code>rel="enclosure"</code> to a hyperlink, a page indicates that the destination of that hyperlink is intended to be downloaded and cached. E.g. with the following hyperlink:<br />
<br />
<pre><nowiki><br />
<a href="http://homepage.mac.com/kevinmarks/wwdc2005.mov" rel="enclosure">WWDC 2005 Keynote with chapters</a><br />
</nowiki></pre><br />
<br />
the author indicates that the movie should be downloaded.<br />
<br />
== Multiple Enclosures ==<br />
Multiple such rel="enclosure" hyperlinks indicate that several media items should be downloaded.<br />
<br />
''Question:'' What if there are several alternative formats, such as high- and low-bandwidth recordings? Since <link rel="alternate" href="..."> is already defined in XHTML for that purpose, so how should it interact with this new rel tag?<br />
<br />
''Proposal:'' Multiple instances of the same enclosure (i.e. same video with different formats, size/resolution, bitrates, etc) could be grouped in a class="enclosure" block with multiple rel="enclosure" links. This would be analogous to <media:group> in [http://video.yahoo.com/mrss MRSS]<br />
<br />
- [[user:JoshuaKinberg|JoshuaKinberg]] at 14 Oct. 2005, 6:37pm EST<br />
<br />
== XMDP profile ==<br />
<pre><nowiki><br />
<dl class="profile"><br />
<dt id="rel">rel</dt><br />
<dd><p><br />
<a rel="help" href="http://www.w3.org/TR/html401/struct/links.html#adef-rel"><br />
HTML4 definition of the 'rel' attribute.</a> <br />
Here is an additional value.</p><br />
<dl><br />
<dt id="enclosure"> enclosure </dt><br />
<dd>Indicates that the referred resource is intended to be downloaded and cached</dd><br />
</dl><br />
</dd><br />
</dl><br />
</nowiki></pre><br />
<br />
== Implementations ==<br />
This section is '''informative'''.<br />
<br />
The following implementations have been developed which either generate or parse rel-enclosure links. If you have a rel-enclosure implementation, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.<br />
<br />
* [http://odeo.com ODEO] [http://odeo.com/blog/2005/07/adding-microformats-to-odeo.html publishes] rel-enclosure links for user podcast MP3s.<br />
<br />
== References ==<br />
=== Normative References ===<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
<br />
=== Informative References ===<br />
* http://www.ietf.org/internet-drafts/draft-ietf-atompub-format-09.txt: <br />
** 4.2.7.2 The "rel" Attribute<br />
4. The value "enclosure" signifies that the IRI in the value of the<br />
href attribute identifies a related resource which is potentially<br />
large in size and might require special handling. For atom:link<br />
elements with rel="enclosure", the length attribute SHOULD be<br />
provided.</div>JoshuaKinberghttps://microformats.org/wiki/index.php?title=rel-enclosure&diff=2156rel-enclosure2005-10-14T22:38:07Z<p>JoshuaKinberg: /* Multiple Enclosures */</p>
<hr />
<div>= rel="enclosure" =<br />
<br />
relEnclosure is a simple, open, format for indicating files to cache which is embeddable in (X)HTML, Atom, RSS, and arbitrary XML. relEnclosure is an [[elemental-microformat|elemental microformat]], one of several [[microformats|microformat]] open standards.<br />
<br />
__TOC__<br />
<br />
== Draft Specification 2005-06-21 ==<br />
=== Author ===<br />
[http://epeus.blogspot.com Kevin Marks], [http://technorati.com Technorati, Inc.]<br />
<br />
=== Copyright ===<br />
{{MicroFormatCopyrightStatement2004}}<br />
<br />
=== Patents ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Abstract ==<br />
<br />
relEnclosure is one of several microformats. By adding <code>rel="enclosure"</code> to a hyperlink, a page indicates that the destination of that hyperlink is intended to be downloaded and cached. E.g. with the following hyperlink:<br />
<br />
<pre><nowiki><br />
<a href="http://homepage.mac.com/kevinmarks/wwdc2005.mov" rel="enclosure">WWDC 2005 Keynote with chapters</a><br />
</nowiki></pre><br />
<br />
the author indicates that the movie should be downloaded.<br />
<br />
== Multiple Enclosures ==<br />
Multiple such rel="enclosure" hyperlinks indicate that several media items should be downloaded.<br />
<br />
''Question:'' What if there are several alternative formats, such as high- and low-bandwidth recordings? Since <link rel="alternate" href="..."> is already defined in XHTML for that purpose, so how should it interact with this new rel tag?<br />
<br />
''Proposal:'' Multiple instances of the same enclosure (i.e. same video with different formats, size/resolution, bitrates, etc) could be grouped in a class="enclosure" block with multiple rel="enclosure" links. This would be analogous to <media:group> in [http://video.yahoo.com/mrss|MRSS]<br />
<br />
- [[user:JoshuaKinberg|JoshuaKinberg]] at 14 Oct. 2005, 6:37pm EST<br />
<br />
== XMDP profile ==<br />
<pre><nowiki><br />
<dl class="profile"><br />
<dt id="rel">rel</dt><br />
<dd><p><br />
<a rel="help" href="http://www.w3.org/TR/html401/struct/links.html#adef-rel"><br />
HTML4 definition of the 'rel' attribute.</a> <br />
Here is an additional value.</p><br />
<dl><br />
<dt id="enclosure"> enclosure </dt><br />
<dd>Indicates that the referred resource is intended to be downloaded and cached</dd><br />
</dl><br />
</dd><br />
</dl><br />
</nowiki></pre><br />
<br />
== Implementations ==<br />
This section is '''informative'''.<br />
<br />
The following implementations have been developed which either generate or parse rel-enclosure links. If you have a rel-enclosure implementation, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.<br />
<br />
* [http://odeo.com ODEO] [http://odeo.com/blog/2005/07/adding-microformats-to-odeo.html publishes] rel-enclosure links for user podcast MP3s.<br />
<br />
== References ==<br />
=== Normative References ===<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
<br />
=== Informative References ===<br />
* http://www.ietf.org/internet-drafts/draft-ietf-atompub-format-09.txt: <br />
** 4.2.7.2 The "rel" Attribute<br />
4. The value "enclosure" signifies that the IRI in the value of the<br />
href attribute identifies a related resource which is potentially<br />
large in size and might require special handling. For atom:link<br />
elements with rel="enclosure", the length attribute SHOULD be<br />
provided.</div>JoshuaKinberghttps://microformats.org/wiki/index.php?title=rel-enclosure&diff=2155rel-enclosure2005-10-14T22:37:45Z<p>JoshuaKinberg: /* Multiple Enclosures */</p>
<hr />
<div>= rel="enclosure" =<br />
<br />
relEnclosure is a simple, open, format for indicating files to cache which is embeddable in (X)HTML, Atom, RSS, and arbitrary XML. relEnclosure is an [[elemental-microformat|elemental microformat]], one of several [[microformats|microformat]] open standards.<br />
<br />
__TOC__<br />
<br />
== Draft Specification 2005-06-21 ==<br />
=== Author ===<br />
[http://epeus.blogspot.com Kevin Marks], [http://technorati.com Technorati, Inc.]<br />
<br />
=== Copyright ===<br />
{{MicroFormatCopyrightStatement2004}}<br />
<br />
=== Patents ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Abstract ==<br />
<br />
relEnclosure is one of several microformats. By adding <code>rel="enclosure"</code> to a hyperlink, a page indicates that the destination of that hyperlink is intended to be downloaded and cached. E.g. with the following hyperlink:<br />
<br />
<pre><nowiki><br />
<a href="http://homepage.mac.com/kevinmarks/wwdc2005.mov" rel="enclosure">WWDC 2005 Keynote with chapters</a><br />
</nowiki></pre><br />
<br />
the author indicates that the movie should be downloaded.<br />
<br />
== Multiple Enclosures ==<br />
Multiple such rel="enclosure" hyperlinks indicate that several media items should be downloaded.<br />
<br />
''Question:'' What if there are several alternative formats, such as high- and low-bandwidth recordings? Since <link rel="alternate" href="..."> is already defined in XHTML for that purpose, so how should it interact with this new rel tag?<br />
<br />
''Proposal:'' Multiple instances of the same enclosure (i.e. same video with different formats, size/resolution, bitrates, etc) could be grouped in a class="enclosure" block with multiple rel="enclosure" links. This would be analogous to <media:group> in [http://video.yahoo.com/mrss|MRSS]<br />
<br />
- [[user:JoshuaKinberg]] at 14 Oct. 2005, 6:37pm EST<br />
<br />
== XMDP profile ==<br />
<pre><nowiki><br />
<dl class="profile"><br />
<dt id="rel">rel</dt><br />
<dd><p><br />
<a rel="help" href="http://www.w3.org/TR/html401/struct/links.html#adef-rel"><br />
HTML4 definition of the 'rel' attribute.</a> <br />
Here is an additional value.</p><br />
<dl><br />
<dt id="enclosure"> enclosure </dt><br />
<dd>Indicates that the referred resource is intended to be downloaded and cached</dd><br />
</dl><br />
</dd><br />
</dl><br />
</nowiki></pre><br />
<br />
== Implementations ==<br />
This section is '''informative'''.<br />
<br />
The following implementations have been developed which either generate or parse rel-enclosure links. If you have a rel-enclosure implementation, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.<br />
<br />
* [http://odeo.com ODEO] [http://odeo.com/blog/2005/07/adding-microformats-to-odeo.html publishes] rel-enclosure links for user podcast MP3s.<br />
<br />
== References ==<br />
=== Normative References ===<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
<br />
=== Informative References ===<br />
* http://www.ietf.org/internet-drafts/draft-ietf-atompub-format-09.txt: <br />
** 4.2.7.2 The "rel" Attribute<br />
4. The value "enclosure" signifies that the IRI in the value of the<br />
href attribute identifies a related resource which is potentially<br />
large in size and might require special handling. For atom:link<br />
elements with rel="enclosure", the length attribute SHOULD be<br />
provided.</div>JoshuaKinberg