feat(edint-fotovoltaica): add 5 candidate models for photovoltaic systems - #9
Open
albertoabellagarcia wants to merge 1 commit into
Open
feat(edint-fotovoltaica): add 5 candidate models for photovoltaic systems#9albertoabellagarcia wants to merge 1 commit into
albertoabellagarcia wants to merge 1 commit into
Conversation
…tems Translates the EDINT Photovoltaic System Ontology (v0.2.1), covering solar installations on municipal infrastructure elements and the measurement of electricity generation, consumption, accumulation and grid export. Five entities, the only ones native to this ontology (it bundles ~30 other referenced-but-external classes, none modeled here, consistent with this candidate family's practice): PhotovoltaicSystem (status, usage type, installed power, installation org), PhotovoltaicMeter (Sensor+Meter pattern, same as CountingSensor/AccessSensor), PhotovoltaicGeneration (SOSA Observation pattern, same as CountingObservation/TrafficObservation), PhotovoltaicSystemContract, and PhotovoltaicSystemRate (thin entity). Unlike its EDINT siblings, this ontology already uses the migrated edint.es namespace and has no real example data at all (no examples/or mappings/ directory) -- examples are synthetic. A known gap (Facility should ideally gain a hasPhotovoltaicSystem relationship, mirroring its v0.2.1 additions) is documented rather than acted on, to keep this PR scoped to the fotovoltaica ontology itself. 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
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 Photovoltaic System Ontology (v0.2.1) from
https://github.com/EDINT-Ontologia/edint-ontologia-fotovoltaica — solar
installations on municipal infrastructure elements, and measurement of
electricity generation, consumption, accumulation and grid export.
Five entities (out of ~35 referenced classes)
The source file bundles a large number of imported/referenced external
classes for context —
edint-infraestructura's ownFacility/InfrastructureElement,edint-aparcamiento'sParking(interestinglyunder its new
edint.esnamespace — suggesting that ontology may have anewer version too; out of scope here), SOSA/SAREF, QUDT, W3C Time, and
Spain's territorial hierarchy. None of these are modeled, consistent with
this candidate family's established practice. Only 5 classes are native:
PhotovoltaicSystem: status, usage type (grid/stand-alone/hybrid),installed power, installation organization, in-service date.
PhotovoltaicMeter: Sensor+Meter pattern, same treatment asCountingSensor/AccessSensor.PhotovoltaicGeneration: SOSA Observation pattern, same asCountingObservation/TrafficObservation. The class comment coversgeneration/consumption/storage/export, but the source declares no
categorization property for which is which — expected to be conveyed via
observedProperty's target concept instead.PhotovoltaicSystemContract: applies-to, contract holder, rate.PhotovoltaicSystemRate: thin entity, no source-declared properties.Two things worth flagging
edint.esnamespace — no pending namespace-mismatch issue here.(no
examples/ormappings/directory) — all 5 examples are synthetic.A documented gap, not acted on
The source declares
hasPhotovoltaicSystemwith domainedint-infraestructura'sInfrastructureElement— the forward relationshipfrom an infrastructure element to its photovoltaic system. Mirroring how
Facilitygained 3 properties in its own v0.2.1 update, it should ideallygain this one too. Not added here, to keep this PR scoped to the
fotovoltaica ontology itself rather than reopening
edint-infraestructuraagain — noted in
standard-metadata.yamlas a follow-up opportunity.Testing
schema.json/context.jsonld/example files parse as JSON, all 5example.jsonvalidate against their ownschema.json.standard-metadata.yamlparses as YAML.Note: based on current
master, which doesn't yet include the still-open#6/#7/#8 — no dependency between any of them.