Resource Registry Service Documentation

Fundamentals and Model

Data Representation

REST API Reference

Architecture

  • Architectural Decisions A manifesto of the fundamental implementation choices, tracking why the model behaves the way it does.

  • References The origins of the architecture and consolidated bibliography.


Appendices

  • Formal Semantics The mathematical set theory defining Context membership and intersections.

  • Element Category Matrix A quick reference for the structural differences and capabilities of the various categories of elements within the Information System.

  • Complex Topology Scenarios Advanced scenarios, including cyclic graphs and their resolution during avalanches.

  • Response Shape Matrix A unified reference for how query parameters and HTTP headers alter the structural density and schema of the JSON response payload.

  • API Operational Cookbook Real-world operational patterns, including Facet Forking, Hierarchical Distribution, and surgical Relation deletion.

  • Ecosystem Tooling & Clients The Java ecosystem: annotations, documentation generators, and modular REST clients.

  • JSON Query Syntax Reference Manual for executing structured JSON queries with _emit, _or, _and.

  • HATEOAS Navigation Controls The exact matrix of Hypermedia HTTP Link relations emitted by the various API endpoints.

  • X-Result-Scope Conventions The normative values emitted by the X-Result-Scope header to signal dynamic visibility filtering.

Type Dictionaries

Both the foundational IS-Model types (Resource, Facet, IsRelatedTo, ConsistsOf, Property) and this deployment’s gcube-model types — dynamically-registered, runtime-mutable data — are documented at /model-docs, generated directly from this instance’s live schema so it is never out of date with what is actually registered. gcube-model types can also be queried directly (GET /types/{type-name}, QUERY /types/query).