You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lenya.apache.org by Felix Röthenbacher <fe...@wyona.com> on 2005/09/14 10:52:59 UTC
Metadata
Hi
I had a quick look at the meta data code.
There is the notion of elements and terms? Does
anybody know what these two notions denote?
What about making the meta data implementation
configurable in the publication.xconf? The idea
is that different meta data implementations
may be used. At the moment, the meta data
implementations are restricted to dc and
custom meta data. The lenya internal meta
data will not be configurable as they are needed
by the system.
I've seen that always a namespace
"http://apache.org/cocoon/lenya/page-envelope/1.0"
is used for lenya. Are there any reasons for doing
so? Or is it just by tradition? Are other namespaces
also possible? For example:
http://apache.org/cocoon/lenya/metadata/1.0
- Felix
--
Felix Röthenbacher felix.roethenbacher@wyona.com
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Metadata
Posted by Andreas Hartmann <an...@apache.org>.
Felix Röthenbacher wrote:
> Hi
>
> I had a quick look at the meta data code.
>
> There is the notion of elements and terms? Does
> anybody know what these two notions denote?
>
> What about making the meta data implementation
> configurable in the publication.xconf?
+1, whereas I'd rather do it Avalon style:
cocoon.xconf
<meta-data>
<component-instance name="...">
<configuration uri="..."/>
</component-instance>
...
</meta-data>
This way, meta data components can be added by publications, modules
etc.
ServiceSelector selector = manager.lookup(MetaData.ROLE + "Selector");
MetaData dublinCore = selector.select(DublinCore.HINT);
title = dublinCore.getFirstValue(documentNode, DublinCore.ELEMENT_TITLE);
For custom meta data:
MetaData foo = selector.select("foo");
bar = foo.getFirstValue(documentNode, "bar");
> The idea
> is that different meta data implementations
> may be used. At the moment, the meta data
> implementations are restricted to dc and
> custom meta data. The lenya internal meta
> data will not be configurable as they are needed
> by the system.
>
> I've seen that always a namespace
> "http://apache.org/cocoon/lenya/page-envelope/1.0"
> is used for lenya. Are there any reasons for doing
> so? Or is it just by tradition? Are other namespaces
> also possible? For example:
> http://apache.org/cocoon/lenya/metadata/1.0
+1
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Metadata
Posted by "Gregor J. Rothfuss" <gr...@apache.org>.
Andreas Hartmann wrote:
> 12) We also started moving our web and internal URI naming scheme
> towards reflecting our toplevel status, i.e. http://cocoon.apache.org/
> for our external web presence, and http://apache.org/cocoon/ for
> internal (namespace) URIs.
> </snip>
>
> IMO we should stick to that. It makes sense to me
> (increasingly specific from left to right).
+1
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Metadata
Posted by Andreas Hartmann <an...@apache.org>.
Antonio Gallardo wrote:
> Michael Wechner wrote:
>
[...]
>> since Lenya is a TL project it might make more sense
>>
>> http://apache.org/lenya/metadata/1.0
>
>
> IMHO, then
>
> http://lenya.apache.org/metadata/1.0
Cocoon explicitely decided to use apache.org/cocoon:
<snip
src="http://www.apache.org/foundation/records/minutes/2003/board_minutes_2003_05_21.txt">
12) We also started moving our web and internal URI naming scheme
towards reflecting our toplevel status, i.e. http://cocoon.apache.org/
for our external web presence, and http://apache.org/cocoon/ for
internal (namespace) URIs.
</snip>
IMO we should stick to that. It makes sense to me
(increasingly specific from left to right).
Just my CHF 0.02
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Metadata
Posted by Michael Wechner <mi...@wyona.com>.
Antonio Gallardo wrote:
> Michael Wechner wrote:
>
>> Felix Röthenbacher wrote:
>>
>>> Hi
>>>
>>> I had a quick look at the meta data code.
>>>
>>> There is the notion of elements and terms? Does
>>> anybody know what these two notions denote?
>>>
>>> What about making the meta data implementation
>>> configurable in the publication.xconf? The idea
>>> is that different meta data implementations
>>> may be used. At the moment, the meta data
>>> implementations are restricted to dc and
>>> custom meta data. The lenya internal meta
>>> data will not be configurable as they are needed
>>> by the system.
>>>
>>> I've seen that always a namespace
>>> "http://apache.org/cocoon/lenya/page-envelope/1.0"
>>> is used for lenya. Are there any reasons for doing
>>> so? Or is it just by tradition? Are other namespaces
>>> also possible? For example:
>>> http://apache.org/cocoon/lenya/metadata/1.0
>>
>>
>>
>>
>> since Lenya is a TL project it might make more sense
>>
>> http://apache.org/lenya/metadata/1.0
>
>
> IMHO, then
>
> http://lenya.apache.org/metadata/1.0
whatever ;-) I am not sure if there is a policy at Apache, but it might
make sense to establish one.
Michi
>
> Best Regards,
>
> Antonio Gallardo.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
> For additional commands, e-mail: dev-help@lenya.apache.org
>
>
--
Michael Wechner
Wyona - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
michael.wechner@wyona.com michi@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Metadata
Posted by Antonio Gallardo <ag...@agssa.net>.
Michael Wechner wrote:
> Felix Röthenbacher wrote:
>
>> Hi
>>
>> I had a quick look at the meta data code.
>>
>> There is the notion of elements and terms? Does
>> anybody know what these two notions denote?
>>
>> What about making the meta data implementation
>> configurable in the publication.xconf? The idea
>> is that different meta data implementations
>> may be used. At the moment, the meta data
>> implementations are restricted to dc and
>> custom meta data. The lenya internal meta
>> data will not be configurable as they are needed
>> by the system.
>>
>> I've seen that always a namespace
>> "http://apache.org/cocoon/lenya/page-envelope/1.0"
>> is used for lenya. Are there any reasons for doing
>> so? Or is it just by tradition? Are other namespaces
>> also possible? For example:
>> http://apache.org/cocoon/lenya/metadata/1.0
>
>
>
> since Lenya is a TL project it might make more sense
>
> http://apache.org/lenya/metadata/1.0
IMHO, then
http://lenya.apache.org/metadata/1.0
Best Regards,
Antonio Gallardo.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: Metadata
Posted by Michael Wechner <mi...@wyona.com>.
Felix Röthenbacher wrote:
> Hi
>
> I had a quick look at the meta data code.
>
> There is the notion of elements and terms? Does
> anybody know what these two notions denote?
>
> What about making the meta data implementation
> configurable in the publication.xconf? The idea
> is that different meta data implementations
> may be used. At the moment, the meta data
> implementations are restricted to dc and
> custom meta data. The lenya internal meta
> data will not be configurable as they are needed
> by the system.
>
> I've seen that always a namespace
> "http://apache.org/cocoon/lenya/page-envelope/1.0"
> is used for lenya. Are there any reasons for doing
> so? Or is it just by tradition? Are other namespaces
> also possible? For example:
> http://apache.org/cocoon/lenya/metadata/1.0
since Lenya is a TL project it might make more sense
http://apache.org/lenya/metadata/1.0
Michi
>
>
> - Felix
>
--
Michael Wechner
Wyona - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
michael.wechner@wyona.com michi@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org