[
https://issues.apache.org/jira/browse/TIKA-928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tyler Palsulich updated TIKA-928:
---------------------------------
Fix Version/s: 2.0
> 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
> Fix For: 2.0
>
> Attachments: tika-core-properties-metadata-refactor-core.diff,
> tika-core-properties-metadata-refactor-parsers.diff, 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 was sent by Atlassian JIRA
(v6.3.4#6332)
