Specialise the Related Service and Spatial properties

Description

This issue was raised by Dieter De Paepe through the mailing list:

The Related Service property is mapped to dct:relation, which has a pretty vague definition: "A related resource...". As this might overlap with other uses of dct:relation, I suggest subclassing this property.

Same remark as previous for use of spatial, which is defined as "Spatial characteristics of the resource."

 

Proposed solution

Unless there is a specific need from the WG, we would propose to leave both properties as they are since we want to reuse existing specifications as much as possible.

Component

Documentation

Category

improvement

Comments

Mon, 18/09/2017 - 13:56

Tue, 19/09/2017 - 13:40

Allow me to clarify my issue:

 

My service descriptions (semantically correct).

:myService :issueTracker <http://example.com/issues&gt;.

:myService dct:related :myService2.

 

My own ontology (semantically correct).

:issueTracker a rdf:Property.

:issueTracker rdfs:subProperty dct:related

 

However, a reasoning-enabled client will now think my issue tracker is a service.

Login or create an account to comment.