You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by Quinton McCombs <qm...@nequalsone.com> on 2003/01/30 19:25:55 UTC
[Proposal] Versioning DTDs
The DTD for intake could change for each released version of Intake.
The same would hold true for any sort of DTD that we use as part of the
application. The sample XML file that we supply to the users has a
defined DTD on the jakarta site. This doesn't really matter for running
turbine since Intake will pull the DTD from the jar file.
However, XML editing tools will use the DTD as defined in the XML file.
For that reason, I think that we should put the intake.dtd fiel for each
version of Turbine on the jakarta site with the version number added to
the file name.
Exmaples:
Intake.dtd (leave this one as is for version 2.1)
Intake_2_1.dtd (just to be consistent)
Intake_2_2.dtd
Intake_2_3.dtd
Etc...
The sample XML files would reference the correct one for the version of
turbine being used. The DTD resolver would need a slight modification
to check for this.
Any objections?
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
RE: [Proposal] Versioning DTDs
Posted by Quinton McCombs <qm...@nequalsone.com>.
Good to see you back on the list :-)
> -----Original Message-----
> From: henning@forge.intermeta.de
> [mailto:henning@forge.intermeta.de] On Behalf Of Henning P.
> Schmiedehausen
> Sent: Saturday, February 01, 2003 7:26 AM
> To: turbine-dev@jakarta.apache.org
> Subject: Re: [Proposal] Versioning DTDs
>
>
> "Quinton McCombs" <qm...@nequalsone.com> writes:
>
> >The DTD for intake could change for each released version of Intake.
> >The same would hold true for any sort of DTD that we use as
> part of the
> >application. The sample XML file that we supply to the users has a
> >defined DTD on the jakarta site. This doesn't really matter for
> >running turbine since Intake will pull the DTD from the jar file.
>
> +1
>
> --
> Dipl.-Inf. (Univ.) Henning P. Schmiedehausen
> INTERMETA GmbH
> hps@intermeta.de +49 9131 50 654 0
> http://www.intermeta.de/
>
> Java, perl, Solaris, Linux, xSP
> Consulting, Web Services -- hero for hire
> freelance consultant -- Jakarta Turbine Development -- RHSCLG
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
Re: [Proposal] Versioning DTDs
Posted by "Henning P. Schmiedehausen" <hp...@intermeta.de>.
"Quinton McCombs" <qm...@nequalsone.com> writes:
>The DTD for intake could change for each released version of Intake.
>The same would hold true for any sort of DTD that we use as part of the
>application. The sample XML file that we supply to the users has a
>defined DTD on the jakarta site. This doesn't really matter for running
>turbine since Intake will pull the DTD from the jar file.
+1
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
hps@intermeta.de +49 9131 50 654 0 http://www.intermeta.de/
Java, perl, Solaris, Linux, xSP Consulting, Web Services -- hero for hire
freelance consultant -- Jakarta Turbine Development -- RHSCLG
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
Re: [Proposal] Versioning DTDs
Posted by Scott Eade <se...@backstagetech.com.au>.
+1 (Torque should also do this for database.dtd)
Cheers,
Scott
--
Scott Eade
Backstage Technologies Pty. Ltd.
http://www.backstagetech.com.au
.Mac Chat/AIM: seade at mac dot com
On 31/01/2003 5:25 AM, "Quinton McCombs" <qm...@nequalsone.com> wrote:
> The DTD for intake could change for each released version of Intake.
> The same would hold true for any sort of DTD that we use as part of the
> application. The sample XML file that we supply to the users has a
> defined DTD on the jakarta site. This doesn't really matter for running
> turbine since Intake will pull the DTD from the jar file.
>
> However, XML editing tools will use the DTD as defined in the XML file.
> For that reason, I think that we should put the intake.dtd fiel for each
> version of Turbine on the jakarta site with the version number added to
> the file name.
>
> Exmaples:
>
> Intake.dtd (leave this one as is for version 2.1)
> Intake_2_1.dtd (just to be consistent)
> Intake_2_2.dtd
> Intake_2_3.dtd
> Etc...
>
> The sample XML files would reference the correct one for the version of
> turbine being used. The DTD resolver would need a slight modification
> to check for this.
>
> Any objections?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org