feat(edint-trafico): add 7 candidate models for the standalone traffic ontology - #15
Open
albertoabellagarcia wants to merge 1 commit into
Open
feat(edint-trafico): add 7 candidate models for the standalone traffic ontology#15albertoabellagarcia wants to merge 1 commit into
albertoabellagarcia wants to merge 1 commit into
Conversation
…c ontology Translates the standalone EDINT Traffic Ontology (v0.1.1), a more current, dedicated version of a pattern already partially bundled into edint-infraestructura's v0.2.1 update. Seven entities: StreetSection, PlannedIncident, UnplannedIncident, ControlEquipment (new -- properly splits what the bundled copy handled by directly materializing bare TrafficEquipment), TrafficMeasurementDevice, TrafficObservation, TrafficObservationPoint (new, parallels edint-infraestructura's ObservationPoint but specific to traffic). Documented in standard-metadata.yaml rather than silently reconciled: real naming differences from the bundled copy (Incident vs Incidence, TrafficMeasurementDevice vs TrafficMeasuringDevice) and a property redistribution (numDirections/urban moved from TrafficEquipment to ControlEquipment specifically). edint-infraestructura's already-merged v0.2.1 PR is not touched. No real example data exists in the source repo; examples are synthetic. 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 standalone EDINT Traffic Ontology (v0.1.1) from
https://github.com/EDINT-Ontologia/edint-ontologia-trafico — a more
current, dedicated version of a pattern already partially bundled into
edint-infraestructura's own v0.2.1 update.
Seven entities: StreetSection, PlannedIncident, UnplannedIncident,
ControlEquipment, TrafficMeasurementDevice, TrafficObservation,
TrafficObservationPoint.
Real differences from the earlier bundled copy, documented not silently reconciled
TrafficMeasuringDevice.
handled the same use case by directly materializing bare TrafficEquipment,
since no dedicated subclass existed at the time.
ControlEquipment specifically; TrafficMeasurementDevice no longer carries
them.
edint-infraestructura's ObservationPoint but specific to traffic.
edint-infraestructura's already-merged v0.2.1 PR is not touched by this
PR — the discrepancy is documented in standard-metadata.yaml for whoever
reconciles the EDINT candidate family later.
Testing
All 7 models' schema/context/example files parse and validate;
example.json validates against schema.json; standard-metadata.yaml parses;
index regenerated. No real example data exists in the source repo;
examples are synthetic.