Since we’re using Linked Data, in the long term, whether data pods use
vcard:fn , or
schema:name shouldn’t really matter.
However, in the short term, app developers need clear expectations about what kind of properties to ask for. If one application writes
foaf:name , another reads
vcard:fn , and a third writes
schema:name , not only will we fail at interoperability, we will also have data inconsistencies.
Having a default choice is important, because while everything is possible, only one thing can be made easy. E.g., in a JSON-LD context, there can only be one
firstName ; the rest will have to be prefixed names or fully qualified URLs. So which one should it be? Since the dev kit is starting to take shape, this discussion is becoming urgent.
This decision might need to be made per domain, i.e., different for people, photos, etc.
Maybe a good first question is how to model profiles. I see three broad choices:
Call for input
Good arguments can be made for each one, and please make yours below (I will). But the more important one is that we make a decision and document it.
In LDflex for Solid, we currently support;
However, there can only be one
and this currently is
But what should it really be?