[uf-new] hNews and rel=principles
I've added this issue to the wiki. http://microformats.org/wiki/hnews-issues#Open_Issues open issue! 2010-11-14 raised by TobyInk Meaning of rel=principles. It's currently defined as represents the statement of principles and ethics used by the news organization that produced the news story - but are those the principles the ones used by the organisation at the time the article was written, or are they the principles that are being used by the organisation currently? If the latter, this property might be better as an extension to hCard. Either way, I think it should be clarified. -- Toby A Inkster mailto:m...@tobyinkster.co.uk http://tobyinkster.co.uk ___ microformats-new mailing list microformats-new@microformats.org http://microformats.org/mailman/listinfo/microformats-new
Re: [uf-new] note/notereference class-pattern microformat?
On Tue, 7 Sep 2010 13:26:20 -0400 Sebastian Heath sh1...@nyu.edu wrote: So perhaps the place to start is small: two classes for indicating the relationship between notes and references to those notes in a text. I'm purposefully punting on whether these notes are end/foot/sidenotes, because that seems to be a runtime decision and/or personal preference. I want to cover both. rel=footnote is pretty widely used. Despite the name, it doesn't have do point to a note in the traditional footnote style, but could point to an endnote or a note on another page. It's mentioned in this old W3C pre-HTML-4.0 document: http://www.w3.org/TR/relations.html Various versions of Markdown include it in their HTML output. I'm an RDFa and Digital Humanities geek who is dipping my toes into the microformat community for the first time. Well, with RDFa 1.1 profiles, rel=footnote can even be successfully interpreted as RDFa. -- Toby A Inkster mailto:m...@tobyinkster.co.uk http://tobyinkster.co.uk ___ microformats-new mailing list microformats-new@microformats.org http://microformats.org/mailman/listinfo/microformats-new
[uf-new] hRecipe issue - value and type
See http://microformats.org/wiki/hrecipe-issues#issue-20100325. The suggested way of using 'value' and 'type' within hRecipe is strange, and quite different from hCard. This is especially problematic for 'value' because of its role in value excerpting. My suggestion, and how I plan on implementing hRecipe in HTML::Microformats is to parse class=ingredients and class=nutrition as simple strings with no subproperties, using class=value for value excerpting in a manner consistent with other microformats. -- Toby A Inkster mailto:m...@tobyinkster.co.uk http://tobyinkster.co.uk ___ microformats-new mailing list microformats-new@microformats.org http://microformats.org/mailman/listinfo/microformats-new
[uf-new] hResume issue: embedding hCard for job title leads to ambiguities.
I quickly documented this issue on the wiki yesterday: http://microformats.org/wiki/hresume-issues#issue-20100317 While porting/testing my hResume parser, I ran into an issue. It is suggested that to mark up job titles, roles, etc within hResume experiences, an hCard should be embedded into the experience. I'm going to call this the JThC (Job Title hCard), just because I'd like a term to unambiguously refer to it. With the experience already being an hCalendar event, there are several places an hCard could already legitimately be embedded within it - e.g. class=location vcard. So the issue is that there's not really any way to differentiate between the JThC versus other hCards within the experience. There seem to be three possible ways of disambiguating - two that involve spec changes, and one that doesn't but I think would be less reliable and harder to implement. 1. The JThC should be given class=contact within the hCalendar event. The CONTACT property is defined in RFC 2445 (iCalendar) as: Purpose: The property is used to represent contact information or alternately a reference to contact information associated with the calendar component. So an hResume experience would look something like: div class=experience vevent h3 class=summary abbr class=dtstart title=2005-05-01May 2005/abbr - abbr class=dtend title=2008-06-24June 2008/abbr - i class=contact vcard a href=#name class=include/a span class=titleSenior Vice-President/span span class=orgCompuGlobalHyperMeganet/span /i /h3 p class=description This industry moves so fast it's really hard to tell. /p /div 2. Same dealy, but defining a new hResume-specific property rather than reusing hCalendar's contact property. e.g. div class=experience vevent h3 class=summary abbr class=dtstart title=2005-05-01May 2005/abbr - abbr class=dtend title=2008-06-24June 2008/abbr - i class=me vcard a href=#name class=include/a span class=titleSenior Vice-President/span span class=orgCompuGlobalHyperMeganet/span /i /h3 p class=description This industry moves so fast it's really hard to tell. /p /div 3. This is the option which requires no spec changes. We simply specify that the JThC is the first hCard within the experience which is not also a location/attendee/organizer/contact(?) hCard. div class=experience vevent h3 class=summary abbr class=dtstart title=2005-05-01May 2005/abbr - abbr class=dtend title=2008-06-24June 2008/abbr - i class=vcard a href=#name class=include/a span class=titleSenior Vice-President/span span class=orgCompuGlobalHyperMeganet/span /i /h3 p class=description This industry moves so fast it's really hard to tell. /p /div -- Toby A Inkster mailto:m...@tobyinkster.co.uk http://tobyinkster.co.uk ___ microformats-new mailing list microformats-new@microformats.org http://microformats.org/mailman/listinfo/microformats-new
Re: [uf-new] hResume issue: embedding hCard for job title leads to ambiguities.
On Thu, 2010-03-18 at 11:58 +0100, Sarven Capadisli wrote: The hCard with class=location vcard could legitimately contain rel=contact. This may give that distinction. The definition of rel=contact is: Someone you know how to get in touch with. Which seems like it's only intended when linking to a page that represents a person - not an organisation or place. Though perhaps Tantek (as co-author of the XFN profile) could clarify that. Either way, this is only useful for hCards that contain a link, which not all do. -- Toby A Inkster mailto:m...@tobyinkster.co.uk http://tobyinkster.co.uk ___ microformats-new mailing list microformats-new@microformats.org http://microformats.org/mailman/listinfo/microformats-new
Re: [uf-new] Microformats for hidden data
On Thu, 2009-11-26 at 15:23 +, Fiann O'Hagan wrote: As I understand it, these limitations are what led the W3C to create RDF, which is cross-linked from the meta element in the HTML spec. And the complexity of RDF, is of course what led to the rise of microformats. Have you considered using RDFa? This is a set of XHTML attributes which brings the RDF data model to XHTML. (Many parsers also support tag soup HTML too.) -- Toby A Inkster mailto:m...@tobyinkster.co.uk http://tobyinkster.co.uk ___ microformats-new mailing list microformats-new@microformats.org http://microformats.org/mailman/listinfo/microformats-new
Re: [uf-new] nutrition-facts in XHTML
p class=hmeasure span class=typeVitamin C/span span class=num15/span span class=unitmg/span. /p This is indeed a good application of hmeasure. However... span class=tolerance100%/span of the recommended a title=Recommended Dietary Allowance rel=glossary href=http://en.wikipedia.org/wiki/Dietary_Reference_Intake;RDA/a That's not what tolerance is for - tolerance is more for recording the possible error in a measurement (e.g. plus or minus 5%). This doesn't seem to be used very much, which is why the current hmeasure draft mentions it as an at-risk feature. hMeasure also contains an optional item property much like the property of the same name in hReview. It records what the measurement is actually measuring. i.e. what is the thing that contains 15mg of Vitamin C. e.g. p class=hmeasure span class=item100 mL of Orange Juice/span contains span class=num15/span span class=unitmg/span of span class=typeVitamin C/span. /p -Toby ___ microformats-new mailing list microformats-new@microformats.org http://microformats.org/mailman/listinfo/microformats-new
Re: [uf-new] Document Sources/References
On Mon, 2009-06-29 at 23:44 +0100, Jamie Rumbelow wrote: Is there a semantic, POSH way of linking to a document's source or reference. For example, on most Wikipedia articles, it lists a set of sources for the article's content at the bottom - these surly have semantic value (building inter-site links, inter-document links, relevance of a document in a set of categories through rel=tag, etc.) In addition to Ben's suggestion, (X)HTML offers some existing (but fairly basic) facilities for citation: If you're directly quoting from a source, both q and blockquote have a cite attribute that allows you to include a link back. Sadly, it seems browsers tend not to make this citation visible in the UI, but it's possible to expose it using a little unobtrusive scripting. e.g. http://www.6times9.com/javascript/citelink/ http://www.sitepoint.com/article/structural-markup-javascript/ Current XHTML 1.2 and XHTML 2.0 drafts allow a cite rel value. i.e. your links can use rel=cite. There's also of course the cite element. -- Toby A Inkster mailto:m...@tobyinkster.co.uk http://tobyinkster.co.uk ___ microformats-new mailing list microformats-new@microformats.org http://microformats.org/mailman/listinfo/microformats-new
Re: [uf-new] New proposal: Elemental microformat for content boundaries
On Thu, 2009-04-23 at 19:55 +0530, Indus Khaitan wrote: I'm interested in finding a way to identify the content boundaries for content aggregated/published on a composite page. Surely hAtom entries are perfect for this purpose. What specific need do you have which isn't addressed by hAtom? -- Toby Inkster m...@tobyinkster.co.uk ___ microformats-new mailing list microformats-new@microformats.org http://microformats.org/mailman/listinfo/microformats-new
