This is a follow-on for #22 . For that issue, I just did the bare minimum. But it would be nice to convert all the data from that resource into compatible RDF, and dump it into the output.
That way, each RDF representation for an article would be more hyperlinked, providing a means to discover other expressions of a given work.
I think it would make sense to provide an XQuery module that converts the idconverter output into RDF independent of any JATS document. That is, just a thin wrapper around that API.
This is a follow-on for #22 . For that issue, I just did the bare minimum. But it would be nice to convert all the data from that resource into compatible RDF, and dump it into the output.
That way, each RDF representation for an article would be more hyperlinked, providing a means to discover other expressions of a given work. I think it would make sense to provide an XQuery module that converts the idconverter output into RDF independent of any JATS document. That is, just a thin wrapper around that API.