The following entries are marked with "namespaceEmbeddedInLui": true, but I do not think they should not be. None of their sample identifiers actually contain the prefix, and the CURIE that follows https://identifiers.org/{curie} also is completely normal, following the same pattern as all of the other entries with "namespaceEmbeddedInLui": false.
Additionally, all of the provider's format strings seem to only take in the identifier (though some do seem to also contain hard-coded copies of the prefix), so is it that I am misunderstanding the usage of "namespaceEmbeddedInLui"?
This is of general importance because given a prefix/identifier pair, it is still often unclear how to construct a valid URL for identifiers.org. Typically, examples marked with "namespaceEmbeddedInLui": true come from the OBO world where the solution is to uppercase the prefix to make a valid URL for identifiers.org, but beyond this, there don't seem to be any general rules for how to handle true entries.
cc: @bgyori @dhimmel @cgreene this might be of interest to you too
The following entries are marked with
"namespaceEmbeddedInLui": true
, but I do not think they should not be. None of their sample identifiers actually contain the prefix, and the CURIE that followshttps://identifiers.org/{curie}
also is completely normal, following the same pattern as all of the other entries with"namespaceEmbeddedInLui": false
.Additionally, all of the provider's format strings seem to only take in the identifier (though some do seem to also contain hard-coded copies of the prefix), so is it that I am misunderstanding the usage of
"namespaceEmbeddedInLui"
?This is of general importance because given a prefix/identifier pair, it is still often unclear how to construct a valid URL for identifiers.org. Typically, examples marked with
"namespaceEmbeddedInLui": true
come from the OBO world where the solution is to uppercase the prefix to make a valid URL for identifiers.org, but beyond this, there don't seem to be any general rules for how to handletrue
entries.cc: @bgyori @dhimmel @cgreene this might be of interest to you too
This table was generated with the following code: