[Osr-101] Adding metadata to checkin/save operations

[Thomas Comiotto]

Hi

What about considering metadata being just some regular resource? You 
can attach metadata to another resource by using a resource-set and set 
constraints by attaching a schema. We could still introduce resource 
naming schemes for protocol extensions (versioning for instance).

BTW, a possibly useful neutron addition would be some directive that 
hints the client to use a form/treenode based editor (instead of 
WYSIWYG) for a resource. For some resources like metadata, database 
records etc.. I also can think of special hints to identify metadata 
resources - to simplify GUI integration a bit. Will elaborate on that 
in a seperate thread, ok?

--
Bests
Thomas








Am 02.08.2006 um 16:40 schrieb Andreas Wuest:

> Hi
>
> It would be nice to be able to send some metadata alongside the 
> document upon document checkin/save.
>
> This requires the following:
>
>  * A well-defined way for enveloping the document
>  * A way for the server to tell the client which metadata it expects, 
> and which of those would be mandatory (solved as an addition to the 
> introspection document)
>  * An exception for the server to tell the client that the client did 
> not fulfill its request completely (mandatory metadata missing).
>
> As a simple usecase, imagine the CMS to be Subversion based, and the 
> server like to receive a commit message alongside the document.
>
> WDYT?
>
> -- 
> Kind regards,
> Andi
>
> _______________________________________________
> Osr-101 mailing list
> Osr-101 at wyona.org
> http://wyona.com/cgi-bin/mailman/listinfo/osr-101
>