You are viewing a plain text version of this content. The canonical link for it is here.
Posted to slide-user@jakarta.apache.org by Andreas Probst <an...@gmx.net> on 2002/11/02 16:40:53 UTC

RE: Content-Language

Hi Peter,

thanks a lot. This is working fine now.

Andreas


On 31 Oct 2002 at 15:56, Nevermann, Dr., Peter wrote:

> Andreas, this should be fixed now.
> 
> Regards,
> Peter
>  
> 
> > -----Original Message-----
> > From: Nevermann, Dr., Peter [mailto:Peter.Nevermann@softwareag.com]
> > Sent: Wednesday, October 30, 2002 17:52
> > To: 'Slide Users Mailing List'
> > Subject: RE: Content-Language
> > 
> > 
> > Thanks, Andreas!
> > I will take care of this tomorow.
> > 
> > Regards,
> > Peter
> >  
> > 
> > > -----Original Message-----
> > > From: Andreas Probst [mailto:andpro77@gmx.net]
> > > Sent: Wednesday, October 30, 2002 12:13
> > > To: Slide Users Mailing List
> > > Subject: RE: Content-Language
> > > 
> > > 
> > > Hi Peter,
> > > 
> > > I got the latest and greatest code from CVS now. Setting 
> > > DAV:getcontentlanguage works fine on a VCR. However, as stated 
> > > in varios places of RFC3253, only the content and the dead 
> > > properties are stored on a VR. Although DAV:getcontentlanguage 
> > > is a live property and therefor not versioned, it seems strange 
> > > for me, that the default "en" keeps set on the VR. The same 
> > > applies to DAV:comment for instance, which isn't set on a VR.
> > > 
> > > Regards,
> > > Andreas
> > > 
> > > 
> > > On 29 Oct 2002 at 14:32, Nevermann, Dr., Peter wrote:
> > > 
> > > > Hi Andreas,
> > > >  
> > > > > > A property p is writable iff !p.isProtected(). Furthermore, 
> > > > > teh follwong
> > > > > > implications hold:
> > > > > > 1) p.isComputed() => p.isProtected => p.isLiveProperty()
> > > > > > 2) p.isDeadProperty() => !p.isProtected() (i.e. is writable)
> > > > > > 
> > > > > Where is this specified? I don't find anything about protected 
> > > > > and computed properties in RFC2518 or in 
> > > > > \docs\schema\webdav.xsd. The spec is only about dead and live 
> > > > > properties, I think.
> > > > 
> > > > RFC2518 does not talk about protected and computed 
> > > properties but DeltaV
> > > > does (see RFC3253, section 1.4). We decided to classify the 
> > > *all* live
> > > > properties (i.e. including RFC2518 and ACL) according to 
> > > DeltaV's scheme ...
> > > > and also made some mistakes :-).
> > > > 
> > > > > > It's a bug: the property is currently "protected" but it 
> > > > > shouldn't. I will
> > > > > > fix that immediately.
> > > > > 
> > > > > Thank you very much!
> > > > 
> > > > Fix is already checked-in.
> > > > 
> > > > Regards,
> > > > Peter


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>