This section describes definitions when mapped to an actual communication method (e.g., HTTPS, file transfer, WebSocket). All content described below is non-normative (examples).
Concrete Specification (Implementation Example)
Prerequisites
Communication protocol: HTTPS (TLS 1.2 or higher)
Message format: JSON-LD
Encoding: UTF-8
Service definition method: SAMM (Semantic Aspect Metamodel)
<base> indicates the connector base URL
Field Definitions
For each field used in this binding, the following information is provided:
Issuing a SPARQL Query
Method
Endpoint
Description
POST
/v1/api/query
Issue a SPARQL query
The request body is as follows.
Parameter
Required
Type
Description
query
✔
string
SPARQL query string
target
-
string
Destination URL. If omitted, issue to the cache
options
-
object
Optional parameters
A sample is as follows.
Resource Metadata
An example of metadata in a drone route domain is shown below.
RDF Patch update notifications from a domain application are received via AMQP.
Delivery Semantics
At-least-once delivery
Arrival order is not guaranteed (ordering is controlled on the distributed catalog side)
Message Format
Field
Description
id
Update sequence identifier (version ID)
prev
ID of the previous patch (used for ordering control)
RDF Patch body
Patch in Apache Jena/Fuseki format
AMQP Headers (Optional)
Header Name
Description
domain_app_id
Domain application identifier (a default value is used if not specified)
RDF Patch Format (Apache Jena/Fuseki)
Element
Description
H
Header (id, prev, etc.)
TX / TC / TA
Transaction boundaries
PA / PD
Add/remove prefixes
A / D
Add/remove triples
Functional Description
For concrete implementations such as Sent by, Resulting state(s), Request, Response, Examples, Error lists, and API-specific field definitions, refer to the API specification.