Closed mgberg closed 3 months ago
@steveraysteveray Just a heads up in case you didn't know- the shape qudt:Concept-plainTextDescription
is causing 138 errors because some qudt:plainTextDescription
s have datatype rdf:langString
instead of xsd:string
and/or some resources have multiple values for that property.
I'm going ahead and merging this PR, but meanwhile, I'm not seeing any validation error with qudt:Concept-plainTextDescription. It's because back on 2024-03-22, we removed the sh:datatype xsd:string triple in that shape. This was when we were reworking the LaTex delimiters for dcterms:description, and ran into the plainTextDescription violations as well. We decided to relax the constraint. However, I don't think there are any remaining multiple values.
Bottom line, could you re-sync to the current main branch?
I'm going ahead and merging this PR, but meanwhile, I'm not seeing any validation error with qudt:Concept-plainTextDescription. It's because back on 2024-03-22, we removed the sh:datatype xsd:string triple in that shape. This was when we were reworking the LaTex delimiters for dcterms:description, and ran into the plainTextDescription violations as well. We decided to relax the constraint. However, I don't think there are any remaining multiple values.
Bottom line, could you re-sync to the current main branch?
@steveraysteveray Like the quantitykind file I mentioned above, my Composer got into a weird state. Those are gone after a Composer restart.
This adds:
unit:CAL_TH-PER-CentiM3-K
unit:CentiM2-PER-V-SEC
unit:ERG-PER-CentiM2
unit:J-PER-CentiM3-K
Also, this removes two lingering references to
quantitykind:CO2Equivalent
(which seems to no longer exist) to ensure SHACL validation passes.