|
Amy Krause: 06/24/2005 10:11 AM EST
|
|
Comment: |
The interface for managing schemas in a collection will be optional.
|
|
Action: |
Update
|
|
Amy Krause: 06/24/2005 10:11 AM EST
|
|
Action: |
Update
artifact_status changed from Open to Closed
close_date changed from - to 2005-06-24 16:11:33
|
|
Shannon Hastings: 11/29/2004 12:34 PM EST
|
|
Comment: |
I propose that we architect our solution so that AddSchema is an in optional access interface that can be put on an XML Collection which is "
structured" or something to that effect.
|
|
Action: |
Update
|
|
Scott Oster: 09/21/2004 11:47 AM EST
|
|
Comment: |
I would expect the data resource would provide the capability and would not expect it to bind to individual documents just by adding the schema to the
Collection.
There are several potential uses of the schema, including but not limited to: validation on addDocument, limiting acceptable instance documents, and
providing hints for storage optimization.
In this manner I also disagree addSchema would assume that existing documents should have to adhere to the schema. I don't believe it makes sense that
validated and non-validated documents should co-exist in the same collection.
|
|
Action: |
Update
|
|
Mario Antonioletti: 09/01/2004 6:24 AM EST
|
|
Action: |
Update
assigned_to changed from 100 to 915
|
|
|
|