Skip to content
OpenCOOS

OpenCOOS — for strata and condo communities across Canada

A Common Language for Canada's Strata and Condo Data.

The Common Ownership Operating Schema (COOS) is an open, community-driven data standard that makes strata and condominium information consistent, connected and interoperable — from strata corporations in British Columbia to condominium corporations in Ontario, Alberta and across Canada.

COOS is maintained by OpenCOOS, an open initiative founded by ManageStrata. It is industry infrastructure, not another property management product.

Pigeons carrying a data card between a strata mid-rise, a condo tower and townhouses
  • Strata management software
  • Financial tools
  • Maintenance platforms
  • Analytics and AI

Shared definitions

Common Ownership Operating Schema (COOS)

Entities · fields · relationships · vocabularies

Consistent, interoperable data

{
  "type": "StrataCorporation",
  "strataPlanNumber": "EPS0001",
  "jurisdiction": "BC"
}
Illustration: different applications map their data to the same shared definitions, so information means the same thing wherever it goes.

COOS at a glance

What it is
An open, vendor-neutral data model for shared-ownership communities. A data standard, not a software product.
Coverage
Strata in BC; condominiums in Ontario, Alberta and across Canada
Status
Early development · working draft v0.1.0-draft
Format
JSON Schema (2020-12) with example payloads
Licence
Apache-2.0: free for commercial use
Maintained by
OpenCOOS, an open initiative founded by ManageStrata

The problem

Community data means different things in different systems

Strata and condominium corporations, managers and vendors rely on many tools. Each one describes the same units, meetings, fees and repairs in its own way — and every province adds its own vocabulary.
  • 01The same strata concepts are represented differently across software platforms.
  • 02Integrations require custom mappings and duplicated effort.
  • 03Inconsistent terminology makes reporting, analytics and automation harder.
  • 04Data portability and cross-platform innovation become unnecessarily difficult.

The approach

One openly documented way to represent strata information

Common Definitions

Shared definitions that map each province's terms — strata lot or unit, council or board — to the same concepts.

Interoperable Systems

Consistent structures and machine-readable schemas that make integrations simpler and more predictable.

Open Collaboration

A transparent specification the industry can review, adopt and improve together, with no single vendor in control.

How the pieces fit

One initiative, one schema, one founding implementer

Keeping these roles separate is what lets the standard stay vendor-neutral.

OpenCOOS

Open standards for community management

Common Ownership Operating Schema (COOS)

An open, vendor-neutral data model for shared-ownership communities.

An initiative founded by ManageStrata
  • OpenCOOS

    The open initiative and community.

  • COOS

    The technical specification: the Common Ownership Operating Schema.

  • ManageStrata

    The software company helping initiate and implement the standard.

  • Read how ManageStrata relates to the standard

Built in Canada, for Canada

Strata or condo, one common language

BC has strata corporations; Ontario and Alberta have condominium corporations. The concepts are largely shared — the words differ. COOS maps them to one model, starting with BC and extending to Ontario and Alberta next.
  • BCWorking draft

    British Columbia

    Strata

    Strata Property Act

  • ONNext priority

    Ontario

    Condominium

    Condominium Act, 1998

  • ABNext priority

    Alberta

    Condominium

    Condominium Property Act

  • +Welcome

    Other provinces and territories

    Strata, condominium and co-ownership

    Provincial and territorial legislation

Terminology used for the same concept in British Columbia, Ontario and Alberta
ConceptBC (strata)Ontario (condo)Alberta (condo)
The community's legal entityStrata corporationCondominium corporationCondominium corporation
Registered plan creating the communityStrata planDeclaration and descriptionCondominium plan
Individually owned propertyStrata lotUnitUnit
Shared areasCommon propertyCommon elementsCommon property
Shared areas for one owner's exclusive useLimited common propertyExclusive-use common elementsExclusive use common property
Owner's share of expensesUnit entitlementProportion of common interestUnit factor
Full terminology crosswalk

How it works

From definitions to working integrations

  1. 1

    Shared definitions

    Each entity, such as StrataLot or Resolution, has a plain-language definition, fields, types and controlled vocabularies.

  2. 2

    Machine-readable schemas

    Every definition is published as a JSON Schema with an example payload that is validated automatically.

  3. 3

    Map and validate

    Implementers map their own data to the standard at their system boundary and validate exports and imports against the schemas.

  4. 4

    Versioned releases

    Changes are proposed in the open and published as versioned releases with migration notes.

The standard defines data, not an API. Systems remain free to choose their own storage, APIs and technology. Read the developer documentation.

Current status

Early development

Nothing is final yet. This is the right time to influence the definitions.
Working draft
v0.1.0-draft
Stable releases
0
Proposed entitiesProposed
15
Experimental entitiesExperimental
10
Planned entitiesPlanned
16
Domains
6

What “draft” means

Draft schemas are published so people can review them and try them out. They are illustrative and not yet normative: names, fields and permitted values can change before the first stable release. Provincial legal terminology is flagged for review before it is treated as normative guidance.

Who can participate

Built with the people who use strata data

You do not need to be a developer to contribute. Feedback on terminology and real-world workflows is as valuable as code.
  • Developers and software vendors

    Build compatible strata applications and reduce custom integration work.

  • Strata councils, condo boards and owners

    Help make community records more transparent, portable and consistent.

  • Property management companies

    Push for better integrations and less fragmented data across tools.

  • Industry organizations

    Share terminology and data definitions across initiatives.

  • Researchers and data practitioners

    Work with strata information that has consistent meaning.

  • Open-source contributors

    Improve the schemas, documentation and validation tooling.

Ways to contribute

Early adopters and implementations

Implementations

Because no stable release exists, no product can claim conformance yet. Planned implementations are listed transparently.
Known implementations
ImplementationTypeStatus
ManageStrata.caFounder of OpenCOOSStrata management platformPlanned: intends to adopt the standard as the foundation of its data model
SearchStrata.comStrata document analysis for buyers, owners and councilsPlanned implementation

Building something compatible? Tell us about your implementation. Read how ManageStrata relates to the standard on the About page.

Latest specification updates

What changed recently

v0.1.0-draftProposed

Initial working draft

First public working draft of the proposed domains, shared definitions, and draft JSON Schemas. Nothing in this draft is stable; every definition is open for review and may change without notice.

Full changelog

Frequently asked questions

Questions and answers

Help shape a common language for strata data.

Review the draft, try the schemas in your own systems, or tell us where the definitions don't match how your strata corporation works.