- From: Tomasz Pluskiewicz via GitHub <sysbot+gh@w3.org>
- Date: Fri, 22 May 2020 08:33:57 +0000
- To: public-hydra-logs@w3.org
I think you mean that its range is a `schema:Class`. Yes it is [defined as](https://github.com/schemaorg/schemaorg/blob/104238766458b465e6a60cc7d049f887c542563a/data/releases/3.7/ext-meta.nq#L5) ```turtle schema:rangeIncludes schema:rangeIncludes schema:Class . ``` Note that it still does not use `rdfs:range`. The difference is that `rdfs:range` has strong semantics. Broadly speaking, using the `hydra:expects` example, it means that > Every object of `hydra:expects` is implicitly a `hydra:Class` and thus a `rdfs:Class` IMO this is not desired. With `schema:rangeIncludes` you don't get this effect. It is only a hint that the property objects may be one of the listed types. Or something completely different -- GitHub Notification of comment by tpluscode Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/214#issuecomment-632571074 using your GitHub account
Received on Friday, 22 May 2020 08:33:58 UTC