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

Re: FYI: Fwd: Schema.org v3.5 release candidate for review

From: Bill Kasdorf <kasdorf.bill@gmail.com>
Date: Thu, 21 Mar 2019 10:56:54 -0400
Message-ID: <CALhciFgAxDiXyzJ+92Z=Gdw5Pf9isX_3RX72kXK0DxqTrCOy5Q@mail.gmail.com>
To: Ivan Herman <ivan@w3.org>
Cc: W3C Publishing Working Group <public-publ-wg@w3.org>
"subjectOf" goes on the thing that is a subject of a Creative Work or an
Event, not on the Creative Work itself, so that may not be applicable.

I agree that "startTime" and "endTime" on Media Object are definitely
useful. Adding "startOffset" and "endOffset" to Clip is useful for media,
but I'm not sure how they would be used in a WP or EPUB--more likely
something somebody would do _to_ a WP or EPUB.

I could see "encodesCreativeWork" being useful for accessibility, e.g., the
Braille version of a WP that might be included in an EPUB package or even
distributed as a WP/PWP/EPUB itself.

On Thu, Mar 21, 2019 at 5:25 AM Ivan Herman <ivan@w3.org> wrote:

> This may be of interest. There is a table for terms that will be in the
> core and, therefore, can also be used in the Manifest without further ado.
> Looking at it I did not see any term of a great importance for publishing,
> but I may be wrong (I was wondering about 'subjectOf', 'startTime',
> 'endTime').
> On the other hand, in the 'changes in pending section' I noted a number of
> educational credential vocabulary, these may become relevant if we do any
> educational publishing profile.
> Ivan
> Begin forwarded message:
> *From: *Dan Brickley <danbri@google.com>
> *Subject: **Schema.org <http://Schema.org> v3.5 release candidate for
> review*
> *Date: *21 March 2019 at 03:27:18 GMT+1
> *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>
> *Resent-From: *public-schemaorg@w3.org
> *Archived-At: *<
> https://www.w3.org/mid/CAK-qy=6KKryCuZ_X2oBP+iLdpomOgZsX=3_C3Ug+Qfw1KxzaZQ@mail.gmail.com
> >
> *List-Id: *<public-schemaorg.w3.org>
> *Message-Id: *<
> CAK-qy=6KKryCuZ_X2oBP+iLdpomOgZsX=3_C3Ug+Qfw1KxzaZQ@mail.gmail.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).
> ----
> Ivan Herman, W3C
> Publishing@W3C Technical Lead
> Home: http://www.w3.org/People/Ivan/
> mobile: +31-641044153
> ORCID ID: https://orcid.org/0000-0003-0782-2704

*Bill Kasdorf*
*Principal, Kasdorf & Associates, LLC*

*Founding Partner, Publishing Technology Partners
+1 734-904-6252

ISNI: http://isni.org/isni/0000000116490786
ORCiD: https://orcid.org/0000-0001-7002-4786
Received on Thursday, 21 March 2019 14:57:53 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:52:37 UTC