Terms for Classes and Properties

[jeff-zucker]

Here are my current suggestions for the terms and ontologies to support the catalog. These do not require any new vocabulary terms although we should probably makes sure we are using the terms as intended in the existing ontologies and then perhaps consider creating new terms.

temporary name     DCAT equivalent   range
-------------------------------------------------------------------------------
name               dct:title         string
subType            dct:type          skos:Concept
description        dct:description   string
about              foaf:primaryTopic dcat:Resource
technicalKeyword   dcat:theme        skos:Concept  # temporarily string
softwareKeyword    dcat:theme        skos:Concept  # temporarily string
landingPage        dcat:landingPage  dcat:Document
provider           dcat:publisher    schema:Person or schema:Organization
status             adams:status      skos:Concept
serviceEndpoint    dcat:endpointURL  rdfs:Resource
webAppEndpoint     dcat:endpointURL  rdfs:Resource
partOf             dct:isPartOf      schema:Product
serviceBackend     dct:requires      schema:Product
serviceFrontend    dct:requires      schema:Product

temporary name     possible equivalent
--------------------------------------
Service            schema:Service
Product            schema:Product or maybe schema:SoftwareApplication
LearningResource   schema:LearningResource
Event              schema:Event
Person             schema:Person
Organization       schema:Organization
Specification      doap:Specification
Ontology           owl:Ontology
contactEmail       vcard:hasEmail
logo               vcard:hasPhoto
namespaceURI       vann:preferredNamespaceUri
prefix             vann:preferredNamespacePrefix
schedule           schema:eventSchedule
serviceAudience    doap:audience
resourcesWanted    schema:ofers
resourcesOffered   schema:ofers
forumHandle        foaf:accountName    see [solidOS profile](https://github.com/SolidOS/profile-pane/blob/main/src/ontology/profileForm.ttl#L447)
matrixHandle       foaf:accountName
repository         doap:repository
videoCallPage      meet:videoCallPage  # from the pim/meeting ontology
webID              vcard:url           see [WebIdShape](https://github.com/solid/contacts/blob/main/shapes/contacts-shapes.ttl#L191)
clientID           vcard:url

[elf-pavlik]

There is already some relevant feedback across

• PersonShape #16
• Align Software and Specification with specification-tests #18
• Modeling Services (Deployments) #22

Do you want to use this issue as an epic to keep track of conversations across all the other issues?

[jeff-zucker]

Those three discussions relate to what the shapes should look like and I think we should continue those discussions there. This issue is meant more for what terms/'ontologies we use. So the other discussions may result in some of the above terms being modified or removed and other terms added. But, my guess is that most of the above will probably remain and we'll need to find terms for them. So, let's use this issue to discuss what we call things and other issues to discuss the shapes. We can start with terms in the above list we all agree should be present in one form or another.

Deciding on these terms is not our highest priority but I've posted it now because I think we need to keep it in mind for such things as the SKOS discussion. We need to decide how high a priority it is for us to remain DCAT compatible so I've shown the correspondences so far as I can see them. Also, this makes it clear for which predicates DCAT defines a range of skos:Concept. Our discussion of use of SKOS for ProductClass must occur in this larger context of how SKOS is used in DCAT and how it currently works in the catalog, those being AFAIK the same at the moment.