Hi,
I've a question regarding microformats and whether they might be applicable
to a problem I'm trying to solve. As I read the 'process' on the
microformat wiki I come up against things which seem to deem them
unsuitable, but I wanted to post to ask the experts.
The (initial) problem I'm
Brian Suda wrote:
the advantage of saying what you have available will minumized the
crawl space. I can get one file that tells me everything, or crawl the
entire 40,000 Avon hCard pages to try to get the same thing.
This seems counter to the DRY and/or users-first mantra of
microformats.
On Nov 24, 2005, at 6:45 AM, Simon Kittle wrote:
Hi,
I've a question regarding microformats and whether they might be
applicable
to a problem I'm trying to solve. As I read the 'process' on the
microformat wiki I come up against things which seem to deem them
unsuitable, but I wanted to
On 11/24/05, David Janes -- BlogMatrix [EMAIL PROTECTED] wrote:
I'm not much of an XSLT guy, to tell you truth. When I was in CompSci
and studying Prolog, our prof mentioned that the great thing about
Prolog was you didn't have to tell it everything like other languages.
My friend remarked not
I'm curious, do people think there are sufficient examples of
naked phone numbers on the web (outside of contact
information for a specific person or
organization) to justify the creation of an elemental tel
microformat to mark them up explicitly?
For what it's worth with my limited
Instead of narrowing the problem to letting users specify their own
avatar, why not let them specify their own vcard (or the URI to that
vcard), solving not only the the avatar image problem but allowing
alternate ids depending on the context?
At this point, I'll mention a uF I started
