Re: looking for patterns vs. dreaming up patterns (was Re: ecommerce was Re: [uf-discuss] Principles of Microformats?)

Ah, thanks for the context Ben. The quote makes more sense in that context, but I still feel makes a statement that I wouldn't make. Oops! I didn't mean to do anything like that! It's an interesting hypothesis, but I believe what I was pointing out from the IRC conversation is that you may w

Re: looking for patterns vs. dreaming up patterns (was Re: ecommerce was Re: [uf-discuss] Principles of Microformats?)

On 12/21/06 10:24 AM, "Benjamin West" <[EMAIL PROTECTED]> wrote: > On 12/21/06, Tantek Çelik <[EMAIL PROTECTED]> wrote: >> I'm not sure who originally wrote: > > I did. > >> Others skip the collecting examples (data) step and simply dream up patterns >> based on their intuition (or "expertise")

Re: looking for patterns vs. dreaming up patterns (was Re: ecommerce was Re: [uf-discuss] Principles of Microformats?)

On 12/21/06, Tantek Çelik <[EMAIL PROTECTED]> wrote: I'm not sure who originally wrote: I did. Others skip the collecting examples (data) step and simply dream up patterns based on their intuition (or "expertise") - perhaps that is what you mean by "allowing myself to look for patterns". It

looking for patterns vs. dreaming up patterns (was Re: ecommerce was Re: [uf-discuss] Principles of Microformats?)

I'm not sure who originally wrote: > Tantek suggests I'm being > a bad scientist by allowing myself to look for patterns. To be clear, collecting examples (data) and looking for patterns is exactly what the process asks you to do. Others skip the collecting examples (data) step and simply dream

RE: ecommerce was Re: [uf-discuss] Principles of Microformats?

Benjamin West wrote: > I don't know if it's true either. Tantek suggests I'm being > a bad scientist by allowing myself to look for patterns. Maybe that's why I'm a fish out of water here; discovering patterns is one of my strongest interests and one of my best skills. BTW, I didn't see this

Re: ecommerce was Re: [uf-discuss] Principles of Microformats?

Mike, Nice reply. > I've also noticed that many of the more successful > technologies I can think of first implemented use cases with > user-centric data: people, places, things, times, and events. I don't know that to be true, but it certainly makes sense. I don't know if it's true either.

Re: ecommerce was Re: [uf-discuss] Principles of Microformats?

On 12/16/06, Andy Mabbett <[EMAIL PROTECTED]> wrote: In message <[EMAIL PROTECTED]>, Benjamin West <[EMAIL PROTECTED]> writes >e-commerce issues >Can you elaborate a bit more on these kinds of use cases? (-examples page created 19 July 2006) I don't f

RE: ecommerce was Re: [uf-discuss] Principles of Microformats?

Benjamin West wrote: > I'm only vaguely familiar with some e-commerce issues. You > may find that the the early creators of microformats, because > of a relatively common background, may simply not have enough > exposure to this kind of thing. After all, they are only human (as am I.) > I

Re: ecommerce was Re: [uf-discuss] Principles of Microformats?

In message <[EMAIL PROTECTED]>, Benjamin West <[EMAIL PROTECTED]> writes >e-commerce issues >Can you elaborate a bit more on these kinds of use cases? (-examples page created 19 July 2006) -- Andy Mabbett * Say "NO!" to compulsory ID Cards:

ecommerce was Re: [uf-discuss] Principles of Microformats?

Mike, I was particularly interested in a part of your reply: On 12/16/06, Mike Schinkel <[EMAIL PROTECTED]> wrote: > > 17.) Inspired by needs of Bloggers and blog-related services > Use cases involving bloggers are easy to come up with, > however I started working on microformats before I had a

RE: [uf-discuss] Principles of Microformats?

Andy Mabbett wrote: > >> 20.) Aims to avoid changing publishing behavior > Claiming to aim to is all well and good, but, again, there > has recently been evidence posted to show that that is not > being achieved. My goal was to document and clarify philosophy, not current behaviour. :) The form

RE: [uf-discuss] Principles of Microformats?

Siegfried Gipp wrote: > > Mike, interesting list. > > > 1.) Includes visible-only > > Yeah, microformats only represent visible data. > Sure? Think of: > http://www.microformats.org/xfolk"; > title="xfolk"/> When I've discussed proposing numerous non-visible Microformats, Tantek (and others) told

RE: [uf-discuss] Principles of Microformats?

Thanks for taking the time to review; it was very helpful. I've answered your questions and/or clarified my comments. Benjamin West wrote: > > 2.) One flat namespace > Not sure what this means. There is one "namespace" for class > names, yet the markup itself is hierarchical. That's what I mea

Re: [uf-discuss] Principles of Microformats?

In message <[EMAIL PROTECTED]>, Ciaran McNulty <[EMAIL PROTECTED]> writes >>Think of: >> http://www.microformats.org/xfolk"; title="xfolk"/> > >Actually, the rel-tag microformat explicitly excludes usage on LINK >elements for precisely this reason. > >See: >http://microformats.org/wiki/rel-tag#Tag

Re: [uf-discuss] Principles of Microformats?

In message <[EMAIL PROTECTED]>, Benjamin West <[EMAIL PROTECTED]> writes >Mike, interesting list. >> >> 1.) Includes visible-only >Yeah, microformats only represent visible data. There are exceptions to that, as has been pointed out, but also including the "rel-" based uFs. >> 6.) Recognition is

Re: [uf-discuss] Principles of Microformats?

On 12/14/06, Siegfried Gipp <[EMAIL PROTECTED]> wrote: > Yeah, microformats only represent visible data. Sure? Think of: http://www.microformats.org/xfolk"; title="xfolk"/> Actually, the rel-tag microformat explicitly excludes usage on LINK elements for precisely this reason. See: http://micro

Re: [uf-discuss] Principles of Microformats?

Am Donnerstag, 14. Dezember 2006 01:47 schrieb Benjamin West: > Mike, interesting list. > > > 1.) Includes visible-only > > Yeah, microformats only represent visible data. Sure? Think of: http://www.microformats.org/xfolk"; title="xfolk"/> > > 11.) Considers existing HTML usage > > If a particula

Re: [uf-discuss] Principles of Microformats?

Mike, interesting list. 1.) Includes visible-only Yeah, microformats only represent visible data. 2.) One flat namespace Not sure what this means. There is one "namespace" for class names, yet the markup itself is hierarchical. 3.) No solution for resolving ambiguities Not sure about thi