Diffo - TMF Service and Resource Management with a difference
Poi - NBN Point of Interconnect
A POI is the physical interconnect site where RSPs hand traffic to/from the
NBN. Each POI has a fixed location (a point) and is paired 1:1 with the CSA
(Connectivity Serving Area) it interconnects, via a PlaceRef (POI -> CSA).
A TMF675 GeographicLocation (a location point), keyed by the NBN POI Ref
(e.g. "5EDW" Edwardstown). NNI Groups are at a POI (#26).
An NBN Point of Interconnect (POI)
Summary
Types
@type t() :: %DiffoExample.Nbn.Poi{ __lateral_join_source__: term(), __meta__: term(), __metadata__: term(), __order__: term(), accuracy: term(), aggregates: term(), bounds: term(), calculations: term(), created_at: term(), href: term(), id: term(), location: term(), name: term(), place_refs: term(), referred_type: term(), type: term(), updated_at: term() }
Functions
Validates that the keys in the provided input are valid for at least one action on the resource.
Raises a KeyError error at compile time if not. This exists because generally a struct should only ever
be created by Ash as a result of a successful action. You should not be creating records manually in code,
e.g %MyResource{value: 1, value: 2}. Generally that is fine, but often with embedded resources it is nice
to be able to validate the keys that are being provided, e.g
Resource
|> Ash.Changeset.for_create(:create, %{embedded: EmbeddedResource.input(foo: 1, bar: 2)})
|> Ash.create()Same as input/1, except restricts the keys to values accepted by the action provided.