Consider adopting DASH property roles in SHACL

[bergos]

The DASH vocabulary defines property roles that are used to indicate the function or purpose of properties within a shape.

These roles are especially useful in UI use cases (labels or icons), but some may have broader usage outside the UI context.

The DASH specification currently defines the following property roles:

• dash:LabelRole: labels or names of the resource
• dash:DescriptionRole: summary texts describing the resource
• dash:IconRole: icons for the resource or its type
• dash:DepictionRole: images depicting the individual resource
• dash:IDRole: identifiers, often unique and machine-readable
• dash:KeyInfoRole: other relevant values that should be rendered in summaries

But there are also non-UI-specific roles, particular dash:IDRole. That property role, but maybe also others could be relevant for other specifications.

Are there existing or potential use cases where property roles could be used in other SHACL-related specifications?

Should we consider bringing the generic concept of property roles into SHACL namespace? UI or core?

[danielbeeke]

Here are two additional use cases:

SearchRole or SearchableContentRole

This property role would specify that this property should be used when searching over resources. An implementer could use it then to generate more specific search queries or could add the triples containing the property as predicate to the search index.

SubTitleRole or ClassificationRole

In SKOS there are skos:ConceptSchemes, each concept is linked to a concept scheme via skos:inScheme. When searching over concepts in a dash:AutoCompleteEditor it would be nice to see the title of each skos:Concept via dash:LabelRole and then after the title the rdfs:label of the skos:ConceptScheme the concept is attached to.

This can also be used for regular resources to display its rdf:type.