forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dave Brondsema <d...@brondsema.net>
Subject Re: svn commit: rev 21092 - in forrest/trunk/src: core/context/resources/schema core/context/resources/schema/dtd core/context/skins/krysalis-site/xslt/html core/fresh-site/src/documentation documentation
Date Fri, 11 Jun 2004 15:06:09 GMT
Juan Jose Pablos wrote:
> brondsem@apache.org escribió:
> 
>> ============================================================================== 
>>
>> --- forrest/trunk/src/core/context/resources/schema/catalog.xcat    
>> (original)
>> +++ forrest/trunk/src/core/context/resources/schema/catalog.xcat    
>> Fri Jun 11 06:42:00 2004
>> @@ -45,6 +45,8 @@
>>          uri="dtd/skinconfig-v06.dtd"/>
>>  <public publicId="-//APACHE//DTD Skin Configuration V0.6-1//EN"
>>          uri="dtd/skinconfig-v06-1.dtd"/>
>> +<public publicId="-//APACHE//DTD Skin Configuration V0.6-2//EN"
>> +        uri="dtd/skinconfig-v06-2.dtd"/>
>>  <public publicId="-//APACHE//ENTITIES Documentation V2.0a//EN"
>>          uri="dtd/v20a/document-v20.mod"/>
>>  <public publicId="-//APACHE//DTD FAQ V2.0a//EN"
>>
> 
> 
> why do we need to add a new DTD for each change?
> 
> 
> Cheers,
> Cheche

A DTD should never change.  Of course with new required elements we 
would need a new DTD so we don't break end-user's validations suddenly. 
  However even for small changes even for developers we should do this 
because it's simpler to have this policy instead of deciding for each 
change whether it merits a new DTD or not.

And users (including us devs) don't need to keep changing their DTD 
references.  You can stay at -v06-1 (probably -v06 too) with no problem.

-- 
Dave Brondsema : dave@brondsema.net
http://www.splike.com : programming
http://csx.calvin.edu : student org
http://www.brondsema.net : personal

Mime
View raw message