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 RAA21651; Sat, 2 Nov 2002 17:35:17 +0100 (MET) X-Authentication-Warning: pauillac.inria.fr: majordomo set sender to owner-caml-list@pauillac.inria.fr using -f Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id RAA21136 for ; Sat, 2 Nov 2002 17:35:16 +0100 (MET) X-SPAM-Warning: Sending machine is listed in blackholes.five-ten-sg.com Received: from athlon.baretta.com ([62.211.4.13]) by concorde.inria.fr (8.11.1/8.11.1) with ESMTP id gA2GZD520447 for ; Sat, 2 Nov 2002 17:35:14 +0100 (MET) Received: from baretta.com (localhost.localdomain [127.0.0.1]) by athlon.baretta.com (Postfix) with ESMTP id 4C85A27405; Sat, 2 Nov 2002 17:34:45 +0100 (CET) Message-ID: <3DC3FEA5.3020300@baretta.com> Date: Sat, 02 Nov 2002 17:34:45 +0100 From: Alessandro Baretta Organization: Baretta srl -- www.baretta.com User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: it, en MIME-Version: 1.0 To: "Yurii A. Rashkovskii" , ocaml Subject: Re: [Caml-list] module namespace References: <20021102002456.GC8925@rashko> <3DC39206.5080504@baretta.com> <20021102161015.GB1082@rashko> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-caml-list@pauillac.inria.fr Precedence: bulk Yurii A. Rashkovskii wrote: > Hi Alessandro! > > > As you can understand, I've proposed using reverse domains > as namespaces - Org.Ocaml, and so on. > It's not really equivalent. Consider my present work. I have three ongoing projects: one named afo, one named lib, and one named vsg. It would be natural to have a means of identifying my company first, and subsequently identifying each single project. Your proposal would be to use such namespace ids as Com.Baretta.VSG, Com.Baretta.Lib and Com.Baretta.Afo. There's nothing wrong with this, but it is much less intuitiva and comprehensible than "http://priv.baretta.com/afo", "http://priv.baretta.com/lib", "http://priv.baretta.com/svg". This latter schema allows for the identification of a URL -- in this case a private one on an intranet -- associated with the project. Further, such a schema allows for multiple versions of the same sw -- i.e. a private alpha such as the above, and a public release -- to coexist without interfering with each other. Your schema is viable, and it is good to have your proposal around. Hopefully, the developers will take a stand on the issue and propose a standard themselves, in which case it's likely to resemble what you submitted. Yet, I still advocate the use of the XML single layered namespace schema as a simple, flexibile and effective solution. Alex ------------------- 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