The Period of Time class in the CPSV-AP represents an interval of time indicating from when to when a Public Service is available for use.
In the CPSV-AP_IT, more detail was added in the model for capturing this information. The class TimeInterval was added, of which PeriodOfTime is a subclass. TimeInterval has the following properties:
- startInterval
- endInterval
- hasDayOfTheWeek
hasDayOfTheWeek is an association between TimeInterval and an additional class DayOfTheWeek.
Component
DocumentationCategory
feature
Login or
create an account to comment.
Comments
See joinup.ec.europa.eu/asset/cpsv-ap/issue/extending-processing-time-property-public-service
Actually this turns out to be rather complicated.
The Italian exampel shows a method of handling days of the week but a more general case needs to be able to handle recurring periods of arbitrary type. For periods with a nice start date and end date it's easy. But for recurring periods, like April-Spetember, it's harder. Looking to schema.org for inspiration leads me to the following proposed text.
I am aware that this is entirely made up - better suggestions will be gratefully received. ISO8601 has a method of encoding recurring periods, see https://en.wikipedia.org/wiki/ISO_8601#Repeating_intervals which is more machine processable but less user-friendly.
Period Of Time -> Recurring [0..1]
This property represents recurring time periods which should be encoded using text. However, this can be made machine processable by using regular abbreviations as suggested by schema.org's open hours property . Following that structure, days of the week are represented by two letter codes (Mo, Tu, We, Th, Fr, Sa, Su). Months need three letters (Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec). Lists should be comma separated (for example: Mo, We, Fr) and periods separated by a hyphen (for example: May-Sep). As these are based on specifically English language words, the language used should be made explicit. The recurring property may, of course, be used with other languages, but for cross border interoperability, English should be one of the offered languages.
If it is appropriate to add opening hours then this follows the day so if a phone service is available 08:00 – 20:00 Monday to Saturday and 08:00 – 18:00 on Sundays that would be encoded as Mo-Sa 08:00-20:00, Su 08:00-18:00.
I agree on using schema.org's Opening Hours in using this class. We should keep it maximable user-friendly while retaining machine interoperability. Schema.org seems more suitable here.
The proposal made for the meeting of 24/5/16 included a complex set of properties and values which although agreed to by the WG, seemed opento improvement. Further research, notably into the Good Relations vocabulary (http://www.heppnetz.de/ontologies/goodrelations/v1.html#validFrom) led to a suggestion that is compatible with that agreed in the telco but simpler and more in line with GR as well as the Italian experience.