Skip to content
This repository has been archived by the owner on Feb 16, 2022. It is now read-only.

Use link for contact field #31

Open
duckontheweb opened this issue Sep 7, 2021 · 0 comments
Open

Use link for contact field #31

duckontheweb opened this issue Sep 7, 2021 · 0 comments
Assignees
Labels
change Involves change to existing spec discussion needed Requires further discussion/input before implementing

Comments

@duckontheweb
Copy link
Collaborator

contacts has email required. I'd go the STAC way here to allow (and require?) a URL to be able to link to a more detailed (contac?) page where you usually can get more details. Requiring e-mail could is not so nice because some people may not like to provide one in an easily machine readable way to avoid spamming etc. Why is organization different from name? Usually it seems a general name property is enough to fullfill both personal and organizational contributions. Also, names (and emails) get quickly outdated with people switching companies etc. Roles from STAC could also be useful (host, creator, licensor, etc). So proposal is name (required), url (maybe required), roles (maybe required) and email (not required).

Originally raised in #25

@duckontheweb duckontheweb added discussion needed Requires further discussion/input before implementing change Involves change to existing spec labels Sep 7, 2021
@duckontheweb duckontheweb self-assigned this Sep 7, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
change Involves change to existing spec discussion needed Requires further discussion/input before implementing
Projects
None yet
Development

No branches or pull requests

1 participant