WCMP2 ID s/reco/recommended/g #65
Conversation
There was a problem hiding this comment.
I am not convinced this update is required. The metadata-id needs to be unique for each dataset, there is no requirement for it to contain the fully spelled out data-policy.
If we do want to include the word "recommended" in the metadata-id I would bundle this with an update to abbreviate the metadata-id in the templates to avoid strings exceeding the size of the display in the form.
|
Correct, there is no requirement for the "local identifier" token of a WCMP2 id. At the same time, in the wis2box context there is an inconsistency ("core -> core", "recommended" -> "reco"), driven by a user interface layout. I'm fine if we can discuss a consistent approach to "local" identifiers in wis2box without morphing official values into conventions driven by a UI. |
|
How about we use "rcmd" instead of "reco" or "recommended" in the id as the wis2box-convention ? |
|
If we are going to use the WTH data policy as part of the WCMP2 id, then we should use the canonical values and not aliases or shortcuts/conventions. Is there even a requirement for having the data policy as part of the WCMP2 id? |
No description provided.