Re: Napster, Gnutella: URN lookup services?

Date view Thread view Subject view Author view

From: Gregory Alan Bolcer (
Date: Wed Jun 28 2000 - 10:28:02 PDT

The problem with Napster is that there are
no standard style requirements for putting songs into the

Artist -- Song
artist / song
Song -- Artist
song / artist
Song -- Artist -- Comments
atirst -- song (looking for artist vs. atirst)

etc, etc.

Here's the problem. Searches are context sensitive and non-idempotent.
Putting in a search into the artist box will yield one set
of results, but putting in the artist into the title box will
find a whole different set of the same music.

Add the spoofing problem and they have a big problem on their hands. The
abundance of music makes it usable, but not exact.

Jim Whitehead wrote:
> So, it dawned on me today that the name of a song, along with its band name,
> acts as an identifier for the song. Hence, it is possible to construct a
> Uniform Resource Name (URN) for songs, following syntax rules given in RFC
> 2141 <>. Examples being:
> urn:music:The%20Cars:Good%20Times%20Roll:
> (The Cars, Good Times Roll)
> urn:music:The%20Beatles:Lucy%20in%20the%20Sky%20with%20Diamonds:
> (The Beatles, Lucy in the Sky with Diamonds)
> An additional field could be added for song variants:
> urn:music:Orb:Little%20Fluffy%20Clouds:Live:
> (Orb, Little Fluffy Cluds, Live)
> This being the case, Napster and Gnutella start looking like URN resolution
> services. Of course, Napster and Gnutella are also capable of handling
> searches just on song name, and just on group name, which could also be
> handled by introducing a wildcard into the name:
> urn:music:The%20Cars:#:
> (A collection resource containing all of the songs by The Cars)

Gregory Alan Bolcer        |    | work: 949.833.2800
Chief Technology Officer   | | cell: 714.928.5476
Endeavors Technology, Inc. | efax: 603.994.0516     | wap:  949.278.2805

Date view Thread view Subject view Author view

This archive was generated by hypermail 2b29 : Wed Jun 28 2000 - 10:28:43 PDT