[
https://issues.apache.org/jira/browse/TIKA-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113473#comment-13113473
]
Ken Krugler commented on TIKA-728:
----------------------------------
Jukka said (on the list):
{quote}
>From the client perspective the Metadata class should still provide a
simple key-value interface for basic things, just like the Tika facade
hides the more powerful constructs of the Parser and Detector
interfaces under a simplified API. Of course the implementation side
would be more complex...
Until Someone (TM, :-) does that, I'd be very happy to see the simple
property=xxx mapping you described added to HtmlParser. It's obviously
an improvement to the way Tika currently works, and I don't see any
major backwards compatibility issues caused by starting with a simple
solution like that and later on migrating to a more complete RDF-based
metadata model.
{quote}
> Return RDFa meta tags via Metadata
> ----------------------------------
>
> Key: TIKA-728
> URL: https://issues.apache.org/jira/browse/TIKA-728
> Project: Tika
> Issue Type: Improvement
> Reporter: Ken Krugler
> Assignee: Ken Krugler
> Priority: Minor
>
> Open Graph <meta> tags currently get stripped out, and also aren't put into
> the metadata map.
> The reason why is that Open Graph uses RDFa:
> http://stackoverflow.com/questions/2704942/html-validation-error-for-property-attribute/2705090#2705090
> Since <meta property="xxx" content="yyy" /> isn't valid for XHTML 1.0, these
> tags can't be emitted.
> We could take a tag like:
> <meta property="og:url" content="http://www.imdb.com/title/tt0117500/"; />
> and put it into the metadata map as "og:url" =>
> "http://www.imdb.com/title/tt0117500/";
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
