Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 34638 invoked from network); 19 Oct 2003 22:11:43 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 19 Oct 2003 22:11:43 -0000 Received: (qmail 64050 invoked by uid 500); 19 Oct 2003 22:11:26 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 64020 invoked by uid 500); 19 Oct 2003 22:11:26 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 64006 invoked from network); 19 Oct 2003 22:11:25 -0000 Received: from unknown (HELO pulse.betaversion.org) (217.158.110.65) by daedalus.apache.org with SMTP; 19 Oct 2003 22:11:25 -0000 Received: (qmail 4530 invoked from network); 19 Oct 2003 22:11:30 -0000 Received: from unknown (HELO apache.org) (stefano@62.167.66.71) by pulse.betaversion.org with SMTP; 19 Oct 2003 22:11:30 -0000 Date: Mon, 20 Oct 2003 00:11:38 +0200 Subject: Re: [RT] Moving towards a new documentation system Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) From: Stefano Mazzocchi To: dev@cocoon.apache.org Content-Transfer-Encoding: 7bit In-Reply-To: <200310192144.h9JLiGb29489@server1.livestoryboard.com> Message-Id: <35C19DB8-0281-11D8-88B2-000393D2CB02@apache.org> X-Mailer: Apple Mail (2.552) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N On Sunday, Oct 19, 2003, at 23:41 Europe/Rome, Robert Koberg wrote: > Hi, > > This is probably a minor and implementation detail but I when I see the > examples of datatypes being giving I was wondering if you were taking > into > consideration of XML Schema datatypes (and therefore RNG datatypes, > though I > don't understand the desire of clearly object oriented-type people > using > RNG). Some of the examples I have seen do not conform to the structures > allowed. > > For example, unique IDs cannot start with a number, but all examples > of IDs > have been strictly numerical. Also the date below: > > http://host/path/id!date=20031015 > > does not conform to ISO 8601. hmmm, http://www.cl.cam.ac.uk/~mgk25/iso-time.html, says part from the recommended primary standard notation YYYY-MM-DD, ISO 8601 also specifies a number of alternative formats for use in applications with special requirements. All of these alternatives can easily and automatically be distinguished from each other: The hyphens can be omitted if compactness of the representation is more important than human readability, for example as in 19950204 > Am I just being to nit-picky or is this something that simply has no > value > here? but I agree: if we can, reusing datatypes from other standards is a good thing (might well give us code to reuse for parsing already implemented in other projects!) -- Stefano.