Thanks for this information. I have not read it, yet, but I noticed that HEADing
does not provide any charset information in the Content-Type HTTP response
header. I am aware that the charset of XML files should be made obvious
within the file itself, but giving this information consistently in the
HTTP header improves interoperability.
http://id.loc.gov/ontologies/premis.rdf validates according to
http://json-p.org/validator.html find errors in premis.nt and premis.json
respectively. I suggest to fix these issues.