Consider optional GivenName and FamilyName for people
See original GitHub issueIt is best practice (e.g. schema.org) to allow givenName
and familyName
in addition to name
. Makes it easier to generate correct citation, as names frequently need to be formatted.
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
How should I fill the "First name" and "Last name" in an ...
For the first name, put whatever you want people to actually call you. · For the last name, put both names, or else...
Read more >SEVIS Names FAQ - Study in the States
Q: Why do the standards say that Given Name is optional? A: Not everybody has more than one name. If you have only...
Read more >Why Your Form Only Needs One Name Field - UX Movement
Single “Full Name” Field A single field labeled “Full Name” is more culturally inclusive. The full name may include first, middle, last, family ......
Read more >Personal names - Internationalization
Given a three-word name, you can't tell whether it's two given names and a family name, like John Jacob Astor, or a given...
Read more >Personal name - Wikipedia
This article is about the full names of individual human beings. For the name distinguishing one person from others with the same surname,...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yup, this makes sense to me,
Note that since we’re essentially defining a vocabulary, not a schema, nothing actually prevents you from using these existing
schema.org
terms in yourcodemeta.json
, e.g.:Is just as good as:
the only difference being that you have to use the namespace since
name
is explicitly in thecontext
and so fargivenName
&familyName
are not.For programmatic use, I believe we ought to be defining a JSON frame (#128) for framing input jsonld into a practical & predictably structured JSON tree. We don’t have such a frame defined yet; I suppose it should just permit all three options as possible members of an agent (e.g.
name
,givenName
andfamilyName
?)This has been added to the proposed codemeta-v2.jsonld, which goes along with the re-alignment towards schema.org anyhow (#134). So closing this out as subsumed by #134