You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Nick Burch (JIRA)" <ji...@apache.org> on 2012/05/17 00:39:09 UTC
[jira] [Commented] (TIKA-928) Separation of Tika Core Properties
From Metadata Processing
[ https://issues.apache.org/jira/browse/TIKA-928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13277215#comment-13277215 ]
Nick Burch commented on TIKA-928:
---------------------------------
Thanks, applied (with a few extra JavaDoc bits) in r1339404.
It's good to finally make clear which bits of metadata we try to ensure are consistent across formats, and which ones will be file type specific. That way, external consumers who need format specific details know which ones they are, while general users can be sure that the metadata they're looking at is a consistent one
> Separation of Tika Core Properties From Metadata Processing
> -----------------------------------------------------------
>
> Key: TIKA-928
> URL: https://issues.apache.org/jira/browse/TIKA-928
> Project: Tika
> Issue Type: Improvement
> Components: metadata
> Affects Versions: 1.1
> Reporter: Ray Gauss II
> Attachments: tika-core-properties.diff
>
>
> The Metadata class is a bit overloaded with both processing and core Tika properties defined in the same place.
> Separating the core properties into a TikaCoreProperties class which contains only composite properties which reference other standards like DublinCore will allow the Metadata class to focus on processing and ease the transition from the now deprecated String properties that were directly included in Metadata via the implements clause.
> This will also allow us to cherry pick only the properties we want from a standard as Tika core properties rather than having to include all the properties in a standard's interface, some of which may be more specific to a particular content type than we want.
--
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