[ https://issues.apache.org/jira/browse/TIKA-859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Burch resolved TIKA-859. ----------------------------- Resolution: Fixed This has been fixed as part of TIKA-925, using a slightly different technique which maintains backwards compatibility in a cleaner way > DublinCore Metadata Keys Should be Prefixed and Property Objects > ---------------------------------------------------------------- > > Key: TIKA-859 > URL: https://issues.apache.org/jira/browse/TIKA-859 > Project: Tika > Issue Type: Improvement > Components: metadata > Affects Versions: 1.1 > Reporter: Ray Gauss II > Fix For: 1.2 > > Attachments: dublincore-prefixed-and-updated-references-core-patch, > dublincore-prefixed-and-updated-references-parsers-patch > > > To help avoid collisions of key names in interfaces Metadata implements and > allow for more precise definition of DublinCore the keys should be defined as > Property objects with the object name and name attribute containing a prefix > and the existing String keys deprecated, i.e. > {code:title=DublinCore.java} > String SUBJECT = "subject"; > {code} > would become: > {code:title=DublinCore.java} > @Deprecated > String SUBJECT = "subject"; > Property DC_SUBJECT = Property.internalTextBag(PREFIX_DC + PREFIX_DELIMITER + > "subject"); > {code} > Since the use of the simpler key definition is desired eventually, at some > point in the future, perhaps 2.0, these prefixed definitions could themselves > be deprecated and the move made back to the simpler names. -- 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