Re: Schema.org version 6.0 release draft for review

I agree that it is problematic. I spent some time yesterday digging around
and my conclusion is that it would be best to back out the enums change and
ship the rest of V6 than to rush a redesign.

 The core problem is that some terms continue to be  effectively operating
as types, but that information was removed from the schemas. This in part
came from UI assumptions in the schema.org site codebase, which wasn't
built for terms that play multiple roles.

That situation will need addressing (alongside other aspects of the enum
cleanup) but let's get v6.0 out, and give our technical debts some serious
attention for v7.0

Dan

On Tue, 21 Jan 2020, 23:51 Eyas Sharaiha, <eyas@google.com> wrote:

> Is it possible for https://github.com/schemaorg/schemaorg/pull/2443 to be
> merged before this release is published?
>
> I commented on there, but it seems like some of the enum rationalizations
> break some assumptions that tooling currently makes. I.e. DrugClass is now
> an enum value type only (has property (rdf:type sdo:MedicalEnumeration) and
> no other rdf:type) but is used as a type name (e.g. sdo:drugClass
> sdo:domainIncludes sdo:DrugClass). Previously, any object described by
> domainIncludes would be either an rdfs:Class or a DataType.
>
> On Wed, Jan 8, 2020 at 12:10 PM Hans Polak <info@polak.es> wrote:
>
>> LGTM
>> Cheers,
>> Hans
>>
>> On 7/1/20 16:42, Dan Brickley wrote:
>>
>> Schema.org Steering Group and wider community,
>>
>> https://webschemas.org/docs/releases.html ... has our draft for the
>> upcoming Schema.org 6.0 release. Leaving ~10 non-weekend days for review
>> puts as at Jan 21st release date.
>>
>> Discussion welcome here or in the github link from the releases page.
>>
>> cheers,
>>
>> Dan
>>
>>