Open Haigutus opened 2 years ago
Open issues to transofrm to dcat namespace/domain
Linking
[ ] StandardEicTypeList Concept -> EIC Collection
[ ] EIC Concept -> StandardEicTypeList Concept
[ ] Open question: How to link Concept -> Collection
http://energy.referencedata.eu/StandardEicTypeList/Z -> skos:Collection rdf:about="http://data.europa.eu/energy/EIC/Function/AccountingPoint" http://data.europa.eu/energy/EIC/10Z-CH-DE-00017K -> http://energy.referencedata.eu/StandardEicTypeList/Z
Another good option to use is dcterms:isPartOf
for EICCode_MarketDocument.docStatus (active/inactive) we have adms:status in DCAT
For the phone, email we can use https://www.w3.org/TR/vcard-rdf/
ACERCode_Name.name - is this needed?
Of course. The more ids the better. ACER itself has BIC, GLEI, GLN.
You need to make a distinction about an organization or resource, its identifiers, and docs about those identifiers.
[ ] For Address:
[x] VAT
[ ] Postal Code
Question for Alvaro:
Reply from Alvaro:
Schema v1.0 references to EIC document v1.1.
Schema and market document versions are not correlated
urn:iec62325.351:tc57wg16:451-n:eicdocument:1:1
To summarize v1.1 of eic document is the last version of the profile. Version 1.1 of the profile is reference in v1.0 of the schema above
Initial version ready, example -> https://energy.referencedata.eu/EIC/10Y1001A1001A39I
@Sveino @griddigit please review
The sample file looks good to me at first sight.
Just for me to understand, how are we going to refer to an EIC code from a 61970 instance file? I guess that it will be using the dcterms:identifier but just to be sure. e.g. urn:eic:10Y1001A1001A39I
@marrodal That is correct. I've added urn:eic:$1
as "URN formatter" on Wikidata: https://www.wikidata.org/wiki/Property:P8645 in Dec 2021.
I've also added http://energy.referencedata.eu/EIC/$1
as "formatter URI for RDF resource"
@Haigutus @Sveino @griddigit Here is some feedback about the current representation. You can compare http://energy.referencedata.eu/EIC/53XPL000000OSMP5 to https://transparency.ontotext.com/resource/eic/53XPL000000OSMP5, which has the following data (Note "VIES" refers to the EU VAT Information Exchange System, in the Transparency project we consulted it regarding the validity of VAT numbers):
@prefix tr: <https://transparency.ontotext.com/resource/tr/>.
@prefix eic: <https://transparency.ontotext.com/resource/eic/>.
@prefix xsd: <http://www.w3.org/2001/XMLSchema#>.
eic:53XPL000000OSMP5> a tr:EnergyResource;
tr:addressInVies """DĘBOGÓRZE
RUMSKA 28
81-198 KOSAKOWO""";
tr:countryCode "PL";
tr:dateUpdated "2017-05-22"^^xsd:date;
tr:description "Consumer, Metered Point Operator, Network User, Party Connected To Grid, Storage System Operator";
tr:eic "53XPL000000OSMP5";
tr:eicType <https://transparency.ontotext.com/resource/type/Eic/X>;
tr:function "Consumer", "Information Provider",
"Meter Administrator", "Metered Data Aggregator", "Metered Data Responsible", "Metering Point Administrator",
"Metering Point Operator", "Network User", "Nomination Validator", "Party Connected To Grid",
"Storage System Operator";
tr:name "Gas Storage Poland sp. z o.o.";
tr:nameInVies "GAS STORAGE POLAND SPÓŁKA Z OGRANICZONĄ ODPOWIEDZIALNOŚCIĄ";
tr:notation "GSP";
tr:vatInVies true;
tr:vatNumber "PL5272643619";
tr:viesCheckDate "2022-02-14"^^xsd:date .
You can also see the EIC data that we map at https://transparency.ontotext.com/spec/#eic-fields and https://transparency.ontotext.com/spec/#eic-mapping.
schema:Thing
is not useful because it's too general,skos:Concept
is not correct: an individual is not a concept, only general concepts like ENTSOE lookup list values areEICCode_MarketDocument
is not correct: a document transmits that information, but the individual identified by EIC is an EnergyResource
(PowerSystemResource, MarketParticipant, Zone, etc)EnergyResource
is lackingdcterms:identifier
should be URI not string. This pertains both to http://energy.referencedata.eu/EIC and its members.
Eg instead of "urn:eic:53XPL000000OSMP5"
use <urn:eic:53XPL000000OSMP5>
skos:Collection.skos:member
. That's a valid approach, but when you download the resource's entity RDF, these inverse links are not present, so a linked data crawler cannot discover them. Please include the links: read about symmetric concise bounded description.<eicType/X>
, which means "Party". I.e. to represent the "meaning" of the 3rd letter of the EIC explicitlycim:DateAndOrTime.date
: it is not clear enough that this is "date updated"countryCode
is missing (MarketParticipantIsoCountryCode
in CSV, eICCode_MarketParticipant.streetAddress/townDetail/country
in XML)<http://energy.referencedata.eu/EIC/19XVSP---------I>
cim:Names.name
"A0001933F.PL", # ACER code
"Balance Responsible Party", # function
"Energy Supplier", # function
"PL6312241337", # VAT code
"TAURON_TSGZE" ; # name
parent
is missing (EicParent
in CSV, eICParent_MarketDocument.mRID
in XML). Eg eic:19XVSP---------I
should have parent eic:19XTAURON-PE-SAJ
responsibleParty
is missing (EicResponsibleParty
in CSV, eICResponsible_MarketParticipant.mRID
in XML). Eg eic:19W000000000203G
should have responsible eic:10XPL-TSO------P
Currently CIM flields are there
Some initial mapping:
But all fields form XSD should be mapped or then excluded