schedules schema draft

[Dan Brickley]

fyi, i just merged in a draft from Leigh Dodds,

https://github.com/schemaorg/schemaorg/pull/1693#issuecomment-315449029

We ought to consider IoT/WoT usecases, eg periodic sensor measurements, or commands into device apis, heating etc. Can one basic pattern serve here?

Dan

[Thad Guidry]

I guess your asking specifically about Scheduling and Frequency of repeating Events ?

If so, then I would say YES, a basic pattern surfaces under both of those.  But...

## WARNING BEFORE READING THE REST - I DO NOT WORK FOR NASA, BUT LOVE ASTRONOMY ##

There are 2 use cases of IoT Things knowing their position on a time line and also describing that position in a Coordinated Time System .  This happens when you break out into astronomical entities, or where IoT Things are on the surface of Mars :) and need to describe a Schedule or Frequency along several alternative time lines or the Coordinated Time System the Schedule is referenced against.  Some manufacturers do state Schedules in a particular Coordinated Time System.

So there's the need to describe like WHICH Schedule time line or Coordinated Time System.  A picture is worth a thousand words I guess ??

"eventSchedule":
 {
 "@type": "Schedule",
 "startDate": "2016-12-24",
 "repeatFrequency": "P1D",
 "repeatCount": 10,
 “startTime": "09:00",
 “endTime": "10:00",

// USECASE 1:  Need is to say something string-like

// http://spiff.rit.edu/classes/phys301/lectures/time/time.html

"TemporalCoordinatesIn": "Local Sidereal time",  

// OR

"TemporalCoordinatesIn":"barycentric"

// USECASE 2:  The other need is having the whole Schedule declared against a Coordinated Time System

// https://space.stackexchange.com/questions/12987/how-to-calculate-coordinated-mars-time-mtc

"inCoordinatedTimeSystem": "MTC"

 }
} 

Hope that clarifies the immediate need that I know of for some scheduling systems both on Earth and far far away.  Can't speak about their API's or wanted properties therein, but perhaps others have gut feelings or have done research and actual knowledge of some.

-Thad

+ThadGuidry  

--
You received this message because you are subscribed to the Google Groups "sdo-iot-sync" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sdo-iot-sync...@googlegroups.com.
To post to this group, send email to sdo-io...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/sdo-iot-sync/CAK-qy%3D6yaq5VESH2os5JDCU3%2B8mVmpF7Y2GQtg2BM_d9Bp2VwA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Dave Raggett]

One class of use cases involves data streaming, e.g. medical monitoring and remote diagnosis of a heart condition, involving several channels of sensor data that is sampled several hundred times a second.  In my demo, I have metadata for the source of the stream, the sampling frequency and the latency, which is useful for figuring out how to support a continuously scrolling display of the sensor data as lines on a graph.  Other metadata describes each of the channels.

Note that some streaming cases embed time stamps while others do not.

Dave Raggett <d...@w3.org> http://www.w3.org/People/Raggett

W3C champion for the Web of things