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
It doesn't make sense to have an extended ref on a Notional CITE Object, so we should not allow that at construction time for CITE URNs. We currently do.
I will fix that, but not until after the workshop in Kraków, this being no time to get into version-dependency hell ;-)
I have put a test in place that checks for this. It currently passes. Once I'm ready to edit the CITE code, I'll wrap it in a shouldFail { }.
The text was updated successfully, but these errors were encountered:
I will catch these in SparqlCC and reject them, for now. When we update the CITE library, those checks will become redundant, but they won't have much overhead.
It doesn't make sense to have an extended ref on a Notional CITE Object, so we should not allow that at construction time for CITE URNs. We currently do.
I will fix that, but not until after the workshop in Kraków, this being no time to get into version-dependency hell ;-)
I have put a test in place that checks for this. It currently passes. Once I'm ready to edit the CITE code, I'll wrap it in a shouldFail { }.
The text was updated successfully, but these errors were encountered: