W3C home > Mailing lists > Public > www-webdav-dasl@w3.org > July to September 1998

RE: datatyping is not needed

From: Babich, Alan <ABabich@filenet.com>
Date: Tue, 21 Jul 1998 11:18:35 -0700
Message-ID: <72B1992276A9D111A20E00805FEAC96D01324C7F@cm-expo1.filenet.com>
To: "'Dale Lowry'" <Lowry.Dale@gw.novell.com>, www-webdav-dasl@w3.org
If your "Date Published" property is an
obscure dead property, then they may not be
what I thought they were. I thought that "obscure"
implied "not defined in the schema". I assume that
"stored with the document metadata" means that your 
Date Published property IS defined in the schema. 
Is this assumption accurate?
(If it's not in the schema, then it seems unlikely 
to me that the server could search on it, since
your example is based on "a document management system".)

If a property is not in the DMS schema, clients would 
seem to be free to put whatever they want as the value
of the property on a resource by resource basis.
Wouldn't the DMS constrain the values stored for
"Date Published" to be datetimes? (If so, that
implies it is defined in the DMS schema.)

I would think that DMS property level security would
be used to make the property invisible or at least
readonly to other applications. (Accomplishing
that with security implies "Date Published" is defined
in the DMS schema.)

Thanks a lot for trying to help me out. The WebDAV 
spec. defines live and dead properties in section
3.1, but if the spec. defines obscure and famous dead
properties, I managed to overlook that (sorry).

Alan Babich

> -----Original Message-----
> From: Dale Lowry [mailto:Lowry.Dale@gw.novell.com]
> Sent: July 21, 1998 10:10 AM
> To: www-webdav-dasl@w3.org
> Subject: RE: datatyping is not needed
> Let me take a stab at providing a use case for obscure dead 
> properties. Someone correct me if my example is wrong.
> In a document management system you may have a rigid schema 
> for a given repository. That schema may include live 
> properties such as "Date Created" and dead properties such as 
> "Comment." However, it may be possible to store other 
> properties in the metadata. For example, "Date Published" 
> could be a property that is stored with the document metadata 
> by a custom application. This property is only known and 
> manipulated by this external application. 
> In the above scenario you want the end user to know about, be 
> able to update and be able to search the "Date Created" and 
> "Client" properties but not the "Date Published" property. 
> You certainly don't want "Date Published " to show up in the 
> schema for that repository. 
> I would catagorize "Date Published" in the above example as 
> an obscure dead property.
> Dale A. Lowry ( dlowry@novell.com )
> Novell GroupWise Document Management
> 801-222-4662
Received on Tuesday, 21 July 1998 14:21:34 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:22:40 UTC