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

Re: Abstract services and organisations under LocalBusiness

From: Marco Brandizi <marco.brandizi@gmail.com>
Date: Wed, 7 Jun 2017 21:21:44 +0100
To: Martin Hepp <mfhepp@gmail.com>
Cc: "schema.org Mailing List" <public-schemaorg@w3.org>
Message-ID: <20df81b9-e894-ca89-4f14-9dc9db07d987@gmail.com>
Hi Martin,

that's very useful information, thank you so much.

The problem I have is I'd like to model something like bank 
(schema:BankOrCreditUnion), I'd like to standardise it a bit by using 
schema.org, but in my context I mean the bank as the whole organisation, 
not one of its locations (I have them too). I understand the point of 
view of schema.org, not ideal for my case, but I will try to adapt my 
case to it.

Best,
Marco


On 07/06/2017 18:15, Martin Hepp wrote:
> Marco:
>
> The underlying GoodRelations model uses two distinct types for this
>
>      http://purl.org/goodrelations/v1#BusinessEntity
>
> for the legal agent and
>
>      http://purl.org/goodrelations/v1#Location
>
> for a place from which goods or services, or rights on these, can be obtained.
>
> In schema.org, the business entity is either a schema:Organization or schema:Person (there is to date no common superclass, like schema:Agent despite quite some argument for such a type).
>
> Places are modeled as schema:LocalBusiness.
>
> Now, in schema.org, schema:LocalBusiness is hard-wired to be a subtype of both schema:Place and schema:Organization, because in most practical cases ("Joe's Pizza Place"), the two entities are practically conflated and many owners would find it a mere exercise to model the two distinct entities behind it. Often, available data also does not readily provide the distinction; so it makes sense to have this somewhat blurry type.
>
> Linking between the legal entity and its points of sale is easy; simply use http://schema.org/hasPOS between the two.
>
> Now, as for the subtypes of schema:LocalBusiness: I am no big fan of modeling the range of products and services by subtyping schema:LocalBusiness.
> Way more flexible and conceptually cleaner is it to model the range of products and services via a schema:Offer type attached to the entity. Note that you can perfectly model a schema:Offer with just a textual description of what you offer in the schema:name and schema:description properties.
>
> Hope this helps.
>
>
> Best
>
> Martin
> -----------------------------------
> martin hepp  http://www.heppnetz.de
> mhepp@computer.org          @mfhepp
>

-- 

=========================================================================
Marco Brandizi <marco.brandizi@gmail.com>
http://www.marcobrandizi.info
Received on Wednesday, 7 June 2017 20:22:19 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:12:35 UTC