W3C home > Mailing lists > Public > public-bioschemas@w3.org > March 2019

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

From: Dan Brickley <danbri@google.com>
Date: Thu, 21 Mar 2019 11:27:21 -0700
Message-ID: <CAK-qy=5p4hUAJFuwGH5g1eH2Amc0fyF2n41ErdOZAq_sbMqWWQ@mail.gmail.com>
To: Dan Brickley <danbri@danbri.org>
Cc: "Gray, Alasdair J G" <A.J.G.Gray@hw.ac.uk>, public-bioschemas@w3.org
(-public-schema.org@ list)

Here's an example:
https://github.com/schemaorg/schemaorg/blob/master/data/ext/pending/issue-1156.rdfa

plus examples of term usage in this format
https://github.com/schemaorg/schemaorg/blob/master/data/ext/pending/issue-1156-examples.txt

others: https://github.com/schemaorg/schemaorg/tree/master/data/ext/pending

How are your drafts represented currently?

cheers,

Dan

On Thu, 21 Mar 2019 at 10:15, Dan Brickley <danbri@danbri.org> wrote:

>
>
> On Thu, 21 Mar 2019, 08:10 Gray, Alasdair J G, <A.J.G.Gray@hw.ac.uk>
> wrote:
>
>> Hi Dan
>>
>> Thanks for cross-posting this to the Bioschemas mailing list and keeping
>> us abreast of the updates to schema.org processes.
>>
>> I think that the new approach will improve the understandability of the
>> schema.org vocabulary and in particular its namespaces.
>>
>> What is not so clear is the process for getting types and properties into
>> the pending area. In the Bioschemas community we have been working on types
>> and properties for describing life sciences resources and are stabilising
>> on a particular set of types and properties. In a few months time we hope
>> to be in a position of being able to demonstrate many resources marked up
>> with these types and properties as well as a range of applications
>> consuming the markup. However, one difficulty that we already encounter is
>> that our types and properties do not appear in the schema.org namespace.
>> So how do we now go about pushing these to pending?
>>
>
> That's why I have been bugging you all for a proposal of what
> changes/additions you actually want! Once we have that the work of adding
> is a technicality. Look in the data/ext/pending/ folder for examples of
> other definitions. You can either send a PR on Github or I can help. Why
> don't we do that this week rather than in a few months?
>
> Dan
>
>
> thanks
>>
>> Alasdair
>>
>> On 21 Mar 2019, at 02:57, Dan Brickley <danbri@google.com> wrote:
>>
>>
>> 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).
>>
>>
>> --
>> Alasdair J G Gray
>> Associate Professor in Computer Science,
>> School of Mathematical and Computer Sciences
>> Heriot-Watt University, Edinburgh, UK.
>>
>> Email: A.J.G.Gray@hw.ac.uk <A.J.G.Gray@hw.ac.uk>
>> Web: http://www.macs.hw.ac.uk/~ajg33
>> ORCID: http://orcid.org/0000-0002-5711-4872
>> Office: Earl Mountbatten Building 1.39
>> Twitter: @gray_alasdair
>>
>> To arrange a meeting: http://doodle.com/ajggray
>>
>> ------------------------------
>>
>> *Heriot-Watt University is The Times & The Sunday Times International
>> University of the Year 2018*
>>
>> Founded in 1821, Heriot-Watt is a leader in ideas and solutions. With
>> campuses and students across the entire globe we span the world, delivering
>> innovation and educational excellence in business, engineering, design and
>> the physical, social and life sciences. This email is generated from the
>> Heriot-Watt University Group, which includes:
>>
>>    1. Heriot-Watt University, a Scottish charity registered under number
>>    SC000278
>>    2. Edinburgh Business School a Charity Registered in Scotland,
>>    SC026900. Edinburgh Business School is a company limited by guarantee,
>>    registered in Scotland with registered number SC173556 and registered
>>    office at Heriot-Watt University Finance Office, Riccarton, Currie,
>>    Midlothian, EH14 4AS
>>    3. Heriot- Watt Services Limited (Oriam), Scotland's national
>>    performance centre for sport. Heriot-Watt Services Limited is a private
>>    limited company registered is Scotland with registered number SC271030 and
>>    registered office at Research & Enterprise Services Heriot-Watt University,
>>    Riccarton, Edinburgh, EH14 4AS.
>>
>> The contents (including any attachments) are confidential. If you are not
>> the intended recipient of this e-mail, any disclosure, copying,
>> distribution or use of its contents is strictly prohibited, and you should
>> please notify the sender immediately and then delete it (including any
>> attachments) from your system.
>>
>
Received on Thursday, 21 March 2019 18:27:57 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:08:08 UTC