Ryan King wrote:
Actually I think it *is* quite reasonable to make parsers know about
every microformat.
This is not viable from a consumer perspective. New formats can
immediately invalidate old parsers by changing the semantics the
consumer expects without so much as an annotation in the defi
> Is there any plan/interest to work on a hMood or hPresence microformat
> that could describe information related to the mood or the activity of
> a person/group? Bloggers typically express their feelings over the
> web, or what they have been doing during the day, so it would be
> interesting to
I agree; I think that we should use the -new list for research/
discussion of *new* ideas for microformats. It would be confusing to
move something to another list that has always been discussed here.
--
+ Nick Drago
+ e: [EMAIL PROTECTED]
+ w: http://weekendcycling.com
On 2/7/07, Benjamin West
On 2/7/07, Michael McCracken <[EMAIL PROTECTED]> wrote:
So, is the microformats-new mailing list now the appropriate place for
discussing hCite development?
Thanks,
-mike
Good question. My personal opinion is that we should kind of
grandfather older stuff, while encouraging newcomers with new
So, is the microformats-new mailing list now the appropriate place for
discussing hCite development?
Thanks,
-mike
On 2/7/07, Ryan King <[EMAIL PROTECTED]> wrote:
Ok, after much feedback, deliberation and procrastination, we've
started a new mailing list, microformats-new[1] for developing new
On 2/7/07, Ryan King <[EMAIL PROTECTED]> wrote:
On Feb 7, 2007, at 12:50 PM, David Janes wrote:
> On 2/7/07, Ryan King <[EMAIL PROTECTED]> wrote:
>> Yes there are several problems:
>>
>> 1. XFN applies to whole pages. This means that you can't reliably put
>> different people's hCards on the sam
On Feb 7, 2007, at 1:44 PM, Ryan Cannon wrote:
On Feb 7, 2007, Ryan King wrote:
2. We have prior art that is being ignored. Publishers are already
using ... to do this.
However, UID is not a field that takes a URL for its value, just a
string, so therefore:
http://ryancannon.com/";>Ryan
S
On Feb 7, 2007, at 12:50 PM, David Janes wrote:
On 2/7/07, Ryan King <[EMAIL PROTECTED]> wrote:
Yes there are several problems:
1. XFN applies to whole pages. This means that you can't reliably put
different people's hCards on the same page and do this.
2. We have prior art that is being igno
On Feb 7, 2007, at 1:59 PM, Edward O'Connor wrote:
However, UID is not a field that takes a URL for its value, just a
string, so therefore:
Perhaps this is addressed in [1] or [2]?
1. http://microformats.org/wiki/uid-brainstorming
2. http://microformats.org/discuss/mail/microformats-discuss/
Edward O'Connor wrote:
James Craig wrote:
Requiring a restful URL for rel-tag (though the ideal solution) is
expecting a lot more of a µf author than requiring authors to add a
bit of markup.
While properly implementing a tag space may be slightly more
difficult[1] than other methods for so
Ok, after much feedback, deliberation and procrastination, we've
started a new mailing list, microformats-new[1] for developing new
microformats.
One of the goals is to keep this list (microformats-discuss) focused
on practical matters for people working with microformats. Though who
wish
Ryan wrote:
> uid goes on @class, not rel.
Yes, thanks for the correction.
Ted
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
James Craig wrote:
> Requiring a restful URL for rel-tag (though the ideal solution) is
> expecting a lot more of a µf author than requiring authors to add a
> bit of markup.
While properly implementing a tag space may be slightly more
difficult[1] than other methods for some developers or organi
> However, UID is not a field that takes a URL for its value, just a
> string, so therefore:
Perhaps this is addressed in [1] or [2]?
1. http://microformats.org/wiki/uid-brainstorming
2.
http://microformats.org/discuss/mail/microformats-discuss/2006-April/003726.html
(See also the rest of th
On Feb 7, 2007, Ryan King wrote:
2. We have prior art that is being ignored. Publishers are already
using ... to do this.
However, UID is not a field that takes a URL for its value, just a
string, so therefore:
http://ryancannon.com/";>Ryan
Should be parsed as
URL: http;//ryancannon.com/
On Feb 7, 2007, at 3:09 PM, Ryan King wrote:
Perhaps we need a "class="pgp-public-key" property for hCard?
There's already a KEY field in vCard. From RFC2624:
Type purpose: To specify a public key or authentication certificate
associated with the object that the vCard represents.
I'm su
On Feb 7, 2007, at 12:00 PM, Edward O'Connor wrote:
Ryan wrote:
Right, but there's also a lot of use to reusing things from the
present microformat (hCard).
vCard has a property called UID, which is defined as:
"""
Type purpose: To specify a value that represents a globally unique
identifier
On Feb 7, 2007, at 12:47 PM, David Janes wrote:
On 2/7/07, Ara Pehlivanian <[EMAIL PROTECTED]> wrote:
On 2/7/07, David Janes <[EMAIL PROTECTED]> wrote:
> I think you're missing a stage:
>
> - fragment hcard (anywhere on the net by anybody)
> - points to home page, using class="url"
> - home pag
On 2/7/07, David Janes <[EMAIL PROTECTED]> wrote:
On 2/7/07, Ara Pehlivanian <[EMAIL PROTECTED]> wrote:
> On 2/7/07, David Janes <[EMAIL PROTECTED]> wrote:
> > I think you're missing a stage:
> >
> > - fragment hcard (anywhere on the net by anybody)
> > - points to home page, using class="url"
>
On 2/7/07, Ryan King <[EMAIL PROTECTED]> wrote:
Yes there are several problems:
1. XFN applies to whole pages. This means that you can't reliably put
different people's hCards on the same page and do this.
2. We have prior art that is being ignored. Publishers are already
using ... to do this.
On 2/7/07, Ara Pehlivanian <[EMAIL PROTECTED]> wrote:
On 2/7/07, David Janes <[EMAIL PROTECTED]> wrote:
> I think you're missing a stage:
>
> - fragment hcard (anywhere on the net by anybody)
> - points to home page, using class="url"
> - home page, using class="something" rel="something-else", p
On 2/7/07, David Janes <[EMAIL PROTECTED]> wrote:
I think you're missing a stage:
- fragment hcard (anywhere on the net by anybody)
- points to home page, using class="url"
- home page, using class="something" rel="something-else", points to
authoritative hcard
e.g. Ryan King hCards in the wild
Ryan King wrote:
Requiring authors to add markup in order to make rel-tag's scope
explicit makes it hard to publish the data and doesn't solve any
real problem.
Hijacking a thread to mention another rel-tag oddity:
Requiring a restful URL for rel-tag (though the ideal solution) is
expect
On 2/7/07, Ara Pehlivanian <[EMAIL PROTECTED]> wrote:
On 2/7/07, Ryan King <[EMAIL PROTECTED]> wrote:
> You're right, rel=me requires symmetry in order to be trusted at all.
> For this reason, and others XFN is not the simplest way to do
> Authoritative hCards.
I guess the real question is, "who
On 2/7/07, Ryan King <[EMAIL PROTECTED]> wrote:
You're right, rel=me requires symmetry in order to be trusted at all.
For this reason, and others XFN is not the simplest way to do
Authoritative hCards.
I guess the real question is, "who will be creating the partial hCards
that will be referring
On Jan 30, 2007, at 4:06 PM, Ben Ward wrote:
Chris Messina:
http://factoryjoe.com/blog/hcard/#hcard";
class="fn
url" rel="me self">Chris Messina
Citizen Agency
...
John Allsopp:
The "definition" of the self attribute value in Atom is "self: the
feed itself". The term "the" seems to
Ryan wrote:
> Right, but there's also a lot of use to reusing things from the
> present microformat (hCard).
>
>
> vCard has a property called UID, which is defined as:
>
> """
> Type purpose: To specify a value that represents a globally unique
> identifier corresponding to the individual or reso
On Feb 2, 2007, at 2:57 PM, Ara Pehlivanian wrote:
On 2/1/07, John Allsopp <[EMAIL PROTECTED]> wrote:
use case - sure - for example, at our conference sites, we markup
speakers with hCard, and this often includes a link to their blog
etc. In this case, a link to an authoritative (or perhaps, to
On Jan 30, 2007, at 2:28 PM, John Allsopp wrote:
Chris,
(all the following simply thoughts in the spirit of brainstorming,
rather than any particular argument in favour of my original
suggestion)
I pretty much came up with a very similar proposal for handling this
issue, though from the
On Jan 30, 2007, at 11:50 AM, Chris Messina wrote:
Well, I certainly am coming to the party late.
I actually started a post on this topic over a week ago -- and
absentmindedly hadn't checked on this list first before posting and
therefore published without the benefit of this discussion (I can
Sorry, I'm way behind on this thread. I wish I weren't but there's
nothing I can do about that now...
On Jan 29, 2007, at 5:50 PM, John Allsopp wrote:
Ben,
For my money, John Allsopp's idea to reuse rel="bookmark self" [1]
makes most sense. As well as being gorgeously consistent with
oth
On Jan 31, 2007, at 7:07 PM, Derrick Lyndon Pallas wrote:
If I have a parser that only knows (and only cares about) the rel-
tag format, it will be confused by people that use rel-tag for the
category property in hCard. It seems unreasonable that every
microformat should have to know about e
On Jan 31, 2007, at 8:41 AM, Andy Mabbett wrote:
In message
<[EMAIL PROTECTED]>, Ara
Pehlivanian <[EMAIL PROTECTED]> writes
what if someone registers ben-ward.net and puts up a fake
card on that site.
Perhaps we need a "class="pgp-public-key" property for hCard?
There's already a KEY fiel
On Tuesday 06 February 2007 19:50, Scott Reynen wrote:
> On Feb 6, 2007, at 1:56 PM, Dan Libby wrote:
> > This has likely already been discusssed, but
> > I think that some standard parsing classes in various languages
> > could help
> > pave the way for other implementors. If such exists for PHP
Hi Dan and welcome.
I've been following Videntity for some time and appreciate your
support of microformats -- and would appreciate it if you would
document your thinking and experience with regards to XFN + hcard. I
personally think that OpenID + XFN + hcard has enormous potential for
opening de
35 matches
Mail list logo
