Model Concepts (OWL Ontology)
Extension ontology for modeling the EA function as an internal
management consultancy. Provides vocabulary for EA service catalogs, service
engagements, stakeholder satisfaction, EA capability portfolios, and maturity
assessment.
Addresses the Gartner 2025 prediction that by 2028, half of EA teams will
rebrand themselves to emphasize their strategic role as business partners.
Formalizes the shift from "architecture practice" to "architecture services"
by making service offerings, engagements, outcomes, and satisfaction into
queryable elements in the knowledge graph.
Designed to be lightweight and adaptable — organizations customize the
service catalog and maturity model to their operating model.
https://meta.linked.archi/ea-service/onto#
Formal Rules (SHACL Shapes)
SHACL shapes for validating EA-as-a-Service models. Enforces
governance rules: every service must declare required capabilities, every
engagement must have an assigned architect and status, and every EA service
must have a label.
https://meta.linked.archi/ea-service/shapes#
Concept Classification (SKOS)
Classification of EA service concepts by service type, engagement duration, stakeholder type, and maturity level.
https://meta.linked.archi/ea-service/tax#EAServiceConceptScheme
Reference Data
Reference data for EA-as-a-Service — service types, engagement
statuses, and maturity levels.
https://meta.linked.archi/ea-service/reference-data#
| Type | Resource | Description | URI |
| Model Concepts (OWL Ontology) |
onto |
Extension ontology for modeling the EA function as an internal
management consultancy. Provides vocabulary for EA service catalogs, service
engagements, stakeholder satisfaction, EA capability portfolios, and maturity
assessment.
Addresses the Gartner 2025 prediction that by 2028, half of EA teams will
rebrand themselves to emphasize their strategic role as business partners.
Formalizes the shift from "architecture practice" to "architecture services"
by making service offerings, engagements, outcomes, and satisfaction into
queryable elements in the knowledge graph.
Designed to be lightweight and adaptable — organizations customize the
service catalog and maturity model to their operating model. |
https://meta.linked.archi/ea-service/onto# |
| Formal Rules (SHACL Shapes) |
shapes |
SHACL shapes for validating EA-as-a-Service models. Enforces
governance rules: every service must declare required capabilities, every
engagement must have an assigned architect and status, and every EA service
must have a label. |
https://meta.linked.archi/ea-service/shapes# |
| Concept Classification (SKOS) |
EA-as-a-Service Concept Scheme |
Classification of EA service concepts by service type, engagement duration, stakeholder type, and maturity level. |
https://meta.linked.archi/ea-service/tax#EAServiceConceptScheme |
| Reference Data |
reference-data |
Reference data for EA-as-a-Service — service types, engagement
statuses, and maturity levels. |
https://meta.linked.archi/ea-service/reference-data# |