Skip to content

Flexo Ecosystem Level.md

Latest commit

 

History

History
36 lines (21 loc) · 2.56 KB

Flexo Ecosystem Level.md

File metadata and controls

36 lines (21 loc) · 2.56 KB

Flexo Ecosystem Level

Concern: Organizations sharing model assets across enterprise boundaries.

Standards-Based Interoperability

The guiding principle for Flexo modules is to adopt open, web-compatible standards for data exchange at every interface — both data format and exchange protocols. [[SPARQL]], [[Graph Store Protocol]], [[Linked Data Platform]], [[GraphQL]], [[OSLC]], [[SysML v2]], JSON HyperSchema, gRPC, and so on, are all web-friendly protocols with broad tooling support in their respective ecosystems (Architecture).

The [[SysML v2]] API layer conforms to the OMG standard, enabling interoperability with any compliant tooling (flexo-mms-sysmlv2).

Models in Flexo are not limited to enterprise model development platforms — Flexo can store anything expressed as [[RDF]] (openmbee.org).

Operational Considerations

  • Each organization typically runs its own Flexo deployment (no federated multi-tenant architecture in the current release)
  • Asset sharing occurs via API exchange (export/import) or [[OSLC]] linking
  • Standards compliance (OMG [[SysML v2]] API) enables tool interoperability across organizational boundaries

Consistency Model

Within a single Flexo deployment, the [[quadstore]] provides strong consistency: SPARQL UPDATE operations are atomic within a transaction, and queries against a named graph see a complete snapshot. The Layer 1 service reinforces this with ETags and transaction mutexes for branch updates (see [[Merge#Concurrency Control]]).

Across deployments, no consistency protocol is currently specified. If organizations exchange model state via API or [[OSLC]] linking, the consistency guarantees depend on the exchange mechanism. A federated architecture would need to define whether it provides eventual consistency (all replicas converge given quiescence) or causal consistency (causally related commits are observed in order).

Gap

The [[Flexo Conflict Resolution Mapping|conflict resolution formalism]] assumes a single repository; cross-organization federation would require additional coordination protocols.

References

← [[Flexo MMS]]