Nanopublications LDF server

Matches in Nanopublications for { ?s <https://w3id.org/kpxl/gen/terms/hasContent> ?o ?g. }

• paragraph hasContent "We aim to kick-start the next revolution in scientific publishing and knowledge sharing. Using our core technology, nanopublications, we are building a global knowledge ecosystem to make humanity's knowledge radically more efficient and effective. Our work is guided by openness and freedom to operate." assertion.
• paragraph hasContent "We aim to kick-start the next revolution in scientific publishing and knowledge sharing. Using our core technology, nanopublications, we are building a global knowledge ecosystem to make humanity's knowledge radically more efficient and effective. Our work is guided by openness and freedom to operate." assertion.
• paragraph hasContent "<a href="https://nanopub.net/">Nanopublications</a> are a format consisting of tiny snippets of information about any topic whatsoever that is encoded in a way that computers can understand and humans can easily create. Nanopublications allow researchers to access the findings of their fields with their relevant contexts as a connected global knowledge graph." assertion.
• paragraph hasContent "<p>Nanopublication SPARQL templates use an extended version of the <a href="https://grlc.io/">grlc</a> syntax.</p>" assertion.
• paragraph hasContent "some testing..." assertion.
• paragraph hasContent "grlc templates use variable names starting with "_" to denote placeholders. Those that end in "_iri" like "?_resource_iri" are IRI placeholder; otherwise they are literal placeholders, like "?_name"." assertion.
• paragraph hasContent "Optional placeholders in grlc, which don't necessarily need to be filled before running the query, start with two underscores instead of just one, e.g. "?__filter_iri" or "?__filtertext"." assertion.
• paragraph hasContent "<p>Nanopublication query templates extend grlc by supporting placeholders that can have more than one value. Those have the suffix of "_multi_iri" (for IRIs) or just "_multi" (for literals). Importantly, they only work if there is at least one occurrence of a "values" statement like "values ?_resource_multi_iri {}", which indicates where the values are filled in. These multi-value placeholders take 1 or more IRIs/literals.</p> <p>This feature can be combined with optional placeholders, starting with two underscores like "?__resource_multi_iri", which can be filled with zero or more IRIs/literals.</p>" assertion.
• paragraph hasContent "<p>This is an ontology of the FAIR Implementation Profiles (FIP) for the FAIR principles. This diagram shows the general structure of this model:</p> <img src="https://peta-pico.github.io/FAIR-nanopubs/fip/sections/fip-overview-diagram.svg" alt="">" assertion.
• paragraph hasContent "What are nanopublications?" assertion.
• paragraph hasContent "How are nanopublications published, retrieved, and queried?" assertion.
• paragraph hasContent "Who is there and who are they? What about bots/agents?" assertion.
• paragraph hasContent "How can we collaborate with nanopublications?" assertion.
• paragraph hasContent "Adding and querying data with templates." assertion.
• paragraph hasContent "Adding data with templates that generate forms." assertion.
• paragraph hasContent "Adding data with templates that generate forms." assertion.
• paragraph hasContent "Querying data with query templates and specific endpoints." assertion.
• paragraph hasContent "<p>Nanopublication SPARQL templates use an extended version of the <a href="https://grlc.io/">grlc</a> syntax.</p>" assertion.
• paragraph hasContent "<p>Nanopublication SPARQL templates use an extended version of the <a href="https://grlc.io/">grlc</a> syntax.</p>" assertion.
• paragraph hasContent "<p>Nanopublication SPARQL templates use an extended version of the <a href="https://grlc.io/">grlc</a> syntax.</p>" assertion.
• paragraph hasContent "Nanopublication query templates use variable names starting with "_" to denote placeholders, following grlc syntax. Those that end in "_iri" like "?_resource_iri" are IRI placeholder; otherwise they are literal placeholders, like "?_name"." assertion.
• paragraph hasContent "Optional placeholders in nanopublication query templates also follow grlc syntax. Such optional placeholders, which don't necessarily need to be filled before running the query, start with two underscores instead of just one, e.g. "?__filter_iri" or "?__filtertext"." assertion.
• paragraph hasContent "Nanopublication query templates extend grlc syntax by supporting placeholders that can have more than one value. Those have the suffix of "_multi_iri" (for IRIs) or just "_multi" (for literals). Importantly, they only work if there is at least one occurrence of a "values" statement like "values ?_resource_multi_iri {}", which indicates where the values are filled in. These multi-value placeholders take 1 or more IRIs/literals." assertion.
• paragraph hasContent "<p>Result columns that hold a URI can have a companion variable with a "_label" suffix to control how the value is displayed. The UI renders the label text as a clickable link to the URI. For example, a "?event" column paired with "?event_label" will display the label linked to the event URI. Without a label companion, the system renders URIs with its default formatting.</p>" assertion.
• paragraph hasContent "<p>Result columns that hold a URI can have a companion variable with a "_label" suffix to control how the value is displayed. The UI renders the label text as a clickable link to the URI. For example, a "?event" column paired with "?event_label" will display the label linked to the event URI. Without a label companion, the system renders URIs with its default formatting.</p>" assertion.
• paragraph hasContent "<p>Result columns that hold a URI can have a companion variable with a "_label" suffix to control how the value is displayed. The UI renders the label text as a clickable link to the URI. For example, a "?event" column paired with "?event_label" will display the label linked to the event URI. Without a label companion, the system renders URIs with its default formatting.</p>" assertion.
• paragraph hasContent "<p>To include a link to the source nanopub in query results, add "?np" and "?np_label" as the last two columns in the SELECT clause, in that order. Use <code>("^" as ?np_label)</code> to display a short clickable caret symbol instead of the full nanopub URI. These should always be placed at the end of the column list.</p>" assertion.
• paragraph hasContent "<p>Result columns (not placeholders) can use the "_multi_iri" and "_multi" suffixes to hold multiple concatenated values produced by <code>group_concat</code>. Use "_multi_iri" when the values are URIs (space-separated) and "_multi" for literals (newline-separated). For example:</p> <p><code>(group_concat(str(?item); separator=" ") as ?items_multi_iri)</code> for IRI lists.</p> <p><code>(group_concat(?text; separator="\n") as ?texts_multi)</code> for literal lists.</p>" assertion.
• paragraph hasContent "<p>When concatenating literal values with a newline separator in <code>group_concat</code>, always escape existing backslashes and newlines in the individual values first: <code>replace(replace(?val, "\\\\" , "\\\\\\\\"), "\\n", "\\\\n")</code>. First escape existing backslashes (\\ → \\\\), then escape existing newlines (newline → \\n). This ensures values containing these characters can be safely split on newlines later.</p>" assertion.
• paragraph hasContent "<p>The "_label" naming convention extends to multi-value columns. For a "?things_multi_iri" column holding space-separated URIs, use "?things_label_multi" as its label companion holding newline-separated labels (with the same escaping as for "_multi" literals). For example, "?authors_multi_iri" (space-separated ORCIDs) paired with "?authors_label_multi" (newline-separated names) displays each author name linked to their URI.</p>" assertion.