Example for Re: [Osr-101] Adding metadata to checkin/save operations

[Thomas Comiotto]

.. I forgot to add an example to my last post;) So here it is:

[Metadata as part of a resource-set]

<edit>
   <resource-set name="Some Article">
     <resource name="Article Content">
       <open url="article.xml"/>
       <style type="xslt" url="page.xsl">
         <template url="page.xml"/><!-- note that page.xml hasn't to 
include meta.rdf -->
       </style>
       <schema type="relaxNG" url="article.rng"/>
     </resource>
     <resource name="Article Metadata">
       <open url="meta.rdf"/>
       <style type="form"/><!-- split pane widget, left: element 
navigator, right: form fields for text nodes & attributes  -->
       <schema type="relaxNG" url="meta.rng"/>
     </resource>
   </resource-set>
</edit>

Clients might want to deal with metadata in a special way GUI wise. 
They might only want to display metadata on demand, might want to 
provide some hard wired "Edit Metadata" menuitem or whatever. To 
achieve this another hinting directive (apart from <style type="XXX"/> 
would be needed.

--
Bests,
Thomas



Am 02.08.2006 um 22:08 schrieb 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
>>
>
>
> _______________________________________________
> Osr-101 mailing list
> Osr-101 at wyona.org
> http://wyona.com/cgi-bin/mailman/listinfo/osr-101
>