Support for client-generated markup

[aurel-l]

The tool might want to be able to support schema injected asynchronously/dynamically on the client (typically as a result of API calls).

Things to look into might be Chrome headless, or PhantomJS. These tools would load the page and execute the JavaScript, and then, when the page is idle for x amount of time, dump the HTML to do the parsing that is already implemented by this tool.

Server-side rendering might be a way to avoid this problem, but I'm not sure we should assume every page implementing schemas.org markup would be willing to do so.

[terazus]

Going to correct #14 and then tackle this issue.
Bioschemas people suggested having a look @ PhantomJS

[aurel-l]

I'd say have a look at Chrome headless instead, see ariya/phantomjs#15105 which indicates that PhantomJS might eventually disappear.

[terazus]

Thanks for that, I'll investigate!