Re: quick question about polymorphism in schema.org

Hi,

Thanks Alasdair. It was part of the process of letting you know about
the deployment for the bioschema deployment list, that I checked how the
example would appear and found the problem.

Stian has suggested a workaround could be to declare the type as both
Project and Organization ( @type:["Project","Organization"]) which
appears to work and make the tool happy. In this case, I don't think
we've used any Project specific attributes so should be OK. Infact, I've
just double checked and there aren't any. In this case, and since its
pending, I think we'll just use Organization for the time being.

many thanks,

Stuart

On 04/10/2019 09:40, Gray, Alasdair J G wrote:
> Hi Stuart,
>
> Great to hear that markup will soon be included in SEEK. Once this is
> done, please let us know the deployment locations so that we can add
> these to the list of live deploys.
>
> I cannot speak for the inner workings of the Google structured testing
> tool. There are two possible causes. First is that Project is still in
> the pending part of schema.org <http://schema.org> and the structure
> data testing tool is using an older context (I believe that the tool
> does not load the context dynamically). Second is that the tool does
> not apply class hierarchy reasoning and therefore does not infer that
> things that are of type Project are also of type Organization.
>
> It is probably safe to ignore the error since RDF aware tools will
> correctly characterise a Project as being an Organization, and I
> believe that Google’s tool chain is quite relaxed about typing and
> errors in the markup.
>
> I hope this helps
>
> Alasdair
>
>> On 3 Oct 2019, at 13:32, Stuart Owen <stuart.owen@manchester.ac.uk
>> <mailto:stuart.owen@manchester.ac.uk>> wrote:
>>
>> Hi,
>>
>> I guess this is more of a schema.org <http://schema.org> question,
>> rather than bioschema.org <http://bioschema.org> specifically, but
>> still relevant and hopefully somebody can help.
>>
>> Thanks to some productive days at the ELIXIR UK Hackathon, we've now
>> added and deployed quite a lot of new Bioschema descriptions to
>> https://fairdomhub.org and will be included in our next SEEK release.
>> When testing with Googles structured data testing tool, I've noticed
>> it reports an error due to a link from Dataset#provider to a Project,
>> when it expects and Organization (or Person). However, Project is a
>> subclass of Organization, so I'd expect it to be OK.
>>
>> Should I be concerned about this, or is it safe to say its a
>> limitation of the Structured Testing tool?
>>
>> thanks,
>>
>> Stuart.
>>
>>
>>
>
> --
> 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
> ORCID: http://orcid.org/0000-0002-5711-4872
> Office: Earl Mountbatten Building 1.39
> Twitter: @gray_alasdair
>
> To arrange a meeting: http://doodle.com/ajggray
>
> Untitled Document
> ------------------------------------------------------------------------
>
> */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. 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.
>