On 04 Dec 2006, at 21:48, Michael McCracken wrote:
I do think that a URL field (class=url) should be included, to
represent a link to a copy of the cited work, and if we want to mark
up one or more identifiers, we can use a separate class (I suggest
uid) to do so. If we're lucky and there's a
On 12/8/06, Alf Eaton [EMAIL PROTECTED] wrote:
On 04 Dec 2006, at 21:48, Michael McCracken wrote:
I do think that a URL field (class=url) should be included, to
represent a link to a copy of the cited work, and if we want to mark
up one or more identifiers, we can use a separate class (I
I've added a spot in the straw format section in
citation-brainstorming to start documenting the fields we've discussed
thoroughly:
http://microformats.org/wiki/citation-brainstorming#Working_straw_schema
I put in URI for now, since I'm now mostly convinced that it will
solve more problems than
On 08 Dec 2006, at 18:05, Michael McCracken wrote:
On 12/8/06, Alf Eaton [EMAIL PROTECTED] wrote:
On 08 Dec 2006, at 17:26, Michael McCracken wrote:
On 12/8/06, Alf Eaton [EMAIL PROTECTED] wrote:
On 04 Dec 2006, at 21:48, Michael McCracken wrote:
If there are enough useful identifiers
On Dec 8, 2006, at 12:05 PM, Michael McCracken wrote:
I'm not sure why you'd mark up a CMS ID that wasn't also a URI as part
of a microformat. Can you expand on your example?
I'm not sure where this is going, but it looks like a discussion that
I believe happened once already leading to
PROTECTED] On
Behalf Of Michael McCracken
Sent: Thursday, December 07, 2006 6:05 PM
To: Microformats Discuss
Subject: Re: Re: RE: [uf-discuss] [citation] url field
This seems to have been buried - so again, to anyone
interested in hCite:
I want to define a new field URL to denote an http
McCracken
Sent: Thursday, December 07, 2006 6:05 PM
To: Microformats Discuss
Subject: Re: Re: RE: [uf-discuss] [citation] url field
This seems to have been buried - so again, to anyone
interested in hCite:
I want to define a new field URL to denote an http URL that
points to the location of a copy
On 02 Dec 2006, at 16:51, Ross Singer wrote:
On 12/2/06, Alf Eaton [EMAIL PROTECTED] wrote:
/http:\/\/dx.doi.org\/(.+)/
Well, this requires the user to understand a lot about DOIs. A user
might /find/ a dx.doi.org URL, but it's definitely not going to be the
URL they wind up at
On 12/2/06, Mike Schinkel [EMAIL PROTECTED] wrote:
A couple points on this subject. I have recently been doing a *lot* of
research in the area of URLs/URIs and having discussions with numerous
people on REST-discuss and www-TAG lists so I feel I'm pretty well-versed on
this subject now.
Andy Mabbett wrote:
What about:
a class= tag isbn href=http://www.example.com/wibble/71194301X;
which could be a URL on the same site as the citation,
or on a trusted bibliographic website.
Agreed, but is there the latter?
-Mike Schinkel
http://www.mikeschinkel.com/blogs/
Ross Singer wrote:
Also, where do get that Jon Udell's Library Lookup 'is reliably
extracting ISBNs from URLs'? LibraryLookup finds ISBNs in /HTML/ and
writes a URL to a library catalog based on it.
LibraryLookup does actually get the ISBN from the URL: it looks for
On Dec 1, 2006, at 10:44 PM, Ross Singer wrote:
But how many 'citable' URLs contain ISBNs?
Apparently every book on Amazon.com, BarnesAndNoble.com and ISBN.nu
has a URL containing its ISBN.
DOIs are likely to be in a
URL, but they are, sadly, impossible to discern (don't let the 10.foo
As a peripheral observer of this discussion, may I note that parsing
within a URI/URL has a precident in rel-tag [1]
Regards, etc...
David
[1] http://microformats.org/wiki/rel-tag#Abstract
--
David Janes
Founder, BlogMatrix
http://www.blogmatrix.com
http://www.onamine.com
Scott Reynen wrote:
On Dec 1, 2006, at 10:44 PM, Ross Singer wrote:
DOIs are likely to be in a
URL, but they are, sadly, impossible to discern (don't let the 10.foo
fool you -- a DOI can contain any character and as many characters
until whitespace - there is no way to know if the DOI ends
On 12/2/06, Alf Eaton [EMAIL PROTECTED] wrote:
Ross Singer wrote:
Also, where do get that Jon Udell's Library Lookup 'is reliably
extracting ISBNs from URLs'? LibraryLookup finds ISBNs in /HTML/ and
writes a URL to a library catalog based on it.
LibraryLookup does actually get the ISBN from
A couple points on this subject. I have recently been doing a *lot* of
research in the area of URLs/URIs and having discussions with numerous
people on REST-discuss and www-TAG lists so I feel I'm pretty well-versed on
this subject now.
Although it is possible to infer an ISBN or maybe even a DOI
In message
[EMAIL PROTECTED], David
Janes [EMAIL PROTECTED] writes
parsing within a URI/URL has a precident in rel-tag
What about:
a class= tag isbn href=http://www.example.com/wibble/71194301X;
which could be a URL on the same site as the citation, or on a trusted
bibliographic website.
--
On 11/30/06, Michael McCracken [EMAIL PROTECTED] wrote:
If you mean why not call it URI?,
Yeah, that's what I mean, and worried about collapsing the notion of
URI as a name, and URL as a location. I'm skeptical we can rely on
parsing a URL fo extracting a DOI/ISBN/etc.
Bruce
On Dec 1, 2006, at 3:55 PM, Bruce D'Arcus wrote:
If you mean why not call it URI?,
Yeah, that's what I mean, and worried about collapsing the notion of
URI as a name, and URL as a location. I'm skeptical we can rely on
parsing a URL fo extracting a DOI/ISBN/etc.
Data point: ISBNs are
But how many 'citable' URLs contain ISBNs? DOIs are likely to be in a
URL, but they are, sadly, impossible to discern (don't let the 10.foo
fool you -- a DOI can contain any character and as many characters
until whitespace - there is no way to know if the DOI ends before the
URL does).
Also,
On Dec 1, 2006, at 3:55 PM, Bruce D'Arcus wrote:
Scott Reynen
If you mean why not call it URI?,
Yeah, that's what I mean, and worried about collapsing the notion of
URI as a name, and URL as a location. I'm skeptical we can rely on
parsing a URL fo extracting a DOI/ISBN/etc.
Have you
On 11/30/06, Michael McCracken [EMAIL PROTECTED] wrote:
I also suggest that in the case of identifiers like a DOI or ISBN
which can be represented as a parameter in a link to doi.org or some
other resolver, that the format encourage using a URL field for those
identifiers and not include
On 11/30/06, Bruce D'Arcus [EMAIL PROTECTED] wrote:
On 11/30/06, Michael McCracken [EMAIL PROTECTED] wrote:
I also suggest that in the case of identifiers like a DOI or ISBN
which can be represented as a parameter in a link to doi.org or some
other resolver, that the format encourage using a
23 matches
Mail list logo
