You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@lenya.apache.org by an...@apache.org on 2006/07/20 10:12:21 UTC

svn commit: r423816 - /lenya/trunk/src/webapp/lenya/config/cocoon-xconf/misc/metadata.xconf

Author: andreas
Date: Thu Jul 20 01:12:17 2006
New Revision: 423816

URL: http://svn.apache.org/viewvc?rev=423816&view=rev
Log:
Added DC terms + elements to meta data config

Modified:
    lenya/trunk/src/webapp/lenya/config/cocoon-xconf/misc/metadata.xconf

Modified: lenya/trunk/src/webapp/lenya/config/cocoon-xconf/misc/metadata.xconf
URL: http://svn.apache.org/viewvc/lenya/trunk/src/webapp/lenya/config/cocoon-xconf/misc/metadata.xconf?rev=423816&r1=423815&r2=423816&view=diff
==============================================================================
--- lenya/trunk/src/webapp/lenya/config/cocoon-xconf/misc/metadata.xconf (original)
+++ lenya/trunk/src/webapp/lenya/config/cocoon-xconf/misc/metadata.xconf Thu Jul 20 01:12:17 2006
@@ -25,9 +25,59 @@
     <meta-data>
       <component-instance name="http://purl.org/dc/elements/1.1/"
         class="org.apache.lenya.cms.metadata.ConfigurableElementSet">
-        
         <element name="title" multiple="false"/>
-        
+        <element name="creator" multiple="false"/>
+        <element name="subject" multiple="false"/>
+        <element name="description" multiple="false"/>
+        <element name="publisher" multiple="false"/>
+        <element name="contributor" multiple="false"/>
+        <element name="date" multiple="false"/>
+        <element name="type" multiple="false"/>
+        <element name="format" multiple="false"/>
+        <element name="identifier" multiple="false"/>
+        <element name="source" multiple="false"/>
+        <element name="language" multiple="false"/>
+        <element name="relation" multiple="false"/>
+        <element name="coverage" multiple="false"/>
+        <element name="rights" multiple="false"/>
+      </component-instance>
+      <component-instance name="http://purl.org/dc/terms/"
+        class="org.apache.lenya.cms.metadata.ConfigurableElementSet">
+        <element name="abstract" multiple="false"/>
+        <element name="accessRights" multiple="false"/>
+        <element name="alternative" multiple="false"/>
+        <element name="audience" multiple="false"/>
+        <element name="available" multiple="false"/>
+        <element name="bibliographicCitation" multiple="false"/>
+        <element name="conformsTo" multiple="false"/>
+        <element name="created" multiple="false"/>
+        <element name="dateAccepted" multiple="false"/>
+        <element name="dateCopyrighted" multiple="false"/>
+        <element name="dateSubmitted" multiple="false"/>
+        <element name="educationLevel" multiple="false"/>
+        <element name="extent" multiple="false"/>
+        <element name="hasFormat" multiple="false"/>
+        <element name="hasPart" multiple="false"/>
+        <element name="hasVersion" multiple="false"/>
+        <element name="isFormatOf" multiple="false"/>
+        <element name="isPartOf" multiple="false"/>
+        <element name="isReferencedBy" multiple="false"/>
+        <element name="isReplacedBy" multiple="false"/>
+        <element name="isRequiredBy" multiple="false"/>
+        <element name="issued" multiple="false"/>
+        <element name="isVersionOf" multiple="false"/>
+        <element name="license" multiple="false"/>
+        <element name="mediator" multiple="false"/>
+        <element name="medium" multiple="false"/>
+        <element name="modified" multiple="false"/>
+        <element name="references" multiple="false"/>
+        <element name="replaces" multiple="false"/>
+        <element name="requires" multiple="false"/>
+        <element name="rightsHolder" multiple="false"/>
+        <element name="spatial" multiple="false"/>
+        <element name="tableOfContents" multiple="false"/>
+        <element name="temporal" multiple="false"/>
+        <element name="valid" multiple="false"/>
       </component-instance>
     </meta-data>
     



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@lenya.apache.org
For additional commands, e-mail: commits-help@lenya.apache.org


Re: dublin core revisited

Posted by Jörn Nettingsmeier <po...@uni-duisburg.de>.
Jörn Nettingsmeier wrote:
> in it's implementation guideline, dublin core does not define fixed
     ^^^^^^
yuck. i did it again.
"the apostrophe is there to warn the reader that an 's' is coming up."


-- 
"Open source takes the bullshit out of software."
	- Charles Ferguson on TechnologyReview.com

--
Jörn Nettingsmeier, EDV-Administrator
Institut für Politikwissenschaft
Universität Duisburg-Essen, Standort Duisburg
Mail: pol-admin@uni-due.de, Telefon: 0203/379-2736

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org


Re: dublin core revisited

Posted by Andreas Hartmann <an...@apache.org>.
Comiotto Thomas wrote:
> Hi Jörn, Andi
> 
> Might be OT, anyway..
> 
> 
> Am 10.08.2006 um 16:12 schrieb Jörn Nettingsmeier:
>>
>> for a good real-world implementation, check out the dspace project,
>> notably http://www.dspace.org/technology/metadata.html. i'd like to see
>> a similar scheme in lenya.
> 
> All I'd like to see with regard to the Lenya metadata handling is a 
> lightweight abstraction layer providing for a flexible binding of keys 
> that must be considered mandatory for the core usecases to function to 
> whatever datatypes (n-dimensional, take rdf tripples for instance) an 
> integrator might choose to describe her resources - on publication 
> level, sourcetype level and even on resource level.
> 
> With regard to managing metadata; I'd consider metadata being just 
> another sourcetype. GUI bindings/editing of that data should be schema 
> driven as "regular" xml resources are too. I don't think a refinement 
> approach of otherwise hardwired 1-dimensional datatypes will lead to a 
> decent solution.

That's a very interesting idea, and shouldn't be too hard to implement.
Using resource types for meta data could even reduce the complexity
of the code base, since the validation functionality can be reused.

Thanks for the input!

-- Andreas

-- 
Andreas Hartmann
Wyona Inc.  -   Open Source Content Management   -   Apache Lenya
http://www.wyona.com                      http://lenya.apache.org
andreas.hartmann@wyona.com                     andreas@apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org


Re: dublin core revisited

Posted by Comiotto Thomas <th...@unicom.unizh.ch>.
Hi Jörn, Andi

Might be OT, anyway..


Am 10.08.2006 um 16:12 schrieb Jörn Nettingsmeier:
>
> for a good real-world implementation, check out the dspace project,
> notably http://www.dspace.org/technology/metadata.html. i'd like to see
> a similar scheme in lenya.

All I'd like to see with regard to the Lenya metadata handling is a 
lightweight abstraction layer providing for a flexible binding of keys 
that must be considered mandatory for the core usecases to function to 
whatever datatypes (n-dimensional, take rdf tripples for instance) an 
integrator might choose to describe her resources - on publication 
level, sourcetype level and even on resource level.

With regard to managing metadata; I'd consider metadata being just 
another sourcetype. GUI bindings/editing of that data should be schema 
driven as "regular" xml resources are too. I don't think a refinement 
approach of otherwise hardwired 1-dimensional datatypes will lead to a 
decent solution.

Thanks for keeping up the good work!

--
Best regards
Thomas



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org


dublin core revisited

Posted by Jörn Nettingsmeier <po...@uni-duisburg.de>.
Jörn Nettingsmeier wrote:
> Andreas Hartmann wrote:
>> Doug Chestnut wrote:
>>> Hi Andreas,
>>> My understanding of the dublin core terms (of type element-refinement)
>>> is that they are qualifiers which "enhance the precision" of the
>>> elements.
>>> http://dublincore.org/resources/faq/#dumbdown
>>>
>>> It seems that we are treating the terms as an extended set of
>>> elements.    Perhaps the interface just needs to be changed so that
>>> the term can be selected on the dc element which it refines.
>>>
>>> Perhaps the conf below could reference terms like:
>>>         <element name="abstract" refines="dc:description"/>
>>>         <element name="accessRights" refines="dc:rights"/>
>>>         <element name="alternative" refines="dc:title"/>

i just re-read the dublincore.org site, and i realized that the dc core
recommendations (which few people seem to use as-is) are not especially
clear or even useful in this regard. for a good definition of
two-dimensional qualified metadata, refer to the library working groups'
application profile at
http://dublincore.org/documents/2002/04/16/library-application-profile/

in it's implementation guideline, dublin core does not define fixed
relations between elements and refinements, i.e. you can't say which
element you're refining. that is mind-bogglingly stupid and should be
ignored. probably design-by-committee disease.

for a good real-world implementation, check out the dspace project,
notably http://www.dspace.org/technology/metadata.html. i'd like to see
a similar scheme in lenya.


-- 
"Open source takes the bullshit out of software."
	- Charles Ferguson on TechnologyReview.com

--
Jörn Nettingsmeier, EDV-Administrator
Institut für Politikwissenschaft
Universität Duisburg-Essen, Standort Duisburg
Mail: pol-admin@uni-due.de, Telefon: 0203/379-2736


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org


Re: svn commit: r423816 - /lenya/trunk/src/webapp/lenya/config/cocoon-xconf/misc/metadata.xconf

Posted by Jörn Nettingsmeier <po...@uni-duisburg.de>.
Andreas Hartmann wrote:
> Doug Chestnut wrote:
>> Hi Andreas,
>> My understanding of the dublin core terms (of type element-refinement)
>> is that they are qualifiers which "enhance the precision" of the
>> elements.
>> http://dublincore.org/resources/faq/#dumbdown
>>
>> It seems that we are treating the terms as an extended set of
>> elements.    Perhaps the interface just needs to be changed so that
>> the term can be selected on the dc element which it refines.
>>
>> Perhaps the conf below could reference terms like:
>>         <element name="abstract" refines="dc:description"/>
>>         <element name="accessRights" refines="dc:rights"/>
>>         <element name="alternative" refines="dc:title"/>
>> [...]
>>
>> WDYT?
> 
> Yes, that sounds reasonable. Can this concept be generalized for our
> meta data handling?
> 
> A little comment on the syntax:
> refines="dc:description" depends on a "dc" prefix, which would have to
> be globally unique and declared somewhere. I guess it is easier to use
> the namespace URI instead, e.g.

in dc, all elements can have a cardinality > 1, which is something that
is not currently covered by lenya either.

if lenya were able to handle multiple occurrences of the same element
name (which it should imho, since there may be co-authors etc), we could
get rid of the "refines" stuff, and just say
<element name="dc:contributor" qualifier="editor".../>
<element name="dc:contributor" qualifier="author".../>
...
mapping each qualified variant of a dc element to a lenya metadata
element of cardinality one is only half the way...

all in all, i'd love to see the expressive power of full xml for the
lenya metadata, although i can see that it's awkward to implement. just
dreaming...


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org


Re: svn commit: r423816 - /lenya/trunk/src/webapp/lenya/config/cocoon-xconf/misc/metadata.xconf

Posted by Andreas Hartmann <an...@apache.org>.
Doug Chestnut wrote:
> Hi Andreas,
> My understanding of the dublin core terms (of type element-refinement) 
> is that they are qualifiers which "enhance the precision" of the elements.
> http://dublincore.org/resources/faq/#dumbdown
> 
> It seems that we are treating the terms as an extended set of elements. 
>    Perhaps the interface just needs to be changed so that the term can 
> be selected on the dc element which it refines.
> 
> Perhaps the conf below could reference terms like:
>         <element name="abstract" refines="dc:description"/>
>         <element name="accessRights" refines="dc:rights"/>
>         <element name="alternative" refines="dc:title"/>
> [...]
> 
> WDYT?

Yes, that sounds reasonable. Can this concept be generalized for our
meta data handling?

A little comment on the syntax:
refines="dc:description" depends on a "dc" prefix, which would have to
be globally unique and declared somewhere. I guess it is easier to use
the namespace URI instead, e.g.

   <element name="abstract"
     refinesElement="description"
     refinesNamespace="http://purl.org/dc/elements/1.1/"/>

Or if we can assume that the whole element set refines a certain
element set:

   <component-instance
     name="http://purl.org/dc/elements/1.1/"
     refines="http://purl.org/dc/elements/1.1/"
     class="org.apache.lenya.cms.metadata.ConfigurableElementSet">

     <element name="abstract" refines="description"/>
     ...
   </component-instance>

-- Andreas

> 
> --Doug
> 
> andreas@apache.org wrote:
>> Author: andreas
>> Date: Thu Jul 20 01:12:17 2006
>> New Revision: 423816
>>
>> URL: http://svn.apache.org/viewvc?rev=423816&view=rev
>> Log:
>> Added DC terms + elements to meta data config
>>
>> Modified:
>>     lenya/trunk/src/webapp/lenya/config/cocoon-xconf/misc/metadata.xconf
>>
>> Modified: 
>> lenya/trunk/src/webapp/lenya/config/cocoon-xconf/misc/metadata.xconf
>> URL: 
>> http://svn.apache.org/viewvc/lenya/trunk/src/webapp/lenya/config/cocoon-xconf/misc/metadata.xconf?rev=423816&r1=423815&r2=423816&view=diff 
>>
>> ============================================================================== 
>>
>> --- 
>> lenya/trunk/src/webapp/lenya/config/cocoon-xconf/misc/metadata.xconf 
>> (original)
>> +++ 
>> lenya/trunk/src/webapp/lenya/config/cocoon-xconf/misc/metadata.xconf 
>> Thu Jul 20 01:12:17 2006
>> @@ -25,9 +25,59 @@
>>      <meta-data>
>>        <component-instance name="http://purl.org/dc/elements/1.1/"
>>          class="org.apache.lenya.cms.metadata.ConfigurableElementSet">
>> -                 <element name="title" multiple="false"/>
>> -        +        <element name="creator" multiple="false"/>
>> +        <element name="subject" multiple="false"/>
>> +        <element name="description" multiple="false"/>
>> +        <element name="publisher" multiple="false"/>
>> +        <element name="contributor" multiple="false"/>
>> +        <element name="date" multiple="false"/>
>> +        <element name="type" multiple="false"/>
>> +        <element name="format" multiple="false"/>
>> +        <element name="identifier" multiple="false"/>
>> +        <element name="source" multiple="false"/>
>> +        <element name="language" multiple="false"/>
>> +        <element name="relation" multiple="false"/>
>> +        <element name="coverage" multiple="false"/>
>> +        <element name="rights" multiple="false"/>
>> +      </component-instance>
>> +      <component-instance name="http://purl.org/dc/terms/"
>> +        class="org.apache.lenya.cms.metadata.ConfigurableElementSet">
>> +        <element name="abstract" multiple="false"/>
>> +        <element name="accessRights" multiple="false"/>
>> +        <element name="alternative" multiple="false"/>
>> +        <element name="audience" multiple="false"/>
>> +        <element name="available" multiple="false"/>
>> +        <element name="bibliographicCitation" multiple="false"/>
>> +        <element name="conformsTo" multiple="false"/>
>> +        <element name="created" multiple="false"/>
>> +        <element name="dateAccepted" multiple="false"/>
>> +        <element name="dateCopyrighted" multiple="false"/>
>> +        <element name="dateSubmitted" multiple="false"/>
>> +        <element name="educationLevel" multiple="false"/>
>> +        <element name="extent" multiple="false"/>
>> +        <element name="hasFormat" multiple="false"/>
>> +        <element name="hasPart" multiple="false"/>
>> +        <element name="hasVersion" multiple="false"/>
>> +        <element name="isFormatOf" multiple="false"/>
>> +        <element name="isPartOf" multiple="false"/>
>> +        <element name="isReferencedBy" multiple="false"/>
>> +        <element name="isReplacedBy" multiple="false"/>
>> +        <element name="isRequiredBy" multiple="false"/>
>> +        <element name="issued" multiple="false"/>
>> +        <element name="isVersionOf" multiple="false"/>
>> +        <element name="license" multiple="false"/>
>> +        <element name="mediator" multiple="false"/>
>> +        <element name="medium" multiple="false"/>
>> +        <element name="modified" multiple="false"/>
>> +        <element name="references" multiple="false"/>
>> +        <element name="replaces" multiple="false"/>
>> +        <element name="requires" multiple="false"/>
>> +        <element name="rightsHolder" multiple="false"/>
>> +        <element name="spatial" multiple="false"/>
>> +        <element name="tableOfContents" multiple="false"/>
>> +        <element name="temporal" multiple="false"/>
>> +        <element name="valid" multiple="false"/>
>>        </component-instance>
>>      </meta-data>
>>     
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: commits-unsubscribe@lenya.apache.org
>> For additional commands, e-mail: commits-help@lenya.apache.org
>>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org


Re: svn commit: r423816 - /lenya/trunk/src/webapp/lenya/config/cocoon-xconf/misc/metadata.xconf

Posted by Jörn Nettingsmeier <po...@uni-duisburg.de>.
Doug Chestnut wrote:
> Hi Andreas,
> My understanding of the dublin core terms (of type element-refinement)
> is that they are qualifiers which "enhance the precision" of the elements.
> http://dublincore.org/resources/faq/#dumbdown
> 
> It seems that we are treating the terms as an extended set of elements.
>    Perhaps the interface just needs to be changed so that the term can
> be selected on the dc element which it refines.
> 
> Perhaps the conf below could reference terms like:
>         <element name="abstract" refines="dc:description"/>
>         <element name="accessRights" refines="dc:rights"/>
>         <element name="alternative" refines="dc:title"/>
> [...]
> 
> WDYT?

definitely.
i had meant to comment on this earlier but forgot. i think the
"qualifying" is the one key feature of dublin core, and reducing it to a
one-dimensional set is contrary to dc compliance.

the very nice thing about those qualifiers is that if you don't
understand the details, you still get the big picture.
i.e. you (or your code) may not know what a "thesis advisor" is, but at
least you know that it's some sort of dc:contributor. very neat.

we should be able to represent this two-tier structure in lenya metadata.



btw: a hearty "whoooohooo" to the committers! svn is running hot :-D
it's great to see such a level of activity - i've been chasing the trunk
for a week now, and still no hope of catching up :-D





---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org


Re: svn commit: r423816 - /lenya/trunk/src/webapp/lenya/config/cocoon-xconf/misc/metadata.xconf

Posted by Doug Chestnut <dh...@virginia.edu>.
Hi Andreas,
My understanding of the dublin core terms (of type element-refinement) 
is that they are qualifiers which "enhance the precision" of the elements.
http://dublincore.org/resources/faq/#dumbdown

It seems that we are treating the terms as an extended set of elements. 
    Perhaps the interface just needs to be changed so that the term can 
be selected on the dc element which it refines.

Perhaps the conf below could reference terms like:
         <element name="abstract" refines="dc:description"/>
         <element name="accessRights" refines="dc:rights"/>
         <element name="alternative" refines="dc:title"/>
[...]

WDYT?

--Doug

andreas@apache.org wrote:
> Author: andreas
> Date: Thu Jul 20 01:12:17 2006
> New Revision: 423816
> 
> URL: http://svn.apache.org/viewvc?rev=423816&view=rev
> Log:
> Added DC terms + elements to meta data config
> 
> Modified:
>     lenya/trunk/src/webapp/lenya/config/cocoon-xconf/misc/metadata.xconf
> 
> Modified: lenya/trunk/src/webapp/lenya/config/cocoon-xconf/misc/metadata.xconf
> URL: http://svn.apache.org/viewvc/lenya/trunk/src/webapp/lenya/config/cocoon-xconf/misc/metadata.xconf?rev=423816&r1=423815&r2=423816&view=diff
> ==============================================================================
> --- lenya/trunk/src/webapp/lenya/config/cocoon-xconf/misc/metadata.xconf (original)
> +++ lenya/trunk/src/webapp/lenya/config/cocoon-xconf/misc/metadata.xconf Thu Jul 20 01:12:17 2006
> @@ -25,9 +25,59 @@
>      <meta-data>
>        <component-instance name="http://purl.org/dc/elements/1.1/"
>          class="org.apache.lenya.cms.metadata.ConfigurableElementSet">
> -        
>          <element name="title" multiple="false"/>
> -        
> +        <element name="creator" multiple="false"/>
> +        <element name="subject" multiple="false"/>
> +        <element name="description" multiple="false"/>
> +        <element name="publisher" multiple="false"/>
> +        <element name="contributor" multiple="false"/>
> +        <element name="date" multiple="false"/>
> +        <element name="type" multiple="false"/>
> +        <element name="format" multiple="false"/>
> +        <element name="identifier" multiple="false"/>
> +        <element name="source" multiple="false"/>
> +        <element name="language" multiple="false"/>
> +        <element name="relation" multiple="false"/>
> +        <element name="coverage" multiple="false"/>
> +        <element name="rights" multiple="false"/>
> +      </component-instance>
> +      <component-instance name="http://purl.org/dc/terms/"
> +        class="org.apache.lenya.cms.metadata.ConfigurableElementSet">
> +        <element name="abstract" multiple="false"/>
> +        <element name="accessRights" multiple="false"/>
> +        <element name="alternative" multiple="false"/>
> +        <element name="audience" multiple="false"/>
> +        <element name="available" multiple="false"/>
> +        <element name="bibliographicCitation" multiple="false"/>
> +        <element name="conformsTo" multiple="false"/>
> +        <element name="created" multiple="false"/>
> +        <element name="dateAccepted" multiple="false"/>
> +        <element name="dateCopyrighted" multiple="false"/>
> +        <element name="dateSubmitted" multiple="false"/>
> +        <element name="educationLevel" multiple="false"/>
> +        <element name="extent" multiple="false"/>
> +        <element name="hasFormat" multiple="false"/>
> +        <element name="hasPart" multiple="false"/>
> +        <element name="hasVersion" multiple="false"/>
> +        <element name="isFormatOf" multiple="false"/>
> +        <element name="isPartOf" multiple="false"/>
> +        <element name="isReferencedBy" multiple="false"/>
> +        <element name="isReplacedBy" multiple="false"/>
> +        <element name="isRequiredBy" multiple="false"/>
> +        <element name="issued" multiple="false"/>
> +        <element name="isVersionOf" multiple="false"/>
> +        <element name="license" multiple="false"/>
> +        <element name="mediator" multiple="false"/>
> +        <element name="medium" multiple="false"/>
> +        <element name="modified" multiple="false"/>
> +        <element name="references" multiple="false"/>
> +        <element name="replaces" multiple="false"/>
> +        <element name="requires" multiple="false"/>
> +        <element name="rightsHolder" multiple="false"/>
> +        <element name="spatial" multiple="false"/>
> +        <element name="tableOfContents" multiple="false"/>
> +        <element name="temporal" multiple="false"/>
> +        <element name="valid" multiple="false"/>
>        </component-instance>
>      </meta-data>
>      
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commits-unsubscribe@lenya.apache.org
> For additional commands, e-mail: commits-help@lenya.apache.org
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org