paulmillar commented on issue #1663: URL: https://github.com/apache/jena/issues/1663#issuecomment-1337297517
Hi @namedgraph, I don't think it's guaranteed that the file is read from an online location: it may be downloaded and read from the filesystem. Also, the file may appear with multiple network locations (either as aliases or as the file is copied to a different systems). Therefore, I don't think any absolute URL will identify the file under all circumstances, unless it is some kind of special "place holder" absolute location. All the XMP examples I've seen so far (which, I admit, isn't _that_ many) have used the empty relative URL as the subject IRI in the RDF graph, when identifying the file. Therefore, I think it would be best to keep with that convention. This is achievable with `riot`, without needing any changes, by specifying a suitable `--base` command-line option. The RDF/XML output then only needs to be embedded within a `xmpmeta` element and the resulting XML may be used to generate a new PDF that includes this XMP metadata. These two steps are achievable with existing tools. My thanks to everyone for their comments and help. I think this issue may be closed. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
