Looking at 11-06-20.xml, I see elements such as <thecustomprofile:interface base_Class="EAID_F37A3B0D_CFE6_448a_A95F_26FDC113F2A2"/>, which are EA-specific representations. This needs to be fixed to be properly XMI compliant.

PIM: N/A
PSM: N/A
The UML 2.x Specification insists that Stereotypes be bound to a
profile.
But in EA, users can freely type-in any name in the "Stereotype" field (
in the "Properties" dialog of a construct ).
Such freely typed-in stereotypes do not belong to any profile.

When exporting to XMI 2.x, we cannot export a stereotype unless we
specify its profile.
So, we create a dummy profile called "thecustomprofile" in the namespace
http://www.sparxsystems.com/profiles/thecustomprofile/1.0 and bind all
the freely typed-in stereotypes to this profile.

For example, refer to the attached Snapshot.png - Class1's stereotype is
"opt" ( I typed-in this in the "Stereotype" field in the "Properties"
dialog of the class ) & Activity1 is a BPMN 2.0 activity.
When exported to XMI 2.x, the stereotype "opt" is linked to
"thecustomprofile" as underlined in green.

NOTE :
XML Namespace is just a method to avoid name conflicts & using the
namespace http://www.sparxsystems.com/profiles/thecustomprofile/1.0
doesn't means that our XMI is OMG in-compliant.
If you want, you can manually change the namespace of the
"thecustomprofile" ( or any other profile used in the XMI file ) from
http://www.sparxsystems.com/profiles/thecustomprofile/1.0 to the desired
namespace ( at the location boxed in brown ).

Revised Text:
PIM: N/A
PSM: N/A
N\A - No Change Necessary

Disposition: Closed No Change

subjectType is not documented on page 3 of the Statement Information Model

Logged: https://github.com/cts2/cts2-specification/issues/92

PIM: Update PIM text
PSM: N/A

11-09-02 CTS2 Code System and Code System Version Catalog Services

On page 16 the attribute of the CodeSystemCatalogVersionEntry the defaultLanguage is defined as the default spoken or written language used in this version. If we look at the cardinality we see it is [0..1]. We believe this should be [0..*]. HL7 CTS2 specifies " The different languages (supportedLanguages) supported by the Code System in this version". For certain official terminology providers the same version can be multilingual. For example the file supplied by ISO ISO-639-2_utf-8.txt is both in English and in French. STS implements the attribute supportedLanguages as a list of languages, which we believe is much more fitted than a defaultLanguage attribute (with only one language). Proposition: Change cardinality.

Logged: https://github.com/cts2/cts2-specification/issues/71

PIM: Updated Diagram (Figure 3.1: Code System Version, Page 19.)
PSM:
Change Location: CodeSystemVersion.xsd
Added a 'supportedLanguage' element to "CodeSystemVersionCatalogEntry."
<xs:element name="supportedLanguage" type="core:LanguageReference" minOccurs="0" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation>all languages recognized by this particular code system version</i></xs:documentation>
</xs:annotation>
</xs:element>

The introductory section about conventions and the like needs to be included in all of the modules. Currently it is just in the Core

Logged: https://github.com/cts2/cts2-specification/issues/93

PIM: Update PIM text
PSM: N/A

restrictToCodeSystem lists InvalidDirectoryType twice in the exception list.

Logged: https://github.com/cts2/cts2-specification/issues/95

PIM:
Update PIM text
PSM:
N/A

The type of knownCodeSystem should be CodeSystemReference instead of CodeSystemVersionReference. This needs to be corrected in both the PIM and the Service schema

Logged: https://github.com/cts2/cts2-specification/issues/94

PIM: Update Diagram (Figure 3.2: Entity Description Query Service)

PSM: In the 'EntityDescriptionReadService' and 'EntityDescriptionQueryService' types, change:
<xs:element name="knownCodeSystem" type="core:CodeSystemVersionReference" minOccurs="0" maxOccurs="unbounded"/>
to
<xs:element name="knownCodeSystem" type="core:CodeSystemReference" minOccurs="0" maxOccurs="unbounded"/>

The stereotype indicates that the operation may change the service state, which is the opposite of the UML isQuery tag. You need to set the isQuery tag to true on all non-delta operations and then include documentation on each operation to repeat what it means because everyone will ignore it otherwise.

Logged: https://github.com/cts2/cts2-specification/issues/111

PIM: Update PIM text
PSM: N/A

MatchValueFormatException was incorrectly typed as "exeption" instead of "exception", which means that it isn't included in the formal PDF documents or Exceptions.xsd. Need to add it to the documentation and the schema.

Logged: https://github.com/cts2/cts2-specification/issues/117

PIM: Update PIM text

PSM: Change the MatchValueFormatException type to 'exception.'

This is related to the string issue pointed out by Manfred. Boolean cannot be defined as a data type, as it is already part of the UML core.

Logged: https://github.com/cts2/cts2-specification/issues/116

PIM: Update PIM text
PSM: N/A

ValidationResponse was missing in final model.

Logged: https://github.com/cts2/cts2-specification/issues/115

PIM: Update PIM text
PSM: N/A

String cannot be defined as a data type, as it is already part of the UML core.

Logged: https://github.com/cts2/cts2-specification/issues/113

PIM: Update PIM text
PSM: N/A

In the WADL (REST PSM), a Create is done with an HTTP 'PUT' and an update is done with an HTTP 'POST'. This is problematic because a client must have knowledge of the URL structure before doing a create. It will limit implementation as-is because clients cannot be expected to know the URL structure of a resource before it is created. In the case of an update, a 'PUT' is more appropriate because we assume that at that point the client does know the URL of the resource.

Logged: https://github.com/cts2/cts2-specification/issues/84

PIM: N/A
PSM:
Change all creates to an HTTP 'POST' and all updates to an HTTP 'PUT'.

In the StructuralProfile enum, should there be 'SP_STATEMENT' and/or 'SP_MAP_ENTRY' ?

It could be that Statement is intended to be included in the 'Association' profile and MapEntry in the 'MapVersion' profile. If that is the case this issue would be a no-op, or at most a documentation note.

Logged: https://github.com/cts2/cts2-specification/issues/86

PIM: N/A
PSM:
Added two new enum values: 'SP_MAP_ENTRY" and "SP_STATEMENT" to the StructuralProfile enum.
<xs:enumeration value="SP_MAP_ENTRY">
<xs:annotation>
<xs:documentation>The <b>Map_Entry</b> profile represents
individual entries in a
<b>Map_Version</b></xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="SP_STATEMENT">
<xs:annotation>
<xs:documentation>The <b>Statement</b> profile provides a
bridge between the CTS2 model structure and the
underlying RDF/XML/etc.</xs:documentation>
</xs:annotation>
</xs:enumeration>

Map.xsd MapCatalogEntry currentVersion does not have an XSD type. Should be MapVersionReference...

Logged: https://github.com/cts2/cts2-specification/issues/89

PIM: N/A
PSM:
Changed the type of 'currentVersion' to 'MapVersionReference.'
Original:
<xs:element name="currentVersion" minOccurs="0">
Updated:
<xs:element name="currentVersion" type="core:MapVersionReference" minOccurs="0">

ScopedEntityName.name is set to LocalIdentifier in the XML Schema. The UML specification shows it as "String" and its current setting is preventing us from using SNOMED CT fully specified names and other useful sources.

Logged: https://github.com/cts2/cts2-specification/issues/91

PIM: N/A
PSM:
Changed the 'name' element from 'LocalIdentifier' to 'String.'

The documentation got stripped in the RestResource type in Core.xsd. We propose it read as:

xs:annotation

xs:documentationThe relative URI of the resource with respect to the resourceRoot. As an example,

if the resource URI was "http://informatics.mayo.edu/cts2/rest/codesystems", the resourceURI would

be "codesystems". Fragment and query identifiers should also be included./xs:documentation

xs:appinfoPSM/xs:appinfo

/xs:annotation

/xs:element

xs:annotation

xs:documentationThe paramaters that were used in executing the query. This carries all of the parameters that

are needed to reconstruct the complete query in either a RESTful or procedural environment. The service provider

may or may not include non-CTS2 related parameters such as security tokens, routing requests, etc./xs:documentation

xs:appinfoPSM/xs:appinfo

/xs:annotation

/xs:element

xs:annotation

xs:documentationThe date and time that the resource was accessed./xs:documentation

xs:appinfoPSM/xs:appinfo

/xs:annotation

/xs:element

Logged: https://github.com/cts2/cts2-specification/issues/87

PIM: N/A
PSM:
Added in documentation to the 'RestResource' type as described in the updated xml below.

The current xml schemas in the rest/schema directory present an inconsistent combination of the "Venetian Blind" and "Garden of Eden" schema patterns (http://developers.sun.com/jsenterprise/archive/nb_enterprise_pack/reference/techart/design_patterns.html), where all elements except the elemMsg, elemList and elemDirectory have both complexType and element declarations. The approaches to these two patterns can be quite different in a schema compiler such as pyxb. We propose that all element declarations follow the general pattern:

...

/xs:complexType

For resources that can be document level elements and complex (or simple) for the rest)

Logged: https://github.com/cts2/cts2-specification/issues/88

PIM: N/A
PSM:
Changed any XSD Element in the form of:
<xs:element name='x'>
<xs:complexType>
...
</xs:complexType>
</xs:element>
to:
<xs:element name='x' type = 'x'/>
<xs:complexType name='x'>
...
</xs:complexType>

Rename method 'getKnownCodeSystems' to 'getKnownCodeSystem'.

Rename method 'getKnownCodeSystemVersions' to 'getKnownCodeSystemVersion'.

In method 'restrictToTargetExpression' change the type of param 'target' to EntityExpression

In method 'count' add parameter 'timeout'.

In method 'restrict' change the type of param 'directory' to DirectoryURI

In method 'restrictToTargetLiteral' change the type of param 'target' to String

Logged: https://github.com/cts2/cts2-specification/issues/50

PIM: N/A
PSM:
• Rename method 'getKnownCodeSystems' to 'getKnownCodeSystem'.
• Rename method 'getKnownCodeSystemVersions' to 'getKnownCodeSystemVersion'.
• In method 'restrictToTargetExpression' change the type of param 'target' to EntityExpression
• In method 'count' add parameter 'timeout'.
• In method 'restrict' change the type of param 'directory' to DirectoryURI
• In method 'restrictToTargetLiteral' change the type of param 'target' to String

The QueryControl parameter was omitted from the read and readByURI operations in ConceptDomainBindingService.

Logged: https://github.com/cts2/cts2-specification/issues/81

PIM:
In the ConceptDomainBindingService - methods 'read' and 'readByUri', add a parameter 'queryControl of type 'AssociationDirectoryURI.'
Updated Diagram (Figure 4.1: Concept Domain Binding Read. Concept Domain Binding, Page 20.)

PSM:
Add in the following element to types 'read' and 'readByURI':

<xs:element minOccurs="0" name="queryControl" type="coreService:QueryControl" />

In the AssociationQueryService, the method 'getAllSourceAndTargetEntities' accepts an 'EntityDirectoryURI' as an input. I believe that it should accept an 'AssociationDirectoryURI' (as 'getSourceEntities', 'getTargetEntities', and 'getPredicates' do).

Logged: https://github.com/cts2/cts2-specification/issues/83

PIM: N/A
In the AssociationQueryService - method 'getAllSourceAndTargetEntities', change the parameter 'directory' to type 'AssociationDirectoryURI.'

PSM: N/A

11-09-03 CTS2 Concept Domain and Concept Domain Binding Services

In section 2.2 Concept Domain Catalog Query Service the section goes onto describing Concept Domain Catalog History. Is is possible that the Query service description (resolve and resolveAsList) were missed due to a cut and paste error?

Logged: https://github.com/cts2/cts2-specification/issues/75

PIM: N/A
PSM: N/A
After review, the existing text is correct, and the change should not be applied to the PIM.

11-09-08 Value Set services - The ValueSetCatalogReadService provides direct access to the service map catalog. Typo - Value Set Catalog instead of service map catalog.

Logged: https://github.com/cts2/cts2-specification/issues/78

PIM: Update PIM text
PSM: N/A

In the pdf2 in section 1.1.2.1 Class CodeSystemCatalogEntryDirectory we think this is a typo and it should be CodeSystemDirectory.

Logged: https://github.com/cts2/cts2-specification/issues/69

PIM: N/A
PSM: N/A
After review, the existing text is correct, and the change should not be applied to the PIM.

In method 'putChangeSet' add param 'errorResponse'

In method 'validateChangeSet' add param 'validationLevel'

In method 'updateChangeSetMetadata' add param 'officialEffectiveDate'

In method 'updateChangeableMetadata' remove params 'target' and 'owner' and add param 'entryID'

Removed methods 'createAssociationsFromExpression' and 'createAssociationFromExpression'

Added method 'addAssociation

Added params 'subject', 'predicate', 'target', 'ecternalStatementId' to method 'updateAssociation;

Logged: https://github.com/cts2/cts2-specification/issues/54

PIM: N/A
PSM:
• In method 'putChangeSet' add param 'errorResponse'
• In method 'validateChangeSet' add param 'validationLevel'
• In method 'updateChangeSetMetadata' add param 'officialEffectiveDate'
• In method 'updateChangeableMetadata' remove params 'target' and 'owner' and add param 'entryID'
• Removed methods 'createAssociationsFromExpression' and 'createAssociationFromExpression'
• Added method 'addAssociation

In method 'count' add parameter 'timeout'

For methods 'getLatestChangeFor', 'getChangeHistoryFor', and 'getEarliestChangeFor' change param 'assocation' type to URI

Add methods 'getEarliestServiceChange', 'getLatestServiceChange', and 'getLatestServiceChange'

Logged: https://github.com/cts2/cts2-specification/issues/53

PIM: N/A
PSM:
• In method 'count' add parameter 'timeout'
• For methods 'getLatestChangeFor', 'getChangeHistoryFor', and 'getEarliestChangeFor' change param 'assocation' type to URI
• Added methods 'getEarliestServiceChange', 'getLatestServiceChange', and 'getServiceHistoryFor'

In method 'readByExternalStatementId' remove param 'assertingCodeSystemVersion' and replace with 'scopingNamespace'.

In method 'existsByExternalStatementId' remove param 'assertingCodeSystemVersion' and replace with 'scopingNamespace'.

In method 'read' change type of 'associationId' param to URI

In method 'exists' change type of 'associationId' param to URI

Logged: https://github.com/cts2/cts2-specification/issues/52

PIM: N/A
PSM:
• In method 'readByExternalStatementId' remove param 'assertingCodeSystemVersion' and replace with 'scopingNamespace'.
• In method 'existsByExternalStatementId' remove param 'assertingCodeSystemVersion' and replace with 'scopingNamespace'.
• In method 'read' change type of 'associationId' param to URI
• In method 'exists' change type of 'associationId' param to URI

Rename method 'getKnownCodeSystems' to 'getKnownCodeSystem'.

Rename method 'getKnownCodeSystemVersions' to 'getKnownCodeSystemVersion'.

Rename method 'getSupportedVersionTags' to 'getSupportedVersionTag'.

In method 'restrictToTargetExpression' change the type of param 'target' to EntityExpression

In method 'count' add parameter 'timeout'.

In method 'getAllSourceAndTargetEntities' change the type of param 'directory' to EntityDirectoryURI

In method 'restrict' change the type of param 'directory' to DirectoryURI

In method 'restrictToTargetLiteral' change the type of param 'target' to String

Logged: https://github.com/cts2/cts2-specification/issues/51

PIM: N/A
PSM:
• Rename method 'getKnownCodeSystems' to 'getKnownCodeSystem'.
• Rename method 'getKnownCodeSystemVersions' to 'getKnownCodeSystemVersion'.
• In method 'restrictToTargetExpression' change the type of param 'target' to EntityExpression
• In method 'count' add parameter 'timeout'.
• In method 'restrict' change the type of param 'directory' to DirectoryURI
• In method 'restrictToTargetLiteral' change the type of param 'target' to String

In method 'readChangeSet' add param 'queryControl;

In method 'updateChangeSetMetadata added param 'officialEfectiveDate;

In method putChangeSet change return type to ProcessStatus

Logged: https://github.com/cts2/cts2-specification/issues/63

PIM: N/A
PSM:
• In method 'readChangeSet' add param 'queryControl'
• In method 'updateChangeSetMetadata added param 'officialEffectiveDate'
• In method putChangeSet change return type to ProcessStatus'

In 'count' method added 'timeout' param.

Renamed method 'restrictToCodeSystemVersions' to 'restrictToCodeSystemVersion'

Added method 'restrictToEntities', 'isEntityInSet', and 'intersectEntityList'

Renamed method 'restrictToCodeSystems' to 'restrictToCodeSystem'

Logged: https://github.com/cts2/cts2-specification/issues/62

PIM: N/A
PSM:
• In 'count' method added 'timeout' param.
• Renamed method 'restrictToCodeSystemVersions' to 'restrictToCodeSystemVersion'
• Added method 'restrictToEntities', 'isEntityInSet', and 'intersectEntityList'
• Renamed method 'restrictToCodeSystems' to 'restrictToCodeSystem'

Rename method 'getKnownCodeSystems' to 'getKnownCodeSystem'.

Rename method 'getKnownCodeSystemVersions' to 'getKnownCodeSystemVersion'.

Rename method 'getSupportedVersionTags' to 'getSupportedVersionTag'.

Logged: https://github.com/cts2/cts2-specification/issues/49

PIM: N/A
PSM:
• Rename method 'getKnownCodeSystems' to 'getKnownCodeSystem'.
• Rename method 'getKnownCodeSystemVersions' to 'getKnownCodeSystemVersion'.
• Rename method 'getSupportedVersionTags' to 'getSupportedVersionTag'

In method 'count' add param 'timeout'.

Rename 'getLatestChange' to 'getLastChange'.

In method 'getChangeHistoryFor' rename param 'codeSystem' to 'codeSystemVersion'

In method 'getEarliestChangeFor' rename param 'codeSystem' to 'codeSystemVersion'

Logged: https://github.com/cts2/cts2-specification/issues/48

PIM: N/A
PSM:
• In 'count' method added 'timeout' param.
• Rename 'getLatestChange' to 'getLastChange'.
• In method 'getChangeHistoryFor' rename param 'codeSystem' to 'codeSystemVersion'
• In method 'getEarliestChangeFor' rename param 'codeSystem' to 'codeSystemVersion'

In method 'putChangeSet' added param 'errorResponse'

In method 'updateChangeSetMetadata' added param 'officialEffectiveDate'

In method 'readChangeSet' added param 'queryControl'

In method 'updateConceptDomainBinding' renamed param 'conceptDomain' to conceptDomainBinding'

In method 'validateChangeSet' added param 'validationLevel'

In method 'updateChangeableMetadata' removed 'target' and 'owner' params and added 'entryID' param.

In method 'newProperty' removed param 'entity' and added param 'predicate'

Logged: https://github.com/cts2/cts2-specification/issues/58

PIM: N/A
PSM:
• In method 'putChangeSet' add param 'errorResponse'
• In method 'validateChangeSet' add param 'validationLevel'
• In method 'updateChangeSetMetadata' add param 'officialEffectiveDate'
• In method 'readChangeSet' added param 'queryControl'
• In method 'updateChangeableMetadata' remove params 'target' and 'owner' and add param 'entryID'
• In method 'updateConceptDomainBinding' renamed param 'conceptDomain' to conceptDomainBinding'
• In method 'newProperty' removed param 'entity' and added param 'predicate'

In method 'count' add a 'timeout' param.

Logged: https://github.com/cts2/cts2-specification/issues/57

PIM: N/A
PSM: In 'count' method added 'timeout' param.

Changed all URI param types from String to LocalURI or DocumentURI

Logged: https://github.com/cts2/cts2-specification/issues/56

PIM: N/A
PSM: Changed all URI param types from String to LocalURI or DocumentURI

Renamed method 'getKnownCodeSystems' to 'getKnownCodeSystemVersion'

Removed method 'getSupportedVersionTags'

Logged: https://github.com/cts2/cts2-specification/issues/61

PIM: N/A
PSM: Renamed method 'getKnownCodeSystems' to 'getKnownCodeSystemVersion'

In method 'count' added a 'timeout' param

In method 'readChangeSet' renamed param 'URI' to 'changeSetURI'

Logged: https://github.com/cts2/cts2-specification/issues/60

PIM: N/A
PSM:
• In 'count' method added 'timeout' param.
• In method 'readChangeSet' renamed param 'URI' to 'changeSetURI'

Removed method 'getSupportedVersionTags' and 'fromEntityDirectory'

In method 'toAssociationFormat' changed type of param 'codeSystemVersion' to 'CodeSystemVersionReference'

Logged: https://github.com/cts2/cts2-specification/issues/55

PIM: N/A
PSM:
Removed method 'getSupportedVersionTags' and 'fromEntityDirectory'
• Reason: Refactored into BaseService

In method 'toAssociationFormat' changed type of param 'codeSystemVersion' to 'CodeSystemVersionReference'
• Reason: Typo

In method 'count' added a 'timeout' param

Logged: https://github.com/cts2/cts2-specification/issues/59

PIM: N/A
PSM: In 'count' method added 'timeout' param.

SortCriteria contains PropertyReference, which implies that the user needs to know the EntityName AND URI of the Property to sort. We want all user input to be Name OR URI. There needs to be a flavor of SortCriteria that doesn't require the user to know the Name AND URI of the Property to sort.

Logged: https://github.com/cts2/cts2-specification/issues/5

PIM: N/A
PSM:
In the type 'SortCriterion', the element 'sortElement' was changed from:
type="core:PropertyReference"
to
type="PropertyNameOrURI"

'applicableContext' cardinality in ConceptDomainBinding (XSD) needs to change to 0..1 to align with the PIM.

Logged: https://github.com/cts2/cts2-specification/issues/4

PIM: N/A
PSM:
Changed the 'applicableContext' attribute of ConceptDomainBinding from:
minOccurs="0" maxOccurs="unbounded"
to:
minOccurs="0" maxOccurs="1"

'bindingQualifier' in ConceptDomainBinding (XSD) should be moved to an Element of type BindingQualifierReference and be 0..1.

Logged: https://github.com/cts2/cts2-specification/issues/3

PIM: N/A
PSM:
• Attribute 'bindingQualifier' in ConceptDomainBinding (XSD) was removed.
• Element of type BindingQualifierReference with cardinality 0..1 was added.

'boundValueSet' cardinality in ConceptDomainBindingDirectoryEntry (XSD) needs to change from 0..* to to 1..1

Logged: https://github.com/cts2/cts2-specification/issues/2

PIM: N/A
PSM:
Change cardinality of ConceptDomainBindingDirectoryEntry from:
minOccurs="0" maxOccurs="unbounded"
to the XML default, which is:
minOccurs="1" maxOccurs="1"

Add effectiveDate, changeNotes, changeSource parameters, all optional. Used to update ChangeDescription if supported by the service

Logged: https://github.com/cts2/cts2-specification/issues/11

PIM: Updated Diagram (Figure 3.7: Maintenace Service. Core, Page 56.)
PSM:
Add in the following elements to the type 'UpdateChangeableMetadataRequest':

<xs:element name="updatedEffectiveDate" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element name="effectiveDate"
type="core:DateAndTime" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="updatedChangeNotes" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element name="changeNotes" type="core:OpaqueData"
minOccurs="0"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="updatedChangeSource" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element name="changeSource"
type="core:SourceReference" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
</xs:element>

Changeable/ChangeDescription typo

PIM: Update PIM text
PSM: N/A

FilterComponent is a PropertyReference and contains a MatchAlgorithm reference, which implies that the user needs to know the Name AND URI of both of these. We want all user input to be Name OR URI. There needs to be a flavor of FilterComponent that doesn't require the user to know the Name AND URI of these.

Logged: https://github.com/cts2/cts2-specification/issues/6

PIM: N/A
PSM:
A new FilterComponent type was introduced to extend from "PropertyNameOrURI" instead of "PropertyReference". This type is to be used for all client interaction into the interfaces on the PSM level.

Target cardinalityTarget should be 1..* to allow things like unionof(a,b,c...). Need to change spec and schema

PIM:
Updated Diagram (Figure 1.1: Statement Model. Statement, Page 2.)
PSM:
Change the 'target' element in the type 'AnonymousStatement' from
<xs:element name="target" type="StatementTarget" minOccurs="1" maxOccurs="1">
to
<xs:element name="target" type="StatementTarget" minOccurs="1" maxOccurs="unbounded">

ChangeType, committed, containingChangeSet, prevChangeSet, changeDate and clonedResource should be ReadOnly

Logged: https://github.com/cts2/cts2-specification/issues/9

PIM:
Updated Diagram (Figure 2.12: CTS2 Change Model. Core, Page 30.)
PSM: N/A

StatmentQualifier -> statementQualifier

Logged: https://github.com/cts2/cts2-specification/issues/8

PIM:
Update PIM text
Updated Figure 1.1: Statement Model. Statement Information Model, Page 2.

PSM: N/A

in ValuseSetDefinition.xsd, SpecificEntityList is defined as an extension of ValueSetDefinitionEntry. This is not correct - it should be a stand alone type.

Logged: https://github.com/cts2/cts2-specification/issues/24

PIM: N/A
PSM:
Remove the 'ValueSetDefinitionEntry' extension from the complex type 'SpecificEntityList'.

Core.xsd defines Note with both assertingInCodeSystemVersion and externalId as attributes, making the type of assertingCodeSystemVersion "CodeSystemVersionName". Entity.xsd defines Designation them both as elements, with the type of assertingCodeSystemVersion set to "CodeSystemVersionReference".

Recommend that the Note pattern be used in Designation as well

Logged: https://github.com/cts2/cts2-specification/issues/23

PIM: N/A
PSM:
Apply the element/attribute convention of the type 'Note' to the type 'Designation'.

The XML Schema uses xsd:restriction to constrain the type of URI that can be used in EntityDescription. It accidentally factored out the name and description attributes, however. This change has been submitted to version control

Logged: https://github.com/cts2/cts2-specification/issues/25

PIM: N/A
PSM:
A sequence was inserted include the name and description attributes (addtion shown below):
<xs:sequence>
<xs:element name="name" type="ScopedEntityName" minOccurs="0">
<xs:annotation>
<xs:documentation>the namespace and name by which this
entity is known within the context of the service
implementation</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="knownEntityDescription"
type="DescriptionInCodeSystem" minOccurs="0"
maxOccurs="unbounded">
<xs:annotation>
<xs:documentation>a reference to a version of a code
system that makes one or more assertions about the
referenced entity. Note that only one version of a
given code system is allowed in the
<i>describingCodeSystem</i> list. Unless specified
otherwise in a specific call, the code system version
with the tag "CURRENT" must be
used.</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>

Should be 0..*

Logged: https://github.com/cts2/cts2-specification/issues/15

PIM:
Updated Diagram (Figure 2.4 :Code System Catalog Maintenance. Code System Catalog, Page 15.)

PSM:
Update the ''UpdateCodeSystemCatalogEntry' type with a new element to allow for updates of 'usedOntologyEngineeringTool'.

Add in an element to 'UpdateCodeSystemCatalogEntry' to allow for updates of 'usedOntologyEngineeringTool'

<xs:element name="updatedUsedOntologyEngineeringTools"
minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element name="usedOntologyEngineeringTool"
type="core:OntologyEngineeringToolReference"
minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>

CTS2: Core spec p57 typo
Createchangeset condition 8
https://github.com/cts2/cts2-specification/issues/12

Core spec p62 typo
AbstractResourc.... Goes off page
Logged: https://github.com/cts2/cts2-specification/issues/13

CTS2: Core spec p75 typo
ExportStatus missing documentation
Logged: https://github.com/cts2/cts2-specification/issues/14

PIM:
Update PIM text
PSM:
N/A

The documentation for ProfileElement in CoreService.xsd is not correct. Need to chase this back to its source and fix it.

Logged: https://github.com/cts2/cts2-specification/issues/27

PIM:
N/A

PSM:
Add the following documentation to the 'ProfileElement' type:

ProfileElement appears in service implementations, once per structural profile that is supported by the implementation instance. Each occurrence records the set of functional profiles that are supported for the specific structural profile

There is currently no way to get to each of the service implementations from the main page of the service. The XML Schema for Profile Element needs to support (require?) a href for each of the profile element functions. As an example, if a service supports SP_CODE_SYSTEM FP_READ, there should be a URL that links to the service implementation of CodeSystemCatalogEntryReadService

Logged: https://github.com/cts2/cts2-specification/issues/26

PIM:
N/A

PSM:
Create a new type 'FunctionalProfileEntry' and associated it to 'ProfileElement' as shown below.

Type should be OntologyEngineeringToolReference...

Check omv for "used" vs. "uses"

Logged: https://github.com/cts2/cts2-specification/issues/16

PIM:
Updated Diagram (Figure 1.1: Code System Catalog Entry. Code System, Page 3.)

PSM:
Add in a 'usedOntologyEngineeringTool' element to the type 'CodeSystemCatalogEntry'.
<xs:element name="usedOntologyEngineeringTool"
type="core:OntologyEngineeringToolReference" minOccurs="0"
maxOccurs="unbounded">
<xs:annotation>
<xs:documentation>information about a tool used to create
the ontology</xs:documentation>
</xs:annotation>
</xs:element>

Need to add all parameters to UpdateEntityDescription and add the optparam pattern:

xs:complexType

xs:sequence

/xs:sequence

/xs:complexType

/xs:element

Logged: https://github.com/cts2/cts2-specification/issues/22

PIM: N/A
PSM:
Wrapper all mutable elements in the pattern show above

EntityDescriptionServices.xsd doesn't have suppportedVersionTag in the query service

Logged: https://github.com/cts2/cts2-specification/issues/21

PIM: N/A
PSM:
Add a new Element to the complexType "EntityDescriptionQueryService."
<xs:element name="supportedVersionTag" type="core:VersionTagReference"
minOccurs="1" maxOccurs="unbounded"/>

The ChangeSet element in the Updates schematic doesnt have the message header.

https://github.com/cts2/cts2-specification/issues/19

PIM: N/A
PSM:
Add a 'ChangeSetMsg' element.

"To accomplish this, every EntityDescription ..." -> EntitySynopsis

Logged: https://github.com/cts2/cts2-specification/issues/18

PIM: Update PIM text
PSM: N/A

EntityDescriptionServices.xsd doesn't have knownCodeSystem, knownCodeSystemVersion or supportedVersionTag in the schema.

Logged: https://github.com/cts2/cts2-specification/issues/20

PIM: N/A
PSM:
Added the following elements to the complexType "EntityDescriptionReadService"

<xs:element name="knownCodeSystem" type="core:CodeSystemVersionReference" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="knownCodeSystemVersion" type="core:CodeSystemVersionReference" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="supportedVersionTag" type="core:VersionTagReference" minOccurs="1" maxOccurs="unbounded"/>

Last line is "tetrieve"

Logged: https://github.com/cts2/cts2-specification/issues/17

PIM: Update PIM text
PSM: N/A

All CTS2 WSDLs contain inline XSD type definitions. We would like to refactor those out into separate XSD files in order to make code generation easier for tooling (mainly, Castor).

Logged: https://github.com/cts2/cts2-specification/issues/41

PIM: N/A
PSM:
XSD declarations inside of WSDL files were making it difficult for tooling to process and generate code from the WSDL files. To work around this, and to make a clean separation between WSDL 'types' and WSDL 'functionality', all types that were previously inlined into the wsdl via the wsdl:types tag have been refactored into an XSD file.

ResolvedValueSet needs two additional service entries - a read service that carries:

read (by RVS URI)

resolveAsEntityDirectory

resolveAsCompleteSet

(Same methods as the ValueSetResolutionService except that the argument is a single ResolvedValueSetURI)

and a simple query service that carries:

contains(resolvedSet, EntityNameOrURIList (move from loader)

resolvedSetsFor(EntityNameOrURI, ...) -> tells which resolved sets carry the entity

Logged: https://github.com/cts2/cts2-specification/issues/40

PIM:
1. Introduce a new type - 'IterableResolvedValueSet' - and change the 'ResolvedValueSetDirectoryEntry' to be a subtype of 'ResolvedValueSetSummary.'
2. Added a new service, 'ResolvedValueSetResolution' Service, which follows the same general resolution patterns as 'ValueSetDefinitionResolution' service. The 'contains' method is moved from 'ResolvedValueSetLoader' to this new 'ResolvedValueSetResolution' service.

3. Add a new type of DirectoryURI, "ResolvedValueSetDirectoryURI.
4. In order to query for 'ResolvedValueSets', a new service - 'ResolvedValueSetQuery' Service was added
PSM:
Added an 'IterableResolvedValueSet' type.

ResolvedValueSetDirectory is the return type of the "resolve" function for ValueSetDefinitionResolution, which should return a ResolvedValueSetHeader as part of the directory and an iteratable EntitySynopsis list. Both the name and model of this particular return type need to be fixed. This change applies to the UML and spec, the XML Schema and the WSDL/WADL

Logged: https://github.com/cts2/cts2-specification/issues/39

PIM: Updated Diagram (Figure 3.4: Resolved ValueSet. ValueSetDefinition, Page 27.)
PSM: Add the type 'IteratableResolvedValueSet' to allow for iterable access of a 'ResolvedValueSet'.

The AdvancedAssociationQuerySerivce is not fully specified in the WADL (REST PSM). The actual AdvancedAssociationQuerySerivce url (/service/advancedassociationqueryservice) is specified, but not the implementation.

Logged: https://github.com/cts2/cts2-specification/issues/38

PIM: N/A
PSM:
The AdvancedAssociationQuerySerivce resources were added to the cts2.wadl. A resource 'graph' was added with all parameters outlined below.

Derivation and derivationReasoningAlgorithm shouldn't be marked as

, as it is not part of the identity of Association. These two fields need to be added as optparams in UpdateAssociationRequest (Needs to be changed in the WADL and Schema as well.

Logged: https://github.com/cts2/cts2-specification/issues/37

PIM:
Updated Diagram (Figure 4.1: Association Model. Association, Page 43.)
Updated Diagram (Figure 5.4: Association Maintenance. Association, Page 67.)

PSM:
Add the following elements to the 'UpdateAssociationRequest' type:
<xs:element minOccurs="0" name="updatedDerivation">
<xs:complexType>
<xs:sequence>
<xs:element name="derivation" type="association:AssociationDerivation" minOccurs="1" maxOccurs="1"/>
</xs:sequence>
</xs:complexType>
</xs:element>
and
<xs:element minOccurs="0" name="updatedDerivationReasoningAlgorithm">
<xs:complexType>
<xs:sequence>
<xs:element name="derivationReasoningAlgorithm" type="core:ReasoningAlgorithmReference" minOccurs="1" maxOccurs="1"/>
</xs:sequence>
</xs:complexType>
</xs:element>

blank exceptions entry

Logged: https://github.com/cts2/cts2-specification/issues/36

PIM:
Update PIM text
PSM:
N/A

subject - ahe subject

Logged: https://github.com/cts2/cts2-specification/issues/35

PIM: Update PIM text
PSM: N/A

Need to add an identifier to the statement model:

statementURI : ExternalURI

to indicate that they are part of the statement identity.

Logged: https://github.com/cts2/cts2-specification/issues/34

PIM:
Updated Diagram (Figure 1.1: Statement Model. Statement, Page 2.)

PSM:
Added a 'StatementURI' element to the type 'Statement'

<xs:element name="statementURI" type="core:URI"
minOccurs="1" maxOccurs="1">
<xs:annotation>
<xs:documentation>The unique statement identifier. Must be globally unique if information is to be exchanged and updated on the statement leve.</xs:documentation>
</xs:annotation>
</xs:element>

Renamed method 'getCodeSystemVersionByExternalId' to 'getCodeSystemByVersionId'.

Renamed method 'existsExternalId' to 'existsVersionId'.

Logged: https://github.com/cts2/cts2-specification/issues/45

PIM: N/A
PSM:
• Renamed method 'getCodeSystemVersionByExternalId' to 'getCodeSystemByVersionId'.
• Renamed method 'existsExternalId' to 'existsVersionId'.

In the 'count' method, added a 'timeout' parameter.

Logged: https://github.com/cts2/cts2-specification/issues/44

PIM: N/A
PSM:
• In the 'count' method, added a 'timeout' parameter.

Added 'timeout' parameter to 'count' method

Changed 'getLatestChangeFor' method name to 'getLastChangeFor' to match the PIM

Logged: https://github.com/cts2/cts2-specification/issues/43

PIM: N/A
PSM:
• In 'count' method added 'timeout' param.
• Changed 'getLatestChangeFor' method name to 'getLastChangeFor' to match the PIM

In method 'updateChangeableMetadata', removed params 'target' and 'owner' and addded 'entryID' to match the spec.

In method 'validateChangeSet', added param 'validationLevel'.

In method 'readChangeSet', added param 'queryControl'.

In method 'putChangeSet', added parameter 'errorResponse'.

Logged: https://github.com/cts2/cts2-specification/issues/42

PIM: N/A
PSM:
• In method 'putChangeSet' add param 'errorResponse'
• In method 'validateChangeSet' add param 'validationLevel'
• In method 'readChangeSet' add param 'queryControl'
• In method 'updateChangeableMetadata' remove params 'target' and 'owner' and add param 'entryID'

Need to add an id attribute to ConceptDomainBinding:

bindingURI: DocumentURI

Need to add an assertion that bindingURI = entryID

Logged: https://github.com/cts2/cts2-specification/issues/33

PIM:
Updated Diagram (Figure 3.1: Concept Domain Binding Model. Concept Domain, Page 17.)

PSM:
Added a 'bindingURI' element to the type ''ConceptDomainBinding'

<xs:element name="bindingURI" type="core:DocumentURI"
minOccurs="1" maxOccurs="1">
<xs:annotation>
<xs:documentation>The unique identifier of this particular
binding instance.</xs:documentation>
</xs:annotation>
</xs:element>

The filter property (type Filter) on BaseQueryService does not work as an input parameter. It needs to be replaced, instead, with:

matchAlgorithm: NameOrURI

matchValue: String OPT

refType: TargetReferenceType

referenceTarget: EntityNameOrURI

Logged: https://github.com/cts2/cts2-specification/issues/32

PIM: Change the signature of restrict to the following: (Diagram below)
PSM:
Added the following elements to the 'Query' element:
<xs:element name="matchAlgorithm" type="NameOrURI" minOccurs="0">
<xs:annotation>
<xs:documentation> The match algorithm of the filter to be
applied. If a 'setOperation' is specified, the filter
will apply to the resulting aggregate.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="matchValue" type="core:String" minOccurs="0">
<xs:annotation>
<xs:documentation> The match value of the filter to be
applied. If a 'setOperation' is specified, the filter
will apply to the resulting aggregate.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="filterComponent" type="NameOrURIList"
minOccurs="0">
<xs:annotation>
<xs:documentation> The target components of the filter to
be applied. If a 'setOperation' is specified, the
filter will apply to the resulting aggregate.
</xs:documentation>
</xs:annotation>
</xs:element>

while removing the following element:
<xs:element name="filter" type="core:Filter" minOccurs="0">
<xs:annotation>
<xs:documentation> The filter to be applied. If a
'setOperation' is specified, the filter will apply to
the resulting aggregate. </xs:documentation>
</xs:annotation>
</xs:element>

The type of SupportedProfile should be ProfileElement, not StructuralProfile

Logged: https://github.com/cts2/cts2-specification/issues/28

PIM: N/A
PSM:
In the type 'BaseService', change 'SupportedProfile' from:
<xs:element name="supportedProfile" type="StructuralProfile" minOccurs="1" maxOccurs="unbounded">
to:
<xs:element name="supportedProfile" type="ProfileElement" minOccurs="1" maxOccurs="unbounded">

In method 'updateChangeSetMetadata', add param 'officialEffectiveDate/

In method 'updateChangeableMetadata' remove params 'target' and 'owner' and add param 'entryID'.

In method 'deleteChangeable' remove param 'target' and add param 'changeableResource'.

In method 'validateChangeSet' add param 'validationLevel'.

In method 'readChangeSet' add param 'queryControl'.

In method 'putChangeSet' add param 'errorResponse'.

Logged: https://github.com/cts2/cts2-specification/issues/47

PIM: N/A
PSM:
• In method 'putChangeSet' add param 'errorResponse'
• In method 'validateChangeSet' add param 'validationLevel'
• In method 'readChangeSet' add param 'queryControl'
• In method 'updateChangeableMetadata' remove params 'target' and 'owner' and add param 'entryID'
• In method 'deleteChangeable' remove param 'target' and add param 'changeableResource'.
• In method 'updateChangeSetMetadata', add param 'officialEffectiveDate'

In method 'resolveAsList', rename param 'control' to 'queryControl' to match spec.

In method 'count', add a 'timeout' param.

Logged: https://github.com/cts2/cts2-specification/issues/46

PIM: N/A
PSM:
• In 'count' method added 'timeout' param.
• In method 'resolveAsList', rename param 'control' to 'queryControl' to match spec.

Need to add an invariant to Changeable indicating that the changeDescription cardinality must be 1..1 if the profile supports HISTORY or MAINTENANCE

Logged: https://github.com/cts2/cts2-specification/issues/31

PIM: Update PIM text
PSM: N/A

Need to check whether this is used anywhere in the spec and pull it if not.

Logged: https://github.com/cts2/cts2-specification/issues/30

PIM: Change the signature of restrict to the following: (Diagram below)
PSM: N/A

Concept Domain Bindings are not referenced anywhere in the specification and the entry needs to be removed from the ReferenceType model

Logged: https://github.com/cts2/cts2-specification/issues/29

PIM:
Updated Diagram (Figure 2.4: Reference Types. Core, Page 10.)

PSM:
N/A