OSYNIA proposed ecosystem of researchers, developers, enterprises, platforms, communities and governance
OPEN BY DESIGN · PROPOSED GOVERNANCE

Open foundations. Independent adoption.

OSYNIA is intended to be a shared set of specifications, not a product that everyone must buy or a replacement for existing websites.

What does “open” mean here?

Use your existing website

Adopt shared descriptions without rebuilding all your pages or replacing your content platform.

Choose your provider

Use open tools, build in-house, or choose an optional managed service. The standard should not lock you in.

Stay in control

Publishers retain ownership of information and decide which actions people or systems can perform.

Proposed open-core boundaries

Publish specifications, schemas, validators, conformance tests, baseline SDKs and a self-hostable reference runtime under appropriate open licences. Permit independent, interoperable implementations. Any commercial hosting, indexing, governed synchronisation, analytics or service-level support remains optional.

Compatibility-first strategy

Reuse HTTP/URI, JSON-LD, Schema.org, OpenAPI, OAuth/OIDC and relevant agent protocols where suitable. Build interoperability profiles and mapping adapters before proposing incompatible new infrastructure.

Governance is not yet established

Community decision-making, contribution policies, licensing, trademark usage, security reporting and specification change control must be published and reviewed before claims of formal standards status.

RISKS AND SAFEGUARDS

What could go wrong?

Incorrect information

Keep sources and editorial status visible. Do not treat generated descriptions as unquestionable facts.

Unsafe actions

Check identity and permissions on the server. Require consent and approval for consequential actions.

Conflicting updates

Use version checks, approval, history and rollback rather than silently changing all linked content.

Cost of authoring

Start with small useful schemas and automate only where the benefits justify the work.

Untrusted discovery

Assess source authority, freshness, spam and manipulation before showing federated results.

Adoption barriers

Provide migration adapters and conformance tools, and test against incremental improvements to existing standards.

HELP SHAPE THE FOUNDATION

Governance should be earned through participation.

Contribute technical review, licensing expertise, accessibility feedback or an independent implementation.

Get involved ↗