tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Burch (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TIKA-842) IPTC Properties Should be Defined Completely and Independently of the Drew Library
Date Fri, 27 Jan 2012 17:04:09 GMT

    [ https://issues.apache.org/jira/browse/TIKA-842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13194916#comment-13194916
] 

Nick Burch commented on TIKA-842:
---------------------------------

Following the confirmation from the IPTC that we can use parts of the specification in the
JavaDocs describing these new properties, I've gone ahead and added the new metadata keys
in r1236754.

As part of this, I've updated the notice and license files with the required attribution and
license

Parts of the IPTC specification incorporate Dublin Core attributes. At the moment, Tika does
have Dublin Core metadata, but as per TIKA-61 these are not prefixed. For now, I've renamed
the IPTC ones temporarily as _DCPROPERTY to avoid a name clash. These can be merged as part
of a solution for TIKA-61. I'd suggest we try to tackle this shortly, before these new keys
are widely used
                
> IPTC Properties Should be Defined Completely and Independently of the Drew Library
> ----------------------------------------------------------------------------------
>
>                 Key: TIKA-842
>                 URL: https://issues.apache.org/jira/browse/TIKA-842
>             Project: Tika
>          Issue Type: Improvement
>          Components: metadata
>    Affects Versions: 1.0
>            Reporter: Ray Gauss II
>             Fix For: 1.1
>
>         Attachments: IPTC-metadata-def-patch.diff
>
>
> All of the IPTC XMP specification should be defined in tika-core and should not be reliant
on the Drew Noakes library as it is incomplete in its support of the standard and the properties
are not defined in proper namespaces or prefixed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message