Open james-martin-jd opened 5 years ago
True. Problem is that we'd be breaking backward compatibility if we change this now. I probably want to wait until we have consensus about what fields to use by default.
For now, I would suggest to indeed stick to givenName
etc.
Maybe we could provide multiple aliases for the same predicate, to preserve backwards compatibiility
We have .givenName
and .familyName
set I believe; it might mainly be a matter of updating the examples.
Looking through the aliases for predicates in context.json, it was pointed out to me that some of them are specific to western audiences. For example, foaf:givenName being aliased as "firstName" is not very internationalization-friendly.