Fwd: Changes to the hosted extension model Fwd: Schema.org v3.5 release candidate for review

Hello bioschemas folk. Here's a note on some changes we're making at
Schema.org in terms of how extensions are structured, published and named.
I've mentioned to some of you that such a change was likely. It should not
affect the detail of bioschema proposals heavily, but it does re-iterate
the importance of establishing the use of new schemas. We'll use the
"Pending" area for any proposals that bubble out of the Bioschemas
community, which is the way most recent substantive additions to Schema.org
have also been handled. Any questions - feel free to ask...

cheers,

Dan

---------- Forwarded message ---------
From: Dan Brickley <danbri@google.com>
Date: Wed, 20 Mar 2019 at 19:54
Subject: Changes to the hosted extension model Fwd: Schema.org v3.5 release
candidate for review
To: schema.org Mailing List <public-schemaorg@w3.org>



I'm creating a separate thread here for one topic, regarding changes to our
"hosted extensions" model. The document at
https://webschemas.org/docs/extension.html provides an overview.

The essential change is a move away from using named subdomains (
xyz.schema.org) to tag subsections of schema.org, e.g. "bib", "auto", etc.
For now we retain the notion that terms are "in" areas of the site, but
this is no longer to be reflected in site navigation URLs.

This change is motivated by a desire for greater simplicity and clarity.
Publishers were confused about whether the URL for a term when used in
markup needed the subdomain, and on whether the "hosted extension" terms
were "really in" schema.org or not. It has also become clear that the use
of subdomains was a poor fit with the complex, inter-connected nature of
schema development - many topics overlap in subtle ways, and cannot easily
be partitioned into separate disconnected areas.

We continue to welcome collaborations around improving schema.org, and as
always retain our explicit focus
<https://github.com/schemaorg/schemaorg/blob/master/README.md> on "designs
that are grounded in large scale usage on the Web, in particular usage by
data-consuming applications since these in turn motivate data publishers".
The updated extensions documentation
<https://webschemas.org/docs/extension.html> highlights our existing use of
the "Pending" area as our preferred way to bring in new proposed
vocabulary. The Pending section gives us a faster way of publishing
proposals and experimental improvements. As and when applications start
using those terms, we can move them out of the Pending area.

cheers,

Dan

---------- Forwarded message ---------
From: Dan Brickley <danbri@google.com>
Date: Wed, 20 Mar 2019 at 19:27
Subject: Schema.org v3.5 release candidate for review
To: schema.org Mailing List <public-schemaorg@w3.org>, Stéphane Corlosquet <
scorlosquet@gmail.com>, Tom Marsh <tmarsh@exchange.microsoft.com>, Vicki
Tardif Holland <vtardif@google.com>, Nicolas Torzec <torzecn@oath.com>,
Yuliya Tihohod <tilid@yandex-team.ru>, R.V. Guha <guha@google.com>



Dear Schema.org Community Group, Steering Group, interested parties,
Based on discussions here and in Github, here is a
proposal for a new Schema.org release, version 3.5:

http://webschemas.org/docs/releases.html#v3.5

I'd like to aim at publishing this in the first week of April. Bugs,
mistakes,
typos, modeling and example improvements and other detailed review
comments are welcome here or in the issue tracker at
https://github.com/schemaorg/schemaorg/issues/2052

cheers,

Dan

ps. as usual there are a few pieces of the release that will be put together
at the end (anything involving exact release dates, dated snapshots etc.,
plus a better release summary and hyperlinking of terms in the release
notes).