Github user lewismc commented on the pull request:
https://github.com/apache/any23/pull/17#issuecomment-201537723
hi @ansell OK I've added in the correct rule and fix as well as a test to
verify that empty itemscope values are identified and fixed.
Whilst debugging this however the core issue persists. Reasoning for this
is that ```RDFa11Extractor extends BaseRDFExtractor``` which inherits the
[parser function inputstream
parameter](https://github.com/apache/any23/blob/63ba2fc82966cc056a2e475af849154d0dfdcf93/core/src/main/java/org/apache/any23/extractor/rdf/BaseRDFExtractor.java#L105).
This input stream is not the 'fixed' steam but the raw document.
The only way I can think around this is for us to
* refactor the
[RDFa1.1Extractor](https://github.com/apache/any23/blob/master/core/src/main/java/org/apache/any23/extractor/rdfa/RDFa11Extractor.java)
such that it extends
[TagSoupDomExtractor](https://github.com/apache/any23/blob/63ba2fc82966cc056a2e475af849154d0dfdcf93/api/src/main/java/org/apache/any23/extractor/Extractor.java#L60)
as oppose to (eventually) the
[ContentExtractor](https://github.com/apache/any23/blob/63ba2fc82966cc056a2e475af849154d0dfdcf93/api/src/main/java/org/apache/any23/extractor/Extractor.java#L44),
or
* undertake a mass refactoring which essentially removes the
[ContentExtractor](https://github.com/apache/any23/blob/63ba2fc82966cc056a2e475af849154d0dfdcf93/api/src/main/java/org/apache/any23/extractor/Extractor.java#L44)
altogether... this would provide us with a much more flexible and adaptable
extraction framework IMHO.
What do you think?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
