ontology: id: property-business-ontology title: Australian Property Investment, Accommodation and Operations Ontology ontology_iri: https://ontology.property.local/pbo base_iri: "https://ontology.property.local/pbo#" prefix: pbo version: 0.1.0 status: release_candidate created: "2026-09-14" modified: "2026-09-14" creator: Ryan Ballantyne licence: CC-BY-4.0 description: > An evidence-first ontology derived from the property-pages corpus (31 scraped web sources, seven category syntheses, seven combined source references and two deep-research reports, all compiled 14 September 2026). It models property assets and their identifiers, the parties and roles involved in owning, leasing, operating and managing residential and commercial accommodation, the agreements that bind them, the accommodation and operating models (rooming houses, HMOs, rent-to-rent/master leasing, coliving, corporate leasing, dual-income property, single- and multi-tenant commercial leasing), ownership structures, investment strategies, the Australian regulatory regimes that gate them (planning, building classification, fire safety, tenancy law, residential-service registration and rooming-house licensing, tax), business planning artefacts, financial scenarios and metrics, risks and mitigations, property-management operations, agency business models, and the open/licensed data sources that describe properties. intended_use: primary: ai_grounding secondary: [retrieval_cataloguing, integration, validation] notes: > The corpus is a research library assembled to support decisions about an Australian (primarily South East Queensland and Greater Melbourne) property investment, development, rooming-accommodation and leasing business. The ontology is intended to ground AI assistants and a future property-intelligence platform in a shared, source-traceable vocabulary, to catalogue claims by source and jurisdiction, and to validate structured records (scenarios, agreements, authorisations) with SHACL. Full OWL DL reasoning is a secondary concern; the ontology stays within OWL 2 DL but does not depend on entailment to answer its core competency questions. audience: - property investor / developer / accommodation operator (project owner) - application developers building a property intelligence platform - AI assistants answering questions grounded in the corpus - advisers reviewing feasibility, compliance and planning documents scope: breadth: > Residential and small commercial property investment and accommodation operations in Australia, with jurisdiction-specific detail for Queensland (South East Queensland, Brisbane, Logan) and Victoria (Greater Melbourne), plus generic business-planning, property-management and business-model concepts drawn from Australian and international sources. depth: > Deep enough to distinguish accommodation types, operating models, agreement types, regulatory regimes and their occupancy thresholds, ownership structures, financial scenario assumptions and metrics, and the source/authority of every claim. Not deep enough to encode statutory text, planning-scheme codes, tax computations or building-code clauses. inclusions: - property assets (land parcels, dwellings, rooms, commercial premises) and their identifiers (address, lot/plan, title reference, cadastral parcel) - parties (persons, organisations, government bodies) and the context-dependent roles they bear (owner, investor, operator, resident/tenant, property manager, lender, insurer, regulator, council, developer, adviser) - agreements between parties (residential tenancy, rooming accommodation agreement, head/master lease, sublease, management agreement, corporate lease, commercial lease, co-tenancy clause) and the risk allocation each creates - accommodation types and operating models (single-lease rental, room-by-room / rooming house / HMO, coliving, rent-to-rent / master lease, revenue-share / management, ownership, hybrid/franchise, corporate leasing, short-stay, dual-income configurations, single- vs multi-tenant commercial) - investment strategies and ownership structures (individual, joint tenants, tenants in common, discretionary trust, unit trust, company, SMSF) and their stated tax/legal characteristics - regulatory regimes and authorisations (planning use approval, building classification, fire-safety compliance, residential-service registration and accreditation in QLD, rooming-house operator licence and council registration in VIC, tenancy-law application, short-stay levy) with jurisdiction, governing legislation, regulator and occupancy thresholds - tax classifications (rental investment vs rental business vs profit-making undertaking; GST input-taxed vs commercial residential; negative gearing and CGT regime changes with effective dates) - business-planning information artefacts (business plan, project plan, feasibility study, information memorandum, financial model, risk register, implementation schedule) and their required sections - financial scenarios, assumptions and metrics (gross/net yield, NOI, cash-on-cash, IRR, occupancy, economic vacancy, RevPAR, CAC, EBITDA/EBITDAR, DSCR, LVR, break-even occupancy) - risks, mitigations and decision gates for strategies, operating models and development projects - property-management business operations (services, fee models, workflows, KPIs, trust accounting, portals, scale thresholds) - real-estate agency business models and innovation constructs (franchise, cooperative, joint venture, boutique, independent; open innovation; resource strategy) - property data sources and datasets (open authoritative, public paid, commercial, first-party, derived) and the attributes and identifiers they supply - source provenance for every claim, including authority, jurisdiction and currency exclusions: - statutory text, planning-scheme codes, building-code clauses and tax legislation are referenced as named instruments only; their internal structure and computation rules are out of scope - residential conveyancing and title transfer mechanics - construction methods, building materials and engineering design - personal financial or legal advice, credit assessment rules and lender product catalogues - market statistics as a time series; specific quoted figures are kept as evidence records and fixture values, not modelled as an observational data cube - Spanish and other non-Australian legal regimes (only referenced as out-of-jurisdiction source context) - property sales/marketing content, website navigation, promotional pricing and vendor product features - strata / owners-corporation governance beyond the recorded short-stay restriction power - human-resources, payroll and general accounting practice for property businesses interoperability: required: false target_ecosystems: - internal property-intelligence platform (PostgreSQL/PostGIS property master described in SRC-202) - future alignment candidates recorded in model.yaml mappings (schema.org, W3C ORG, PROV-O, SKOS, Dublin Core, GeoSPARQL, OWL-Time) but no import is asserted notes: > External vocabularies are reused by IRI reference only (PROV-O, SKOS, Dublin Core Terms). schema.org / W3C ORG / GeoSPARQL alignments are recorded as candidate mappings with skos:closeMatch or annotation strength; no owl:equivalentClass is asserted because definitions were not compared against pinned versions. standards: rdf: "1.1" turtle: "1.1" rdfs: "1.1" owl: "2 DL" owl_profile_rationale: > OWL 2 DL is used because the ontology needs disjointness, inverse properties, functional data properties and a small number of existential restrictions on event/agreement classes. No construct exceeds DL and the ontology deliberately avoids nominals and complex property chains so it stays within EL-friendly territory for most classes. skos: "2009" shacl: "2017" sparql: "1.1" prov: "PROV-O 2013" competency_questions: - id: CQ-001 question: > Which regulatory authorisations (planning approval, building classification, fire-safety compliance, registration, licence, accreditation) does a given accommodation operating model require in a given jurisdiction, and which legislation and regulator govern each authorisation? priority: core purpose: compliance_grounding status: active expected_answer_shape: rows of (operatingModel, jurisdiction, authorisationType, legislation, regulator) - id: CQ-002 question: > What occupancy or size threshold (number of residents, rooms, bedrooms or floor area) triggers or exempts a regulatory regime in a given jurisdiction? priority: core purpose: compliance_grounding status: active expected_answer_shape: rows of (regime, jurisdiction, thresholdKind, thresholdValue, effect) - id: CQ-003 question: > Under a given agreement (head/master lease, sublease, management agreement, corporate lease, commercial lease), which party bears which role, who carries fixed rent and vacancy risk, and who is responsible for outgoings? priority: core purpose: risk_allocation status: active expected_answer_shape: rows of (agreement, agreementType, party, role, riskOrObligation) - id: CQ-004 question: > For a given financial scenario, what assumptions (rooms, tariff, vacancy, operating-expense ratio, leverage, interest rate, growth) were used and what metric values (NOI, cash flow, cash-on-cash, IRR) resulted? priority: core purpose: feasibility_grounding status: active expected_answer_shape: rows of (scenario, assumptionMetric, assumptionValue, resultMetric, resultValue) - id: CQ-005 question: > Which ownership structures are described for property investment and what tax, liability, distribution and estate characteristics does each carry? priority: core purpose: structuring_grounding status: active expected_answer_shape: rows of (ownershipStructure, characteristic, source) - id: CQ-006 question: > Which investment strategies does the corpus describe, and which accommodation type, operating model and tenant segment does each rely on? priority: core purpose: strategy_catalogue status: active expected_answer_shape: rows of (strategy, accommodationType, operatingModel, tenantSegment) - id: CQ-007 question: > Which risks apply to a given strategy, operating model or development project, and what mitigation or decision gate is recorded for each? priority: core purpose: risk_register status: active expected_answer_shape: rows of (subject, risk, riskCategory, mitigation) - id: CQ-008 question: > Which sections must a business-planning artefact (business plan, feasibility study, information memorandum) contain according to which source? priority: supporting purpose: document_template_grounding status: active expected_answer_shape: rows of (artefactType, section, source) - id: CQ-009 question: > Which data sources supply which property attributes or identifiers for a jurisdiction, under what access tier, refresh cadence and licence? priority: core purpose: data_integration status: active expected_answer_shape: rows of (dataSource, publisher, attribute, accessTier, refresh) - id: CQ-010 question: > Which lease types allocate which outgoings (taxes, insurance, maintenance, common-area costs) to the landlord versus the tenant? priority: supporting purpose: commercial_leasing status: active expected_answer_shape: rows of (leaseType, outgoing, bearer) - id: CQ-011 question: > Which sources make a quantitative claim about a given metric (for example rooming-house gross yield), with what value, basis, authority level, jurisdiction and date? priority: core purpose: provenance_and_conflict status: active expected_answer_shape: rows of (claim, metric, value, source, authority, jurisdiction, date) - id: CQ-012 question: > Which tax rules or incentives apply to which property class from which effective date, and which grandfathering cut-off applies? priority: supporting purpose: temporal_tax_grounding status: active expected_answer_shape: rows of (rule, propertyClass, effectiveFrom, cutoffDate) - id: CQ-013 question: > Which services does a property-management business provide, under what fee model, and which workflows and KPIs support them? priority: supporting purpose: operations_grounding status: active expected_answer_shape: rows of (service, feeModel, workflow, kpi) - id: CQ-014 question: > Which real-estate agency business-model structures exist and how does each source its capabilities (internally controlled versus externally accessed)? priority: supporting purpose: business_model_catalogue status: active expected_answer_shape: rows of (agencyModel, capabilitySourcing) - id: CQ-015 question: > Which properties in a portfolio have a lawful-use authorisation that is missing, pending or expired for their intended operating model? priority: supporting purpose: validation status: active expected_answer_shape: rows of (property, operatingModel, missingAuthorisationType) release_policy: require_all_core_cqs: true require_annotation_coverage: 1.0 require_evidence_coverage: 1.0 require_external_reasoner: false require_shacl_engine: true shacl_inference: rdfs shacl_engine_note: > SHACL execution is required because shapes.ttl carries operational validation for scenarios, agreements and authorisations. pySHACL conformed on 2026-09-14 with RDFS inference, using ontology.ttl and taxonomy.ttl as the ontology graph.