Open APIs

Hi,

our team is a bit confused and would like to clarify the attribute validFor in appointment. Does this represent the start and end time of the apointment (i.e. the time when the technician is at the customer premise) or is this meant as the duration of the validity of this appointment?



------------------------------
Markus Wolf
T-Systems International Services GmbH
------------------------------

Hi Markus

Looking at the latest schema for appointment, it is the start and end time.
I quote:
"validFor": {
"$ref": "../Common/TimePeriod.schema.json#TimePeriod",
"description": "A time period (TimePeriod). Appointment beginning date time and end date time."
}

It appears that this description is not present in the published Swagger file, so it may have been fixed afterwards. @Gregoire Laurent - the lead for this API - may be able to relate to this.

Hope it helps


​​

------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
------------------------------

Hi Johnathan,

thanks, that clarifies it. We suspected it to be this way, but were not completely sure.

Thanks,

Markus

------------------------------
Markus Wolf
T-Systems International Services GmbH
------------------------------

Original Message:
Sent: May 27, 2020 10:26
From: Jonathan Goldberg
Subject: TMF 646 Appointment validFor

Hi Markus

Looking at the latest schema for appointment, it is the start and end time.
I quote:
"validFor": {
"$ref": "../Common/TimePeriod.schema.json#TimePeriod",
"description": "A time period (TimePeriod). Appointment beginning date time and end date time."
}

It appears that this description is not present in the published Swagger file, so it may have been fixed afterwards. @Gregoire Laurent - the lead for this API - may be able to relate to this.

Hope it helps


​​

------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
------------------------------

Is firing up on old thread allowed around here? Please let me know if it's not. This one is pretty much the perfect context for what I need, so I decided to risk it.

Based on the Appointment object in v4.0.0 of the TMF 646 spec including a calendarEvent property of type CalendarEventRef and other APIs using validFor to expire an entity, it would seem that calendarEvent is the more likely place for holding the time-related properties of the appointment. Given an appointment I am expecting to see startTime and duration at minimum, however, I cannot find CalendarEvent anywhere in any of the TMF APIs. All of the other *Ref objects across TMForum seem to have an associated API and object defined somewhere. 

@Gregoire Laurent are you still the lead for TMF 646 as @Jonathan Goldberg had previously suggested. Is there a CalendarEvent buried somewhere?

CC: @Jason Funk

​​​​​​​

------------------------------
Jacob King
MetroNet
------------------------------

Original Message:
Sent: May 27, 2020 10:26
From: Jonathan Goldberg
Subject: TMF 646 Appointment validFor

Hi Markus

Looking at the latest schema for appointment, it is the start and end time.
I quote:
"validFor": {
"$ref": "../Common/TimePeriod.schema.json#TimePeriod",
"description": "A time period (TimePeriod). Appointment beginning date time and end date time."
}

It appears that this description is not present in the published Swagger file, so it may have been fixed afterwards. @Gregoire Laurent - the lead for this API - may be able to relate to this.

Hope it helps


​​

------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
------------------------------