View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000474130070: MTConnectDocumentation Erratapublic2019-04-23 19:352019-04-26 18:18
ReporterStan Brubaker Assigned ToWilliam Sobel  
PrioritynormalSeveritymajorReproducibilityN/A
Status closedResolutionno change required 
Product Version2.0 RC8 
Summary0004741: NamespaceUri - should it change in this version?
Description

Changing the NamespaceUri means that all defined types are incompatible with previous versions.

TagsNo tags attached.

Activities

William Sobel

2019-04-23 19:46

developer   ~0010219

The change was intentional since the new specification is a complete departure from the prior spec. The new one is not backward compatible and therefor a new URI was suggested.

Stan Brubaker

2019-04-26 17:57

manager   ~0010232

From: William Sobel will@govimana.com
Sent: Tuesday, April 23, 2019 3:44 PM
To: Stan Brubaker stan.brubaker@beeond.net
Cc: Karl Deiretsbacher (OPC) karl.deiretsbacher@opcfoundation.org; Tom Copeland tomc@trakmt.com
Subject: Re: [OPC-F] Published: OPC UA MTConnect Companion Specification, V2.0

Hi Stan,

Sorry for taking a while to get back.

The namespace URI change was intentional since the two models are completely different. There is a path of conversion but they do not interoperate. Since there was little to no adoption for the prior standard and it was not officially accepted, we decided to use a new URI to avoid confusion.

Does that provide sufficient context?

Thanks
W

Issue History

Date Modified Username Field Change
2019-04-23 19:35 Stan Brubaker New Issue
2019-04-23 19:35 Stan Brubaker Status new => assigned
2019-04-23 19:35 Stan Brubaker Assigned To => William Sobel
2019-04-23 19:46 William Sobel Note Added: 0010219
2019-04-26 17:57 Stan Brubaker Target Version 2.0 RC9 =>
2019-04-26 17:57 Stan Brubaker Note Added: 0010232
2019-04-26 18:18 Stan Brubaker Status assigned => closed
2019-04-26 18:18 Stan Brubaker Resolution open => no change required