Hi,
I posted on this originally back in August last year but we are now just getting to thinking about the implementation of this and wanted to raise it again as there would seem to be a gap in the API specifications. What I'm interested in is defining things that are relevant to an address rather than the address itself, for example
- Site restrictions - it's a secure site which has restrictions who can access or to contact before arriving
- Hazard information - there are working at height requirements if accessing the property, or it's near water and needs specific equipment to work
I can't see anything similar in either the previous or current APIs but these are a requirement for Openreach to be able to communicate with it's customers and partners to successfully deliver services and would like to see if a request to look at a formal specification in the APIs can be raised. Currently I'm thinking that a set of site characteristics with a specification file is the most extensible way to do it but I know from a comment by
@Jonathan Goldberg last time he wasn't very much in favour of that, we could add specific sub-classes to the address such as "Hazards" and "SiteRestrictions" but then a tightly coupled solution requires API changes if we want to modify the details that are passed which I'd like to avoid too. Also, each region or country may have different requirements for their own site characteristics and end up with localised solutions which are non-conformant.
#OpenDigitalArchitecture------------------------------
Steve Ranford-Bragg
BT Group plc
------------------------------