You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But I'm tolerant towards reusing props in a wider context, so I think such use is ok
11: category, subCategory suggest that you should make another ConceptScheme, turn these values to Concepts and add broader relation between them
12: Similarly, systemId could be turned into a resource. At least, you can later attach multilingual labels to it; and it might be possible there is extra data about these system types?
13: systemId is not a precise name, systemType would be better. But I guess you generate all this automatically from CIM, so no manual tweaking is "allowed"
The text was updated successfully, but these errors were encountered:
"2022-02-18"
->"2022-02-18"^^xsd:date
"cim:ReadingQualityType"
is broken (string not URL)prefLabel "MeterReadingsQualityTypes"
is no label, which should be an English phrase not CamelCasedPhrasedefinition "Meter Reading Quality Types"@en
is no definition: that's the prefLabeldct:identifier
as in BaseVoltage.ttl."1.4.131"
inskos:notation
and remove it fromname
"Value Acquired By HHT"@en
inskos:prefLabel
dcat:version
might be a bit problematic:ConceptScheme
because https://w3c.github.io/dxwg/dcat/#Property:resource_version doesn't define a domain, and https://w3c.github.io/dxwg/dcat/#version-info only gives an example withdcat:Dataset
: can dcat:version be used on any resource? w3c/dxwg#1534category, subCategory
suggest that you should make anotherConceptScheme
, turn these values toConcepts
and addbroader
relation between themsystemId
could be turned into a resource. At least, you can later attach multilingual labels to it; and it might be possible there is extra data about these system types?systemId
is not a precise name,systemType
would be better. But I guess you generate all this automatically from CIM, so no manual tweaking is "allowed"The text was updated successfully, but these errors were encountered: