# Make decisions regarding default vocabularies for footprints

**URL:** <https://forum.solidproject.org/t/make-decisions-regarding-default-vocabularies-for-footprints/412>\
**Category:** Solid App Development FAQs\
**Created:** [November 6, 2018, 2:10pm UTC](https://forum.solidproject.org/t/make-decisions-regarding-default-vocabularies-for-footprints/412 "2018-11-06T14:10:19Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![MitziLaszlo](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.solidproject.org/mitzilaszlo/32/191_2.png) [@MitziLaszlo](https://forum.solidproject.org/u/MitziLaszlo)\
**Post date:** [November 6, 2018, 2:10pm UTC](https://forum.solidproject.org/t/make-decisions-regarding-default-vocabularies-for-footprints/412/1 "2018-11-06T14:10:19Z")

</div>

@RubenVerborgh wrote:

### Long term

Since we’re using Linked Data, in the long term, whether data pods use `foaf:name` , `vcard:fn` , or `schema:name` shouldn’t really matter.

### Current issue

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.

#### Urgency

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.

#### Domain-specific

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:

- FOAF
- vCard
- [Schema.org](http://Schema.org)

### 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.

### Example

In [LDflex for Solid](https://github.com/solid/query-ldflex), we currently support;

- `solid.data.user.foaf_name`
- `solid.data.user['foaf:name']`
- `solid.data.user['http://xmlns.com/foaf/0.1/name']`
- `solid.data.user.vcard_fn`
- `solid.data.user['vcard:fn']`
- `solid.data.user['http://www.w3.org/2006/vcard/ns#fn']`
- `solid.data.user.schema_name`
- `solid.data.user['schema:name']`
- `solid.data.user['http://www.schema.org/name']`

However, there can only be one `name` :

- `solid.data.user.name`

and this currently is `http://xmlns.com/foaf/0.1/name` .  
But what should it really be?

There has been some discussion on [https://github.com/solid/solid/issues/222](https://github.com/solid/solid/issues/222) with @csarven, @codenamedmitri, and @kjetilk and would like to invite more here.

---

<div class="post-metadata">

**Author:** ![JornWildt](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.solidproject.org/jornwildt/32/112_2.png) [@JornWildt](https://forum.solidproject.org/u/JornWildt)\
**Post date:** [November 14, 2018, 9:40pm UTC](https://forum.solidproject.org/t/make-decisions-regarding-default-vocabularies-for-footprints/412/2 "2018-11-14T21:40:05Z")

</div>

Any consent on this? I guess not 🙂

Right now I am looking for the “right” way to label my items (either RC models or geographic locations).

This topic mentions `foaf:name`, `vcard:fn` and `schema:name`. But what about `rdfs:label` ([https://www.w3.org/TR/rdf-schema/#ch\_label](https://www.w3.org/TR/rdf-schema/#ch_label)) and `dcterms:title`([http://dublincore.org/documents/dcmi-terms/#terms-title](http://dublincore.org/documents/dcmi-terms/#terms-title))?

It really is a jungle, trying to find standard ways of describing resources. What about, for instance, related photos of an item … a thumbnail, a preview and the full size? Or a comment about something, or a description of an item?

---

<div class="post-metadata">

**Author:** ![JornWildt](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.solidproject.org/jornwildt/32/112_2.png) [@JornWildt](https://forum.solidproject.org/u/JornWildt)\
**Post date:** [November 15, 2018, 10:00am UTC](https://forum.solidproject.org/t/make-decisions-regarding-default-vocabularies-for-footprints/412/3 "2018-11-15T10:00:24Z")

</div>

And a follow up on the above, should anyone look for inspiration, [schema.org](http://schema.org) is a great place to find standards for al sorts of “things” one might want to store, which seems a bit better or just more concrete than using the abstract dctertms.

---

<div class="post-metadata">

**Author:** ![pheyvaer](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.solidproject.org/pheyvaer/32/635_2.png) [@pheyvaer](https://forum.solidproject.org/u/pheyvaer)\
**Post date:** [November 15, 2018, 10:41am UTC](https://forum.solidproject.org/t/make-decisions-regarding-default-vocabularies-for-footprints/412/4 "2018-11-15T10:41:36Z")

</div>

> [@MitziLaszlo](#):
>
> However, there can only be one `name` :
> 
> - `solid.data.user.name`
> 
> and this currently is `http://xmlns.com/foaf/0.1/name` .  
> But what should it really be?

Can’t we have here a fallback system? First try foaf, next try schema, next try vcard. And ideally you can configure that yourself. That’s how I would write my SPARQL query if I know that multiple ontologies can be used.

---

<div class="post-metadata">

**Author:** ![pheyvaer](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.solidproject.org/pheyvaer/32/635_2.png) [@pheyvaer](https://forum.solidproject.org/u/pheyvaer)\
**Post date:** [November 15, 2018, 10:43am UTC](https://forum.solidproject.org/t/make-decisions-regarding-default-vocabularies-for-footprints/412/5 "2018-11-15T10:43:33Z")

</div>

> [@JornWildt](#):
>
> Right now I am looking for the “right” way to label my items (either RC models or geographic locations).

Important to note here is that there no “right” away in any case. In the sense that it’s the right way for everybody. It’s all fitness-for-use.
