- From: Richard Wallis <richard.wallis@dataliberate.com>
- Date: Wed, 20 Jul 2016 20:25:28 +0100
- To: Dan Brickley <danbri@google.com>
- Cc: Elias Kaerle <elias.kaerle@sti2.at>, "public-schemaorg@w3.org" <public-schemaorg@w3.org>
- Message-ID: <CAD47Kz7exm6FzgPTewi_Z1QhQeCq1Z7WuFOCw7bSXjY2rFxxUw@mail.gmail.com>
I would concur with Dan and recommend checking out that discussion before picking a transport specific naming. Either that or going for a very generic description of ‘capacity’: “The capacity of the item”. *this was my first thought too, but then my colleague told me, that this* *semantically means that* *lift.elevation = elevationEnd AND lift.elevation = elevationStart* *- which is technically true, but does not fit entirely, because a lift* *always has (at least) two elevations.* That is not the way it works in Schema. elevationEnd being a specialisation of elevation. So instances of elevationEnd and elevationStart are instances of elevation but not the same elevation. ~Richard. Richard Wallis Founder, Data Liberate http://dataliberate.com Linkedin: http://www.linkedin.com/in/richardwallis Twitter: @rjw On 20 July 2016 at 16:08, Dan Brickley <danbri@google.com> wrote: > Hi! I would suggest taking a look at the discussion at > https://github.com/schemaorg/schemaorg/issues/985 towards general > improvements for the use of schema.org for public transportation data. > There is probably relatively little value in doing something purely > ski-related here, but hopefully any larger approach should be > applicable to the ski usecase. > > Dan > > On 20 July 2016 at 10:09, Elias Kaerle <elias.kaerle@sti2.at> wrote: > > Hi, > > > > we were annotating the website of a tourism region and came across the > > need to annotate ski resorts. Unfortunately there was no possibility in > > schema.org to annotate ski lifts and ski slopes. > > > > So while witnessing the hottest days of summer here in Innsbruck we were > > working on a rather chilly subject - the extension of > > schema.org/SkiResort to annotate ski lifts and ski slopes. > > > > Please take a look at the first draft of the documentation [1], the > > extension of schema.org/SkiResort[2] (two new properties 'hasLift' and > > 'hasSlope'), the new class schema.org/SkiLift[3] and the new class > > schema.org/SkiSlope[4]. You can also comment directly in my github > > repo[5] (I did not yet make a pull request to the sdo-github project). > > > > Thank you very much for your feedback in advance, > > best regards, Elias Kärle > > > > [1] http://sdo-skiresort.appspot.com/docs/skiresort.html > > [2] http://sdo-skiresort.appspot.com/SkiResort > > [3] http://sdo-skiresort.appspot.com/SkiLift > > [4] http://sdo-skiresort.appspot.com/SkiSlope > > [5] https://github.com/eliaskaerle/schemaorg > > > > -- > > Elias Kärle, MSc > > Semantic Technology Institute > > University of Innsbruck > > > > ICT - Technologie Park Innsbruck > > 2nd Floor, Room 3S02 > > Technikerstrasse, 21a > > 6020 Innsbruck > > Austria > > > > Tel.: (+43) 512 507 53738 > > Skype: elias.kaerle > > > >
Received on Wednesday, 20 July 2016 19:25:58 UTC