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

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

One thing to bear in mind is that we try to map the metadata from different 
file formats onto the same common metadata keys/properties, so that it's easy 
for people to use Tika in a common way. (We try to avoid them having to know 
about the file format differences if possible)

I'm slightly hesitant to go for something called DC_SUBJECT, as if possible we 
want to avoid the issue of some file formats producing one kind of subject, and 
others a different one, when they both refer to the same sort of thing

However, in this case, we are slightly constrained by the SUBJECT key already 
existing in the old form. Additionally, the aliasing from IPTC to the common 
one does seem to me an OK way to deal with bringing different formats to using 
the same metadata keys, so that could be fine.

It's just a shame that there's not an easy way to turn the existing SUBJECT key 
into a typed property without breaking things... So maybe this is our best bet
                
> 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

        

Reply via email to