This is a question about providing "generic" descriptions for slots that come from external sources and are reused by several classes.
We are using a name slot (property), with slot_uri: schema:name on several classes (Dataset, DataController, and Author, see generated docs), with different definitions ("Identifies the dataset uniquely..." vs "The full name of the responsible entity"... vs. "The full name of the author").
This is modelled in yaml as a slot with just the URI:
slots:
name:
slot_uri: schema:name
and each class listing it in slots and defining description in slot_usage.
This means that we do not define any description for the name slot, see generated docs: name but also the slot table in the docs home page.
Should we:
add a generic description, like "name of something or someone"
use the definition from https://schema.org/name, since that's the URI we use ("The name of the item")
how to acknowledge reuse, to satisfy the CC-BY-SA license of schema.org (see schema FAQ)
e.g. linkml has created_by property that can be used (not included in default doc page template)
have no generic description for name, define it only per-class
This is a question about providing "generic" descriptions for slots that come from external sources and are reused by several classes.
We are using a
name
slot (property), withslot_uri: schema:name
on several classes (Dataset
,DataController
, andAuthor
, see generated docs), with different definitions ("Identifies the dataset uniquely..." vs "The full name of the responsible entity"... vs. "The full name of the author").This is modelled in yaml as a slot with just the URI:
and each class listing it in
slots
and defining description inslot_usage
.This means that we do not define any description for the name slot, see generated docs: name but also the slot table in the docs home page.
Should we:
created_by
property that can be used (not included in default doc page template)name
, define it only per-class