[uf-discuss] testing hreview creator
I've made some updates to the hReview creator and would like some testing before I push it to microformats.org. If you're going to be writing an hReview soon, could you please use http://theryanking.com/ temp/build/hreview/creator.html ? Thanks, ryan ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
[uf-discuss] hResume Check Please
Hi all, Since hResume is only a draft and there's not much in the way of automated checking, I wonder if some of you could give my hResumified CV a look over. http://ben-ward.co.uk/cv For general feedback, I quite enjoyed updating the CV to support hResume. For the most part the plain-HTML version I had before mapped very quickly to the µf, I had to add a few for hevent structure, but that was all very logical so I'm pleased there. A few frustrations/issues: First up, the best-practice method of containing hCard within an ADDRESS element appears hard to implement, given the inline nature of ADDRESS. In my case, I tried to have [div#benmichaelward] (line 100) as an ADDRESS, but the block-level children triggers quirks mode in browsers and causes the block level content (h1, ul, dl) to become siblings in the DOM, not children, which in turn breaks stlyling. Second, I find the mark-up required for skills - using rel=tag - to be rather laborious to author. I appreciate the value of using tags, pointing multiple skill sets to the same place, but there is a lot of typing involved, not to mention the effort of hunting out the URLs. I honestly don't know if there's a better way though, since everything I keep half-thinking of as I type this doesn't actually help very much (briefly the idea of a base URL for tags, but that doesn't actually get around much of the labour problem). Anyway, I felt that worth flagging up in case anyone was sitting on an ingenious idea of a tag shorthand and needed motivation to post it. The last thing regards experience/education hevents that are still ongoing (“2002-present”). Is it safe to assume, or should it perhaps be specified in hResume itself, that ‘present’ is implied by the absence of a dtend field? Mark-up pedantry greatly appreciated. Ben___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
[uf-discuss] Re: More responses to slashdot comments
Scott Reynen wrote: Why isn't "leftColumn" a semantic relationship? It means something, doesn't it? It has meaning, but doesn't give meaning to anything else. "Semantic" would indicate that it told you something 'about' the meaning the content, not where it is located. You might say that term has a "Geographic" relationship to the rest of the content. But given that each user agent displays content differently, and that the CSS might actually contain .leftColumn (position:absolute;bottom:0;right:0;} it doesn't necessarily indicate that. Atamido ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
[uf-discuss] Re: Again
I think that GMane registers itself as a subscriber so that emails can be sent to and fro through it. But I guess it depends on both how Gmane and the Microformats mailing lists are set up. I just found the mailing list archive, and it appears my mails are going through. http://microformats.org/discuss/mail/microformats-discuss/2006-July/004738.html Colin, I would suggest you check to see if your emails are showing up in the archive to better see where the problem is. http://microformats.org/discuss/mail/microformats-discuss/ Atamido Ryan King wrote: The mailing list is subscribers only, so I'd guess the answer is no. -ryan On Jul 12, 2006, at 11:05 AM, Paul Bryson wrote: I just realized that I have no idea if most of my emails make it through. I post through Gmane, so it appears there. But as I don't subscribe to the mailing list, I don't know if it actually gets sent back out. Atamido ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
Re: [uf-discuss] More responses to slashdot comments
On 7/13/06, Sho Kuwamoto <[EMAIL PROTECTED]> wrote: Exactly my point. There are two competing schema living in the same document: the world of HTML (semantically poor and unextensible), and the world of microformats. While this works out OK usually, I believe there are cases where the two worlds combine in uncomfortable ways. There have to be two types of schema because there are, as you rightly said, two orthogonal sets of semantics in HTML. The first is the tag/attribute based semantics, which are very strictly defined by the W3C spec. These are mainly to do with document structure and so on, and everyone understands what they mean. The second set of semantics are class/id based, and are completely 'unregulated', that is to say the specific meanings aren't specified by the HTML spec. If I want @id="shopping-list" then there's no reason I shouldn't mark my pages up that way, and there's some semantic value in doing so over something like @id="centre-column". Microformats form conventions for how the *both* sets of semantics should be used. Microformats will, by preference, use the first set as far as possible (i.e. using ADDR in hCard) and then define sensible semantic ids/classes for stuff that isn't covered. Microformats differ from schemas like the W3C's HTML spec, because pages don't have a mechanism for declaring that they conform to a specific microformat. I don't think this is so much a weakness as a strength! Take @rel="tag" for instance. The microformat for this declares very specifically what semantics we can read from the relationship between the current page and the URL being linked. However, there's nothing to stop someone who's never heard of microformats deciding to use @rel="tag" on one of their pages, because it seems a sensible value to use, and you can't tell my looking at a page whether the author had the microformat in mind or not. I believe that the strength of microformats is that they are always sensible markup, so it doesn't matter if someone knows about the microformat being used or not, the markup still makes sense to them - if I'm looking at a link and see @rel="tag" in there then that's not cryptic - I can understand what the link is saying even if I haven't heard of the microformat. The converse of this is that if I build a parser that understands @rel="tag" into my search engine, then I have a spec that tells me a sensible way to parse and understand the semantics of the link. When my search engine finds the hypothetical page above, that uses @rel="tag" without knowing the microformat, then because the spec defines a sensible way of parsing it, my search engine will have a good chance of correctly understanding what the link relationship means. -Ciaran ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
