Open APIs

Hello,

(this is a more succinct version of a previous POST).
The conformance spec for TMF622 says that 
"the {apiRoot} is defined as {serverRoot}/productOrderingManagement/v4, being {serverRoot} defines the certification endpoint"

But there is no mention of what {serverRoot} means.
Is {serverRoot} simply scheme+host+port? E.g. http://host.bt.com:5555/
Or can {serverRoot} include some root path  http://host.bt.com:5555/my/root/path/before/apiRoot

I.e. if we have two end-points both exposing the same service, do they need to be on different DNS names/ports, or can they share the same host:port but have different paths?

------------------------------
Alasdair MacLeod
BT Group plc
------------------------------

@Henrique Rodrigues from TM Forum is probably best placed to address this question, since he is responsible for producing the conformance test kits.

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.
------------------------------

Original Message:
Sent: Apr 23, 2020 10:57
From: Alasdair MacLeod
Subject: Ambiguous URL formulation in TMF622 conformance specs


Hello,

(this is a more succinct version of a previous POST).
The conformance spec for TMF622 says that
"the {apiRoot} is defined as {serverRoot}/productOrderingManagement/v4, being {serverRoot} defines the certification endpoint"

But there is no mention of what {serverRoot} means.
Is {serverRoot} simply scheme+host+port? E.g. http://host.bt.com:5555/
Or can {serverRoot} include some root path  http://host.bt.com:5555/my/root/path/before/apiRoot

I.e. if we have two end-points both exposing the same service, do they need to be on different DNS names/ports, or can they share the same host:port but have different paths?

------------------------------
Alasdair MacLeod
BT Group plc
------------------------------

Thanks Jonathon, I will drop Henrique a line and see what he has to say.

------------------------------
Alasdair MacLeod
BT Group plc
------------------------------

Original Message:
Sent: Apr 26, 2020 09:14
From: Jonathan Goldberg
Subject: Ambiguous URL formulation in TMF622 conformance specs

@Henrique Rodrigues from TM Forum is probably best placed to address this question, since he is responsible for producing the conformance test kits.

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.

Original Message:
Sent: Apr 23, 2020 10:57
From: Alasdair MacLeod
Subject: Ambiguous URL formulation in TMF622 conformance specs


Hello,

(this is a more succinct version of a previous POST).
The conformance spec for TMF622 says that
"the {apiRoot} is defined as {serverRoot}/productOrderingManagement/v4, being {serverRoot} defines the certification endpoint"

But there is no mention of what {serverRoot} means.
Is {serverRoot} simply scheme+host+port? E.g. http://host.bt.com:5555/
Or can {serverRoot} include some root path  http://host.bt.com:5555/my/root/path/before/apiRoot

I.e. if we have two end-points both exposing the same service, do they need to be on different DNS names/ports, or can they share the same host:port but have different paths?

------------------------------
Alasdair MacLeod
BT Group plc
------------------------------