You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lenya.apache.org by Andreas Hartmann <an...@apache.org> on 2007/01/19 13:49:57 UTC
[1.4] contentType meta data
Hi Lenya devs,
is the "contentType" meta data of a document used somewhere?
Which information is it supposed to hold?
I guess we should declare which content types should be
supported. Or is this up to the resource type?
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: [1.4] contentType meta data
Posted by Andreas Hartmann <an...@apache.org>.
Doug Chestnut schrieb:
> Hmm,
> Don't know what it is used for but a search resulted in 106 matches in
> my src directory.
>
> /**
> * The name of the content type attribute. Any content managed by
> Lenya has
> * a type; this information can be used e.g. to provide an appropriate
> * management interface.
> */
>
> I will look a little further to see if this rings a bell
Thanks a lot - it's not really important, but I wondered if it
is really evaluated somewhere because DocumentImpl.METADATA_CONTENT_TYPE
is used only for setting the element value.
-- Andreas
>
> Andreas Hartmann wrote:
>> Hi Lenya devs,
>>
>> is the "contentType" meta data of a document used somewhere?
>>
>> Which information is it supposed to hold?
>> I guess we should declare which content types should be
>> supported. Or is this up to the resource type?
>>
>> -- Andreas
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
>> For additional commands, e-mail: dev-help@lenya.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: [1.4] contentType meta data
Posted by Doug Chestnut <dh...@virginia.edu>.
Andreas Hartmann wrote:
> Doug Chestnut schrieb:
>
>> I don't see where it is used. Oddly enough a pdf resource shows up with:
>> <element key="mimeType">
>> <value>application/pdf</value>
>> </element>
>> <element key="resourceType">
>> <value>resource</value>
>> </element>
>> <element key="contentType">
>> <value>xml</value>
>> </element>
>>
>>
>> contentType is the least valuable, it seems that resourceType has
>> replaced contentType (didn't the name change a while ago? Does 1.2.x
>> have a resourceType?).
>>
>
> In 1.2 it was called "document type".
> A resource type could hold different "types of content", depending
> on the granularity of this term - are different image formats different
> "content types"?
>
> IMO we should either abandon the generic contentType element, or we
> should declare a set of options, e.g. xml/text/binary. But I have to
> admit that I doubt the usefulness of this concept. IMO the combination
> of resource type and mime type is sufficient.
>
I don't see the usefulness, here's my +1 to dump it
--Doug
> -- Andreas
>
>
>
>> --Doug
>>
>> Doug Chestnut wrote:
>>
>>> Hmm,
>>> Don't know what it is used for but a search resulted in 106 matches in
>>> my src directory.
>>>
>>> /**
>>> * The name of the content type attribute. Any content managed by
>>> Lenya has
>>> * a type; this information can be used e.g. to provide an
>>> appropriate
>>> * management interface.
>>> */
>>>
>>> I will look a little further to see if this rings a bell
>>>
>>> Andreas Hartmann wrote:
>>>
>>>> Hi Lenya devs,
>>>>
>>>> is the "contentType" meta data of a document used somewhere?
>>>>
>>>> Which information is it supposed to hold?
>>>> I guess we should declare which content types should be
>>>> supported. Or is this up to the resource type?
>>>>
>>>> -- Andreas
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
>>>> For additional commands, e-mail: dev-help@lenya.apache.org
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
>>> For additional commands, e-mail: dev-help@lenya.apache.org
>>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
> For additional commands, e-mail: dev-help@lenya.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: [1.4] contentType meta data
Posted by Joern Nettingsmeier <ne...@folkwang-hochschule.de>.
Andreas Hartmann wrote:
> Doug Chestnut schrieb:
>> I don't see where it is used. Oddly enough a pdf resource shows up with:
>> <element key="mimeType">
>> <value>application/pdf</value>
>> </element>
>> <element key="resourceType">
>> <value>resource</value>
>> </element>
>> <element key="contentType">
>> <value>xml</value>
>> </element>
>>
>>
>> contentType is the least valuable, it seems that resourceType has
>> replaced contentType (didn't the name change a while ago? Does 1.2.x
>> have a resourceType?).
>
> In 1.2 it was called "document type".
> A resource type could hold different "types of content", depending
> on the granularity of this term - are different image formats different
> "content types"?
>
> IMO we should either abandon the generic contentType element, or we
> should declare a set of options, e.g. xml/text/binary. But I have to
> admit that I doubt the usefulness of this concept. IMO the combination
> of resource type and mime type is sufficient.
i agree.
--
jörn nettingsmeier
home://germany/45128 essen/lortzingstr. 11/
http://spunk.dnsalias.org
phone://+49/201/491621
if you are a free (as in "free speech") software developer
and you happen to be travelling near my home, drop me a line
and come round for a free (as in "free beer") beer. :-D
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: [1.4] contentType meta data
Posted by Thorsten Scherler <th...@apache.org>.
On Fri, 2007-01-19 at 16:59 +0100, Andreas Hartmann wrote:
> Doug Chestnut schrieb:
> > I don't see where it is used. Oddly enough a pdf resource shows up with:
> > <element key="mimeType">
> > <value>application/pdf</value>
> > </element>
> > <element key="resourceType">
> > <value>resource</value>
> > </element>
> > <element key="contentType">
> > <value>xml</value>
> > </element>
> >
> >
> > contentType is the least valuable, it seems that resourceType has
> > replaced contentType (didn't the name change a while ago? Does 1.2.x
> > have a resourceType?).
>
> In 1.2 it was called "document type".
> A resource type could hold different "types of content", depending
> on the granularity of this term - are different image formats different
> "content types"?
>
> IMO we should either abandon the generic contentType element, or we
> should declare a set of options, e.g. xml/text/binary. But I have to
> admit that I doubt the usefulness of this concept. IMO the combination
> of resource type and mime type is sufficient.
+1
salu2
--
thorsten
"Together we stand, divided we fall!"
Hey you (Pink Floyd)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: [1.4] contentType meta data
Posted by Andreas Hartmann <an...@apache.org>.
Doug Chestnut schrieb:
> I don't see where it is used. Oddly enough a pdf resource shows up with:
> <element key="mimeType">
> <value>application/pdf</value>
> </element>
> <element key="resourceType">
> <value>resource</value>
> </element>
> <element key="contentType">
> <value>xml</value>
> </element>
>
>
> contentType is the least valuable, it seems that resourceType has
> replaced contentType (didn't the name change a while ago? Does 1.2.x
> have a resourceType?).
In 1.2 it was called "document type".
A resource type could hold different "types of content", depending
on the granularity of this term - are different image formats different
"content types"?
IMO we should either abandon the generic contentType element, or we
should declare a set of options, e.g. xml/text/binary. But I have to
admit that I doubt the usefulness of this concept. IMO the combination
of resource type and mime type is sufficient.
-- Andreas
>
> --Doug
>
> Doug Chestnut wrote:
>> Hmm,
>> Don't know what it is used for but a search resulted in 106 matches in
>> my src directory.
>>
>> /**
>> * The name of the content type attribute. Any content managed by
>> Lenya has
>> * a type; this information can be used e.g. to provide an
>> appropriate
>> * management interface.
>> */
>>
>> I will look a little further to see if this rings a bell
>>
>> Andreas Hartmann wrote:
>>> Hi Lenya devs,
>>>
>>> is the "contentType" meta data of a document used somewhere?
>>>
>>> Which information is it supposed to hold?
>>> I guess we should declare which content types should be
>>> supported. Or is this up to the resource type?
>>>
>>> -- Andreas
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
>>> For additional commands, e-mail: dev-help@lenya.apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
>> For additional commands, e-mail: dev-help@lenya.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: [1.4] contentType meta data
Posted by Doug Chestnut <dh...@virginia.edu>.
I don't see where it is used. Oddly enough a pdf resource shows up with:
<element key="mimeType">
<value>application/pdf</value>
</element>
<element key="resourceType">
<value>resource</value>
</element>
<element key="contentType">
<value>xml</value>
</element>
contentType is the least valuable, it seems that resourceType has
replaced contentType (didn't the name change a while ago? Does 1.2.x
have a resourceType?).
--Doug
Doug Chestnut wrote:
> Hmm,
> Don't know what it is used for but a search resulted in 106 matches in
> my src directory.
>
> /**
> * The name of the content type attribute. Any content managed by
> Lenya has
> * a type; this information can be used e.g. to provide an
> appropriate
> * management interface.
> */
>
> I will look a little further to see if this rings a bell
>
> Andreas Hartmann wrote:
>> Hi Lenya devs,
>>
>> is the "contentType" meta data of a document used somewhere?
>>
>> Which information is it supposed to hold?
>> I guess we should declare which content types should be
>> supported. Or is this up to the resource type?
>>
>> -- Andreas
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
>> For additional commands, e-mail: dev-help@lenya.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
> For additional commands, e-mail: dev-help@lenya.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: [1.4] contentType meta data
Posted by Doug Chestnut <dh...@virginia.edu>.
Hmm,
Don't know what it is used for but a search resulted in 106 matches in
my src directory.
/**
* The name of the content type attribute. Any content managed by
Lenya has
* a type; this information can be used e.g. to provide an appropriate
* management interface.
*/
I will look a little further to see if this rings a bell
Andreas Hartmann wrote:
> Hi Lenya devs,
>
> is the "contentType" meta data of a document used somewhere?
>
> Which information is it supposed to hold?
> I guess we should declare which content types should be
> supported. Or is this up to the resource type?
>
> -- Andreas
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
> For additional commands, e-mail: dev-help@lenya.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org