@danbri one question: I also need to indicate that a schedule can have a startDate, endDate and duration am I safe to just declare the wider domains for those properties here? Couldn't see an example of this in other changes.

Also, what's the process for getting this merged?

Supportive of this, especially if we can get duration in there.

Bikeshed: can we have repeatCount instead of occurencyCount?

It uses more common words, matches the repeatFrequency, and is easier not to spell wrong...

@chaals makes sense to me. I've renamed as suggested

I suggest I merge this in asap (to pending) to help others review it more carefully. Is anything massively in flux or shall I do that now? we can continue to refine after merging

@danbri in case @ldodds isn't about, we chatting about this earlier and it's in a good place to merge as-is, as you say to help others review.

Done. Will stage on webschemas site when I get to https://github.com/t2trg/2017-07-wishi

/cc #1272 re device schedules

Great! Would you also be able to look at @ldodds' question above re: startDate, endDate and duration?

Hey @danbri - sorry if this should be obvious but where can we find this to point people to for feedback?

http://pending.schema.org/Schedule Returns a 404...

@danbri should these terms have appeared at pending.schema.org yet? Getting 404s still. Does a release need to happen?

Normally they'd be on webschemas.org now, and yes will show up on *schema.org with the upcoming release.

@danbri so they'll appear on http://webschemas.org/Schedule and http://pending.schema.org/Schedule after the next release? When will that be?

I want to update our JSON-LD context to refer to the pending terms.