feat(edint-zona-regulatoria): add RegulatedZone candidate model - #6
Open
albertoabellagarcia wants to merge 1 commit into
Open
feat(edint-zona-regulatoria): add RegulatedZone candidate model#6albertoabellagarcia wants to merge 1 commit into
albertoabellagarcia wants to merge 1 commit into
Conversation
Translates the EDINT Regulated Zone Ontology (v0.1.0), a companion ontology to edint-infraestructura covering functional urban zones (low emission zones, regulated parking, pedestrian zones, historical centers, economic interest zones...) that overlay the urban grid without following fixed administrative boundaries. Modeled as a single RegulatedZone entity with a zoneType enum, since none of the source ontology's 22 concrete subclasses declare any property of their own -- all real properties (composedOf, locatedIn, managedBy, startDate, endDate, legalReference, scheduleDescription) are on the base class. Example grounded in real Zaragoza regulated parking zone data. Known issue, documented in standard-metadata.yaml and left unresolved per explicit decision: this creates a type collision with the thin RegulatedZone stub already added to edint-infraestructura in its v0.2.1 update (PR #5), and a namespace mismatch between the two ontologies' current states -- both need reconciling before either candidate is promoted further. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Translates the EDINT Regulated Zone Ontology (v0.1.0) from
https://github.com/EDINT-Ontologia/edint-ontologia-zona-regulatoria — a
companion ontology to
edint-infraestructura, covering functional urbanzones (low emission zones, regulated parking, pedestrian zones, historical
centers, economic interest zones, ...) that overlay the urban grid without
necessarily following fixed administrative boundaries.
Modeling: one entity, not 22
The source ontology defines
RegulatedZoneplus 22 subclasses(
LowEmissionZone,PedestrianZone,ResidentialParkingZone,HistoricalCenter, ...). None of the 22 declares any property of its own —every real property (
composedOf,locatedIn,managedBy,startDate,endDate,legalReference,scheduleDescription) is declared directly onthe base class. This candidate models a single
RegulatedZoneentity with azoneTypeenum covering all 22 (including the two intermediate classesEconomicInterestZone/RegulatedParkingZone, since the real Madrid exampleinstantiates
RegulatedParkingZonedirectly).zoneTypehas no backing property in the source ontology (the sourceexpresses it via
rdf:type/subclassing, not a dedicated property), so itscontext.jsonldmapping usesschema:additionalTyperather than afabricated ontology-specific IRI.
hasGeometrymirrors the source's own real-world pattern: an opaqueRelationship to an external WKT geometry resource, not an inline GeoProperty
— the real Madrid examples reference geometry files up to 3.3MB externally
rather than embedding coordinates, and zones are areas/polygons, not points.
Real example data
Grounded in
examples/zaragoza/example_zona1.ttl— a real Zaragozashort-term ("zona azul") regulated parking zone, with real street names,
schedule and legal reference. Chosen over the Madrid examples because
Zaragoza's is small and self-contained; Madrid's embed the very large WKT
files mentioned above.
This ontology's
RegulatedZone(confirmed via an identicalrdfs:comment)is the real, authoritative definition of the same class that
edint-infraestructuraadded as a thin stub in its own v0.2.1 update(#5, already merged) — same entity type name, different property sets. Per
explicit decision, this is translated as its own separate standard rather
than folded into
edint-infraestructura, so there is now a real NGSI-LDtype collision between the two candidates that needs reconciling before
either is promoted further (most likely resolution: replace
edint-infraestructura's stub with this one).There's also a namespace mismatch:
edint-infraestructura'sFacility.locatedInZonealready points athttps://edint.es/def/zone#...(anticipating a future migration), while this ontology's own currently
real, declared namespace is still
http://vocab.linkeddata.es/datosabiertos/def/common/zone#(not yetmigrated). This candidate uses the ontology's real current namespace, per
explicit decision.
Testing
schema.json/context.jsonld/all four example files parse as JSON.example.jsonvalidates againstschema.json.standard-metadata.yamlparses as YAML.