commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Damjan Jovanovic <damjan....@gmail.com>
Subject Re: [IMAGING] Getting EXIF and IPTC metadata using metadata and image format neutral code
Date Sat, 07 Jul 2012 05:39:11 GMT
Hi Farrukh

Your patch is just an empty file.

Regards
Damjan

On Fri, Jul 6, 2012 at 9:23 PM, Farrukh Najmi
<farrukh@wellfleetsoftware.com> wrote:
> Hi Damjan,
>
> Attached is the patch for implementing the proposed change outlined in
> bullets below.
> Please review and then commit if satisfied or discuss further. Thanks.
>
>
> On 07/06/2012 02:29 PM, Farrukh Najmi wrote:
>>
>>
>> An example of a metadata property that has no IIM mapping defined is Name:
>> Scene Code, XMP property id: Scene (page 15 of 55 in spec)
>>
>>
>> On 07/06/2012 02:25 PM, Farrukh Najmi wrote:
>>>
>>> Hi Damjan,
>>>
>>> Thanks for the +1. As I started on this patch I made some observations in
>>> the IPTC-PhotoMetadata-2008.pdfspec:
>>>
>>>   * Not all metadata properties have an IIM mapping defined. For these
>>>     we will have to invent a type code. I propose we assign codes
>>>     starting at 10000 arbitrarily in such cases
>>>   * Every field does have an XMP property id at present. I am not sure
>>>     if there is any guarantee that future fields will have an XMP
>>>     property id. I think we should continue with XMP property id for
>>>     IptcTypes.name field but if in future versions there is no XMP
>>>     property id then the backup would be to use the Name field from
>>>     the spec
>>>
>>> The only other alternative I can think of for IptcTypes.name field issue
>>> is to use the Name field from the spec which is guaranteed to be present,
>>> will never be translated but has the issue that it has white space in its
>>> content. My preference is to do what is proposed in bullets above.
>>>
>>> Comments? Thanks.
>>>
>>>
>>>
>>
>>
>
>
> --
> Regards,
> Farrukh
>
> Web: http://www.wellfleetsoftware.com
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org

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


Mime
View raw message