W3C home > Mailing lists > Public > public-schemaorg@w3.org > September 2016

Re: Non-schema.org ontologies

From: Martin Hepp <mfhepp@gmail.com>
Date: Fri, 2 Sep 2016 10:49:16 +0200
Cc: Thad Guidry <thadguidry@gmail.com>, Dan Brickley <danbri@google.com>, "schema.org Mailing List" <public-schemaorg@w3.org>
Message-Id: <99F7A98E-186D-4702-AD05-6568B0120DC2@gmail.com>
To: Timothy Holborn <timothy.holborn@gmail.com>
This

> It's seemingly far more complicated than i'd first considered.  Even simply with toilet's - they're not the same around the world.  If people travelling are familiar with one style of toilet, they may really value finding one in a territory that has different culturally influenced outcomes.

is why I designed additionalProperty: for exactly those cases where a single, global model of information is either not feasible due to cultural differences or where it cannot be populated from existing data structures (e.g. back-end databases).

With https://schema.org/amenityFeature, we should be able to handle all these cases.

Note that https://schema.org/LocationFeatureSpecification is a subptype of https://schema.org/PropertyValue with all of its propertis, so you can easily add e.g. identifiers to external standards.

For instance schema:value can be applied to any LocationFeatureSpecification and accepts

https://schema.org/StructuredValue and thus all of its subtypes:

	• ContactPoint
	• EngineSpecification
	• GeoCoordinates
	• GeoShape
	• InteractionCounter
	• MonetaryAmount
	• NutritionInformation
	• OpeningHoursSpecification
	• OwnershipInfo
	• PriceSpecification
	• PropertyValue
	• QuantitativeValue
	• TypeAndQuantityNode
	• WarrantyPromise




-----------------------------------
martin hepp  http://www.heppnetz.de
mhepp@computer.org          @mfhepp




> On 01 Sep 2016, at 18:16, Timothy Holborn <timothy.holborn@gmail.com> wrote:
> 
> Dan,
> 
> It's 1:44am here.  I'll respond more tomorrow.  I started writing a response; but i want to draft it more, so tomorrow is better for me to do that.
> 
> Thad,
> 
> I think that's a positive step forward.  I've done a fair bit of research into the problem domain and will continue my process of drafting initial documents in trying to address both the simple stuff and the more complex stuff; in a simple manner for others to digest, tomorrow.   
> 
> Everyone,
> 
> It's seemingly far more complicated than i'd first considered.  Even simply with toilet's - they're not the same around the world.  If people travelling are familiar with one style of toilet, they may really value finding one in a territory that has different culturally influenced outcomes.
> 
> also, 
> - babyChangeTable's,
> - Ratings 
> - disabled access 
> 
> some of the simple stuff has been modelled here: http://standards.opencouncildata.org/#/toilets 
> 
> and not all toilets available for use by the public - are provided by government.  Of course fast food, petrol stations and an array of other facilities have these sorts of amenities and perhaps that's an important pre-purchase or pre-visit decision for a mum with kids, or a senior couple, etc.
> 
> side note: https://youtu.be/kSHUha9ABNY?t=44s  
> 
> I think we can find some great outcomes by working on this 'human centric' level, resourcing means in which various modern search capabilities can have a better 'sense' of community. :) 
> 
> Tim.H.
> 
> On Fri, 2 Sep 2016 at 01:11 Thad Guidry <thadguidry@gmail.com> wrote:
> To help Timothy and others...
> 
> I have added the 'Grand Idea' proposal for Civic Information which covers the long-tail domain and needs and includes the existing issues.
> Feel free to begin discussion and active work under this grand proposal, Timothy and others.
> 
> Civic Information extension proposal​ #1337​
> 
> ​Includes:
> #627 Museum (or CivicBusiness?) should also subclass LocalBusiness
> #621 Overhaul of Place>CivicStructure necessary!
> #448 opengov.schema.org extension
> #425 Add a Community Service type
> #254 Accessibility of places
> 
> Thad
> +ThadGuidry
Received on Friday, 2 September 2016 08:49:49 UTC

This archive was generated by hypermail 2.3.1 : Friday, 2 September 2016 08:49:49 UTC