[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


This page is part of the web mail archives of SRFI 84 from before July 7th, 2015. The new archives for SRFI 84 contain all messages, not just those from before July 7th, 2015.

Neil Van Dyke writes:

> If "http"-scheme URLs were used for identifying libraries, I'd think
> that each URL would actually be a reference to a Web object that
> could by retrieved via HTTP to define the referenced library.  If we
> only wanted a name for a library, I'd suggest not using URLs.  Is
> that what you had in mind?

Ray Blaak writes:

> If URLs are allowed, why restrict to only http:. Why shouldn't ftp:
> be allowed, or jar: to extract contents from an archive. Why not
> file: for local libs, or for during development?

My goal is to allow a programmer to easily and quickly choose a
readable name for their library that is unlikely to conflict with
other library names.

For programmers who are not putting their library under schemers.org
or who have their own domain name, I was looking for something that
many people would have, or could get easily, that would be readable
and would be largely unique to them.

Someone's email address would, I think, be a good example.  They are
more or less readable, and most people have one or can easily get one.
 While an email address can change hands, it is usually fairly unique
to the individual.  However I didn't think that people would want to
use their email address because of spam considerations.

Most people have their own web page, or can easily get one, and a web
page address is easily recognizable.

A clear disadvantage, I think, of using a web page address as an
identifier is that people will then expect that they should be able to
go to that address and get something.  The library itself perhaps.  Or
at least meta data about it.  And if you can do that, you should be
able to do it for open-source- library based names.  Or for
domain-name based names.  Or allow the meta-data to be pulled from ftp
or jars or files.

Using web page addresses as a name is not my first choice, but I do
think it is important to have it as an option.

Maybe leaving off the "http://"; would make it look less like a URL and
more like a name, and perhaps help avoid the confusing expectation
that you should be able to go to that web page and get something.