Registros públicos

These concepts distinguish an institution, person or physical asset from its registration, authorization and the record describing it. They are reference meanings, not a government submission format, full-domain model, normative specification or a conclusion about anyone's rights. The terms are authored across the organization, ownership, regulation, education, work, transport, environment, tax, elections and physical-asset modules and are at draft maturity. Where a French or Spanish translation is missing, the site falls back to English.

Scope and evidence

The following dispositions account for the government domain families. The source standards informed the definitions; PublicSchema chooses the relationships, optional fields and serialization. None of these sources is claimed as an exact mapping or a complete implemented interchange.

Family	Delivered reference concepts and reuse	Deliberate boundary and counterexample	Evidence
Public organizations	PublicOrganization, InstitutionalRelationship, InstitutionalRole, existing Organization	Public function, legal personality and ownership differ. A ministry's internal unit can be an Organization without its own legal personality. Typed dated institutional links express hierarchy and affiliation; InstitutionalRole records membership, including membership of a producer organization; OrganizationalChangeEvent records mergers, splits and succession.	CPOV 2.1.2, Public Organisation; W3C ORG 2014, Organization, OrganizationalUnit, Membership and ChangeEvent
Business	Organization with legal_form and formation_date, institutional roles and relationships, shared Registration	A sole trader is a Person. A branch need not be a separately incorporated company. Legal form is a coded attribute of an Organization, not a separate class. Corporate filings use evidence/source records rather than turning each filing into another business identity.	Registered Organization Vocabulary 2013, RegisteredOrganization; Companies House companyProfile API, type, jurisdiction, foreign_company_details, date_of_creation
Beneficial ownership	OwnershipInterest (an indirect interest may list its component_interests), LegalArrangement, existing Person/Organization; RegistryEntry records source assertion	Multiple simultaneous interests remain separate. An exact percentage uses interest_percentage; a band uses the inclusive or exclusive bound fields and is never treated as exact. An indirect interest is not a verified route. A corporate interest holder is not necessarily the ultimate natural-person beneficial owner. A source's conclusion that an interest is beneficial ownership or control is beneficial_ownership_or_control, stated only with the beneficial_ownership_definition it applies.	BODS 0.4 reference, Relationship Statement and Interest; BODS model
Education	edu/EducationProvider, edu/ProviderSite, edu/EducationProgram, edu/EducationOffering; reuse edu/School and root ServicePoint for physical delivery	A virtual provider site needs no invented address. The organizational provider, a campus, an education program and an offering remain separate. A program's level (ISCED-P) and field (ISCED-F) are separate classifications. Institutional links represent federation membership, governance and succession; authorization and assessment express accreditation and inspection.	DfE GIAS, establishments and groups; GIAS download implementation; ISCED 2011, section 2; ELM 3, LearningOpportunity and LearningAchievement
Professional licensing	ProfessionalLicense, AwardedQualification, PracticeRole, Person; RegulatoryAction for discipline	A degree, permission to practice and a role at a clinic are different. Specialty codes keep their source scheme. A disciplinary assertion does not silently overwrite a Person identity.	FHIR R5 Practitioner, qualification; PractitionerRole, practitioner, organization, period and location; GMC licensing, registration and license distinctions
Driver licensing	DrivingEntitlement, Person; shared Authorization, evidence and RegulatoryAction	Each license-category entitlement has its own dates and conditions. The card is evidence, not the permission itself. Coded conditions are sensitive because some codes reveal a medical condition; uncoded conditions stay in the authorization's text conditions. A test result is evidence supporting an entitlement, not automatically permission; sanctions remain separate actions.	Directive (EU) 2025/2205, Article 6, Article 8 and Annex I; DVLA licence categories, licence codes, category validity guidance
Taxpayer	TaxRegistration, Person/Organization, Identifier and InstitutionalRole	A TIN does not establish liability or compliance. Tax type and recognition period belong on registration; a subject registered for several taxes can hold one registration for each. Representatives use RepresentationRole, acting for a person, organization, group or legal arrangement; establishment identity remains separate. A filing obligation needs its own legal rule and period in a tax profile.	OECD TIN portal, separate individual/entity jurisdiction guidance; IRS TIN, identifier categories; IRS Form 2848, representative authority; HMRC representation, including organizational assistance
Voter	VoterRegistration, Person, Location and ServicePoint	Registration is neither citizenship nor blanket eligibility for every election. Electoral districts are named areas, polling stations physical service points. The assigned polling station and the electoral districts are sensitive because they can reveal where the person lives, especially for a small district such as a ward. Eligibility evidence belongs to the registration assertion; ballot choices are outside this registry vocabulary.	NIST SP 1500-102 V1, VoterRecord, ReportingUnit and Voter, March 2020 web edition
Buildings	Building, BuildingUnit, Address and SpatialGeometry	An address, building, functional unit and title parcel have different identity. Multiple addresses can describe one building. Detailed 3D encoding remains in the spatial exchange profile.	INSPIRE Buildings technical guidelines, Building, BuildingUnit and BuildingsBase 4.0 schema
Vehicles	Vehicle, AssetPartyRole, shared Registration; ComplianceAssessment, RegulatoryAction	Physical vehicle identity persists when a registration changes. A keeper is not inferred to be an owner. Vehicle inspection is an assessment; a certificate is evidence. AssetPartyRole keeps dated keeper and ownership assertions separate, with role codes from a stated scheme and canonical actor and asset URIs.	DVLA Vehicle Enquiry API 1.2.0, Vehicle response
Environmental facilities	environment/EnvironmentalFacility; shared Registration/Authorization	One site may participate in several regulatory programs. Its operator, permits and program record IDs do not redefine its physical identity. The operator is a dated AssetPartyRole and each address an AssetAddressAssignment. Where an agricultural register also records the site as an agri/AgriculturalFacility, both records keep their identity and a SubjectMatchAssertion states the match; a shared site identifier is supporting evidence, not proof.	EPA FRS description, site/program distinction and Facility Site Identification standard 2.0
Environmental compliance	ComplianceAssessment, RegulatoryAction; shared Authorization for permits	Findings concern a stated requirement and date. Enforcement is an action with authority and legal basis, not a universal lifecycle status. Detailed threshold logic, appeals and procedural finality belong to applicable profiles.	EPA ECHO services, report interface

Address, health facility, agricultural holding, cadastral land and shared registry foundations are covered in registry foundations, not duplicated here. Dataset wrappers are exchange packaging rather than independently meaningful domain concepts. They are intentionally not public classes. Likewise, national code inventories, workflow status enumerations and authority-specific required fields are profile content rather than a universal closed vocabulary.

Modeling decisions and alternatives

All new fields are optional at reference-vocabulary level. Registrations inherit registered_subject (a URI), registration_authority, registration_jurisdiction, valid_from and valid_to from Registration. Professional licenses and driving entitlements further inherit Authorization. The URI permits Person or Organization subjects where the domain permits them without widening Party or accepting software agents as legal actors. A profile must verify target existence and permitted types; JSON Schema cannot establish that a URI resolves to a Person. The example profile below imposes person-only subjects for voter, driving and professional authorizations.

Codes use CodedValue and retain source code, scheme, optional source label and meaning URI. This was chosen over new national enum lists and over reusing Identifier for classifications. Unknown or retired local codes remain representable without assigning a fabricated universal meaning. The enum InterestDirectness describes the relation, not a jurisdiction's beneficial-ownership thresholds. The enum FormOfWork is the closed list of the five forms of work in the 19th ICLS resolution (paragraph 7); status at work stays a CodedValue because ICSaW-18 and national variants carry their own editions.

PublicSchema's existing address property explicitly refers to a household, located_at to a service point, managed_by to a service point operator, and jurisdiction to data protection law. Reusing these merely because the field names looked suitable would change their meaning. These modules therefore record building and facility addresses through dated asset address assignments, facility operators through asset party roles, and public competence through a competence area property. Existing name, identifiers, Person, Organization, dates and ServicePoint meanings are reused unchanged.

An environmental facility's operator is an AssetPartyRole whose subject is the facility, whose actor is a person, organization or group URI and whose role type codes operation. A facility operated by an individual does not require an invented Organization. Because the role is dated, a change of operator adds a role rather than changing the facility, which keeps its identity. Regulation (EU) 2024/1244, which applies from 1 January 2028, recognizes natural-person and legal-person operators in Article 3(2); its definition groups installations on a site by operator, so this identity rule is a deliberate difference.

A second option was to create Person subclasses named Taxpayer, Voter and Practitioner. That obscures canonical identity and the jurisdictional, dated nature of recognition. Another option was copying every registry's specialized containers and records. That conflates exchange envelopes, legal records and real-world subjects. PublicSchema instead specializes relationships when meaning warrants it and uses shared registration, authorization, evidence and record constructs.

Not every statement about a government registry becomes a new universal class. Business filings, professional test evidence and registration certificates can be described through the shared evidence/record layer. Asset roles have optional reference concepts because their identities and meanings exist independently of workflow. Detailed pharmaceutical manufacturing stages and recursive packaging encodings remain with the corresponding interchange profile; PublicSchema does not flatten these into its simpler quantities or free text. These reference concepts answer selected questions; no lossless projection back to a source registry is claimed.

The generic AwardedQualification, ProfessionalLicense and PracticeRole concepts do not replace native Practitioner or PractitionerRole for medical exchange. FHIR Practitioner.qualification includes licenses as well as academic qualifications, so these are not exact field mappings. PracticeRole is a close match for PractitionerRole; AwardedQualification is a close match for the ELM LearningAchievement, not for Practitioner.qualification.

For medical meaning, use the selected native FHIR R5 5.0.0 resource and profile. PublicSchema has no native medicinal product, healthcare service or accreditation classes. Keep medical detail in FHIR and link it to PublicSchema registry and shared identities where that is independently useful. Native FHIR records in a PublicSchema registry documents the synthetic example, its official-shape checks and the known mapping losses.

Tax and other representation uses RepresentationRole, whose representative is a person or organization and whose represented party can also be a group or legal arrangement; it does not assume that representation happens inside an organization. RegistryEntry can describe an OwnershipInterest assertion with its recording time, source records and evidence assertions. The interest remains the dated subject of that statement, and recording it never verifies its truth. Several statements may concern the same interest without merging source identity.

Examples and checks

examples/government-domains/records.json contains synthetic records spanning the government classes. Synthetic entity identifiers use https://example.org/. A company and a public agency remain organizations; separate interests identify natural and institutional holders. Education uses a virtual site without an address. A person holds two category entitlements with different expiry dates. The same vehicle is referenced by a registration and inspection. A site's compliance assessment and regulatory action remain separate, and its operator and address are dated AssetPartyRole and AssetAddressAssignment records. The ownership and education guide covers synthetic ownership routes and offerings.

Run uv run --locked pytest tests/test_government_domains.py from the repository root. The tests build the real catalog and production RDF/JSON-LD/SHACL exporters, validate the same fixtures in JSON Schema and context-expanded SHACL, and assert every authored class and slot survives. Negative fixtures test primitive/cardinality/code rejection in both public representations. The separately named example profile, uv run --locked python examples/government-domains/profile.py, rejects unresolved or wrong-kind subjects, empty or reversed end-exclusive periods, compact or impossible dates, repeated record identities and incoherent percentage bounds. These profile checks are local rules, not enforced by the reference vocabulary (see the examples README).

The ownership percentage slots are bounded to zero to one hundred in the vocabulary. The vocabulary expresses no cross-field conditions, such as an exact value excluding bounds or a lower bound not exceeding an upper bound; the example profile checks interval coherence. Legal eligibility, code membership, unit conversions and applicable regulatory thresholds are likewise profile validation.