Hello! Thanks for this information. I have not read it, yet, but I noticed that HEADing http://id.loc.gov/ontologies/premis.rdf http://id.loc.gov/ontologies/premis.nt http://id.loc.gov/ontologies/premis.json 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://www.w3.org/RDF/Validator/ but librdf.org/ntriples?uri=http%3A%2F%2Fid.loc.gov%2Fontologies%2Fpremis.nt and http://json-p.org/validator.html find errors in premis.nt and premis.json respectively. I suggest to fix these issues. Regards! SaaĊĦha,