Re: Multiple types

Hi all,

Thanks for the responses. We will take advantage of the type 
multiplicity then in order to better model some additional free 
properties. We use additionalProperty to increase flexibility but groups 
should state how they intend to use them. This property expects a 
PropertyValue that has a value property expecting, for instance, a 
StructuredValue. So having to the possibility to add, for instance, 
MedicalCondition as type --in addition to StructuredValue, when we are 
modelling disease association, makes things clearer.

Examples on how we are using this will be available soon for the protein 
case.

Regards,


On 2017-09-14 15:29, Dan Brickley wrote:
> 1. Schema.org does support multiple types, in the sense that a single
> entity can be considered a member of multiple (independent) classes.
> 
> Canonical example would be a book, since you can describe this as a
> member of http://schema.org/Book and http://schema.org/Product
> 
> Note also that some core schema.org [4] types also have multiple
> independent supertypes, e.g. LocalBusiness (Organization + Place).
> 
> 2. Microdata did not have a direct notation to support this, which is
> why additionalType is provided. In JSON-LD or RDFa 1.1 you can use the
> native facilities of that notation to use a general typing mechanism,
> and no need for the schema.org [4] specific additionalType property.
> 
> 3. For several years, unfortunately Google's SDTT assumed that things
> had exactly one type. It still tends to complain if you mention
> something with 0 types, but it is now ok with multiple.
> 
> Hope this helps!
> 
> On 14 September 2017 at 12:55, Alejandra Gonzalez-Beltran
> <alejandra.gonzalezbeltran@oerc.ox.ac.uk> wrote:
> 
>> Hi again,
>> 
>> BTW, given the JSON-LD and microdata examples in
>> http://schema.org/additionalType [1], it might be that to specify
>> multiple types to be interpreted by the Google Structured Data tool,
>> you do need to use that property instead of a list of '@type' or
>> 'itemtype', respectively.
>> 
>> According to this:
>> 
>> 
> https://stackoverflow.com/questions/21961980/can-i-use-multiple-itemtypes-in-one-itemscope-for-schema-org
>> [2]
>> 
>> the tool didn't use to support the itemtype in microdata for
>> multiple types.
>> 
>> Maybe Dan can confirm if this has changed.
>> 
>> If you are using other tools, it should work.
>> 
>> Thanks,
>> 
>> Alejandra
>> 
>> On 14/09/2017 12:40, Alejandra Gonzalez-Beltran wrote:
>> Hi Leyla,
>> 
>> The multiple types issues is not about the vocabulary, but of the
>> languages you will be using to represent the metadata.
>> 
>> Where you asking if the Google Structured Data tool supports the
>> multiple types?
>> 
>> It seems that http://schema.org/additionalType [1] is a property
>> that allows you to specify another type for an entity, as per the
>> examples in that page (see microdata, JSON-LD), but as I understand
>> it, it is only to be used for adding types from a different
>> vocabulary in microdata (and probably this generated the need of
>> this property?).
>> 
>> Note that JSON-LD supports multiple types (see seccion 5.4 in the
>> spec https://www.w3.org/TR/json-ld/)
>> 
>> Microdata also supports multiple types as long as they are from the
>> same vocabulary:
>> https://www.w3.org/TR/2013/NOTE-microdata-20131029/#attr-itemtype
>> [3] And in RDFa you can use 'typeof' for multiple types.
>> 
>> Hope this helps,
>> 
>> Alejandra
>> 
>> On 14/09/2017 12:23, ljgarcia wrote:
>> Hello,
>> 
>> Does anyone know whether schema.org [4]. supports multiple types?
>> From http://schema.org/additionalType [1] I seems like it does.
>> 
>> I want to know if I can have an element with types StructuredValue
>> and MedicalCondition at the same time... so I can use properties
>> from both of them.
>> 
>> Regards,
> 
> 
> 
> Links:
> ------
> [1] http://schema.org/additionalType
> [2]
> https://stackoverflow.com/questions/21961980/can-i-use-multiple-itemtypes-in-one-itemscope-for-schema-org
> [3] https://www.w3.org/TR/2013/NOTE-microdata-20131029/#attr-itemtype
> [4] http://schema.org

Received on Friday, 15 September 2017 00:20:40 UTC