Binding

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

• HTTPS communication

• RDF

• JSON-LD

• UTF-8

• SAMM

• dcterms

Field Definitions

For each field used in this binding, the following information is provided:

Discovery Finder and Discovery Service return "service instance" data. A service instance is expressed in JSON-LD format and consists of the following main elements:

• Field Name: Name used within this binding

• Type: Data type (e.g., integer, string)

• Requirement: Usage condition of the field

  • R = Required

  • C = Conditional

  • O = Optional

• Request: Used in request messages

• Response: Used in response messages

• Description: Meaning and usage of the field

Field Name	Type	Mandatory	Request	Response	Description
@context	string	R		✔	Definition of JSON-LD namespaces. Binds prefixes (e.g., dcterms, ods, service) to URIs.
@graph	array	R		✔	Array containing the service instance data.
ods:Connector	object	R		✔	Definition of the Discovery Service or domain application, including provided endpoints and service provider name.
ods:ConnectorEndpoint	object	R		✔	Definition of individual API endpoints held by the Discovery Service or domain application. Specifies the URI of each endpoint.
ods:BaseEndpoint	object	R		✔	Base URL of the Discovery Service or domain application.
ods:SparqlEndpoint	object	R		✔	URL of the SPARQL endpoint of the RDF server provided by the domain application.

Example of Service Instance Returned by a Discovery Service (e.g. Aviation Industry)

{
  "@context": {
    "dcterms": "http://purl.org/dc/terms/",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "api": "https://localhost.com/v1/api#",
    "inst": "http://www.example.com/myservice/instance#",
    "ods": "https://github.com/ODS-DFS-L4/ods/",
    "service": "urn:samm:com.uasl.service:1.1.0#"
  },
  "@graph": [
    {
      "@id": "inst:MyServiceProd",
      "@type": "ods:Connector",
      "dcterms:conformsTo": [
        {
          "@id": "api:UaslServiceWebService"
        },
        {
          "@id": "service:UaslService"
        }
      ],
      "ods:hasBaseEndpoint": {
        "@id": "inst:myServiceBaseEndpoint"
      },
      "ods:hasEndpoint": [
        {
          "@id": "inst:airwayReservationDetailGetEndpoint"
        },
        {
          "@id": "inst:airwayReservationsPostEndpoint"
        }
      ],
      "ods:hasSparqlEndpoint": {
        "@id": "inst:myServiceSparqlEndpoint"
      },
      "service:serviceProviderName": {
        "@type": "http://www.w3.org/2001/XMLSchema#string",
        "@value": "Service Provider Name"
      }
    },
    {
      "@id": "inst:airwayReservationsPostEndpoint",
      "@type": "ods:ConnectorEndpoint",
      "service:airwayReservationsPostRequestUri": {
        "@type": "http://www.w3.org/2001/XMLSchema#anyURI",
        "@value": "https://example.com/api/v1/path"
      }
    },
    {
      "@id": "inst:airwayReservationDetailGetEndpoint",
      "@type": "ods:ConnectorEndpoint",
      "service:airwayReservationDetailGetRequestUri": {
        "@type": "http://www.w3.org/2001/XMLSchema#anyURI",
        "@value": "https://example.com/api/v1/path"
      }
    },
    {
      "@id": "inst:myServiceSparqlEndpoint",
      "@type": "ods:SparqlEndpoint",
      "ods:accessURL": {
        "@type": "http://www.w3.org/2001/XMLSchema#anyURI",
        "@value": "https://example.com/sparql"
      }
    }
  ]
}

Example of Service Instance Returned by a Discovery Finder (e.g. Aviation Industry)

{
  "@context": {
    "dcterms": "http://purl.org/dc/terms/",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "ods": "https://github.com/ODS-DFS-L4/ods/",
    "ads": "urn:samm:org.eclipse.esmf:1.0.0#",
    "api": "https://airway-discovery.example.com/1.0.0/api#",
    "inst": "http://airway-discovery.example.com/instance#"
  },
  "@graph": [
    {
      "@id": "inst:AirwayDiscoveryServiceProd",
      "@type": "ods:Connector",
      "dcterms:conformsTo": [
        {
          "@id": "ads:AirwayDiscoveryService"
        },
        {
          "@id": "api:AirwayDiscoveryWebService"
        }
      ],
      "dcterms:description": [
        {
          "@language": "en",
          "@value": "Production instance of Airway Discovery Service for finding and managing airway resources"
        },
        {
          "@language": "ja",
          "@value": "航路リソースの検索と管理のための航路ディスカバリーサービスの本番インスタンス"
        }
      ],
      "dcterms:title": [
        {
          "@language": "en",
          "@value": "Airway Discovery Service - Production"
        },
        {
          "@language": "ja",
          "@value": "航路ディスカバリーサービス - 本番環境"
        }
      ],
      "ods:hasEndpoint": [
        {
          "@id": "inst:FindResourceEndpointProd"
        },
        {
          "@id": "inst:RegisterDomainApplicationEndpointProd"
        },
        {
          "@id": "inst:RegisterResourceEndpointProd"
        }
      ],
      "ods:sparqlEndpoint": {
        "@type": "http://www.w3.org/2001/XMLSchema#anyURI",
        "@value": "https://example.com/sparql"
      },
      "ads:serverUrl": {
        "@type": "http://www.w3.org/2001/XMLSchema#anyURI",
        "@value": "https://example.com/rpc-api/v1"
      }
    },
    {
      "@id": "inst:RegisterDomainApplicationEndpointProd",
      "@type": "ods:ConnectorEndpoint",
      "dcterms:conformsTo": {
        "@id": "api:RegisterDomainApplicationAPI"
      },
      "dcterms:title": [
        {
          "@language": "en",
          "@value": "Register Domain Application Endpoint"
        },
        {
          "@language": "ja",
          "@value": "ドメインアプリケーション登録エンドポイント"
        }
      ],
      "ods:endpointInformation": "JSON-RPC endpoint for registering new domain applications",
      "ads:registerDomainApplicationRequestUri": {
        "@type": "http://www.w3.org/2001/XMLSchema#anyURI",
        "@value": "https://example.com/rpc-api/v1/airway/operations"
      }
    },
    {
      "@id": "inst:RegisterResourceEndpointProd",
      "@type": "ods:ConnectorEndpoint",
      "dcterms:conformsTo": {
        "@id": "api:RegisterResourceAPI"
      },
      "dcterms:title": [
        {
          "@language": "en",
          "@value": "Register Resource Endpoint"
        },
        {
          "@language": "ja",
          "@value": "リソース登録エンドポイント"
        }
      ],
      "ods:endpointInformation": "JSON-RPC endpoint for registering new resources",
      "ads:registerResourceRequestUri": {
        "@type": "http://www.w3.org/2001/XMLSchema#anyURI",
        "@value": "https://example.com/rpc-api/v1/airway/operations"
      }
    },
    {
      "@id": "inst:FindResourceEndpointProd",
      "@type": "ods:ConnectorEndpoint",
      "dcterms:conformsTo": {
        "@id": "api:FindResourceAPI"
      },
      "dcterms:title": [
        {
          "@language": "en",
          "@value": "Find Resource Endpoint"
        },
        {
          "@language": "ja",
          "@value": "リソース検索エンドポイント"
        }
      ],
      "ods:endpointInformation": "JSON-RPC endpoint for finding resources by location and drone model",
      "ads:findResourceRequestUri": {
        "@type": "http://www.w3.org/2001/XMLSchema#anyURI",
        "@value": "https://example.com/rpc-api/v1/airway/operations"
      }
    }
  ]
}

---

Functional Description

Discovery Service

• Resolves application endpoints related to resources in a business domain based on resource information (data/services).

• Allows users to search domain data using various search keys and resolves both the data and the metadata of the domain application required to obtain that data.

  • Search keys: latitude/longitude, strings, numeric values

  • Search results: metadata of service instances

Function Category	Summary
Spatial Index	Enables high-speed geospatial search by managing nearby data based on latitude and longitude. Supports bounding box and radius-based queries.
String Index	Enables search for resources sharing the same keyword.
Message Processing Generator	Generates message processing programs from interface definitions.
Database Generation	Creates RDB tables for index management from interface definitions.

When constructing a Discovery Service for a custom business domain, the message processing and database components are auto-generated. Only the integration logic connecting them needs to be implemented.

Discovery Finder

• Used to resolve the endpoint required for users to access a Discovery Service.

• Registers Discovery Service endpoints.

  • Can register under an existing keyword or create a new keyword.

• Searches Discovery Service endpoints (access URLs).

  • Search keys:

    1. Discovery Service keyword (e.g., UAS Lines)

    2. Business domain keyword (e.g., drone, drone route, port)

---

Sequence Diagram