W3C home > Mailing lists > Public > public-bioschemas@w3.org > November 2017

Re: Protein representation with and without BioChemEntity

From: Gray, Alasdair J G <A.J.G.Gray@hw.ac.uk>
Date: Thu, 2 Nov 2017 12:04:55 +0000
To: Melanie Courtot <mcourtot@ebi.ac.uk>
CC: Justin Clark-Casey <justinccdev@gmail.com>, "public-bioschemas@w3.org" <public-bioschemas@w3.org>
Message-ID: <C2324C62-CBCB-42E5-85F8-8498A2DE50C0@hw.ac.uk>
Hi Melanie,

I think we are talking at cross purposes. The three examples show different ways of representing a protein.

My original motivation was to compare the BioChemEntity wrapper approach using additionProperty with an approach that would involve the Bioschemas community proposing multiple new types to schema.org<http://schema.org>*. When I discussed these two examples with Dan, he pointed out that we don’t need to use additionalProperty, we can just use the ontology terms directly. In the first and third example, i was just using the ontology terms that were proposed by the Protein Group in the Protein Profile. In the second example, I was playing with the idea that we create these properties in schema.org<http://schema.org>.

The markup in the first example, BioChemEntity with additionalProperty, is complex and increases the complexity of the tools needed for creating and consuming that markup. The third set of examples, using the ontology terms directly, gives us a simplified markup and therefore simplifies our tooling. It will also make adoption more straightforward. It would be up to the profiles to decide which are the appropriate ontology terms to use.

I hope this clears things up

Alasdair

*This approach was ruled out in the May meeting, but I felt that it was important to do a comparison of the two approaches with a concrete example

On 2 Nov 2017, at 10:34, Melanie Courtot <mcourtot@ebi.ac.uk<mailto:mcourtot@ebi.ac.uk>> wrote:

Hi Alastair,

I'm not sure I understand, are you talking about validating profiles? For validation purpose wouldn't it be equivalent to look for a string such as "isContainedIn" or a URI such as http://purl.obolibrary.org/obo/RO_0001018, where the latter has the advantage to not duplicate existing terms as well as offering dereferencing, hierarchy and flexibility?

I'll admit being a bit confused between the 3 examples, so I may be overlooking something.

Cheers,
Melanie

Alasdair J G Gray

Fellow of the Higher Education Academy
Assistant Professor in Computer Science,
School of Mathematical and Computer Sciences
(Athena SWAN Bronze Award)
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
ORCID: 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:

  1.  Heriot-Watt University, a Scottish charity registered under number SC000278
  2.  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
  3.  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 Thursday, 2 November 2017 12:05:22 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:08:00 UTC