W3C home > Mailing lists > Public > public-schemaorg@w3.org > June 2020

RE: Project and outputs

From: Cox, Simon (L&W, Clayton) <Simon.Cox@csiro.au>
Date: Sun, 14 Jun 2020 02:17:06 +0000
To: Hugh Paterson III <sil.linguist@gmail.com>, "public-schemaorg@w3.org" <public-schemaorg@w3.org>
Message-ID: <ME2PR01MB288271270CE1FC0837CC04DF889F0@ME2PR01MB2882.ausprd01.prod.outlook.com>
Maybe some insights here: http://linked.data.gov.au/def/project

It adopts PROV-O `prov:generated` for outputs, which is an `owl:ObjectProperty` which means the object is a URI.
Of course that could denote anything. A DOI or a code repository are options.

Simon

From: Hugh Paterson III <sil.linguist@gmail.com>
Sent: Sunday, 14 June, 2020 04:03
To: public-schemaorg@w3.org
Subject: Project and outputs

Greetings,

I've been loosely watching some of the discussion which has been happening around describing projects in schema terms. https://schema.org/Project (and in my case https://schema.org/ResearchProject)

I'm wondering if or how people are describing the outputs of a project. As my use case I have an academic research project with several publications, several presentations (which are events which feature creative works — but not in any sense that the current documentation insinuates), and a dataset. One potential I see is to use something like hasPart or https://schema.org/isPartOf to describe the relationship between the project and output.

But the design intent for https://schema.org/isPartOf seems to be that it is used between two creative works rather than a conceptualized grouping of activities (a project) and some creative work(s).

Another option is to classify a project as an event (a really long event) which also seems to be abuse of "event".

I could stretch and think of a paper or dataset (which can both be described via schema terms) as a product of the project, but this seems to be a stretch.

Does anyone have any suggestions? Surely I'm not the first to try and cross this bridge ;-)

Thanks in advance,
all the best,
- Hugh


Received on Sunday, 14 June 2020 02:17:29 UTC

This archive was generated by hypermail 2.4.0 : Sunday, 14 June 2020 02:17:31 UTC