Versioning for IEC 61968 Scott Neumann September 30

Versioning for IEC 61968 Scott Neumann September 30, 2009

Introduction • The purpose of this presentation is to describe the issue of versioning of interfaces • Inter. Op efforts recognized this issue and wanted this to be generally considered within IEC 61968 • This is intended as input to the second edition of IEC 61968 -1 and/or 61968 -1 -1 (proposed) 2 Proprietary and Confidential

OASIS Namespace URI Versioning Policy • Intent is to change namespace URI only when subsequent revisions are not backward compatible • The following are examples of backwards compatible changes that would not result in assignment of a new namespace URI: • • • Addition of new global element, attribute, complex. Type and simple. Type definitions Addition of new operations within a WSDL port. Type or binding (along with the corresponding schema, message and part definitions) Addition of new elements or attributes in locations covered by a previously specified wildcard Modifications to the pattern facet of a type definition for which the valuespace of the previous definition remains valid or for which the valuespace of the preponderance of instance would remain valid Modifications to the cardinality of elements for which the value-space of possible instance documents conformant to the previous revision of the schema would still be valid with regards to the revised cardinality rule 3 Proprietary and Confidential

XML NDR • TC 57 has a draft XML NDR being reviewed by WG 19 • Identifies how CIM profile can be syntactically realized as an XSD, with its own namespace • Includes use of sawsdl for traceability of elements to the CIM, where each element is mapped to its source in the CIM, examples: • sawsdl: model. Reference=“http: //iec. ch/TC 57/CIMgeneric#End. Device. Event” • sawsdl: model. Reference=“http: //iec. ch/TC 57/CIMgeneric#Identified. Object. m. RID” • UNCEFACT limits options for extensibility 4 Proprietary and Confidential

IEC Namespaces for Profiles IEC 61968 -9 1 ed: http: //iec. ch/TC 57/2009/<noun># IEC 61968 -9 2 ed (example when significant changes occur to a given schema): http: //iec. ch/TC 57/2011/<noun># Use schema version attribute in XSD to identify minor version changes. 5 Proprietary and Confidential

Summary • Try NOT to needlessly change namespaces • Use schema version attribute: 1. 0, 1. 1, 1. 2 for minor version changes • Where significant changes occur to a profile definition in a subsequent 61968 edition, use a new namespace URI for specific profiles as necessary 6 Proprietary and Confidential

More Information • UISOL web site: http: //uisol. com • E-mail: sneumann@uisol. com • EPRI Technical Report: ESB Implementation Profile Using IEC 61968 7 Proprietary and Confidential