The name of the XSD set that defines the message formats towards Elhub. It is versioned, and the version number is what decides whether two systems speak the same language.
Definition
ElhubNational hub for metering data and market processes in the Norwegian electricity market. does not accept just anything. Messages in and out are defined in schema files, XSDs, describing exactly which elements a message may contain, in what order and with what data types. That set goes by the name EMIF.
The point of a schema is that rejection should happen early and legibly. A message that breaks the schema is rejected by the interface itself, with a precise error, rather than being accepted and failing further inside where nobody can see the connection.
The version number is not a formality. A system built against one version can stop working against the next if a field has become mandatory or a data type has been tightened. That is why integrations state which version they were built against, not merely that they "support Elhub".
Note the distinction from BRSElhub’s process specifications. Each BRS describes one market process step by step - who sends what, when, and what happens when something fails.: the schema says what the message must look like, the business process says what it is for. Both have to match.
An integration towards Elhub cannot be finished by testing against Elhub. Using the production system as a rehearsal room is a bad idea, and the test environments have opening hours and queues that do not fit a development cycle.
STUBB simulates the Elhub central system locally, with file-based SOAP and XML exchange compatible with EMIF XSD v2.4.3. Your system sends the message, the stub validates it against the schema, generates the acknowledgement and updates the status. The format errors are then found before anyone logs into an environment shared with others.
In practice
An integration towards ElhubNational hub for metering data and market processes in the Norwegian electricity market. cannot be finished by testing against Elhub. Using the production system as a rehearsal room is a bad idea, and the test environments have opening hours and queues that do not fit a development cycle.
STUBBTvimenning's simulator platform for integration testing - we build mock environments of the counterparties your systems talk to, so they can be tested without touching production. simulates the Elhub central system locally, with file-based SOAPSimple Object Access Protocol - XML-based messaging protocol used in enterprise integrations, including Elhub. and XMLExtensible Markup Language - universal markup language for structured data, standard in Elhub's Ediel messages. exchange compatible with EMIF XSD v2.4.3. Your system sends the message, the stub validates it against the schema, generates the acknowledgement and updates the status. The format errors are then found before anyone logs into an environment shared with others.
