Closed turbomam closed 2 years ago
"Due diligence"
% grep -i mail src/schema/*
mixs.yaml: range: text value ## syntax: "[attic|bathroom|closet|conference room|elevator|examining room|hallway|kitchen|mail room|private office|open office|stairwell|,restroom|lobby|vestibule|mechanical or electrical room|data center|laboratory_wet|laboratory_dry|gymnasium|natatorium|auditorium|lockers|cafe|warehouse] " mixs.yaml: pattern: "[attic|bathroom|closet|conference room|elevator|examining room|hallway|kitchen|mail room|private office|open office|stairwell|,restroom|lobby|vestibule|mechanical or electrical room|data center|laboratory_wet|laboratory_dry|gymnasium|natatorium|auditorium|lockers|cafe|warehouse]" mixs.yaml: range: text value ## syntax: [attic|bathroom|closet|conference room|elevator|examining room|hallway|kitchen|mail room|office|stairwell] mixs.yaml: pattern: "[attic|bathroom|closet|conference room|elevator|examining room|hallway|kitchen|mail room|office|stairwell]"
the orcid
slot is define in core.yaml
I'd like to give this a domain, but I think entities other than people can have an email address. Should I assert a domain of 'named thing', or is that implicit? Is there something with the right specificity between 'named thing' and 'person value'?
Should I assert a format/pattern or get anything started to enable validation? I know that's a slippery slope when it comes to email addresses. 'orcid' is defined with a string range and no pattern.
the following email slot has been merged into core.yaml
description: >-
An email address for an entitity such as a person
range: string
notes: >-
More specific domain? Acceptable pattern? https://emailregex.com/ ?
possible followups:
multivalued: true
?Add foaf:mbox
IRI? Would need a prefix definition?
@cmungall suggests using https://schema.org/email.
They give a sample object of "mailto:jane-doe@xyz.edu". Would we want to include that service prefix, or just stick to the email address proper?
@cmungall also mentioned mapping to foaf or even obi email terms if available. Pushed slot_uri: schema:email
as above, but no mappings yet.
Will take a string, like the orcid slot does. But maybe 0..inf cardinality?