View Issue Details

IDProjectCategoryView StatusLast Update
000472930070: MTConnectDocumentation Erratapublic2019-07-12 18:07
ReporterJohn Turner Assigned ToWilliam Sobel  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version2.0 RC8 
Target Version2.0 RC9Fixed in Version2.0 RC9 
Summary0004729: Application of Rules for BrowseName
Description

In Section 8.3.3 in the Companion Specification, there are a series of rules for generating BrowseNames for Nodes representing MTConnect Data Items. Rule #3 has a series of lower level rules for generating the BrowseName. Most of these lower level rules are mutually exclusive and the sequence at which you apply these rules does not impact the generation of the BrowseName. However, there is at least on case where the sequence of applying the rules is important to the generation of the BrowseName. The documentation does not clearly define that the rules MUST be applied in sequence.

Here is the example encountered:

  Found a case where I can’t find a clear answer on how to construct a Browse Name for the following case:

   Have two PART_COUNT type data entities associated with a controller.   Both are Discrete.   
    One with name SHT1 and the other with name SHT2

   Which is the correct format?     PartCountDiscrete[SHT1]  or PartCount[SHT1]Discrete?

Recommend updating the documentation to clarify the use of these rules.

Additional Information

Changes made to RC9 draft.

TagsNo tags attached.

Activities

William Sobel

2019-05-21 20:01

developer   ~0010258

Additional language was added to indicate the rules must be followed in order.

Stan Brubaker

2019-07-12 18:07

manager   ~0010484

Fix made in RC9 and included in final 2.0 release

Issue History

Date Modified Username Field Change
2019-04-14 13:28 John Turner New Issue
2019-04-26 18:26 Stan Brubaker Status new => assigned
2019-04-26 18:26 Stan Brubaker Product Version => 2.0 RC8
2019-04-26 18:26 Stan Brubaker Target Version => 2.0 RC9
2019-04-26 18:26 Stan Brubaker Additional Information Updated
2019-04-26 18:26 Stan Brubaker Assigned To => William Sobel
2019-05-21 20:01 William Sobel Status assigned => resolved
2019-05-21 20:01 William Sobel Resolution open => fixed
2019-05-21 20:01 William Sobel Fixed in Version => 2.0 RC9
2019-05-21 20:01 William Sobel Note Added: 0010258
2019-07-12 18:07 Stan Brubaker Status resolved => closed
2019-07-12 18:07 Stan Brubaker Note Added: 0010484