Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 91640 invoked from network); 2 Feb 2005 03:45:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 2 Feb 2005 03:45:32 -0000 Received: (qmail 42198 invoked by uid 500); 2 Feb 2005 03:45:30 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 42135 invoked by uid 500); 2 Feb 2005 03:45:29 -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 42121 invoked by uid 99); 2 Feb 2005 03:45:29 -0000 X-ASF-Spam-Status: No, hits=0.4 required=10.0 tests=DNS_FROM_RFC_ABUSE X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from terror.vuw.ac.nz (HELO terror.vuw.ac.nz) (130.195.86.21) by apache.org (qpsmtpd/0.28) with ESMTP; Tue, 01 Feb 2005 19:45:28 -0800 Received: from [130.195.85.188] (HELO coso.staff.vuw.ac.nz) by terror.vuw.ac.nz (CommuniGate Pro SMTP 3.5.9) with ESMTP id 681526 for dev@cocoon.apache.org; Wed, 02 Feb 2005 16:47:22 +1300 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: Version $Id$ style for xml files (Was: SVN behaviour with "Id" keyword) Date: Wed, 2 Feb 2005 16:42:02 +1300 Message-ID: <802926B6AB8533408C33ADBCA3EE5C2A138D7D@coso.staff.vuw.ac.nz> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Version $Id$ style for xml files (Was: SVN behaviour with "Id" keyword) Thread-Index: AcUIuWS521PvLU3BTnehtDBreRuMkAAHcxPQ From: "Conal Tuohy" To: X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Tim Larson wrote: > On Wed, Feb 02, 2005 at 10:35:03AM +1300, Conal Tuohy wrote: > > > Tim Larson wrote: > > > > As part of my effort to keep whiteboard/forms mergeable, > > > > >Could we pick a style, and then I will make the files I > > > >happen to touch match it? > >=20 > > What about a processing instruction?=20 > > > >=20 > > This has the advantage over a comment that it can be=20 > retrieved unambiguously with an XPath query:=20 > > "processing-instruction('version')"=20 >=20 > I like the ability to retrieve the Id info...not knowing > much about processing instructions, will this produce > valid processing instructions when the version control > system expands $Id$? This expands into lots of stuff: > datestamp, filename, submitter, etc. So long as it doesn't include the string "?>" it will be OK. > Also, can this mess up any existing document processing? It shouldn't. Most XML software should be happy to ignore processing = instructions (unless the pi is targeted at them), just like with = comments.=20 In the SAX pipeline, the processing instructions are passed using a = "processingInstruction" method, so completely independently of = startElement/endElement/characters/etc. Typically, pipeline components = will inherit a "processingInstruction" method from a superclass, which = will do nothing. Cheers Con