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
This would require a change in the CEDS element directly since the element PESC Award Level Type element contains both of those codes. If PESC lists both sets in their element, then CEDS would replicate that. If they have removed one, then CEDS can make the change to remove one as well. And you are correct, we do need to review the "creator" section for elements that are pulled from other standards.
Thank you @AEMDuaneBrown I will check with my friends at PESC on this, but the documentation that I have does not suggest that they use the IPEDs terms. It's possible though that they use them somewhere else.
Either way, I still don't think it is a good idea for CEDS to publish IPEDS levels in a scheme called PESC Award Level Types. It would be better to separate them from the PESC levels and say that the PESC property can take values from both schemes.
There are several members of PESC Award Level Type that are near identical. For example:
and
I can recognize from the codes used for skos:notation that the former comes from PESC and the latter from IPEDS, but this isn't explicit.
It seems wrong to put IPEDS codes in a values space called after PESC.
If you need both you could have an IPEDS Award Level Type and allow values from either it or or the PESC scheme.
(I won't comment on listing CEDS as the creator of either PESC or IPEDS classification schemes)
The text was updated successfully, but these errors were encountered: