Add device example message

[Sander3003]

Community feedback requested an example message for the smartmetering web services. This is the fist example made by @phoutman.

[CLAAdmin]

You should sign our Contributor License Agreement in order to get your pull request merged.

[jenkins-ip-10-4-24-184]

All is well.

[jenkins-ip-10-4-24-184]

All is well.

[jenkins-ip-10-4-24-184]

All is well.

[jenkins-ip-10-4-24-184]

All is well.

[jenkins-ip-10-4-24-184]

All is well.

[rlemmers]

• Smart metering can be implemented using various protocols. The example is very specific for DSMR. I advise putting the example in the Protocols chapter. Then link to the example from the webservice operation page or make a general statement "for examples, see section ..." in a centralized location to prevent constantly updating links.
• Also add a response message example.
• Approving the content should be done by someone from the team in Eindhoven.

[Sander3003]

@phoutman can you take a look at the @rlemmers input? https://smartsocietyservices.atlassian.net/browse/OC-362

@rlemmers your name is in the documentation; if this does not reflect the current situation we need to update it.

Current maintainers:

Open smart grid platform and smart lighting domain: Kevin Smeets Smart metering domain: Bart van der Zwet Documentation & configuration: Ruud Lemmers

[rlemmers]

"@rlemmers your name is in the documentation; if this does not reflect the current situation we need to update it." - when it comes to details about smart metering, someone from that domain should check the content. There's nobody who has expert knowledge about all domains. Therefore, you don't have to modify the maintainer for "Documentation & configuration".

[jenkins-ip-10-4-24-184]

All is well.

[rlemmers]

Any news from @phoutman regarding my input?

[Sander3003]

No, not yet, I send @phoutman an e-mail to remind him of this issue. Btw, made some little tweaks to the maintainer section of the documentation to clarify the role of the documentation/configuration maintainer.

[phoutman]

I agree with @rlemmers that this is very domain specific and that part should be updated by someone with in-depth knowledge of that domain. But I still think it is the responsibilty of the documentation maintainer to get someone to update the documentation.

[Sander3003]

@rlemmers can you file an Jira issue on this topic?

[Sander3003]

device configuration example

SoapUI testuser test-org ${=testCase.getPropertyValue( "DeviceIdentification" )} ALWAYS_ON DISCOVER_ON_POWER_ON 1