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 AAA20248; Sat, 31 Aug 2002 00:39:21 +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 AAA20210 for ; Sat, 31 Aug 2002 00:39:20 +0200 (MET DST) Received: from wetware.wetware.com (wetware.wetware.com [199.108.16.1]) by nez-perce.inria.fr (8.11.1/8.11.1) with ESMTP id g7UMdJD01706 for ; Sat, 31 Aug 2002 00:39:19 +0200 (MET DST) Received: from kallisti.local.(ra06.wetware.com[199.108.16.86]) (2755 bytes) by wetware.wetware.com via sendmail with P:esmtp/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) id for ; Fri, 30 Aug 2002 15:39:16 -0700 (PDT) (Smail-3.2.0.114 2001-Aug-6 #1 built 2002-Aug-4) Date: Fri, 30 Aug 2002 15:39:31 -0700 Subject: Re: [Caml-list] Namespace proposal: XML variant Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v543) Cc: caml-list@inria.fr To: Jeffrey Palmer From: james woodyatt In-Reply-To: <200208301525.07033.jeffrey.palmer@acm.org> Message-Id: <59900BFE-BC69-11D6-A71C-000502DB38F5@wetware.com> Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.543) Sender: owner-caml-list@pauillac.inria.fr Precedence: bulk On Friday, Aug 30, 2002, at 13:25 US/Pacific, Jeffrey Palmer wrote: > On Friday 30 August 2002 01:02 pm, Alessandro Baretta wrote: >> >> I propose to add an optional namespace construct to >> explicitly associate namespace URIs with namespace names. > > 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. [...] A more constructive way to say this might be to observe that any syntax for a global namespace of Objective Caml types and values could be transformed into a URN by simply publishing an Internet RFC that defined the syntax for the namespace specific string, according to the requirements of RFC 2141. It would seem desirable to choose a namespace syntax that lends itself easily to encoding in a URN. Here's another strawman for discussion. ----- The obvious choice for a namespace identifier is "ocaml" and this would produce URN's of the following form: I chose a ':' character to separate levels in the namespace hierarchy arbitrarily. Other characters like '/' or '.' could easily be considered as well. In this example, you could imagine that the compiler could be invoked with a namespace flag, like so: ocamlc -N :some:hierarchy -c yourModuleHere.ml -o yourModuleHere.cmo You could then define a language construct that looks kinda like the following: namespace N = :some:hierarchy module M = N:YourModuleHere The 'namespace' keyword would define an alias for a prefix to the modules in some part of the global namespace, and it would be used in a straightforward way as shown above to construct the names of externally defined module types. The namespace would be encoded in the .cmi and .cmo files, and the tool chain would need to respect them as it searched for signatures and modules to reference. -- j h woodyatt markets are only free to the people who own them. ------------------- 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