Bylaw
ProposedA bylaw or rule of the strata corporation. Bylaws are adopted by the owners; rules may be made by council and later ratified.
Fields
| Field | Type | Description |
|---|---|---|
idrequired | Identifier | Stable identifier of this Bylaw record. |
strataCorporationIdrequired | Identifier | The strata corporation this record belongs to. References StrataCorporation |
kindrequired | enum | Whether this is a bylaw or a rule.
|
referenceoptional | string | Number or section reference used by the corporation (for example "3.4"). max length 32 |
titlerequired | string | Title or subject. min length 1 · max length 200 |
textoptional | string | Full text. max length 50000 |
statusrequired | enum | Current status.
|
approvedByResolutionIdoptional | Identifier | Resolution that approved or ratified it. References Resolution |
effectiveDateoptional | Date | Date it took effect. |
filedDateoptional | Date | Date a bylaw amendment was filed in the Land Title Office, where applicable. |
extensionsoptional | Extensions | Implementation-specific data, namespaced by reverse domain. |
Controlled vocabularies
kind
bylaw- Bylaw.
rule- Rule.
status
proposed- Proposed but not yet approved.
inEffect- Currently in effect.
repealed- Repealed or replaced.
Relationships
Referenced by
None
References
- strataCorporationIdStrataCorporation
- approvedByResolutionIdResolution
Validation rules
Cross-field rules beyond what JSON Schema expresses. Documented in the draft; not yet enforced by tooling.
- filedDate applies only when kind is bylaw.
Open questions for legal and industry review
- Confirm when bylaws and rules take effect and how ratification of rules should be represented.
Example payload
Illustrative only, with fictional data. Validated against the draft schema at build time.
{
"id": "bylaw-3-4",
"strataCorporationId": "sc-0001",
"kind": "bylaw",
"reference": "3.4",
"title": "Pets",
"status": "inEffect",
"approvedByResolutionId": "res-2024-07",
"effectiveDate": "2024-05-10",
"filedDate": "2024-05-10"
}