search

ejp-rd-vp / resource-metadata-schema

Metadata model and schemas for the EJP virtual platform
https://ejp-rd-vp.github.io/resource-metadata-schema/
Creative Commons Zero v1.0 Universal
14 stars 10 forks source link

Personal Data element in template #43

Closed markwilkinson closed 1 year ago

markwilkinson commented 1 year ago

The valid values for xsd:boolean are "true", "false", "1", "0"

yes/no are not valid values...

markwilkinson commented 1 year ago

By the way... the FAIR Data Point cannot create booleans... so we cannot enforce this...

markwilkinson commented 1 year ago

Decision: personal data element is optional; has a string value of "true" or "false" because we cannot capture booleans in the FDP anyway. Decision being ratified at the P2 meeting this friday

markwilkinson commented 1 year ago

PLEASE HOLD ON THIS CHANGE - there are still discussions happening, so this isn't decided yet

henrietteharmse commented 1 year ago

Wrt yes/no versus true/false or 1/0, I think we should distinguish between a template that is suppose to be human readable (my assumption!) vs machine readable. My reason for using yes/no rather than true/false or 1/0 is that I assumed people will fill in the template. However, this does not mean when imported it should be imported as yes/no. Rather, during import there should be a translation from yes->true/1 and no->no/0.

I just wanted to make clear the reason for using yes/no. But I am happy to change whichever way we decide.

markwilkinson commented 1 year ago

Final decision: personalData is optional, associated with Resource, and has the string value "true" or "false" (all lower case). (Making it mandatory will be at the level of onboarding policy decisions, not enforced at the level of the schema.)

henrietteharmse commented 1 year ago

Can be removed from all except Resource

henrietteharmse commented 1 year ago

personalData should be xsd:string for now.