03 / Technical proposals

Six open contracts. One shared direction.

A proposed specification family for reusable resource meaning, authorised capabilities, interoperable experiences, synchronised change, trust and federated discovery.

Proposed — not an approved standard
OSYNIA–RRESEARCH DRAFT

Resources & Meaning

Portable descriptions of resources, semantics, relationships, versions and provenance.

Resource identitiesSemantic representationMultimodal metadataDependencies & provenance
OSYNIA–CRESEARCH DRAFT

Capabilities & Intent

Typed descriptions of actions, inputs, preconditions, permissions and outcomes.

Capability contractsIntent matchingPreconditions & effectsAuthorised execution
OSYNIA–ERESEARCH DRAFT

Experience & Accessibility

Meaning expressed through adaptable web, mobile, assistive and agent experiences.

Presentation independenceAccessible semanticsAdaptive experiencesInternationalisation
OSYNIA–SRESEARCH DRAFT

Synchronisation & Change

Versioned change propagation through connected resource and content graphs.

Change eventsDependency awarenessConflict managementReview & approval
OSYNIA–TRESEARCH DRAFT

Trust & Governance

Authentication, authorisation, consent, provenance and auditability.

Identity & policySigned provenanceConsent controlsAudit & accountability
OSYNIA–DRESEARCH DRAFT

Discovery & Federation

Federated discovery of trusted resources, knowledge and executable capabilities.

Federated discoveryResource registriesCapability matchingRelevance & trust
Principle of restraint

Compatibility before reinvention.

The OSYNIA research process should map each contract against mature specifications including JSON-LD, RDF, Schema.org, Web of Things, OpenAPI, AsyncAPI, WebMCP, MCP, OAuth and accessibility standards. A separate specification is justified only when it addresses a demonstrated interoperability gap.

FROM PROPOSAL TO TESTS

Start small. Implement. Measure. Refine.

See the roadmap ↗