0006881: Client conformance Unit granularity - MantisBT

ID	Project	Category	View Status	Date Submitted	Last Update

0006881	10000-007: Profiles	Spec	public	2021-04-29 14:52	2022-09-13 15:27

Reporter	Paul Hunkar	Assigned To	Karl Deiretsbacher
Priority	normal	Severity	minor	Reproducibility	have not tried
Status	closed	Resolution	won't fix

Summary	0006881: Client conformance Unit granularity
Description	from compliance group: many of the client Conformance Units, especially for services are not granular enough on the client side. For example the client read conformance include MaxAge and timestamps to return, but many clients would not offer this as option they have fixed setting for these parameters. so it does not make sense to require that they can be changed (i.e. exercise the setting of the service) the single conformance unit for the service on the client side should become multiple conformance Units which would allow client that do ot support change to skip them.
Tags	No tags attached.

Commit Version
Fix Due Date

Karl Deiretsbacher 2022-03-05 09:19 developer ~0016224	This may be a testcase issue. The CU does not require MaxAge or timestamps to return.

Jim Luth 2022-08-30 15:26 administrator ~0017465	Alexander to provide clarification to Karl on what is needed.

Alexander Allmendinger 2022-09-05 09:03 developer ~0017515	From my notes of the Compliance WG discussion regarding Read and its parameters: Because the conformance unit nor the spec describe the expectations for Clients on the support/usage of MaxAge, TimestampsToReturn etc. it is considered implied in the generic CU and therefore mandated for all products. If the support of parameters is optional, they should become their own CU like the CUs: Attribute Client Read by Index, Attribute Client Write by Index, Attribute Client Write Quality / Timestamp. Those CUs can then be marked optional in the according facets.

Alexander Allmendinger 2022-09-13 15:22 developer ~0017646	From the UA Working Group discussion: Because there are a lot of parameters in the service calls which a Client may utilize or keep at default values, the option to have those parameters configurable by the user of the product or not is not being implied. If the support of a specific parameter is desired to be configurable this will be either mentioned explicitly in the Conformance Unit description or a separate CU will be created. Following this rule, there is no implication on the configurability of MaxAge or the TimestampToReturn in the Attribute Client Read CU.

Karl Deiretsbacher 2022-09-13 15:26 developer ~0017647	See last note.

Jim Luth 2022-09-13 15:27 administrator ~0017648	Agreed to no change required in telecon.

Date Modified	Username	Field	Change
2021-04-29 14:52	Paul Hunkar	New Issue
2021-11-23 18:13	Jim Luth	Assigned To	=> Karl Deiretsbacher
2021-11-23 18:13	Jim Luth	Status	new => assigned
2022-03-05 09:19	Karl Deiretsbacher	Note Added: 0016224
2022-08-30 15:26	Jim Luth	Note Added: 0017465
2022-09-05 09:03	Alexander Allmendinger	Note Added: 0017515
2022-09-13 15:22	Alexander Allmendinger	Note Added: 0017646
2022-09-13 15:26	Karl Deiretsbacher	Status	assigned => resolved
2022-09-13 15:26	Karl Deiretsbacher	Resolution	open => won't fix
2022-09-13 15:26	Karl Deiretsbacher	Note Added: 0017647
2022-09-13 15:27	Jim Luth	Status	resolved => closed
2022-09-13 15:27	Jim Luth	Note Added: 0017648