Re: Some interesting things that show up when using a reasoner to classify schema.org

I like Martin's idea. We have the same issue with
http://schema.org/itemListElement , which can point to an arbitrary Thing,
but where it's important to call out the special type of ListItem for
numbered lists.

On Wed Jan 21 2015 at 11:48:02 AM Simon Spero <sesuncedu@gmail.com> wrote:

> The issue is somewhat complicated, in that the range is due to a
> historical name collision.
>
> The only things which can have a purpose that is a  MedicalDevicePurpose
> are Medical devices. The only values of purpose these devices can have are
> medical devices-
>
> (interArgIsa1-2 purpose
>       MedicalDevice
>       MedicalDevicePurpose)
>
> Simon
> On Jan 21, 2015 11:21 AM, "Martin Hepp" <martin.hepp@unibw.de> wrote:
>
>> Hi Dan,
>> A hands-on solution would be to add two internal "annotation" properties
>> "rangeHint" and "domainHint" that allow explicitly triggering the display
>> of certain schema.org types in the documentation.
>>
>>
>>     <div typeof="rdf:Property" resource="http://schema.org/purpose">
>> ...
>>       <span>Range: <a property="http://schema.org/rangeHint" href="
>> http://schema.org/MedicalDevicePurpose">MedicalDevicePurpose</a></span>
>>       <span>Range: <a property="http://schema.org/rangeIncludes" href="
>> http://schema.org/Thing">Thing</a></span>
>>     </div>
>>
>>
>> The documentation could then list the formal range (Thing) and popular
>> types for the range (e.g. MedicalDevicePurpose)
>>
>> This requires just ten lines in the RDFa and tweaking the Python code and
>> Jinja templates that generate the documentation.
>>
>> Martin
>>
>> --------------------------------------------------------
>> martin hepp
>> e-business & web science research group
>> universitaet der bundeswehr muenchen
>>
>> e-mail:  martin.hepp@unibw.de
>> phone:   +49-(0)89-6004-4217
>> fax:     +49-(0)89-6004-4620
>> www:     http://www.unibw.de/ebusiness/ (group)
>>          http://www.heppnetz.de/ (personal)
>> skype:   mfhepp
>> twitter: mfhepp
>>
>>
>>
>>
>>
>> On 19 Jan 2015, at 18:18, Dan Brickley <danbri@google.com> wrote:
>>
>> > Hi Simon,
>> >
>> > Thanks for these! I've opened Github issues for most of them, though I
>> > take your point that there are more out there.
>> >
>> > On 18 January 2015 at 17:54, Simon Spero <sesuncedu@gmail.com> wrote:
>> >> 1:  The range of schema:purpose has no purpose.
>> >>     MedicalDevicePurpose OR Thing  = Thing
>> >
>> > https://github.com/schemaorg/schemaorg/issues/233
>> >
>> >> 2: The range for schema:trailer includes MovieGameSeries
>> >
>> > https://github.com/schemaorg/schemaorg/issues/234
>> >
>> >> 3: schema:musicBy has a much smaller domain than actor or director
>> >
>> > https://github.com/schemaorg/schemaorg/issues/235
>> >
>> >> 4: The range of foodEstablishment is  FoodEstablishment or Place;
>> >>  but: FoodEstablishment is a subclass of LocalBusiness
>> >>         LocalBusiness is a subclass of Place,
>> >
>> > On this one I'm more sympathetic to Martin Hepp's point. Many local
>> > businesses have foody aspects to them but it isn't always feasible to
>> > make that explicit. However I'm wary of slipping into using
>> > rangeIncludes and domainIncludes assertions purely as a UI
>> > configuration language  for the Web site.
>> >
>> >> Lots, lots more.
>> >
>> > Feel free to fwd or bug-file the entire horror!
>> >
>> > We have some very basic unit tests expressed in SPARQL -
>> >
>> https://github.com/schemaorg/schemaorg/blob/master/tests/test_graphs.py#L97
>> > etc. which ought to catch more of these (e.g. mentions of types that
>> > don't have definitions should help avoid types). This currently
>> > requires Python RDFLib for the SPARQL tests, and I have had no success
>> > making SPARQL 1.1 property paths work as advertised, which I hoped
>> > might allow some basic matching against hierarchy.
>> >
>> > cheers,
>> >
>> > Dan
>> >
>> >> + The number of children (and adults) for which a Lodging reservations
>> can be made can be a floating point number.
>> > https://github.com/schemaorg/schemaorg/issues/232
>> >
>>
>>