On 2/8/07, Ryan King <[EMAIL PROTECTED]> wrote:
I propose that this is a simpler solution which will work better.
Also, the algorithm for finding the most authoritative hCard:
1. if no uid or uid == the uid from the previous iteration/recursion
=> you're done
2. if url == uid and there's an hCa
Hi, Ryan
Thanks for summarising. It was getting confusing skipping around all
those threads
I want to address your points out of order, if I may. Firstly, just to
check that I have understood your proposal correctly
Also, the algorithm for finding the most authoritative hCard:
1. if no uid or
Ryan King wrote:
> On Feb 8, 2007, at 4:49 PM, Joe Andrieu wrote:
> > I'd like to reintroduce @rel="via" to the conversation[1]:
> >5. The value "via" signifies that the IRI in the value
> of the href
> >attribute identifies a resource that is the source of the
> >information
Ok, I'll try this again...
__
Adrienne,
As someone that was actively involved in creating COinS, it's not a
microformat.
Most of the reasons are semantic, some are pedantic, but it boils down to:
1. Microformats have a process and COinS was developed outside that pr
I've been marking up some content with the hCard format but came across a
puzzling dilemma.
In New Zealand, rural delivery addresses are commonly presented as
Beverleigh and Grant Muir
RD1
Hari Hari 7953
South Westland
New Zealand
Our postal system has another example of how they should be pre
On Feb 8, 2007, at 8:03 PM, Joe Andrieu wrote:
Why not just have a "via" point to "source" hCards and any hCard
that is
self-referential is "authoritative"? That seems both easy for
publishers and relatively straightforward for parsers. Keep
dereferencing @rel="via" attributes until you find
I apologize for being semi-away for awhile.
Catching up in the last few days, I find that there are some
probelems with the "authoritative hcards" proposals. I've already
spoken up a bit, but I want to delineate my perspective and outline
in full my counter-proposal.
First, the problems:
On Feb 8, 2007, at 4:49 PM, Joe Andrieu wrote:
Scott Reynen wrote:
On Feb 8, 2007, at 4:29 PM, David Janes wrote:
That the authoritative hCard is the
one that _doesn't_ have a UID, i.e. potentially has less
information
than a fragment hCard?!
I think this is how authority generally works i
On Feb 8, 2007, at 2:23 PM, David Janes wrote:
On 2/8/07, Scott Reynen <[EMAIL PROTECTED]> wrote:
So as I understand that, the rules for getting the most authoritative
hCard for a given URL are:
1) parse hCard at current URL
2) If the hCard includes , load the URL in the
href, and return to st
On Feb 8, 2007, at 12:00 PM, David Janes wrote:
On 2/8/07, Ben Ward <[EMAIL PROTECTED]> wrote:
On 8 Feb 2007, at 19:02, David Janes wrote:
> On 2/8/07, Ryan King <[EMAIL PROTECTED]> wrote:
>> Nothing special is needed at /blog/contact/.
>>
>> -ryan
>
> But that's the authoritative hCard. […]
>
On Feb 8, 2007, at 11:02 AM, David Janes wrote:
On 2/8/07, Ryan King <[EMAIL PROTECTED]> wrote:
Nothing special is needed at /blog/contact/.
But that's the authoritative hCard. What's the algorithm (or
heuristic) that I follow if I'm a parser looking at the blog at
microformats.org, see your
Scott Reynen wrote:
> On Feb 8, 2007, at 4:29 PM, David Janes wrote:
>
> >> That the authoritative hCard is the
> >> one that _doesn't_ have a UID, i.e. potentially has less
> information
> >> than a fragment hCard?!
>
> I think this is how authority generally works in practice, from
> extern
In message
<[EMAIL PROTECTED]>, Brian
Suda <[EMAIL PROTECTED]> writes
>--- i agree with all of this, and that is why microformats do not
>force you to use your own tagspace. There are plenty of sites that can
>easily be used as tagspaces[1]
There's also an implicit assumption that publishers (who
I hope that this isn't something that's already been referred to ad
nauseam; i'm a newbie on the list. I just found out about this, and it
SEEMS like a microformat, and worth including on the wiki:
http://ocoins.info/
It's a way of including structured bibliographic data for a page in a
very com
On Feb 8, 2007, at 4:29 PM, David Janes wrote:
That the authoritative hCard is the
one that _doesn't_ have a UID, i.e. potentially has less information
than a fragment hCard?!
I think this is how authority generally works in practice, from
external references.
Here's one potential usage s
On 2/8/07, David Janes <[EMAIL PROTECTED]> wrote:
On 2/8/07, Scott Reynen <[EMAIL PROTECTED]> wrote:
> So as I understand that, the rules for getting the most authoritative
> hCard for a given URL are:
>
> 1) parse hCard at current URL
> 2) If the hCard includes , load the URL in the
> href, and
On 2/8/07, Scott Reynen <[EMAIL PROTECTED]> wrote:
So as I understand that, the rules for getting the most authoritative
hCard for a given URL are:
1) parse hCard at current URL
2) If the hCard includes , load the URL in the
href, and return to step 1.
When the consumer gets to http://theryank
On Feb 8, 2007, at 2:00 PM, David Janes wrote:
No no no. I'm looking for the set of rules a consumer has to follow to
get from Ryan's hCard on microformats.org to his authoritative hCard
at *the*ryanking/contact.
I thought Ryan already answer that:
On Feb 7, 2007, at 4:34 PM, Ryan King wrote:
On 2/8/07, Ben Ward <[EMAIL PROTECTED]> wrote:
On 8 Feb 2007, at 19:02, David Janes wrote:
> On 2/8/07, Ryan King <[EMAIL PROTECTED]> wrote:
>> Nothing special is needed at /blog/contact/.
>>
>> -ryan
>
> But that's the authoritative hCard. […]
>
> Sorry if this sounds pedantic, I'm not trying
Hi Roger,
The point of XOXO is that you can trivially encode arrays and
dictionaries in straight HTML. In particular, you can use it as an
alternative to, e.g., JSON, for generic data structures:
http://microformats.org/wiki/rest/datatypes
Somebody's even written a whole blog about such u
Hi Folks,
I have read the Wiki on XOXO and as I understand it, the XOXO
microformat has no properties, it is simply a classname to be used at
the top of a list, e.g.,
...
...
...
Question #1
Is that all there is to the XOXO microformat?
I am puzzled how the XOXO microformat helps
On 8 Feb 2007, at 19:02, David Janes wrote:
On 2/8/07, Ryan King <[EMAIL PROTECTED]> wrote:
Nothing special is needed at /blog/contact/.
-ryan
But that's the authoritative hCard. […]
Sorry if this sounds pedantic, I'm not trying to be. There's some
assumption in what you're saying that
On Feb 7, 2007, at 3:16 PM, Benjamin West wrote:
On 2/7/07, Michael McCracken <[EMAIL PROTECTED]> wrote:
So, is the microformats-new mailing list now the appropriate place
for
discussing hCite development?
Good question. My personal opinion is that we should kind of
grandfather older stuff
On 2/8/07, Ryan King <[EMAIL PROTECTED]> wrote:
Nothing special is needed at /blog/contact/.
-ryan
But that's the authoritative hCard. What's the algorithm (or
heuristic) that I follow if I'm a parser looking at the blog at
microformats.org, see your partial hCard and try to find your
authorit
On Feb 7, 2007, at 2:56 PM, David Janes wrote:
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
re
Would it be worthwhile to draw attention to this list on the blog for
those that only follow that, or get just the digests?
F
--
Frances Berriman
http://fberriman.com
Frances,
Good idea.
MF blog: http://microformats.org/blog/2007/02/08/new-mailing-list/
my blog: http://bewest.wordpress.com/200
On 2/8/07, Chris Newell <[EMAIL PROTECTED]> wrote:
>Firstly, we have a new mailing list for new formats:
>http://microformats.org/mailman/listinfo/microformats-new/
Apologies.
I've also found there is a "Media Info" microformat proposal that encompasses
this requirement but has greater overall
Chris Newell wrote:
Thanks - this is all useful. However TYPE can't convey all the information
needed such as bit-rate.
Chris
HTTP Content-Type does this by putting the MIME type first, followed by
a semi-colon, followed by key value pairs. Usually, I only see
"text/html;charset=utf-8". Ac
Ryan Cannon said on Date: 02/07/2007 10:39:08 PM +0100
> 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 certifica
At 16:05 08/02/2007, Brian Suda wrote:
>On 2/8/07, Chris Newell <[EMAIL PROTECTED]> wrote:
>>Colleagues,
>>
>>I would like to propose a microformat to describe media files and media
>>streams. In particular, groups of files or streams which represent the same
>>content but with different encoding
On 2/8/07, Chris Newell <[EMAIL PROTECTED]> wrote:
Colleagues,
I would like to propose a microformat to describe media files and media
streams. In particular, groups of files or streams which represent the same
content but with different encoding formats.
A suitable starting point for this co
Hello,
my name is Henrich C. Poehls, I have been reading the list for quite
some while now, without writing. It has been very interesting to see
that the topic of authoritative hcards led the discussion to the topic
of trust and Digital Signatures.
>> Perhaps we need a "class="pgp-public-key" pr
Colleagues,
I would like to propose a microformat to describe media files and media
streams. In particular, groups of files or streams which represent the same
content but with different encoding formats.
A suitable starting point for this could be Media RSS
(http://search.yahoo.com/mrss).
I'
On 2/8/07, James Craig <[EMAIL PROTECTED]> wrote:
Quoting from About Microformats: "Designed for humans first and
machines second, microformats are a set of simple, open data formats
built upon existing and widely adopted standards." This also implies
they should be easy to implement. Co-locating
Brian Suda wrote:
I would love to have my host have the latest, greatest version of PHP
technology. If they don't i don't go complain to PHP and ask them to
back-port functionality to an earlier version. I buck it up and either
move hosts, pay for the better service or co-locate my own box. It i
On 07/02/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
microformats.
One of the goals is to keep this list (microformats-discuss) focused
on practical matters for people
There has been several emails here and there about the difficulties of
creating tag spaces and that we should change the rel-tag spec.
I completely disagree. Most of the issues stem from issues in blogging
software, server software or hosting restrictions.
All of these issues are out of the scop
On 2/7/07, Ryan King <[EMAIL PROTECTED]> wrote:
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
On Feb 7, 2007, at 10:30 PM, Derrick Lyndon Pallas wrote:
Yes, there are other ways to solve the problem; in fact, I do solve
the problem in an unelegant way. My real issue now is (as laid out
above) the resistance to real discussion of the problem.
I think what you're seeing is that microf
39 matches
Mail list logo
