Dear Saašha,
Thanks for spotting the malformed ntriples. That's been fixed and passes the tests at librdf.
The JSON is a little more interesting. I tried validating the json with json-p.org, the link you provided, *before* making any changes. It failed for me also. Now, the JSON you see is based on the ntriples, so I started by correcting the ntriples. Once I had the ntriples passing, I tried json-p.org again. And, again, it failed.
I've never used json-p before, so that website was new to me. In the past, I've used http://jsonformatter.curiousconcept.com/. The PREMIS JSON passes using that json validator. For good measure, I also tested the json at http://jsonlint.com/ and it passed validation on JSONLint too.
As for the headers, we'll look into it but, as you noted, not critical.
Regards,
Kevin
--
Kevin Ford
Network Development and MARC Standards Office
Library of Congress
Washington, DC
> -----Original Message-----
> From: PREMIS Implementors Group Forum [mailto:[log in to unmask]] On
> Behalf Of Saašha Metsärantala
> Sent: Friday, June 07, 2013 12:54 PM
> To: [log in to unmask]
> Subject: Re: [PIG] PREMIS OWL ontology and new preservation
> vocabularies available for public review
>
> 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.n
> t 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,
|
