and()function is straightforward and is often more useful for clarity:
and()is implicit, is more convenient in many situations.
and()functional style as this clarifies which functions are sub-clauses of other functions.
.in the chain, and not to any functions further up the chain. If used improperly with clauses that take sub-clauses, it will produce improperly specified queries, especially with negation (
not) and optional functions (
json()function translates any WOQL query to its JSON-LD format, and JSON-LD to its WOQL.js equivalent - a
json_ld) argument, WOQL.js (
wjs) will generate the equivalent
WOQLQuery()object. If an argument is not provided, WOQL.js will return the JSON-LD equivalent of the
from. These functions are used for specifying the graphs against which operations such as queries are carried out.
"http://obscure.w3c.url/with/embedded/dates#type"is shortened to
"@schema:X"and ensure expressions always resolve to valid IRIs in all databases.
"@base"prefix for instance-data IRIs.
"@schema"prefix for schema IRIs.
"@base"applies to woql:subject (first argument to triple) where instance data IRIs are normally required.
"@schema"applies to woql:predicate and other arguments (
type) where schema elements are normally required.