On Apr 24, 2006, at 8:18 PM, Xiaoming Liu wrote:
Hi, I am joining the discussion with background of library system.
I don't think the definition of UID completely matches URI. The
globally unique identifier has a flavour of UUID, as the example
in vcard.
On 4/24/06 7:56 PM, Etan Wexler [EMAIL PROTECTED] wrote:
Third, I actually see disadvantages in using URIs as a basic unit rather
than URLs.
All URLs are URIs. What have I missed?
The opposite. The fact that not all URIs are URLs. That's the point. You
can infer things about a URL in
On 4/24/06 8:09 PM, Benjamin Carlyle [EMAIL PROTECTED]
wrote:
On Mon, 2006-04-24 at 23:39 +0100, Andy Mabbett wrote:
In message [EMAIL PROTECTED], Alf Eaton
[EMAIL PROTECTED] writes
How would you see that sitting inside HTML mark-up?
abbr class=uri title=urn:isbn:09507881200 9507881-2-0/abbr
On 4/24/06 7:50 PM, Etan Wexler [EMAIL PROTECTED] wrote:
Tantek Çelik wrote to the Microformats Discuss mailing list on
2006-04-19 in a message with a title like ³[uf-discuss] UID, URL, live
microformats (was: Microformat auto-discovery WAS: Plazes
Microformats)² (mid:[EMAIL PROTECTED],
On Apr 25, 2006, at 9:21 AM, Tantek Çelik wrote:
The closest thing to UIDs that current publishers of hCards are
publishing
are their unique URLs within their sites (e.g. Upcoming and
Eventful venues
and events).
I have a concern that using URLs as UIDs will prevent them from being
First of all, Welcome Xiaoming Liu!
On 4/25/06 8:19 AM, Xiaoming Liu [EMAIL PROTECTED] wrote:
On Tue, 25 Apr 2006, Ryan King wrote:
URLs, if used propertly can be sufficient for globalby unique
identifier[s]. Sure, you can mess things up by using a non-routeable address
or scheme, but
Tantek Çelik wrote:
I think the case for ISBN is no big difference from telephone number or
zip code, etc.
The average person knows, understands, and uses telephone numbers and zip
codes all the time. The same cannot be said about ISBN. This is a big
difference.
The average person does not
On Tue, 25 Apr 2006, Tantek Çelik wrote:
Please list the specific problems you've found with UID or URL, so we can
make sure they are documented and properly explored/resolved.
Thanks for taking into consideration.
First hopefully we all agree on the problem to be addressed here, I think
On 4/25/06 12:01 PM, Xiaoming Liu [EMAIL PROTECTED] wrote:
On Tue, 25 Apr 2006, Tantek Çelik wrote:
Please list the specific problems you've found with UID or URL, so we can
make sure they are documented and properly explored/resolved.
Thanks for taking into consideration.
First
On Apr 25, 2006, Tantek Çelik wrote:
We *want*
resources that can be identified by network location and thus a
system that
shows a bias *for* that is a *good* thing.
Is the proposal that UIDs SHOULD be URLs or UIDs MUST be URLs? If
it's MUST, that would seem to discourage use of
On 4/25/06, Tantek Çelik [EMAIL PROTECTED] wrote:
On 4/25/06 12:01 PM, Xiaoming Liu [EMAIL PROTECTED] wrote:
First hopefully we all agree on the problem to be addressed here, I think
it is a microformat for indicating something *is* an identifier, and I
will presume there are three
In message [EMAIL PROTECTED], Tantek Çelik
[EMAIL PROTECTED] writes
I'm very concerned that that may be an abuse of abbr; and wonder how
it will sound when read to someone using assistive software?
This is a common misconception[1] about the title attribute.
[1]
In message [EMAIL PROTECTED], Tantek Çelik
[EMAIL PROTECTED] writes
I think the case for ISBN is no big difference from telephone number or
zip code, etc.
The average person knows, understands, and uses telephone numbers and
zip codes all the time. The same cannot be said about ISBN.
On 4/25/06 2:41 PM, Andy Mabbett [EMAIL PROTECTED] wrote:
In message [EMAIL PROTECTED], Tantek Çelik
[EMAIL PROTECTED] writes
I think the case for ISBN is no big difference from telephone number or
zip code, etc.
The average person knows, understands, and uses telephone numbers and
zip
On 4/25/06 2:38 PM, Andy Mabbett [EMAIL PROTECTED] wrote:
In message [EMAIL PROTECTED], Tantek Çelik
[EMAIL PROTECTED] writes
I'm very concerned that that may be an abuse of abbr; and wonder how
it will sound when read to someone using assistive software?
This is a common misconception[1]
Tantek,
Your responses and your reply about 'letting the market decide' what
gets to survive on the web makes me think that your attitude about
microformats is:
Microformats are for commercial-purposes first and foremost. Everything else is an edge case that can be dismissed.
And, quite
On 4/25/06 3:04 PM, Ross Singer [EMAIL PROTECTED] wrote:
Tantek,
Your responses and your reply about 'letting the market decide' what gets to
survive on the web makes me think that your attitude about microformats is:
Microformats are for commercial-purposes first and foremost.
Not
On 4/25/06 1:35 PM, Scott Reynen [EMAIL PROTECTED] wrote:
On Apr 25, 2006, Tantek Çelik wrote:
We *want*
resources that can be identified by network location and thus a
system that
shows a bias *for* that is a *good* thing.
Is the proposal that UIDs SHOULD be URLs or UIDs MUST be URLs?
On Tue, 25 Apr 2006, Tantek Çelik wrote:
ISO8601 is fairly well accepted. The battle is over. So we pick the
current winner and go with it.
Whereas, as you point out, the market for abstract ids, whether ISBN,
pubmed, or whatever is still churning away, so we let it continue to churn.
I
On 4/25/06 3:25 PM, Xiaoming Liu [EMAIL PROTECTED] wrote:
On Tue, 25 Apr 2006, Tantek Çelik wrote:
ISO8601 is fairly well accepted. The battle is over. So we pick the
current winner and go with it.
Whereas, as you point out, the market for abstract ids, whether ISBN,
pubmed, or
On Tue, 25 Apr 2006, Tantek Çelik wrote:
With URI you got all these things free, and you don't have to argue about
persistentence or uniqueness (which are hollow without concrete
schema/mechanism), it's much simpler to directly reference URI RFC.
True. My point is that URL is preferable
On 4/25/06, Tantek Çelik [EMAIL PROTECTED] wrote:
It may be stronger, but it's problematic in many cases.
Then we postpone those cases and focus on the ones that work now.
Except that the thread that got merged into the uid one was, in fact,
about marking up isbns and such, which is one of
On 4/25/06 4:47 PM, Bruce D'Arcus [EMAIL PROTECTED] wrote:
FWIW, I like Xiaoming's suggestion.
Cool. Please add that comment (with your name/WikiAlias) to Xiaoming's
proposal on the uid-brainstorming page.
Thanks,
Tantek
___
microformats-discuss
Chris Messina wrote:
On 4/12/06, Jude Robinson [EMAIL PROTECTED] wrote:
Would it be appropriate to add this to
http://microformats.org/wiki/chat-examples under a tentative *might be
relevant to chat* podcast transcripts heading?
Sure. It's a kind of chat... though I wonder if there isn't some
re:
http://www.dgabcsolutions.com.br/preview/camarascs/cm_home.asp
Is it actually allowed to have a hcalendar event without a date?
If so that could be a problem .. I think in the parser I want to put
together that will have to be a requirement.
(even for recurring events there must be some kind
On Apr 25, 2006, at 8:59 PM, Michael MD wrote:
re:
http://www.dgabcsolutions.com.br/preview/camarascs/cm_home.asp
Is it actually allowed to have a hcalendar event without a date?
If so that could be a problem .. I think in the parser I want to put
together that will have to be a requirement.
On 4/25/06, Tantek Çelik [EMAIL PROTECTED] wrote:
Yes, we get things done because we dismiss the 20% in favor of getting the
80% working well.
Except, in this case, you've dismissed the entire problem that we're
trying to solve here by merging into some only quasi-related 80%
case.
I would
On Apr 25, 2006, at 6:47 PM, Bruce D'Arcus wrote:
FWIW, I like Xiaoming's suggestion.
I'm glad Xiaoming expressed the case for URI so well. I just added it
to the uid-brainstorming [1] page. I have to admit I've seen the need
for a identifying URIs elsewhere and when Tantek pinged
Hello. I'm new to microformats and a bit confused on how one
disambiguates microformat names. It seems to be somewhat related to the
UID/URI issue.
I'm not sure I understand all of the subtleties between the spec and
proposals around these concepts, so I may misuse some of these terms.
I'll
Le 06-04-22 à 18:56, Andy Mabbett a écrit :
In message
[EMAIL PROTECTED], Bruce
D'Arcus [EMAIL PROTECTED] writes
ISBN is a registered URN, so I'd rather see coding that supported
that;
e.g. urn:isbn:0950788120.
How would you see that sitting inside HTML mark-up?
blockquote
Le 06-04-23 à 12:52, Alf Eaton a écrit :
On 22 Apr 2006, at 05:56, Andy Mabbett wrote:
In message
[EMAIL PROTECTED], Bruce
D'Arcus [EMAIL PROTECTED] writes
ISBN is a registered URN, so I'd rather see coding that supported
that;
e.g. urn:isbn:0950788120.
How would you see that sitting
31 matches
Mail list logo
