Ekklesia Scope Types

Publisher: Global.Church · Created: 2026-05-06 · 11 concepts

https://ontology.global.church/core#EkklesiaScopeTypeScheme

Controlled vocabulary for the scope dimension of a gc:EkklesiaSegment. Concepts cover Universal (whole-church scope), Network-AcrossCountries / Network-InCountry (network rollups), LocalBody (single-body scope), and finer geographic / linguistic / diaspora scopes (InCity, InAdminArea, InRegion, InCountry, InLanguage, InDiaspora). Sources include the v0.35.0 Track 12-2 reshape brief and the parallel PG-side scope-type pattern.

Code	Label	Definition
`EKST-ADM`	In Admin Area	Segment of an ekklesia body scoped to an administrative subdivision below the country level (state, province, governorate, ADM1 / ADM2). Useful when a denomination's polity follows admin-area lines (e.g., presbyteries, dioceses, conferences).
`EKST-CIT`	In City	Segment of an ekklesia body scoped to a specific city — typically used for multi-site bodies' per-site segments or for city-rollup queries across networks. The city is identified via gc:locatedIn (SKOS concept) or gc:spatialScope (gc:Location).
`EKST-CMP`	Local Campus	A single located campus of a multi-site church body — one of N venues at which the body gathers under shared eldership, shared teaching, and shared covenant. The per-campus scope of the v0.43.0 multi-site Campus-as-Segment model: a multi-site church is one gc:EkklesiaCommunity realizing one gc:Ekk-InCountry (or Ekk-NetworkInCountry) rollup segment plus one gc:Ekk-LocalCampus segment per campus. Each campus-segment carries gc:campusName, gc:meetsAt a gc:Location venue, and gc:subEkklesiaSegmentOf the rollup. Finer-grained than gc:Ekk-InCity — three campuses in one metro (e.g. 'Oklahoma City', 'South Oklahoma City', 'Northwest Oklahoma City') are three distinct Ekk-LocalCampus segments but one city. Distinct from gc:Ekk-LocalBody, which is the whole gathered collective of a SINGLE-site body; a campus is not an autonomous church.
`EKST-CTY`	In Country	Segment of an ekklesia body scoped to a single country, when the body is not a network (a single Church or HouseChurch operating only within one country). For network and denomination per-country rollups, use Ekk-NetworkInCountry instead.
`EKST-DIA`	In Diaspora	Segment of an ekklesia body scoped to a diaspora population — believers of a particular ethnic or national heritage who have resettled outside their homeland and who gather as a body in their host place. Carries gc:hostPlace (where they gather now) and gc:homelandPlace (where the diaspora originated).
`EKST-LCB`	Local Body	Single-body scope: the segment IS the body's whole gathered collective at its one place of meeting. The default scope for a Church / HouseChurch / CellGroup body that does not span multiple sites or geographies. The scope dimension carrier is typically gc:locatedIn or gc:spatialScope pointing at the body's place.
`EKST-LNG`	In Language	Segment of an ekklesia body scoped to a specific language community — useful when a body convenes in multiple languages and a ministry coordination question concerns one of them. Carries gc:hasLanguageClassification onto a ROL SKOS concept.
`EKST-NAC`	Network Across Countries	The cross-country rollup of a network or denomination — the segment that spans every country in which the network is present. The natural carrier for global counts and multi-country rollups; per-country rollups live on Ekk-NetworkInCountry segments instead. Mirrors the PG-side PGAC scope.
`EKST-NIC`	Network In Country	The per-country segment of a network or denomination — one segment per (network × ROG country) pair. The canonical join target for country-scoped engagement claims and assessments against networked bodies. Mirrors the PG-side PGIC scope.
`EKST-RGN`	In Region	Segment of an ekklesia body scoped to a multi-country region (HIS ROG region or comparable grouping). Useful for cross-border ministry coordination where the operational scope is regional rather than per-country.
`EKST-UNI`	Universal	Universal-scope segment: the whole body across time and place. Used sparingly and only when a query genuinely needs to refer to the universal scope (e.g., a Universal-scoped segment of the gc:UniversalChurch concept). Universal-scoped segments are exempt from the per-scope-dimension SHACL requirement — declaring scope type Universal IS the scope statement.