View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000304410000-007: ProfilesSpecpublic2015-04-22 19:102015-05-19 16:33
ReporterKenneth G. Dunahee Assigned ToKarl Deiretsbacher  
PrioritynormalSeveritytextReproducibilityalways
Status closedResolutionfixed 
Target Version1.03Fixed in Version1.03 
Summary0003044: Entry-Level support Client conformance unit needs additional text
Description

This profile description should explicitly mention both the Micro and Nano server profiles. Possibly text such as "Entry-level Client are expected to be able to interact with server that are built against the Nano Embedded Device server Profile and the Micro Embedded Device Server profile" Additionally it may be useful to convert the single conformance unit into multiple conformance units - one for each of the testable items i.e. read vs subscription, knowledge of OPC UA Types, Single Session support. Although this is a released profile, the conversion will not change the functionality, that having multiple required conformance units should be acceptable.

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

Karl Deiretsbacher

2015-05-04 06:07

developer   ~0006040

Karl:
Initial version called “Standard Flexible Client Profile”:
http://opcfoundation-onlineapplications.org/profilereporting/?All=true

Feedback Ken:
I am thinking of this profile as the peer of the “Standard UA Server Profile”. Two thoughts:
• I think the name should be “Standard UA Client Profile’.
On the Server side, “Standard” defines what is expected from a full-featured PC application. I think that applies here.
• Attribute Write isn’t included. Seems to me it should be.

For “Entry-Level Support Client Facet”, I think we should deprecate Conformance Unit “Client Entry-Level Support” and replace it with a set of more explicit (and testable) conformance units:
Client Single-Session Interoperability The client shall interoperate with Servers that only support one session.
Client OPC UA Type Knowledge The client shall interoperate with Servers that do not expose OPC UA Types in Address Space.
Client No Subscription Operation The client shall interoperate with Servers that do not support Subscriptions, or have exhausted subscription limits, for Monitoring by using Read Service.
Client Honor Server Capabilities The client shall honor Server limits described in ServerCapabilites Object of Server.

Karl Deiretsbacher

2015-05-19 16:32

developer   ~0006073

Fixed in Profiles 1.03 Draft 11.

Jim Luth

2015-05-19 16:33

administrator   ~0006074

Agreed to changes in telecon.

Issue History

Date Modified Username Field Change
2015-04-22 19:10 Kenneth G. Dunahee New Issue
2015-05-04 06:07 Karl Deiretsbacher Note Added: 0006040
2015-05-05 15:46 Jim Luth Target Version => 1.03
2015-05-05 15:46 Jim Luth Assigned To => Karl Deiretsbacher
2015-05-05 15:46 Jim Luth Status new => assigned
2015-05-19 16:32 Karl Deiretsbacher Note Added: 0006073
2015-05-19 16:32 Karl Deiretsbacher Status assigned => resolved
2015-05-19 16:32 Karl Deiretsbacher Fixed in Version => 1.03
2015-05-19 16:32 Karl Deiretsbacher Resolution open => fixed
2015-05-19 16:33 Jim Luth Note Added: 0006074
2015-05-19 16:33 Jim Luth Status resolved => closed