Nanopublications LDF server

Matches in Nanopublications for { ?s ?p "Metadata is harvested by: 1) resolving the GUID (following all redirects) with a Content-Type header specifically searching for some form of structured data. e.g. 'Accept: text/turtle, application/n3, application/rdf+n3, application/turtle, application/x-turtle,text/n3,text/turtle, text/rdf+n3, text/rdf+turtle,application/json+ld, text/xhtml+xml,application/rdf+xml,application/n-triples' 2) resolving any Link 'meta' HTTP Headers (processed independently according to this same process, but not iteratively) 3) parsing the response body either as a hash (for non-linked data) or as a Graph for linked data, or both. 4) All other data is passed to the 'extruct' tool (https://github.com/scrapinghub/extruct) or to the Apache Tika tool (https://tika.apache.org/) for deep exploration 5) Any linked or hash-type data found by those tools are merged with the existing Hash or Graph data To locate the data identifier, hash data is tested for the keys: * codeRepository * mainEntity * primaryTopic * IAO:0000136 (is about) * IAO_0000136 * SIO:000332 (is about) * SIO_000332 * distribution * contains Graph data is tested for the properties: * schema:codeRepository * schema:mainEntity * foaf:primaryTopic * IAO:0000136 (information artifact ontology 'is about') * SIO:000332 (SemanticScience Integrated Ontology 'is about') * schema:distribution * DCAT:distribution (Data Catalogue vocabulary) * ldp:contains (Linked Data Platform) To locate the Metadata's GUID: 1) The values of all Hash keys are compared to the GUID provided to the test (this is not a rigorous test, but the key name cannot be predicted) 2) The Graph metadata is explored for the "objects" of each triple pattern-matching or exact-matching the provided GUID." ?g. }

• Gen2_MI_F3 procedure "Metadata is harvested by: 1) resolving the GUID (following all redirects) with a Content-Type header specifically searching for some form of structured data. e.g. 'Accept: text/turtle, application/n3, application/rdf+n3, application/turtle, application/x-turtle,text/n3,text/turtle, text/rdf+n3, text/rdf+turtle,application/json+ld, text/xhtml+xml,application/rdf+xml,application/n-triples' 2) resolving any Link 'meta' HTTP Headers (processed independently according to this same process, but not iteratively) 3) parsing the response body either as a hash (for non-linked data) or as a Graph for linked data, or both. 4) All other data is passed to the 'extruct' tool (https://github.com/scrapinghub/extruct) or to the Apache Tika tool (https://tika.apache.org/) for deep exploration 5) Any linked or hash-type data found by those tools are merged with the existing Hash or Graph data To locate the data identifier, hash data is tested for the keys: * codeRepository * mainEntity * primaryTopic * IAO:0000136 (is about) * IAO_0000136 * SIO:000332 (is about) * SIO_000332 * distribution * contains Graph data is tested for the properties: * schema:codeRepository * schema:mainEntity * foaf:primaryTopic * IAO:0000136 (information artifact ontology 'is about') * SIO:000332 (SemanticScience Integrated Ontology 'is about') * schema:distribution * DCAT:distribution (Data Catalogue vocabulary) * ldp:contains (Linked Data Platform) To locate the Metadata's GUID: 1) The values of all Hash keys are compared to the GUID provided to the test (this is not a rigorous test, but the key name cannot be predicted) 2) The Graph metadata is explored for the "objects" of each triple pattern-matching or exact-matching the provided GUID." assertion.