-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
> Tres Seaver wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Florent Guillaume wrote:
>>
>>> Jim Fulton wrote:
>>>
>>>
I think that sources are different than initial value. I really don't
see any role
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Florent Guillaume wrote:
Jim Fulton wrote:
I think that sources are different than initial value. I really don't
see any role that "initial value" has in an object specification.
A schema is a specification for an object tha
Florent Guillaume wrote:
Jim Fulton wrote:
But a schema is useful for more than "specifying the values of an
object". All notions of schemas I've encountered (CPS Schemas, XML
Schemas, Archetypes) use the schema to constrain or validate an
existing object, yes, but also to create new objects
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Florent Guillaume wrote:
Jim Fulton wrote:
I think that sources are different than initial value. I really don't
see any role that "initial value" has in an object specification.
A schema is a specification for an object tha
Gary Poster wrote:
On Sep 7, 2005, at 9:13 AM, Florent Guillaume wrote:
Jim Fulton wrote:
I think that sources are different than initial value. I really don't
see any role that "initial value" has in an object specification.
A schema is a specification for an object that provides the sche
Jim Fulton wrote:
But a schema is useful for more than "specifying the values of an
object". All notions of schemas I've encountered (CPS Schemas, XML
Schemas, Archetypes) use the schema to constrain or validate an
existing object, yes, but also to create new objects from scratch
(even in the
Florent Guillaume wrote:
Jim Fulton wrote:
I think that sources are different than initial value. I really don't
see any role that "initial value" has in an object specification.
A schema is a specification for an object that provides the schema.
An initial value doesn't constrain or specify
On Sep 7, 2005, at 9:59 AM, Janko Hauser wrote:
...
But actually this started with the observation that if we keep
default, we need something like a dynamic default, not only a fixed
value in the schema definition. This happens for example if one
wants to set the current date as the default
Am 07.09.2005 um 15:42 schrieb Tres Seaver:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Florent Guillaume wrote:
Jim Fulton wrote:
I think that sources are different than initial value. I really
don't
see any role that "initial value" has in an object specification.
A schema is a sp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Florent Guillaume wrote:
> Jim Fulton wrote:
>
>> I think that sources are different than initial value. I really don't
>> see any role that "initial value" has in an object specification.
>>
>> A schema is a specification for an object that provides
On Sep 7, 2005, at 9:13 AM, Florent Guillaume wrote:
Jim Fulton wrote:
I think that sources are different than initial value. I really
don't
see any role that "initial value" has in an object specification.
A schema is a specification for an object that provides the schema.
An initial valu
Jim Fulton wrote:
I think that sources are different than initial value. I really don't
see any role that "initial value" has in an object specification.
A schema is a specification for an object that provides the schema.
An initial value doesn't constrain or specify the object. If anything,
i
12 matches
Mail list logo
