Open valentinedwv opened 1 year ago
If you hack the context in the debugger you can get triples. Is there some sanity check that we can make along the way to say, hey, source is the long, triples are this long, seems like something did not convert?
{ "@vocab": "https://schema.org/", "gsqtime": "https://vocabs.gsq.digital/object?uri=http://linked.data.gov.au/def/trs", "time": "http://www.w3.org/2006/time#", "xsd": "https://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html" }
Thoughts on this.
common/jsoldProc needs to have a sanity wrapper function for JLDProc.Normalize()
Often if there is a context issue, it generates an empty string, or the same set of triples for many files The empty string is caught in the calSha function, so unique identifiers are generated using the whole file. But if the same set of triples is generated, then the ID will be the same.
Can we check to see if the number of triples is significantly less that the info in the jsonld file Thoughts on this.
Below normalizes a single triple:
_:c14n0 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <Dataset> .