caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Blair Zajac <blair@orcaware.com>
To: Jeffrey Palmer <jeffrey.palmer@acm.org>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Namespace proposal: XML variant
Date: Fri, 30 Aug 2002 15:51:45 -0700	[thread overview]
Message-ID: <3D6FF701.EFDAA166@orcaware.com> (raw)
In-Reply-To: <200208301525.07033.jeffrey.palmer@acm.org>

Jeffrey Palmer wrote:
> 
> On Friday 30 August 2002 01:02 pm, Alessandro Baretta wrote:
> > I thoroughly dislike any "package ~= directory" solution,
> > yet I think a namespace construct should be present in the
> > language in order to allow interoperability between
> > different projects with different naming conventions. I
> > propose a scheme à la XML, where namespaces are URIs
> > belonging to the person or organization which releases the
> > associated code.
> >
> > I propose to add an optional namespace construct to
> > explicitly associate namespace URIs with namespace names.
> >
> > namespace MyBigProject = "http://alexbaretta.com/big_project/"
> >
> >
> 
> Eeek!
> 
> Please, let's not entertain any of the rampant stupidity that the W3C seems so
> mired in. I've always thought that the concept of using URIs for namespaces,
> parameter settings, etc., was the most ridiculous thing I've ever seen. I
> mean, let's be honest here - HTTP is a network _protocol_, and it has nothing
> to do with anything namespace or parameter related. The thing that really
> irks me about the whole scheme is that most of the time these aren't even
> _valid_ URIs (i.e., inaccessible).
> 
> I'm all for a hierarchical namespace that's not related to the filesystem (In
> Java it always ended up causing headaches for large projects - compilers that
> "intelligently" put your compiled code in the correct package directory,
> etc.). It seems that the question of segmenting libraries according to
> directory should be a decision that's left up to the implementor, as it is
> currently.
> 
> All of this is, of course, my own opinion, so take it with the corresponding
> pinch of salt.
> 
> Cheers,

Tag URI may be a good choice.

http://www.taguri.org/

    The tag algorithm lets people create character strings which no
    one else using the same algorithm could ever create. It is simple
    enough to do in your head, and the resulting strings can be easy
    to read, write, and remember. You can use the strings wherever
    you need a unique identifier conforming to the URI (URL) Syntax 

They look like this:

    tag:sandro@world.std.org,2001-06-05:Taiko

Best,
Blair

-- 
Blair Zajac <blair@orcaware.com>
Web and OS performance plots - http://www.orcaware.com/orca/
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


      parent reply	other threads:[~2002-08-30 22:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-15 16:21 [Caml-list] Namespace proposal Gurr, David (MED, self)
2002-08-15 17:00 ` Vitaly Lugovsky
2002-08-15 21:08   ` [Caml-list] " Michaël Grünewald
2002-08-18 17:05 ` [Caml-list] " John Max Skaller
2002-08-30 18:02   ` [Caml-list] Namespace proposal: XML variant Alessandro Baretta
2002-08-30 20:25     ` Jeffrey Palmer
2002-08-30 22:39       ` james woodyatt
2002-08-30 22:51       ` Blair Zajac [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3D6FF701.EFDAA166@orcaware.com \
    --to=blair@orcaware.com \
    --cc=caml-list@inria.fr \
    --cc=jeffrey.palmer@acm.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).