Re: Property reuse versus property minting

Hi Alasdair, all,

The google doc points to this thread as the place to follow discussion regarding the Taxon proposed entity. In the specific case of Taxon I would prefer to reuse the NCBI taxonomy directly - it is a well established vocabulary, and we could easily include it if we were to use the construct from the sample specification <http://bioschemas.org/specifications/Sample/>, in which we use categoryCode with ontology terms.

As indicated in the spec, the *only* change needed for this to work is to include CategoryCode as an expected type for valueReference.

Cheers,
Melanie 


> On 30 Oct 2018, at 09:11, Gray, Alasdair J G <A.J.G.Gray@hw.ac.uk> wrote:
> 
> Hi All,
> 
> The following question has been raised by Franck Michel in the current proposal for Bioschemas (review period ends on Thursday).
> https://docs.google.com/document/d/1Cw9K25N1l-Lbet1cahJuFtYgNKiF76apGcCqJPSeuZg/edit?usp=sharing <https://docs.google.com/document/d/1Cw9K25N1l-Lbet1cahJuFtYgNKiF76apGcCqJPSeuZg/edit?usp=sharing>
> 
> "When do we reuse existing properties from other ontiologies?"
> 
> The approach taken in developing the proposal was that any property that was minimal or recommended should be minted as new properties. Properties that were optional were OK to be taken from existing ontologies. However, we do need to consider the logical implications of the latter. Newly minted properties have been mapped (the exact mapping term is up for discussion) to the existing ontology term that was previously identified.
> 
> The rationale for this decision was that the minimal and recommended properties would then be understood by generic consumers, e.g. the major search engines, and could be exploited in returning rich snippets. 
> 
> This is about trying to strike the right balance between adding a limited set of additional types and properties to schema.org <http://schema.org/> and not reinventing all the work that has taken place in ontology development in the life sciences.
> 
> This email thread is your chance to help shape this design decision for the development of future Bioschemas profiles.
> 
> Best regards
> 
> Alasdair
> 
> --
> Alasdair J G Gray
> Associate Professor in Computer Science, 
> School of Mathematical and Computer Sciences 
> Heriot-Watt University, Edinburgh, UK.
> 
> Email: A.J.G.Gray@hw.ac.uk <mailto:A.J.G.Gray@hw.ac.uk>
> Web: http://www.macs.hw.ac.uk/~ajg33 <http://www.macs.hw.ac.uk/~ajg33>
> ORCID: http://orcid.org/0000-0002-5711-4872 <http://orcid.org/0000-0002-5711-4872>
> Office: Earl Mountbatten Building 1.39
> Twitter: @gray_alasdair
> 
> Heriot-Watt University is The Times & The Sunday Times International University of the Year 2018
> 
> Founded in 1821, Heriot-Watt is a leader in ideas and solutions. With campuses and students across the entire globe we span the world, delivering innovation and educational excellence in business, engineering, design and the physical, social and life sciences. 
> 
> This email is generated from the Heriot-Watt University Group, which includes:
> 
> Heriot-Watt University, a Scottish charity registered under number SC000278
> Edinburgh Business School a Charity Registered in Scotland, SC026900. Edinburgh Business School is a company limited by guarantee, registered in Scotland with registered number SC173556 and registered office at Heriot-Watt University Finance Office, Riccarton, Currie, Midlothian, EH14 4AS 
> Heriot- Watt Services Limited (Oriam), Scotland's national performance centre for sport. Heriot-Watt Services Limited is a private limited company registered is Scotland with registered number SC271030 and registered office at Research & Enterprise Services Heriot-Watt University, Riccarton, Edinburgh, EH14 4AS. 
> The contents (including any attachments) are confidential. If you are not the intended recipient of this e-mail, any disclosure, copying, distribution or use of its contents is strictly prohibited, and you should please notify the sender immediately and then delete it (including any attachments) from your system.
> 

Received on Wednesday, 31 October 2018 10:38:08 UTC