From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (from majordomo@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id AAA20281; Sat, 31 Aug 2002 00:51:52 +0200 (MET DST) X-Authentication-Warning: pauillac.inria.fr: majordomo set sender to owner-caml-list@pauillac.inria.fr using -f Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id AAA20533 for ; Sat, 31 Aug 2002 00:51:51 +0200 (MET DST) Received: from orcaware.com (bdsl.66.12.233.174.gte.net [66.12.233.174]) by nez-perce.inria.fr (8.11.1/8.11.1) with ESMTP id g7UMpnD01822 for ; Sat, 31 Aug 2002 00:51:50 +0200 (MET DST) Received: from orcaware.com (localhost.localdomain [127.0.0.1]) by orcaware.com (8.12.5/8.12.5) with ESMTP id g7UMpjvk018830; Fri, 30 Aug 2002 15:51:45 -0700 Message-ID: <3D6FF701.EFDAA166@orcaware.com> Date: Fri, 30 Aug 2002 15:51:45 -0700 From: Blair Zajac X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U) X-Accept-Language: en,x-ns1rfacHe4WNh5,x-ns2U100btwUq5f MIME-Version: 1.0 To: Jeffrey Palmer CC: caml-list@inria.fr Subject: Re: [Caml-list] Namespace proposal: XML variant References: <3D5FD3DF.60706@ozemail.com.au> <3D6FB33A.9020000@baretta.com> <200208301525.07033.jeffrey.palmer@acm.org> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-caml-list@pauillac.inria.fr Precedence: bulk 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 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