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
@zoe-translates That's correct. Really it needs to be any persistent identifier (PID) in the form of an URI/IRI, so we can take the RRID CURIE and express it as a full URI/IRI using a resolution service like identifiers.org.
So that's the full technical explanation; but that is overly complex for this section, I think.
I would happily review and clarification or simplification you would suggest!
Based on my understanding of the SoftwarePackage in the specification, the specs field should only list full IRIs, rather than compact IDs -- is that correct? Am I correct in assuming that the correct "resolution" of a compact ID to IRI (here using the identifiers.org redirect) is something the user should do, in order to maximize the interoperability of the CWL file being written?
Based on my understanding of the SoftwarePackage in the specification, the specs field should only list full IRIs, rather than compact IDs -- is that correct?
That is correct; full URI/IRIs only.
Am I correct in assuming that the correct "resolution" of a compact ID to IRI (here using the identifiers.org redirect) is something the user should do, in order to maximize the interoperability of the CWL file being written?
user_guide/src/topics/specifying-software-requirements.md
Line 29 in b6c2f66
Should this be uniform resource identifier? (Although I don't think the RRID has a formal URL scheme or URN namespace yet.)
The text was updated successfully, but these errors were encountered: