@iyoung noted that some roles enforce the use of URI type and some don't:
descriptions/role: string
bodies/role: string
headlines/role: string
infosources/role: string of type uri
altids/role: string
trustindicators/role: string of type uri
advices (dev) / role: string of type enum (only one value, "publish" so far)
should we make these consistent? Otherwise it's a bit confusing for implementors.
Solution:
Current thinking is that we could simplify the schema to make them strings, but recommend the use of the CV. It might be enough for users to just use the term name without the full URI.
@iyoung noted that some roles enforce the use of URI type and some don't:
descriptions/role: string bodies/role: string headlines/role: string infosources/role: string of type uri altids/role: string trustindicators/role: string of type uri advices (dev) / role: string of type enum (only one value, "publish" so far)
should we make these consistent? Otherwise it's a bit confusing for implementors.
Solution: Current thinking is that we could simplify the schema to make them strings, but recommend the use of the CV. It might be enough for users to just use the term name without the full URI.
But we haven't agreed that for sure yet.