https://microformats.org/wiki/api.php?action=feedcontributions&user=Ianloic&feedformat=atomMicroformats Wiki - User contributions [en]2024-03-19T08:26:03ZUser contributionsMediaWiki 1.38.4https://microformats.org/wiki/index.php?title=page-summary-formats&diff=11207page-summary-formats2006-12-11T01:11:42Z<p>Ianloic: /* Issues */</p>
<hr />
<div><h1>Page Summary Formats</h1><br />
<br />
This page describes existing formats that enable an author to publish a summary description for a page. Whether or not this is worthy of doing research (e.g. [[page-summary-examples]], [[page-summary-brainstorming]]) for a microformat is open to debate. Nonetheless, it doesn't hurt to at least have a place to document existing formats.<br />
<br />
==Meta description==<br />
<br />
HTML4.01 provides meta description as an example in [http://www.w3.org/TR/html401/appendix/notes.html Appendix B: Performance, Implementation, and Design Notes] of the [http://www.w3.org/TR/html401/ HTML 4.01 spec]. E.g.<br />
<br />
<code><nowiki><META name="description" content="Idyllic European vacations"></nowiki></code><br />
<br />
===Product Support===<br />
<br />
Google search results display the value of the meta description element for a page when that page is listed in Google search results.<br />
<br />
===Issues===<br />
<br />
* '''Invisible.''' meta description is invisible metadata on the page and therefore violates microformats principles.<br />
<br />
* '''Depends on <code>head</code> element.''' This summary format depends on the author having access to the head element which in many (most?) web authoring/ publishing scenarios the content author has no access.<br />
<br />
== Microsummary ==<br />
<br />
Mozilla has introduced a proprietary format called "microsummary", which is used in Firefox 2.0's support for bookmarks.<br />
<br />
Note:<br />
<br />
#that microsummaries are not intended simply to deliver a summary of a page; they may be used, for example, for a "deal of the day", "last updated" date or time, a new headline, or other timely and dynamic information.<br />
#a "microformat" consisting of a <code>class="microsummary"</code> attribute would allow a piece of content (a span including a "last updated date", for example), to be extracted from a page, by software.<br />
#if multiple tags included <code>class="microsummary"</code>, we'd need to decide whether they each represent different microsummaries or they all represent a single microsummary whose value is the concatenation of each tag's content. The former seems saner, but sometimes microsummary content is scattered around the page (f.e. an eBay auction item microsummary might contain the name of the item, the auction end date, and the current high bid, but that information appears in three separate places in the page).<br />
<br />
===Documentation===<br />
* http://wiki.mozilla.org/Microsummaries<br />
<br />
===Code===<br />
* [http://www.xs4all.nl/~jlpoutre/BoT/WP/microsummary/ WP-Microsummary plugin for WordPress]<br />
<br />
===Examples of discussion===<br />
* [http://george.hotelling.net/90percent/geekery/firefox_2s_great_new_feature_with_a_horrible_ui.php George Hotelling]<br />
<br />
===Firefox extension===<br />
* [http://www.melez.com/mykzilla/2006/10/improving-microsummary-discoverability.html Microsummary Buddy]<br />
<br />
===Examples===<br />
*West Midland Bird Club<br />
**[http://www.westmidlandbirdclub.com/new.htm What's New]<br />
**[http://www.westmidlandbirdclub.com/ladywalk/latest.htm Ladywalk News]<br />
<br />
===Issues===<br />
<br />
* '''Invisible.''' Though different from meta description in that the <code>link</code> tag is used to relate to a summary at another URL - this doesn't actually markup the summary content itself. Since the content is not necessarily visible on the page itself, an author could easily change the page content without noticing or even knowing to bother to change the referenced "summary" page/ resource (except, of course, where the microsummary is automatically generated, such as by extracting the first "H2", or the content of a div or span with a specific ID, or the last-updated date). Thus this method has all the same potential flaws of typical invisible metadata publishing, which is that overtime it may rot, become out of date, unreliable and untrustworthy in general.<br />
<br />
* '''Depends on <code>head</code> element.''' This summary format may depend on the author having access to the head element which in many (most?) web authoring/ publishing scenarios the content author has no access.<br />
<br />
* Haven't we already solved 99% of this problem with RSS and the <code>title</code> element? [[User:Ianloic|Ianloic]] 17:11, 10 Dec 2006 (PST)</div>Ianloichttps://microformats.org/wiki/index.php?title=hresume-feedback&diff=11242hresume-feedback2006-12-10T23:58:16Z<p>Ianloic: /* General Comments */</p>
<hr />
<div>= hresume-feedback =<br />
<br />
This document is for keeping track of feedback about [[hresume]], one of several [[microformats]].<br />
<br />
== Feedback ==<br />
=== General Questions ===<br />
See the [[hresume-faq|hresume FAQ]].<br />
<br />
=== General Comments ===<br />
<br />
* Upon implementing [[hresume]] at [http://davecardwell.co.uk/cv/ http://davecardwell.co.uk/cv/], I had the following observations:<br />
<br />
** I used [[hcalendar]]'s optional "description" element to include a short paragraph of text about each section of education/employment. The examples on the [[hresume]] page could be updated to mention this ability.<br />
<br />
** A richer way of marking up qualifications would have been nice. If you view the source of my resume you'll see I marked up each subject as a "skill". This, however, doesn't convey any information about the level or grade achieved. The minimal set for the main educational qualifications in England seems to be qualification(level, subject(s), grade(s)). A section from my resume would then be:<br />
<pre> <tbody class="qualification"><br />
<tr><br />
<td class="level" rowspan="2"><br />
<abbr title="Advanced">A</abbr> Level<br />
</td><br />
<th class="subject" scope="row"><br />
Business Studies<br />
</th><br />
<td class="grade"><br />
B<br />
</td><br />
</tr><br />
<tr><br />
<th class="subject" scope="row"><br />
Computing<br />
</th><br />
<td class="grade"><br />
A<br />
</td><br />
</tr><br />
</tbody></pre><br />
<br />
Further investigation might show the need for optional information about awarding bodies and such. Not sure if a qualification element would satisfy the 80/20 condition.<br />
<br />
[[User:Dave Cardwell|Dave Cardwell]] 06:53, 19 Feb 2006 (GMT)<br />
<br />
* I and others on the #microformats IRC channel have expressed a concern about the way skills are represented. Introducing unnecessary links into a resume is undesirable, especially when you have to link to a page like [http://en.wikipedia.org/wiki/Perl http://en.wikipedia.org/wiki/Perl] to conform to the rel-tag standard while [http://www.perl.org/ http://www.perl.org] might be more intuitive. Non-visual user agents like screen readers will have a great deal of meaningless links to trawl through, and search engines may infer relationships that do not exist.<br />
<br />
[[User:Dave Cardwell|Dave Cardwell]] 04:54, 22 Feb 2006 (GMT)<br />
<br />
<br />
* Our thoughts:<br />
We would love to be able to mark-up the following data:<br />
<br />
Contact Info = hCard<br />
<br />
Experience (our issue is with current employment)*<br />
[company name]<br />
[position/title]<br />
[dates]<br />
[location]<br />
[Description]<br />
<br />
Education<br />
[school]<br />
[major]<br />
[degree]<br />
[dates]<br />
[location]<br />
<br />
Accreditation <br />
[type] (PD, CPA, JD and so on)<br />
[date]<br />
<br />
*how do you represent current positions that have no end date? Maybe lack of date means present?<br />
<br />
Here is our hResume plugin for WordPress (in development):<br />
<a href="http://www.flickr.com/photos/alexmuse/144781779/" title="Photo Sharing"><img src="http://static.flickr.com/44/144781779_ddc4d07460_o.jpg"</a><br />
<br />
[[User:Alexander Muse|Alexander Muse]] 08:54, 11 May 2006 (GMT)<br />
<br />
*Suggestion: Reference information - should there be a field of "References", where hCard information would be held for references? Also, perhaps a distinction between three types (e.g. personal (a friend), professional (e.g. previous boss), educational (e.g. university lecturer)) in a similar method to hCard's telephone type distinctions? If this is already accounted for, what method would you suggest for implementing this?<br />
<br />
*When working on my resume I tried to mark it up as hResume but I hit a couple of show-stoppers for me. If I had the choice of marking it up to look and behave like I wanted or be a valid hResume I'd chose for former and that's what I ended up having to do. My issues were:<br />
**It's recommended to put the contact hCard in an &lt;address&gt; but address is inline and I wanted to put block elements in there. I could have worked around that with CSS display: but I wanted to be able to render to text with links or w3m which don't support enough CSS for that.<br />
**hResume builds on rel-tag for describing skills, but I didn't want my skills section filled with links (no matter how they're rendered - I don't want them clickable).<br />
[[User:Ianloic|Ianloic]] 15:58, 10 Dec 2006 (PST)</div>Ianloichttps://microformats.org/wiki/index.php?title=User:Ianloic&diff=32204User:Ianloic2006-08-31T18:01:17Z<p>Ianloic: </p>
<hr />
<div>Ian McKellar works at Flock, thinks about social bookmarking and atom, and is still sceptical about microformats. He likes RDF more than you do.</div>Ianloichttps://microformats.org/wiki/index.php?title=irc&diff=8458irc2006-08-31T18:00:40Z<p>Ianloic: adding myself</p>
<hr />
<div>__NOTOC__<br />
= Microformats IRC =<br />
<br />
We have an IRC channel, [irc://irc.freenode.net/microformats #microformats on the freenode network].<br />
<br />
There's typically someone there at any point during the day, though there isn't always active discussion. Sometimes, though this is the best place to discuss issues that need lots of back and forth discussion.<br />
<br />
== People on irc ==<br />
A list of IRC regulars and their normal timezones. (winter/summer)<br />
<br />
* [[User:Adam Craven|AdamCraven]] (+0000)<br />
* [[User:Amette|amette]] (+1000)<br />
* [[User:B.K._DeLong|bkdelong]] (-0500/-0400)<br />
* [[User:Ben Ward|BenWard]] (+0000)<br />
* [[User:BenjaminCarlyle|BenjaminCarlyle]] (+1000)<br />
* [[User:Boneill|boneill]] (+0000)<br />
* [[User:Brian|briansuda]] (-0600/-0500)<br />
* [[User:ColinDDevroe|cdevroe]] (-0500/-0600)<br />
* [[User:Cgriego|cgriego]] (-0600/-0500)<br />
* [[User:ChrisCasciano|pnhChris]] (-0500/-0400)<br />
* [[User:ChrisMessina|factoryjoe]] (-0800/-0700)<br />
* [[User:ChristopherStJohn|cks]] (-0600/-0500)<br />
* [[User:DanC|DanC]] (-0600/-0500)<br />
** office hours: Wednesday afternoons, America/Chicago time<br />
* [[User:Dave Cardwell|davecardwell]] (+0000)<br />
* [[User:DeanEro|deanero]] (-0800/-0700)<br />
* [[User:DimitriGlazkov|dglazkov]] (-0600/-0500)<br />
* [[User:DrewMcLellan|drewinthehead]] (+0000/+0100)<br />
* [[User:EdwardOConnor|hober]] (-0800/-0700)<br />
* [[User:Enric|enric]] (-0800/-0700)<br />
* [[User:Evan|evanpro]] (-0500)<br />
* [[User:Fil|Fil]] (+0200)<br />
* [[User:Grantbow|Grantbow]] (-0800/-0700)<br />
* [[User:Hlb|hlb]] (+0800-0700)<br />
* [[User:IanHickson|Hixie]] (-0800/-0700)<br />
* [[User:Izo|IZO]]<br />
* [[User:JoeGregorio|jcgregorio]]<br />
* [[User:Jonathan_Arkell|jonnay]] (-0700/0600)<br />
* [[User:Keri Henare|kerihenare]] (+1200)<br />
* [http://epeus.blogspot.com/ KevinMarks] (-0800/-0700)<br />
* [[User:Mark Mansour|Mark Mansour]] (+1100)<br />
* [[User:MarkNormanFrancis|Mark Norman Francis]] (+0000/+0100)<br />
* [[User:neuro|neuro`]]<br />
* [[User:Phae|Phae]] (+0000/+0100)<br />
* [[User:PriitLaes|plaes]] (+0200/+0300)<br />
* [[User:DavidOsolkowski|qid]] (-0500)<br />
* [[User:Remi|Remi]] (-0500/-0400)<br />
* [[User:RobertBachmann|RobertBachmann]] (+0100/+0200)<br />
** Office hours: <del>Wednesday, 18:00-20:00 UTC</del> (Currently no office hours)<br />
* [[User:RyanKing|kingryan]] (-0800/-0700)<br />
** [http://theryanking.com/blog/archives/2006/04/19/office-hours/ Office hours]: Wednesday, 21:00 UTC<br />
* [[User:Csarven|csarven]] (-0500/-0400)<br />
* [[User:Dana Benson|Snowden]] (-0800/-0700)<br />
* [[User:Steve Ganz|SteveGanz]] (-0800/-0700)<br />
* [[User:Tantek|Tantek]] (-0800/-0700)<br />
* [[User:Trovster|trovster]] (-0800/-0700)<br />
* [[User:Dan Kubb|dkubb]] (-0800/-0700)<br />
* [[User:Ed Summers|edsu]] (-0500/-0400)<br />
* [[User:Smackman|Steve Farrell]] (-0800/-0700)<br />
* [[User:Enric|Enric]] (-0800/-0700)<br />
* [[User:Charlvn|Charl]] (+0200/+0200)<br />
* [[User:MarkoMrdjenovic|friedcell]] (+0100/+0200)<br />
* [[User:Vant|vant]] (+0900)<br />
* [[User:IwaiMasaharu|iwaim]] (+0900)<br />
* [[User:Richard Conyard|WhiskeyM]] (+0000)<br />
* [[User:Ianloic|yakk]] (-0800/-0700)<br />
<br />
<br />
=== Greetings ===<br />
<br />
To display a brief description of who you are each time you join the channel, you can create a definition for your username. To do so pass the <tt>?def</tt> command using something like the following convention (be brief):<br />
<br />
<code>?def jdoe is John Doe and can be found online at <nowiki>http://www.jdoewebsite.com</nowiki></code><br />
<br />
More information about using JiBot commands can be found on the [http://joiwiki.ito.com/joiwiki/index.cgi?jibot jibot website]<br />
<br />
=== bots ===<br />
<br />
* [[mfbot]]<br />
* [[mflogbot]]<br />
* [http://joiwiki.ito.com/joiwiki/index.cgi?jibot jibot]<br />
<br />
== Logs ==<br />
<br />
Available here: http://rbach.priv.at/Microformats-IRC/<br />
<br />
Atom feed of logs available here: http://microformat.makedatamakesense.com/log_feed/<br />
<br />
== IRC meetups ==<br />
<br />
The idea of having IRC meetups (that is, a set time for meeting on IRC) has been suggested by [[User:RyanKing|Ryan King]], as it appears to work well for the WordPress community and may help us from time-to-time. As of yet, there are no plans to have meetups, though.</div>Ianloic