is there any work in progress concerning multimedia captions
http://microformats.org/wiki/media-info-examples
http://microformats.org/wiki/media-info-brainstorming
http://microformats.org/wiki/media-metadata-examples
http://microformats.org/wiki/video-metadata-model
Isn't that just too
On 2/19/07, Jens Meiert [EMAIL PROTECTED] wrote:
If not, I'll announce an initial microformat draft within the next one, two
weeks.
More on that later and as long as there are no objections.
Hi Jens,
Before you announce a microformat-draft, please have a look at the
process [1] and save
On 20/02/07, David Janes [EMAIL PROTECTED] wrote:
I'm also to understand that the mailing list microformats-new is for
discussing new microformats, though damned if I can remember ever
getting any mail from there (?)
That's correct [1]. The list is up and running (I'm receiving
discussions
On Feb 13, 2007, at 2:38 PM, Scott Reynen wrote:
On Feb 13, 2007, at 12:32 PM, Ryan King wrote:
And if the uid is not an url, then authors can't assert
authority, correct?
I'm not even considering authority for now. We need to just deal
with related hCards first.
I'm no longer clear on
On Feb 14, 2007, at 5:34 PM, Joe Andrieu wrote:
Ryan King wrote:
On Feb 10, 2007, at 3:09 AM, Joe Andrieu wrote:
Ryan King wrote:
First off, I'm not saying we should constrain UID to be a URL,
but in
the case that it *is* a URL, we can apply these semantics.
And if the uid is not an url,
On Feb 20, 2007, at 12:25 PM, Ryan King wrote:
On Feb 13, 2007, at 2:38 PM, Scott Reynen wrote:
On Feb 13, 2007, at 12:32 PM, Ryan King wrote:
And if the uid is not an url, then authors can't assert
authority, correct?
I'm not even considering authority for now. We need to just deal
Scott Reynen wrote:
FWIW, at Eventful we have a clear need for related hCards, a need
which is currently well-served by URL+UID. So there is some market
demand.
But do you need related hCards other than authoritative hCards?
We're not using URL+UID for any kind of authoritative
On Feb 20, 2007, at 1:05 PM, Ryan King wrote:
However, the simpler problem of two hcards representing the same
person (or organization) should be solved first, because it is a
simpler problem, with a simpler solution (which may not require
adding any properties to hCard).
The implication
From Bruce D'Arcus on the wiki:
I've mentioned more than once that date-published is misleadingly
specific; too much for real world citations. Consider that many books
are published in the year preceding their copyright date, which is in
fact the date used for citation. I'd prefer just date and
On 2/20/07, Michael McCracken [EMAIL PROTECTED] wrote:
Is anyone against changing 'date-published' to 'date'?
--- the questions is what is the semantics of 'date'? if you create
'date' and use it the date published/updated/copyrighted/etc then
those all have different semantics.
-brian
--
Hi,
Forgive me if this is going over old ground, I just joined this list and
couldn't find what I was looking for on the wiki. Are there any
particular conventions emerging for embedding an OpenID into a hCard?
The openid-brainstorming page mentions using hCard on providers profile
pages etc,
On 2/20/07, Brian Suda [EMAIL PROTECTED] wrote:
On 2/20/07, Michael McCracken [EMAIL PROTECTED] wrote:
Is anyone against changing 'date-published' to 'date'?
--- the questions is what is the semantics of 'date'? if you create
'date' and use it the date published/updated/copyrighted/etc then
On 2/20/07, Michael McCracken [EMAIL PROTECTED] wrote:
A quick scan through the markup examples we have confirms my
impression that most examples from the web are equally vague about
what the dates they show mean. Our condensed summaries on -examples
often describe them as date-published, but
Thom Shannon wrote:
Hi,
Forgive me if this is going over old ground, I just joined this list and
couldn't find what I was looking for on the wiki. Are there any
particular conventions emerging for embedding an OpenID into a hCard?
The openid-brainstorming page mentions using
The problem here is that there is concept of types in URLS
All parsers see is multiple URLS. We don't know which is the openid URL...
Mike Kaply
On 2/20/07, John Panzer [EMAIL PROTECTED] wrote:
Thom Shannon wrote:
Hi,
Forgive me if this is going over old ground, I just joined
but surely we can just use a class like microformats do to apply types
to other elements? either that or a rel?
Mike Kaply wrote:
The problem here is that there is concept of types in URLS
All parsers see is multiple URLS. We don't know which is the openid
URL...
Mike Kaply
On
I think it should also be possible to use openIDs in other elements than
just anchors. You don't necessarily want to link to them, it's the url
itself which is important not the location.
It should also support none canonical urls so they can be written in the
way users expect, we don't want
On Feb 20, 2007, at 3:24 PM, Thom Shannon wrote:
Forgive me if this is going over old ground, I just joined this
list and
couldn't find what I was looking for on the wiki. Are there any
particular conventions emerging for embedding an OpenID into a hCard?
The openid-brainstorming page
Scott Reynen wrote:
On Feb 20, 2007, at 3:24 PM, Thom Shannon wrote:
Forgive me if this is going over old ground, I just joined this list and
couldn't find what I was looking for on the wiki. Are there any
particular conventions emerging for embedding an OpenID into a hCard?
The
Mike said:
From Bruce D'Arcus on the wiki:
I've mentioned more than once that date-published is misleadingly
specific; too much for real world citations. Consider that many books
are published in the year preceding their copyright date, which is in
fact the date used for citation. I'd prefer just
On 2/20/07, Thom Shannon [EMAIL PROTECTED] wrote:
I think it should also be possible to use openIDs in other elements than
just anchors. You don't necessarily want to link to them, it's the url
itself which is important not the location.
It should also support none canonical urls so they can be
On 2/20/07, anders conbere [EMAIL PROTECTED] wrote:
It derives it's meaning and value from the use of the global
DNS system, regardless if you're actually looking to direct
traffic to your openID or not, it's the nature of it being an
anchor that gives it power.
Check out the 2.0 spec. There
On Feb 20, 2007, at 6:56 PM, John Panzer wrote:
Scott Reynen wrote:
On Feb 20, 2007, at 3:24 PM, Thom Shannon wrote:
Forgive me if this is going over old ground, I just joined this
list and
couldn't find what I was looking for on the wiki. Are there any
particular conventions emerging for
Hi Christopher,
On Feb 20, 2007, at 7:00 PM, Christopher St John wrote:
Check out the 2.0 spec. There are some changes:
http://openid.net/specs/openid-authentication-2_0-11.html
It introduces XRI into the mix (think brand new, non-DNS
naming system) Wouldn't expect it to work so well in an a
Scott Reynen wrote:
On Feb 20, 2007, at 6:56 PM, John Panzer wrote:
Scott Reynen wrote:
...
Here's the purpose of UID from vCard:
To specify a value that represents a globally unique
identifier corresponding to the individual or resource associated
with the vCard.
So if two hCards
25 matches
Mail list logo
