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 this
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 ide
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 that aren't URIs (I think
>> there probably
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 that aren't URIs (I think
there probably are), then there needs to be a UID field as well.
Can you
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 tha
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
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
TECTED] 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 n
; [mailto:[EMAIL 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
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 of the cited work.
URIs that encode an identifier of the work can be combined with this
field, but do not need to be.
I unders
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.
Althou
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 (dx.doi.
Andy Mabbett wrote:
>> What about:
>> 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/
http://www.welldesignedurls.
In message
<[EMAIL PROTECTED]>, David
Janes <[EMAIL PROTECTED]> writes
>parsing within a URI/URL has a precident in rel-tag
What about:
http://www.example.com/wibble/71194301X";>
which could be a URL on the same site as the citation, or on a trusted
bibliographic website.
--
Andy Mabbett
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
On 12/2/06, Ross Singer <[EMAIL PROTECTED]> wrote:
[...]
I stand by my point, though, why rely on ambiguity?
Exactly!
Bruce
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microfo
On 12/2/06, Scott Reynen <[EMAIL PROTECTED]> wrote:
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.
This is still my point. When you are 'citing' a
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
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 (dx.doi.org is a redirection service, for those
that don
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 DO
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
http://blogmatrix.blog
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
fo
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
([\/-]|is[bs]n=)(\d{7,9}
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/ISB
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, wh
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 alrea
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 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 u
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 separ
Based on the existence of a URL in the examples listed at the end of
this email, I propose modifying the working straw format at
http://microformats.org/wiki/citation-brainstorming#Brian.27s_Straw_format
to include a URL field, denoting the URL to a copy of the work
available online (often a PDF,
30 matches
Mail list logo
