Issues for Common Terminology Services 2 (CTS2) 1.0 FinalizationTask Force

To comment on any of these issues, send email to [email protected]. (Please include the issue number in the Subject: header, thusly: [Issue ###].) To submit a new issue, send email to [email protected].

List of issues (green=resolved, yellow=pending Board vote, red=unresolved)

List options: All ; Open Issues only; or Closed Issues only

Jira Issues

Issue 16347: CTS2 XML file appears to contain EA proprietary elements (cts2-ftf)

Click here for this issue's archive.
Source: Model Driven Solutions (Mr. Steve Cook, steve-c(at)modeldriven.org)
Nature: Uncategorized Issue
Severity:
Summary:

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.

Resolution: 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
Revised Text:
Actions taken:
June 23, 2011: received issue
July 24, 2013: closed issue

Issue 16937: CTS 2: Change 'boundValueSet' cardinality in ConceptDomainBindingDirectoryEntry (XSD) to 1..1 (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

'boundValueSet' cardinality in ConceptDomainBindingDirectoryEntry (XSD) needs to change from 0..* to to 1..1         Logged:  https://github.com/cts2/cts2-specification/issues/2

Resolution: PIM: N/A PSM: Change cardinality of ConceptDomainBindingDirectoryEntry from: minOccurs="0" maxOccurs="unbounded" to the XML default, which is: minOccurs="1" maxOccurs="1"
Revised Text: PIM: N/A PSM: Change Location: ConceptDomainBinding.xsd Original XML <xs:complexType name="ConceptDomainBindingDirectoryEntry"> <xs:annotation> <xs:documentation>A synopsis of a ConceptDomainBinding along with information about how to access the complete resource.</xs:documentation> </xs:annotation> <xs:complexContent> <xs:extension base="core:ResourceDescriptionDirectoryEntry"> <xs:sequence> ------------------><xs:element name="boundValueSet" type="core:ValueSetReference" minOccurs="0" maxOccurs="unbounded"> <xs:annotation> <xs:documentation>the ValueSet being bound</xs:documentation> </xs:annotation> </xs:element> ... </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> Updated XML <xs:complexType name="ConceptDomainBindingDirectoryEntry"> <xs:annotation> <xs:documentation>A synopsis of a ConceptDomainBinding along with information about how to access the complete resource.</xs:documentation> </xs:annotation> <xs:complexContent> <xs:extension base="core:ResourceDescriptionDirectoryEntry"> <xs:sequence> ------------------><xs:element name="boundValueSet" type="core:ValueSetReference"> <xs:annotation> <xs:documentation>the ValueSet being bound</xs:documentation> </xs:annotation> </xs:element> ... </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType>
Actions taken:
December 30, 2011: received issue
July 24, 2013: closed issue

Issue 16938: CTS2: Move 'bindingQualifier' in ConceptDomainBinding (XSD) to an Element (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

    '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

Resolution: PIM: N/A PSM: � Attribute 'bindingQualifier' in ConceptDomainBinding (XSD) was removed. � Element of type BindingQualifierReference with cardinality 0..1 was added.
Revised Text: PIM: N/A PSM: Change Location: ConceptDomainBinding.xsd Original XML <xs:complexType name="ConceptDomainBinding"> <xs:annotation> <xs:documentation>The binding of a ConceptDomain and a ValueSet that supplies the set of permissible value meanings in a given context. ConceptDomainBinding can also bind specific value set definitions and/or specific code system versions where desired. </xs:documentation> </xs:annotation> <xs:complexContent> <xs:extension base="core:Changeable"> ... --------------> <xs:attribute name="bindingQualifier" type="xs:string" use="optional">...</xs:attribute> ... </xs:extension> </xs:complexContent> </xs:complexType> Updated XML <xs:complexType name="ConceptDomainBinding"> <xs:annotation> <xs:documentation>The binding of a ConceptDomain and a ValueSet that supplies the set of permissible value meanings in a given context. ConceptDomainBinding can also bind specific value set definitions and/or specific code system versions where desired. </xs:documentation> </xs:annotation> <xs:complexContent> <xs:extension base="core:Changeable"> <xs:sequence> ... ---------------------> <xs:element name="bindingQualifier" type="core:BindingQualifierReference" minOccurs="0"> ... </xs:element> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType>
Actions taken:
December 30, 2011: received issue
July 24, 2013: closed issue

Issue 16939: CTS 2: Change 'applicableContext' cardinality in ConceptDomainBinding (XSD) to 0..1 (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

    '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

Resolution: PIM: N/A PSM: Changed the 'applicableContext' attribute of ConceptDomainBinding from: minOccurs="0" maxOccurs="unbounded" to: minOccurs="0" maxOccurs="1"
Revised Text: PIM: N/A PSM: Change Location: ConceptDomainBinding.xsd Original XML <xs:complexType name="ConceptDomainBinding"> <xs:annotation> <xs:documentation>The binding of a ConceptDomain and a ValueSet that supplies the set of permissible value meanings in a given context. ConceptDomainBinding can also bind specific value set definitions and/or specific code system versions where desired. </xs:documentation> </xs:annotation> <xs:complexContent> <xs:extension base="core:Changeable"> <xs:sequence> ... --------------><xs:element name="applicableContext" type="core:ContextReference" minOccurs="0" maxOccurs="unbounded"> ... </xs:element> ... </xs:sequence> ... </xs:extension> </xs:complexContent> </xs:complexType> Updated XML <xs:complexType name="ConceptDomainBinding"> <xs:annotation> <xs:documentation>The binding of a ConceptDomain and a ValueSet that supplies the set of permissible value meanings in a given context. ConceptDomainBinding can also bind specific value set definitions and/or specific code system versions where desired. </xs:documentation> </xs:annotation> <xs:complexContent> <xs:extension base="core:Changeable"> <xs:sequence> ... --------------><xs:element name="applicableContext" type="core:ContextReference" minOccurs="0" maxOccurs="1"> ... </xs:element> ... </xs:sequence> ... </xs:extension> </xs:complexContent> </xs:complexType>
Actions taken:
December 30, 2011: received issue
July 24, 2013: closed issue

Issue 16940: CTS 2: SortCriteria contains PropertyReference (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: PIM: N/A PSM: In the type 'SortCriterion', the element 'sortElement' was changed from: type="core:PropertyReference" to type="PropertyNameOrURI"
Revised Text: PIM: N/A PSM: Change Location: CoreService.xsd Original XML <xs:complexType name="SortCriterion"> <xs:annotation> <xs:documentation>The particular attribute, property or special element to be sorted along with the sort direction</xs:documentation> </xs:annotation> <xs:sequence> <xs:element name="sortDirection" type="SortDirection" minOccurs="1" maxOccurs="1"> <xs:annotation> <xs:documentation>The sort order to be applied to the element.</xs:documentation> </xs:annotation> </xs:element> -------------------><xs:element name="sortElement" type="core:PropertyReference" minOccurs="1" maxOccurs="1"> <xs:annotation> <xs:documentation>The type and name of the attribute, property or special element to be sorted</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType> Updated XML <xs:complexType name="SortCriterion"> <xs:annotation> <xs:documentation>The particular attribute, property or special element to be sorted along with the sort direction</xs:documentation> </xs:annotation> <xs:sequence> <xs:element name="sortDirection" type="SortDirection" minOccurs="1" maxOccurs="1"> <xs:annotation> <xs:documentation>The sort order to be applied to the element.</xs:documentation> </xs:annotation> </xs:element> --------------><xs:element name="sortElement" type="PropertyNameOrURI" minOccurs="1" maxOccurs="1"> <xs:annotation> <xs:documentation>The type and name of the attribute, property or special element to be sorted</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType>
Actions taken:
December 30, 2011: received issue
July 24, 2013: closed issue

Issue 16941: CTS 2: FilterComponent is a PropertyReference and contains a MatchAlgorithm reference (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: 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.
Revised Text: PIM: N/A PSM: Change Location: CoreService.xsd <xs:complexType name="FilterComponent"> <xs:annotation> <xs:documentation>A restriction on an attribute, property or special field</xs:documentation> </xs:annotation> <xs:complexContent> <xs:extension base="PropertyNameOrURI"> <xs:sequence> <xs:element name="matchAlgorithm" type="NameOrURI" minOccurs="1"> <xs:annotation> <xs:documentation>the algorithm to be used for testing the referenced component. Examples might include "starts with", "regular expression match", "exists", "inRange", etc. NOTE: The CTS2 specification needs to establish a core set of match algorithms that all compliant implementations must support.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="matchValue" type="core:String" minOccurs="0"> <xs:annotation> <xs:documentation>the value to be used in comparison. The structure and format of matchValue depends on the specific matchAlgorithm. As an example, a "startsWith" algorithm would be plain text, a "regularExpression" algorithm would have a regular expression while an "exists" algorithm would have nothing in the matchValue attribute.</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType>
Actions taken:
December 30, 2011: received issue
July 24, 2013: closed issue

Issue 17070: AnonymousStatement target cardinality (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: 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">
Revised Text: PIM: Updated Diagram (Figure 1.1: Statement Model. Statement, Page 2.) PSM: Change Location: Core.xsd <xs:complexType name="AnonymousStatement"> <xs:annotation> <xs:documentation>A statement lacking a named subject. </xs:documentation> </xs:annotation> <xs:sequence> <xs:element name="predicate" type="PredicateReference" minOccurs="1" maxOccurs="1"> <xs:annotation> <xs:documentation>the predicate of the anonymous statement</xs:documentation> </xs:annotation> </xs:element> ---Original---> <xs:element name="target" type="StatementTarget" minOccurs="1" maxOccurs="1"/> ---Updated---> <xs:element name="target" type="StatementTarget" minOccurs="1" maxOccurs="unbounded"> <xs:annotation> <xs:documentation>the target of the anonymous statement</xs:documentation> </xs:annotation> </xs:element> <xs:element name="statmentQualifier" type="Property" minOccurs="0" maxOccurs="unbounded"> <xs:annotation> <xs:documentation>assertions whose subject is the anonymous statement </xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType>
Actions taken:
January 30, 2012: received issue
July 24, 2013: closed issue

Issue 17071: AnonymousStatement typo (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: PIM: Update PIM text Updated Figure 1.1: Statement Model. Statement Information Model, Page 2. PSM: N/A
Revised Text: PIM: Change Location: Core Information Model, Page 30. Description: In the 'classStatement' diagram in 'AnonymousStatement' Change text: �statmentQualifier� to: �statementQualifier� Figure 1.1: Statement Model. Statement Information Model, Page 2.
Actions taken:
January 30, 2012: received issue
July 24, 2013: closed issue

Issue 17072: ChangeDescription stereotypes (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

ChangeType, committed, containingChangeSet, prevChangeSet, changeDate and clonedResource should be ReadOnly         Logged:  https://github.com/cts2/cts2-specification/issues/9

Resolution: PIM: Updated Diagram (Figure 2.12: CTS2 Change Model. Core, Page 30.) PSM: N/A
Revised Text: PIM: Updated Diagram (Figure 2.12: CTS2 Change Model. Core, Page 30.) PIM: N/A
Actions taken:
January 30, 2012: received issue
July 24, 2013: closed issue

Issue 17073: Changeable/ChangeDescription typo (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

Changeable/ChangeDescription typo

Resolution: PIM: Update PIM text PSM: N/A
Revised Text: PIM: Change Location: Core Information Model, Page 30. Description: Updated diagram "class Updates" to modify the text of the relationship between 'Changeable' and 'ChangeDescription' to be: �sucessor� instead of: �successor� Figure 2.12: CTS2 Change Model. Core Information Model Elements, Page 30.
Actions taken:
January 30, 2012: received issue
July 24, 2013: closed issue

Issue 17074: BaseMaintenanceService.updateChangeableMetadata parameters (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: 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>
Revised Text: PIM: Updated Diagram (Figure 3.7: Maintenace Service. Core, Page 56.) PSM: Change Location: CoreService.xsd <xs:element name="UpdateChangeableMetadataRequest" type="UpdateChangeableMetadataRequest"/> <xs:complexType name="UpdateChangeableMetadataRequest"> <xs:sequence> <xs:element name="updatedStatus" minOccurs="0"> <xs:complexType> <xs:sequence> <xs:element name="status" type="NameOrURI" minOccurs="0"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="updatedEntryState" minOccurs="0"> <xs:complexType> <xs:sequence> <xs:element name="entryState" type="core:EntryState"/> </xs:sequence> </xs:complexType> </xs:element> ---Start-Added---> <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> ---End-Added---> </xs:sequence> </xs:complexType>
Actions taken:
January 30, 2012: received issue
July 24, 2013: closed issue

Issue 17075: Core spec typos (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: PIM: Update PIM text PSM: N/A
Revised Text: PIM: Change Location: Core Computational Model, Page 57. The blank Postcondition in the operation 'createChangeSet' removed. Change Location: Core Information Model, Page 75. 'ExportStatus' changed to have the following documentation: ExportStatus represents the state of an export process that is currently running or has completed. Change Location: Core Information Model, Page 62. Spelling error corrected to have the following documentation: �when updating an instance of an AbstractResource and a ResourceVersionDescription.� PIM: N/A
Actions taken:
January 30, 2012: received issue
July 24, 2013: closed issue

Issue 17076: UpdateCodesystemCatalogEntry.usedOntologyEngineeringTool optionality (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

Should be 0..*         Logged:  https://github.com/cts2/cts2-specification/issues/15

Resolution: 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>
Revised Text: PIM: Updated Diagram (Figure 2.4 :Code System Catalog Maintenance. Code System Catalog, Page 15.) PSM: Change Location: CodeSystemServices.xsd <xs:complexType name="UpdateCodeSystemCatalogEntry"> <xs:complexContent> <xs:extension base="coreservice:UpdateAbstractResourceDescription"> <xs:sequence> <xs:element name="updatedCodeSystemCatagory" minOccurs="0"> <xs:complexType> <xs:sequence> <xs:element name="codeSystemCatagory" type="core:CodeSystemCategoryReference" minOccurs="0" maxOccurs="1"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="updatedDesignedForOntologyTasks" minOccurs="0"> <xs:complexType> <xs:sequence> <xs:element name="designedForOntologyTask" type="core:OntologyTaskReference" minOccurs="0" maxOccurs="unbounded" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="updatedHasOntologyLanguage" minOccurs="0"> <xs:complexType> <xs:sequence> <xs:element name="hasOntologyLanguage" type="core:OntologyLanguageReference" minOccurs="0" maxOccurs="1"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="updatedOntologyDomains" minOccurs="0"> <xs:complexType> <xs:sequence> <xs:element name="ontologyDomain" type="core:OntologyDomainReference" minOccurs="0" maxOccurs="unbounded" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="updatedOntologyType" minOccurs="0"> <xs:complexType> <xs:sequence> <xs:element name="ontologyType" type="core:OntologyTypeReference" minOccurs="0" maxOccurs="unbounded" /> </xs:sequence> </xs:complexType> </xs:element> ---Added---> <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> ---End-Added---> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType>
Actions taken:
January 30, 2012: received issue
July 24, 2013: closed issue

Issue 17077: CodesystemCatalogEntry.usedOntologyEngineeringTool (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

Type should be OntologyEngineeringToolReference...    Check omv for "used" vs. "uses"         Logged:  https://github.com/cts2/cts2-specification/issues/16

Resolution: 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>
Revised Text: PIM: Updated Diagram (Figure 1.1: Code System Catalog Entry. Code System, Page 3.) PSM: Change Location: CoreService.xsd <xs:complexType name="CodeSystemCatalogEntry"> <xs:annotation> <xs:documentation>Metadata and access information about a code system.</xs:documentation> </xs:annotation> <xs:complexContent> <xs:extension base="core:AbstractResourceDescription"> <xs:sequence> <xs:element name="codeSystemCategory" type="core:CodeSystemCategoryReference" minOccurs="0"> <xs:annotation> <xs:documentation>the category or type of resource that the code system represents.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="ontologyDomain" type="core:OntologyDomainReference" minOccurs="0"> <xs:annotation> <xs:documentation>the subject domain of the ontology</xs:documentation> </xs:annotation> </xs:element> <xs:element name="ontologyType" type="core:OntologyTypeReference" minOccurs="0"> <xs:annotation> <xs:documentation>the nature of the content of the ontology</xs:documentation> </xs:annotation> </xs:element> <xs:element name="designedForOntologyTask" type="core:OntologyTaskReference" minOccurs="0" maxOccurs="unbounded"> <xs:annotation> <xs:documentation>the purpose for which the ontology was originally designed</xs:documentation> </xs:annotation> </xs:element> <xs:element name="versions" type="core:CodeSystemVersionCatalogEntryDirectoryURI" minOccurs="0"> <xs:annotation> <xs:documentation>a DirectoryURI that references the known versions of this code system. </xs:documentation> </xs:annotation> </xs:element> <xs:element name="currentVersion" type="core:CodeSystemVersionReference" minOccurs="0" maxOccurs="1"> <xs:annotation> <xs:documentation>a reference to the code system version marked as CURRENT in the service instance.</xs:documentation> </xs:annotation> </xs:element> ---Added---> <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> ---End-Added---> </xs:sequence> <xs:attribute name="codeSystemName" type="core:CodeSystemName" use="required"> <xs:annotation> <xs:documentation>the local identifier that uniquely identifies the code system within the context of the implementing service. Note that the about URI is the globally unique identifier.</xs:documentation> </xs:annotation> </xs:attribute> </xs:extension> </xs:complexContent> </xs:complexType>
Actions taken:
January 30, 2012: received issue
July 24, 2013: closed issue

Issue 17078: Entity description services p20 typo (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

Last line is "tetrieve"         Logged:  https://github.com/cts2/cts2-specification/issues/17

Resolution: PIM: Update PIM text PSM: N/A
Revised Text: PIM: Change Location: Entity Description Services, Page 20. Description: Change text: �tetrieve an entity description ...� to: �retrieve an entity description ...�
Actions taken:
January 30, 2012: received issue
July 24, 2013: closed issue

Issue 17079: AssociationGraph p45 typo (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

"To accomplish this, every EntityDescription ..." -> EntitySynopsis         Logged:  https://github.com/cts2/cts2-specification/issues/18

Resolution: PIM: Update PIM text PSM: N/A
Revised Text: PIM: Change Location: Association Information Model, Page 45 Description: Change text: �To accomplish this, every EntityDescription that occurs ...� to: �To accomplish this, every EntitySynopsis that occurs ...�
Actions taken:
January 30, 2012: received issue
March 24, 2014: closed issue

Issue 17080: ChangeSet element doesn't have a MSG header (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

The ChangeSet element in the Updates schematic doesnt have the message header.         https://github.com/cts2/cts2-specification/issues/19

Resolution: PIM: N/A PSM: Add a 'ChangeSetMsg' element.
Revised Text: PIM: N/A PSM: Change Location: Updates.xsd <xs:element name="ChangeSetMsg"> <xs:annotation> <xs:documentation>An ordered collection of changes that, when applied, will transform a service instance from one consistent state to another. A ChangeSet is viewed as an atomic unit of change - either all of the Changeable elements in a change set will be applied or none of them will be applied. It is anticipated that service implementations will provide a mechanism by which it can apply local business rules to the validation and application of change sets. These rules may include the option to selectively apply, reject, modify or ignore the elements of change sets as they arrive. In this case, it is up to the developers of the business rules to determine what constitutes a "complete" change set that can be applied.</xs:documentation> <xs:appinfo>PSM</xs:appinfo> </xs:annotation> <xs:complexType> <xs:complexContent> <xs:extension base="core:Message"> <xs:sequence> <xs:element name="changeSet" type="ChangeSet" minOccurs="0"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> </xs:element>
Actions taken:
January 30, 2012: received issue
July 24, 2013: closed issue

Issue 17081: EntityDescriptionReadService lacking local variables (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

EntityDescriptionServices.xsd doesn't have knownCodeSystem, knownCodeSystemVersion or supportedVersionTag in the schema.         Logged:  https://github.com/cts2/cts2-specification/issues/20

Resolution: 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"/>
Revised Text: PIM: N/A PSM: Change Location: EntityDescriptionServices.xsd <xs:element name="EntityDescriptionReadService" type="EntityDescriptionReadService"/> <xs:complexType name="EntityDescriptionReadService"> <xs:complexContent> <xs:extension base="coreservice:BaseReadService"> <xs:sequence> <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"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType>
Actions taken:
January 30, 2012: received issue
July 24, 2013: closed issue

Issue 17082: EntityDescriptionQueryService lacking supportedVersionTag (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

EntityDescriptionServices.xsd doesn't have suppportedVersionTag in the query service         Logged:  https://github.com/cts2/cts2-specification/issues/21

Resolution: PIM: N/A PSM: Add a new Element to the complexType "EntityDescriptionQueryService." <xs:element name="supportedVersionTag" type="core:VersionTagReference" minOccurs="1" maxOccurs="unbounded"/>
Revised Text: PIM: N/A PSM: Change Location: EntityDescriptionServices.xsd <xs:complexType name="EntityDescriptionQueryService"> <xs:complexContent> <xs:extension base="coreservice:BaseQueryService"> <xs:sequence> <xs:element name="knownCodeSystem" type="core:CodeSystemVersionReference" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="knownCodeSystemVersion" type="core:CodeSystemVersionReference" minOccurs="0" maxOccurs="unbounded"/> -----Added----------><xs:element name="supportedVersionTag" type="core:VersionTagReference" minOccurs="1" maxOccurs="unbounded"/> </xs:sequence> <xs:attribute name="entities" type="core:EntityDirectoryURI" use="required"/> </xs:extension> </xs:complexContent> </xs:complexType>
Actions taken:
January 30, 2012: received issue
July 24, 2013: closed issue

Issue 17083: UpdateEntityDescription is missing elements and does not support "optparam" semantics (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: PIM: N/A PSM: Wrapper all mutable elements in the pattern show above
Revised Text: PIM: N/A PSM: Change Location: EntityDescriptionServices.xsd <xs:complexType name="UpdateEntityDescriptionRequest"> <xs:sequence> <xs:element minOccurs="0" name="updatedAlternateEntityIds"> <xs:complexType> <xs:sequence> <xs:element name="alternateEntityId" type="core:ScopedEntityName" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element minOccurs="0" name="updatedDefinitions"> <xs:complexType> <xs:sequence> <xs:element name="definition" type="core:Definition" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element minOccurs="0" name="updatedDesignations"> <xs:complexType> <xs:sequence> <xs:element name="designation" type="entity:Designation" minOccurs="1" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element minOccurs="0" name="updatedComments"> <xs:complexType> <xs:sequence> <xs:element name="note" type="core:Comment" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element minOccurs="0" name="updatedParents"> <xs:complexType> <xs:sequence> <xs:element name="parent" type="coreservice:EntityNameOrURI" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element minOccurs="0" name="updatedProperties"> <xs:complexType> <xs:sequence> <xs:element name="property" type="core:Property" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element minOccurs="0" name="updatedResourceTypes"> <xs:complexType> <xs:sequence> <xs:element name="resourceType" type="coreservice:EntityNameOrURI" minOccurs="1" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType>
Actions taken:
January 30, 2012: received issue
July 24, 2013: closed issue

Issue 17084: Designation and Note have inconsistent pattern in schema (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: PIM: N/A PSM: Apply the element/attribute convention of the type 'Note' to the type 'Designation'.
Revised Text: PIM: N/A PSM: Change Location: Entity.xsd <xs:complexType name="Designation"> <xs:annotation> <xs:documentation>A Designation is identical to a <a href="//http://www.w3.org/TR/skos-reference/#labels" >Lexical Label</a> as defined in <a href="//http://www.w3.org/2004/02/skos/intro" >SKOS</a>. It is a "string of (UNICODE) characters ... in a given natural language, such as English or Japanese." "These labels provide the strongest clues as to the meaning of a (SKOS concept)". The CTS2 specification generalizes the label use to include not only SKOS concepts but any class, predicate or individual - collectively referred to as Entity. Note that Designation is intended only for identifiers that are interpreted by human beings. Numeric codes and other machine readable identifiers should be recorded as ScopedEntityNames.</xs:documentation> </xs:annotation> <xs:complexContent> <xs:extension base="core:EntryDescription"> <xs:sequence> ---Removed---> <xs:element name="assertedInCodeSystemVersion" type="core:CodeSystemVersionReference" minOccurs="0"> <xs:annotation> <xs:documentation>the code system version in which this designation is asserted. If absent, it is the same as the EntityDescription containingCodeSystemVersion.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="correspondingStatement" type="core:RenderingURI" minOccurs="0"> <xs:annotation> <xs:documentation>a URI that, when de-referenced, provides the equivalent Statement that forms this designation. This is only present when the Statement profile is supported by the implementing service.</xs:documentation> </xs:annotation> </xs:element> ---End-Removed---> <xs:element name="usageContext" type="core:ContextReference" minOccurs="0" maxOccurs="unbounded"> <xs:annotation> <xs:documentation>the context(s) in which this designation is applicable</xs:documentation> </xs:annotation> </xs:element> <xs:element name="designationType" type="core:DesignationTypeReference" minOccurs="0"> <xs:annotation> <xs:documentation>the type of designation (e.g. abbreviation, eponym, short name, long name, etc.) of the given designation.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="caseSignificance" type="core:CaseSignificanceReference" minOccurs="0"> <xs:annotation> <xs:documentation>identifies the significance that case plays in the value of this particular designation.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="degreeOfFidelity" type="core:DesignationFidelityReference" minOccurs="0"> <xs:annotation> <xs:documentation>a measure of how closely this designation actually matches the intended meaning of the target entity. Typical values might represent "exact", "approximate", "broader", "narrower", etc.</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> <xs:attribute name="designationRole" type="DesignationRole" default="ALTERNATIVE"> <xs:annotation> <xs:documentation>an indicator that determines the particular role that this designation plays</xs:documentation> </xs:annotation> </xs:attribute> ---Added---> <xs:attribute name="assertedInCodeSystemVersion" type="core:CodeSystemVersionName" use="optional"> <xs:annotation> <xs:documentation>the code system version that contains the assertion(s) represented in the Note</xs:documentation> </xs:annotation> </xs:attribute> ---End-Added---> <xs:attribute name="externalIdentifier" type="core:String" use="optional"> <xs:annotation> <xs:documentation>an identifier that is assigned to this designation / entity pair by the authoring body. As an example this would carry the SCTID for SNOMED-CT concepts.</xs:documentation> </xs:annotation> </xs:attribute> ---Added---> <xs:attribute name="correspondingStatement" type="core:RenderingURI" use="optional"> <xs:annotation> <xs:documentation>a URI that, when de-referenced, provides the equivalent Statement that forms this designation. This is only present when the Statement profile is supported by the implementing service.</xs:documentation> </xs:annotation> </xs:attribute> ---End-Added---> </xs:extension> </xs:complexContent> </xs:complexType>
Actions taken:
January 30, 2012: received issue
July 24, 2013: closed issue

Issue 17085: SpecificEntityList incorrectly supertyped (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: PIM: N/A PSM: Remove the 'ValueSetDefinitionEntry' extension from the complex type 'SpecificEntityList'.
Revised Text: PIM: N/A PSM: Change Location: ValuseSetDefinition.xsd Original XML <xs:complexType name="SpecificEntityList"> <xs:annotation> <xs:documentation>a list of specific entity references that are to be included in the definition. When specified in this form, the service must include all entities in this list whether they are known to the service or not, and whether they are currently ACTIVE or not.</xs:documentation> </xs:annotation> <xs:complexContent> ----To-Be-Removed---><xs:extension base="ValueSetDefinitionEntry"> <xs:sequence> <xs:element name="referencedEntity" type="core:URIAndEntityName" minOccurs="1" maxOccurs="unbounded"> <xs:annotation> <xs:documentation>the namespace / name or URI of an entity to be included</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> Updated XML <xs:complexType name="SpecificEntityList"> <xs:annotation> <xs:documentation>a list of specific entity references that are to be included in the definition. When specified in this form, the service must include all entities in this list whether they are known to the service or not, and whether they are currently ACTIVE or not.</xs:documentation> </xs:annotation> <xs:sequence> <xs:element name="referencedEntity" type="core:URIAndEntityName" minOccurs="1" maxOccurs="unbounded"> <xs:annotation> <xs:documentation>the namespace / name or URI of an entity to be included</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType>
Actions taken:
January 30, 2012: received issue
July 24, 2013: closed issue

Issue 17086: NamedEntityDescription and AnonymousEntityDescription incorrectly defined in schema (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: 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 describingCodeSystem 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>
Revised Text: PIM: N/A PSM: Change Location: Core.xsd <xs:complexType name="AnonymousEntityReference"> <xs:annotation> <xs:documentation>A reference to an entity whose name and description is local to the containing code system and service. Information about anonymous entities cannot be shared between services or across code systems</xs:documentation> </xs:annotation> <xs:complexContent> <xs:restriction base="EntityReference"> ----Start Insert------> <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 describingCodeSystem 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> ----End Insert------> <xs:attribute name="about" type="LocalURI" use="required"> <xs:annotation> <xs:documentation>the local URI that identifies this entity within the context of the particular service</xs:documentation> </xs:annotation> </xs:attribute> </xs:restriction> </xs:complexContent> </xs:complexType> <xs:complexType name="NamedEntityReference"> <xs:annotation> <xs:documentation>A reference to an entity that is identified through a globally unique URI.</xs:documentation> </xs:annotation> <xs:complexContent> <xs:restriction base="EntityReference"> ----Start Insert------> <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 describingCodeSystem 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> ----End Insert------> <xs:attribute name="about" type="ExternalURI" use="required"> <xs:annotation> <xs:documentation>a URI that identifies a unique entity in a global context</xs:documentation> </xs:annotation> </xs:attribute> </xs:restriction> </xs:complexContent> </xs:complexType>
Actions taken:
January 30, 2012: received issue
July 24, 2013: closed issue

Issue 17087: ImplementationProfiles.ProfileElement not RESTful (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: PIM: N/A PSM: Create a new type 'FunctionalProfileEntry' and associated it to 'ProfileElement' as shown below.
Revised Text: PIM: N/A PSM: Change Location: CoreService.xsd <xs:complexType name="ProfileElement"> <xs:sequence> <xs:element name="structuralProfile" type="StructuralProfile" minOccurs="1" maxOccurs="1"> <xs:annotation> <xs:documentation>A resource that is implemented by a service instance</xs:documentation> </xs:annotation> </xs:element> <xs:element name="functionalProfile" type="FunctionalProfileEntry" minOccurs="1" maxOccurs="unbounded"> <xs:annotation> <xs:documentation>A functional profile that the service instance supports for the corresponding structure</xs:documentation> <xs:appinfo>PSM</xs:appinfo> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType> <xs:complexType name="FunctionalProfileEntry"> <xs:annotation> <xs:documentation>The combination of a FunctionalProfile and a link to the service description that describes the function/structure</xs:documentation> <xs:appinfo>PSM</xs:appinfo> </xs:annotation> <xs:simpleContent> <xs:extension base="FunctionalProfile"> <xs:attribute name="href" type="core:ServiceURI" use="optional"> <xs:annotation> <xs:documentation>A link to the service description for this particular function. The href must reference an instance of BaseService</xs:documentation> <xs:appinfo>PSM</xs:appinfo> </xs:annotation> </xs:attribute> </xs:extension> </xs:simpleContent> </xs:complexType>
Actions taken:
January 30, 2012: received issue
July 24, 2013: closed issue

Issue 17088: Documentation issue on ProfileElement (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: 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
Revised Text: PIM: N/A PSM: Change Location: CoreService.xsd <xs:complexType name="ProfileElement"> ---Start-Added---> <xs:annotation> <xs:documentation>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</xs:documentation> </xs:annotation> ---End-Added---> <xs:sequence> <xs:element name="structuralProfile" type="StructuralProfile" minOccurs="1" maxOccurs="1"> <xs:annotation> <xs:documentation>A resource that is implemented by a service instance</xs:documentation> </xs:annotation> </xs:element> <xs:element name="functionalProfile" type="FunctionalProfileEntry" minOccurs="1" maxOccurs="unbounded"> <xs:annotation> <xs:documentation>A functional profile that the service instance supports for the corresponding structure</xs:documentation> <xs:appinfo>PSM</xs:appinfo> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType>
Actions taken:
January 30, 2012: received issue
July 24, 2013: closed issue

Issue 17089: XML Schema for BaseService has wrong type for supported Profile (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

The type of SupportedProfile should be ProfileElement, not StructuralProfile         Logged:  https://github.com/cts2/cts2-specification/issues/28

Resolution: 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">
Revised Text: PIM: N/A PSM: Change Location: CoreService.xsd <xs:complexType name="BaseService"> <xs:annotation> <xs:documentation>BaseService contains the components that are common to any CTS2 service implementation. It includes information about the service itself, the namespaces and formats that are known to the service and the structural, functional and representation profiles that are supported by the service instance.</xs:documentation> </xs:annotation> <xs:sequence> <xs:element name="serviceName" type="core:String" minOccurs="1"> <xs:annotation> <xs:documentation>A short name that identifies the particular service and implementation.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="serviceDescription" type="core:OpaqueData" minOccurs="1"> <xs:annotation> <xs:documentation>A description of the service, its use, etc.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="serviceVersion" type="core:String" minOccurs="1"> <xs:annotation> <xs:documentation>The version or release identifier of the service.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="serviceProvider" type="core:SourceReference" minOccurs="1"> <xs:annotation> <xs:documentation>A reference to the individual or organization that provides the service.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="supportedFormat" type="core:FormatReference" minOccurs="1" maxOccurs="unbounded"> <xs:annotation> <xs:documentation>A list of the representation formats supported by the service. Example: text/html, text/xml, application/json</xs:documentation> </xs:annotation> </xs:element> <xs:element name="defaultFormat" type="core:FormatReference" minOccurs="1" maxOccurs="1"> <xs:annotation> <xs:documentation>The default format used by the service unless otherwise specified.</xs:documentation> </xs:annotation> </xs:element> ---Original---><xs:element name="supportedProfile" type="StructuralProfile" minOccurs="1" maxOccurs="unbounded"> ---Updated---><xs:element name="supportedProfile" type="ProfileElement" minOccurs="1" maxOccurs="unbounded"> <xs:element name="supportedProfile" type="ProfileElement" minOccurs="1" maxOccurs="unbounded"> <xs:annotation> <xs:documentation>The set of service profiles that are supported by this service implementation</xs:documentation> </xs:annotation> </xs:element> <xs:element name="implementationType" type="ImplementationProfile" minOccurs="1" maxOccurs="1"> <xs:annotation> <xs:documentation>The particular implementation type(s) supported by this profile</xs:documentation> </xs:annotation> </xs:element> <xs:element name="knownNamespace" type="core:NamespaceReference" minOccurs="1" maxOccurs="unbounded"> <xs:annotation> <xs:documentation>The set of namespaces recognized by this service. Because many namespace identifiers tend to be cryptic (i.e. HL7 OIDs, BioPortal URL's, etc.), knownNamespace includes the namespace name, an optional URI \emph{and} a place to provide textual detail describing what the namespace references. Note that namespace names must be unique across an entire CTS2 implementation - the same namespace name cannot represent one namespace in code system A and a second in code system B. Note also that namespace names are \emph{local} to a service instance. Information that is communicated between service instances, recorded in data tables or client software \emph{must} use full URIs.</xs:documentation> </xs:annotation> </xs:element> </xs:element> </xs:sequence> </xs:complexType>
Actions taken:
January 30, 2012: received issue
July 24, 2013: closed issue

Issue 17107: Remove CONCEPT_DOMAIN_BINDING from ReferenceType (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: PIM: Updated Diagram (Figure 2.4: Reference Types. Core, Page 10.) PSM: N/A
Revised Text: PIM: Updated Diagram (Figure 2.4: Reference Types. Core, Page 10.) PSM: N/A
Actions taken:
February 9, 2012: received issue
July 24, 2013: closed issue

Issue 17108: EntityReferences - URIAndEntityNameList (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: PIM: Change the signature of restrict to the following: (Diagram below) PSM: N/A
Revised Text: On page 19 of Core, remove 'Class URIAndEntityNameList.' Updated Diagram (Figure 2.7: Entity Reference. Core, Page 16.) PSM: N/A
Actions taken:
February 9, 2012: received issue
July 24, 2013: closed issue

Issue 17109: Changeable changeDescription cardinality constraint (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: PIM: Update PIM text PSM: N/A
Revised Text: PIM: Change Location: Core Information Model, Page 32. Description: Add the following text under 'Class Changeable': Invariants: 1. changeDescription must be present if the profile supports HISTORY or MAINTENANCE
Actions taken:
February 9, 2012: received issue
July 24, 2013: closed issue

Issue 17110: BaseQueryService filter property needs to be individualized (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: 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>
Revised Text: PIM: Updated Figure 3.5: Common Query Service Components. Page 51, Core PSM: Change Location: ValueSetDefinition.xsd <xs:complexType name="Query"> <xs:annotation> <xs:documentation> Message structure for packaging and sending complex queries. A Query may contain a Filter, a Set Operation, or Both. </xs:documentation> <xs:appinfo>PSM</xs:appinfo> </xs:annotation> <xs:sequence> ---Start-Removed---> <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> ---End-Removed---> ----Start-Added----> <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> ----End-Added----> <xs:element name="setOperation" type="core:SetOperator" minOccurs="0"> <xs:annotation> <xs:documentation> The Set Operation to be applied to the two DirectoryURIs. </xs:documentation> </xs:annotation> </xs:element> <xs:choice minOccurs="0"> <xs:annotation> <xs:documentation> Either a 'DirectoryURI' or a 'Query' may participate in a Set Operation. </xs:documentation> </xs:annotation> <xs:element name="query1" type="Query" minOccurs="0"> <xs:annotation> <xs:documentation> The left-hand side of the Set Operation. </xs:documentation> </xs:annotation> </xs:element> <xs:element name="directoryUri1" type="core:DirectoryURI" minOccurs="0"> <xs:annotation> <xs:documentation> The left-hand side of the Set Operation. </xs:documentation> </xs:annotation> </xs:element> </xs:choice> <xs:choice minOccurs="0"> <xs:annotation> <xs:documentation> Either a 'DirectoryURI' or a 'Query' may participate in a Set Operation. </xs:documentation> </xs:annotation> <xs:element name="query2" type="Query" minOccurs="0"> <xs:annotation> <xs:documentation> The right-hand side of the Set Operation. </xs:documentation> </xs:annotation> </xs:element> <xs:element name="directoryUri2" type="core:DirectoryURI" minOccurs="0"> <xs:annotation> <xs:documentation> The right-hand side of the Set Operation. </xs:documentation> </xs:annotation> </xs:element> </xs:choice> </xs:sequence> </xs:complexType>
Actions taken:
February 9, 2012: received issue
July 24, 2013: closed issue

Issue 17111: ConceptDomainbinding needs an identifier (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

Need to add an id attribute to ConceptDomainBinding:         bindingURI: DocumentURI {readOnly}         Need to add an assertion that bindingURI = entryID         Logged:   https://github.com/cts2/cts2-specification/issues/33

Resolution: 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>
Revised Text: PIM: Updated Diagram (Figure 3.1: Concept Domain Binding Model. Concept Domain, Page 17.) PSM: Change Location: ConceptDomainBinding.xsd <xs:complexType name="ConceptDomainBinding"> <xs:annotation> <xs:documentation>The binding of a ConceptDomain and a ValueSet that supplies the set of permissible value meanings in a given context. ConceptDomainBinding can also bind specific value set definitions and/or specific code system versions where desired. </xs:documentation> </xs:annotation> <xs:complexContent> <xs:extension base="core:Changeable"> <xs:sequence> -------Added--------> <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> -------End-Added--------> <xs:element name="bindingFor" type="core:ConceptDomainReference" minOccurs="1" maxOccurs="1"> <xs:annotation> <xs:documentation>the ConceptDomain being bound to a value set.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="boundValueSet" type="core:ValueSetReference" minOccurs="1" maxOccurs="1"> <xs:annotation> <xs:documentation>the bound value set</xs:documentation> </xs:annotation> </xs:element> <xs:element name="applicableContext" type="core:ContextReference" minOccurs="0"> <xs:annotation> <xs:documentation>a realm or context in which the particular binding applies. If not present, the binding applies in any context not stated in another binding</xs:documentation> </xs:annotation> </xs:element> <xs:element name="boundValueSetDefinition" type="core:ValueSetDefinitionReference" minOccurs="0"> <xs:annotation> <xs:documentation>the specific definition of the value set to be bound. If not specified, the definition that is used to determine the permissible values is specified when the concept domain is applied in the context.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="useCodeSystemVersion" type="core:CodeSystemVersionReference" minOccurs="0" maxOccurs="1"> <xs:annotation> <xs:documentation>the specific version(s) of the code systems to be used in the resolution of the value set definition. Note that it is also possible for value set definitions themselves to state which version of a code system is to be used. When this is the case, the code system version(s) specified in the ConceptDomainBinding do not override those stated in the value set definition - the value set definition version information takes precedence.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="bindingQualifier" type="core:BindingQualifierReference" minOccurs="0"> <xs:annotation> <xs:documentation>additional information that qualifies the intent or purpose of the binding. In the HL7 case, this is intended to indicate "whether the binding is 'overall', 'minimum' or 'maximum'." The actual interpretation of the qualifier is outside of the scope of the CTS2 specification but, if present, bindingQualifier contributes to the identity of the specific binding.</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType>
Actions taken:
February 9, 2012: received issue
July 24, 2013: closed issue

Issue 17112: Statement needs an identifier (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

Need to add an identifier to the statement model:         statementURI : ExternalURI {readOnly}         and add an invariant that entryID = statementURI         This is the identity.         subject, predicate, assertedBy, assertedIn all need to be set to {readOnly} to indicate that they are part of the statement identity.         Logged:  https://github.com/cts2/cts2-specification/issues/34

Resolution: 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>
Revised Text: PIM: Updated Diagram (Figure 1.1: Statement Model. Statement, Page 2.) PSM: Change Location: Statement.xsd <xs:complexType name="Statement"> <xs:annotation> <xs:documentation>An assertion about a CTS2 model element. </xs:documentation> </xs:annotation> <xs:complexContent> <xs:extension base="core:Changeable"> <xs:sequence> ---------Added--------> <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> ---------End-Added--------> <xs:element name="subject" type="StatementSubject" minOccurs="1"> <xs:annotation> <xs:documentation>the subject of the statement - either a resource or a reference to a terminological entity. subject may reference a specific Association, CodeSystem, CodeSystemVersion, Map, MapEntry, MapVersion, EntityDescription, ValueSet, ValueSetDefinition, ConceptDomain, ConceptDomainBinding, </xs:documentation> </xs:annotation> </xs:element> <xs:element name="predicate" type="core:URIAndEntityName" minOccurs="1"> <xs:annotation> <xs:documentation>the predicate of the statement. Note that this is type URIAndEntityName as, while it serves as a predicate in the statement itself it is not necessary that it be formally recognized as a predicate by the CTS2 service - it may have been translated or transformed by the load process.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="target" type="core:StatementTarget" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="associatedAttribute" type="core:ModelAttributeReference" minOccurs="0"> <xs:annotation> <xs:documentation>the identifier and name of the CTS2 attribute or element that renders this statement, if any</xs:documentation> </xs:annotation> </xs:element> <xs:element name="source" type="core:SourceAndRoleReference" minOccurs="0" maxOccurs="unbounded"> <xs:annotation> <xs:documentation>the source(s) of the statement and the role(s) they played</xs:documentation> </xs:annotation> </xs:element> <xs:element name="assertedBy" type="core:CodeSystemVersionReference" minOccurs="1"> <xs:annotation> <xs:documentation>the code system version that is asserting this particular statement. In the case of ontologies that import other ontologies, this is the outermost importing ontology.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="assertedIn" type="core:CodeSystemVersionReference" minOccurs="0"> <xs:annotation> <xs:documentation>the code system version (ontology) that actually makes this statement. In the case of ontologies, this is the innermost imported ontology.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="qualifier" type="StatementQualifier" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType>
Actions taken:
February 9, 2012: received issue
July 24, 2013: closed issue

Issue 17113: Typo on page 3 of Statement Information model (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: PIM: Update PIM text PSM: N/A
Revised Text: PIM: Change Location: Statement Information Model, Page 3. Description: Change text: �subject - ahe subject� to: �subject - the subject�
Actions taken:
February 9, 2012: received issue
July 24, 2013: closed issue

Issue 17114: Typo on page 11 of statement information model (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: PIM: Update PIM text PSM: N/A
Revised Text: PIM: Change Location: Statement Information Model, Page 11. The blank exception in the 'StatementDirectoryURI' type should be removed. PIM: N/A
Actions taken:
February 9, 2012: received issue
July 24, 2013: closed issue

Issue 17115: Association Information Model derivation and derivationReasoningAlgorithm (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

Derivation and derivationReasoningAlgorithm shouldn't be marked as {readOnly}, 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

Resolution: 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>
Revised Text: PIM: Updated Diagram (Figure 4.1: Association Model. Association, Page 43.) Updated Diagram (Figure 5.4: Association Maintenance. Association, Page 67.) PSM: Change Location: AssociationServices.xsd <xs:complexType name="UpdateAssociationRequest"> <xs:sequence> <xs:element minOccurs="0" name="updatedAssociationQualifiers"> <xs:complexType> <xs:sequence> <xs:element name="associationQualifier" type="core:Property" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element minOccurs="0" name="updatedTargets"> <xs:complexType> <xs:sequence> <xs:element name="target" type="core:StatementTarget" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:element> ---Start-Additions---> <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> <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> ---End-Additions---> </xs:sequence> </xs:complexType>
Actions taken:
February 9, 2012: received issue
July 24, 2013: closed issue

Issue 17116: AdvancedAssociationQuerySerivce not in WADL (REST PSM) (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: PIM: N/A PSM: The AdvancedAssociationQuerySerivce resources were added to the cts2.wadl. A resource 'graph' was added with all parameters outlined below.
Revised Text: PIM: N/A PSM: Change Location: cts2.wadl <resource path="graph"> <param name="active" type="xsd:string" style="query"> <doc title="ReadContext:active">determines whether the query only applies to only active or all entries. </doc> </param> <param name="changesetcontext" type="xsd:string" style="query"> <doc title="ReadContext:changeSetContext">the URI of an open change set whose contents should be included in the results of the access request. changeSetContext is only applicable in services that support the Authoring profile. If omitted, no change set context is supplied in the service call.</doc> </param> <param name="referencelanguage" type="xsd:string" style="query"> <doc title="ReadContext:referenceLanguage">the spoken or written language that should be used for the results of the inquiry, where appropriate. Should default to the default reference language of the service if omitted.</doc> </param> <param name="referencetime" type="xsd:string" style="query"> <doc title="ReadContext:referenceTime">the contextual date and time of the query. referenceTime is may only be present in services that support the Temporal profile. If omitted, referenceTime defaults to the current system date and time.</doc> </param> <param name="format" type="xsd:string" style="query"> <doc title="QueryControl:format">the local identifier or URI of the return format for query results. This parameter defaults to the defaultFormat in the BaseService interface if not supplied.</doc> </param> <param name="page" type="xsd:string" style="query"/> <param name="maxtoreturn" type="xsd:string" style="query"> <doc title="QueryControl:maxToReturn">the maximum number of entries that may be present in a return Directory. Note that a service may choose to return less than maxToReturn entries - this is simply an upper limit. If maxToReturn is not supplied, the service may use whatever return block size it determines to be most appropriate.</doc> </param> <param name="timelimit" type="xsd:string" style="query"> <doc title="QueryControl:timeLimit">the maximum amount of time that may be taken to process a query before a time out exception occurs. If not present, the service determines the maximum query time out.</doc> </param> <param name="filtercomponent" type="xsd:string" style="query"> <doc title="FilterComponent:filterComponent">the name or URI of the property or model element to be filtered. Properties are referenced by their predicate and model elements all have URI's that are established by this specification.</doc> </param> <param name="matchalgorithm" type="xsd:string" style="query"> <doc title="FilterComponent:matchAlgorithm">the algorithm to be used for testing the referenced component. Examples might include "starts with", "regular expression match", "exists", "inRange", etc. NOTE: The CTS2 specification needs to establish a core set of match algorithms that all compliant implementations must support.</doc> </param> <param name="matchvalue" type="xsd:string" style="query"> <doc title="FilterComponent:matchValue">the value to be used in comparison. The structure and format of matchValue depends on the specific matchAlgorithm. As an example, a "startsWith" algorithm would be plain text, a "regularExpression" algorithm would have a regular expression while an "exists" algorithm would have nothing in the matchValue attribute.</doc> </param> <param name="focus" type="xsd:string" style="query"> <doc title="EntityNameOrURI"/> </param> <param name="graphfocus" type="xsd:string" style="query"> <doc title="GraphFocus"/> </param> <param name="focusentity" type="xsd:string" style="query"> <doc title="EntityNameOrURI"/> </param> <param name="resolvedirection" type="xsd:string" style="query"> <doc title="GraphDirection"/> </param> <param name="resolvedepth" type="xsd:integer" style="query"> <doc title="NaturalNumber"/> </param>   <param name="codesystemversion" type="xsd:string" style="query"> <doc title="Restriction:restrictToCodeSystemVersion">Return a DirectoryURI that represents the subset of the associations in directory that were assertedBy the named code system version.</doc> <doc title="NameOrURI">Carries either a local identifier (name) or a URI (uri) that references a resource in the service. NameOrURI is only used as an input parameter and its type is always defined by the usage context. Note that service calls that use the name option may not be portable across implementations, as there is no guarantee that any two CTS2 service implementations will use the same local identifiers for the same resources.</doc> </param>   <param name="predicate" type="xsd:string" style="query"> <doc title="Restriction:restrictToPredicate">Return a DirectoryURI that represents the subset of the associations in directory whose predicate is predicate.</doc> <doc title="EntityNameOrURI">A reference to a class, property or individual that is described in some Code System. EntityNameOrURI may either reference an entity that is known locally to the service or an entity that is described elsewhere. If the entity is known to the service, it is possible to use the entityName variant, but note that neither scopingNamespace nor the entityName are guaranteed to be the same in different CTS2 implementations. The entityName variant is intended for use in human/browser interactions and should not be hard-coded into data tables or applications.</doc> </param>   <param name="sourceentity" type="xsd:string" style="query"> <doc title="Restriction:restrictToSourceEntity">Return a DirectoryURI that represents the subset of the associations in directory whose subject is sourceEntity.</doc> <doc title="EntityNameOrURI">A reference to a class, property or individual that is described in some Code System. EntityNameOrURI may either reference an entity that is known locally to the service or an entity that is described elsewhere. If the entity is known to the service, it is possible to use the entityName variant, but note that neither scopingNamespace nor the entityName are guaranteed to be the same in different CTS2 implementations. The entityName variant is intended for use in human/browser interactions and should not be hard-coded into data tables or applications.</doc> </param>   <param name="sourceortargetentity" type="xsd:string" style="query"> <doc title="Restriction:restrictToSourceOrTargetEntity">Return a DirectoryURI that represents the subset of the associations having either a source or a target matching the supplied entity. This is equivalent to the union of restrictToSourceEntity and restrictToTargetEntity with source and target being the same</doc> <doc title="EntityNameOrURI">A reference to a class, property or individual that is described in some Code System. EntityNameOrURI may either reference an entity that is known locally to the service or an entity that is described elsewhere. If the entity is known to the service, it is possible to use the entityName variant, but note that neither scopingNamespace nor the entityName are guaranteed to be the same in different CTS2 implementations. The entityName variant is intended for use in human/browser interactions and should not be hard-coded into data tables or applications.</doc> </param>   <param name="targetentity" type="xsd:string" style="query"> <doc title="Restriction:restrictToTargetEntity">Return a DirectoryURI that represents the subset of the associations in directory having a target directly matching target or containing one or more bnodes who reference target</doc> <doc title="EntityNameOrURI">A reference to a class, property or individual that is described in some Code System. EntityNameOrURI may either reference an entity that is known locally to the service or an entity that is described elsewhere. If the entity is known to the service, it is possible to use the entityName variant, but note that neither scopingNamespace nor the entityName are guaranteed to be the same in different CTS2 implementations. The entityName variant is intended for use in human/browser interactions and should not be hard-coded into data tables or applications.</doc> </param>   <param name="targetexpression" type="xsd:string" style="query"> <doc title="Restriction:restrictToTargetExpression">Return a DirectoryURI that represents the subset of the associations in directory whose target matches the supplied expression.</doc> <doc title="AssociationRendering"/> </param>   <param name="targetliteral" type="xsd:string" style="query"> <doc title="Restriction:restrictToTargetLiteral">Return a DirectoryURI that represents the subset of the associations in directory having a string literal that matches target.</doc> <doc title="String">a non-empty sequence of characters. As terminological resources are often multilingual, it is expected that most CTS2 Platform Specific Models (PSMs) will require that the String implementation support international character sets.</doc> </param>   <method name="GET"> <doc title="AdvancedAssociationQueryService:resolveAsGraph"/> <request> <param name="list" required="false" type="xsd:string" style="query" default="false"/> </request> <response> <representation element="association:AssociationGraph"/> </response> </method> <method name="POST"> <doc title="AdvancedAssociationQueryService:resolveAsGraph"/> <request> <param name="list" required="false" type="xsd:string" style="query" default="false"/> <representation element="coreService:Query"> <doc xmlns="http://www.w3.org/2001/XMLSchema" title="Representation Type"/> </representation> </request> <response> <representation element="association:AssociationGraph"> </representation> </response> </method> </resource>
Actions taken:
February 9, 2012: received issue
July 24, 2013: closed issue

Issue 17117: ResolvedValueSetDirectory misnamed and mistyped (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: PIM: Updated Diagram (Figure 3.4: Resolved ValueSet. ValueSetDefinition, Page 27.) PSM: Add the type 'IteratableResolvedValueSet' to allow for iterable access of a 'ResolvedValueSet'.
Revised Text: PIM: Updated Diagram (Figure 3.4: Resolved ValueSet. ValueSetDefinition, Page 27.) PSM: Change Location: ValueSetDefinition.xsd <xs:element name="IteratableResolvedValueSet"> <xs:annotation> <xs:documentation>A ResolvedValueSet whose contents are available as a set of directory entries that allows iteration.</xs:documentation> </xs:annotation> <xs:complexType> <xs:complexContent> <xs:extension base="core:Directory"> <xs:sequence> <xs:element name="resolutionInfo" type="ResolvedValueSetHeader" minOccurs="1" maxOccurs="1"> <xs:annotation> <xs:documentation>the set of parameters that were used in the resolution of this set. resolutionInfo provides all the information necessary to recreate the actual resolution when presented to a CTS2 service instance that contains all of the necessary definitions and code system versions.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="entry" type="core:EntitySynopsis" minOccurs="0" maxOccurs="unbounded"> <xs:annotation> <xs:documentation>a synopsis of the EntityDescription that has been determined to be a member of the value set named in resolutionInfo according to the stated criteria or "bindings"</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> </xs:element>
Actions taken:
February 9, 2012: received issue
July 24, 2013: closed issue

Issue 17118: ResolvedValueSetReadService and QueryService omitted from spec (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: 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.
Revised Text: PIM: Updated Diagram (Figure 3.4: Resolved ValueSet. Value Set Definition, Page 27.) Updated Diagram (Figure 5.1: Value Set Definition Resolution Service. Value Set Definition, Page 46.) and Added new ResolvedValueSetQuery Diagram as shown below. Updated Diagram (Directory Types) New Diagram (ResolvedValueSetQueryService) PSM: Change Location: ValueSetDefinition.xsd <xs:element name="IteratableResolvedValueSet" type="IteratableResolvedValueSet"/> <xs:complexType name="IteratableResolvedValueSet"> <xs:annotation> <xs:documentation>A ResolvedValueSet whose contents are available as a set of directory entries that allows iteration.</xs:documentation> </xs:annotation> <xs:complexContent> <xs:extension base="core:Directory"> <xs:sequence> <xs:element name="resolutionInfo" type="ResolvedValueSetHeader" minOccurs="1" maxOccurs="1"> <xs:annotation> <xs:documentation>the set of parameters that were used in the resolution of this set. resolutionInfo provides all the information necessary to recreate the actual resolution when presented to a CTS2 service instance that contains all of the necessary definitions and code system versions.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="entry" type="core:EntitySynopsis" minOccurs="0" maxOccurs="unbounded"> <xs:annotation> <xs:documentation>a synopsis of the EntityDescription that has been determined to be a member of the value set named in resolutionInfo according to the stated criteria or "bindings"</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType>
Actions taken:
February 9, 2012: received issue
July 24, 2013: closed issue

Issue 17119: Refactor inline XSD types from WSDLs (SOAP PSM) (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: 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.
Revised Text: PIM: N/A PSM: Change Location: *.wsdl (every WSDL file) Original XML <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"> <wsdl:types> <xs:schema xmlns:xs="�"> <xs:import namespace="..." schemaLocation="http://informatics.m..."/> <xs:import namespace="http://schema.om..." schemaLocation="http://informatics.may..."/> <xs:import namespace="http://schema.omg.org..." schemaLocation="http://informatics.mayo..."/> <xs:import namespace="http://schema.omg.or..." schemaLocation="http://informatic..." /> ... </xs:schema> </wsdl:types> ... </wsdl:definitions> Updated XML Everything in the wsdl:types tag was refactored into a {WSDLName}Types.xsd file. Sample Types.xsd file: <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" ... > {insert here everything from the <wsdl:types> tag in the WSDL} </xs:schema>
Actions taken:
February 9, 2012: received issue
July 24, 2013: closed issue

Issue 17173: CodeSystemCatalogMaintenanceServices WSDL corrections (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Issue 17174: CodeSystemCatalogHistoryServices WSDL corrections (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: PIM: N/A PSM: � In 'count' method added 'timeout' param. � Changed 'getLatestChangeFor' method name to 'getLastChangeFor' to match the PIM
Revised Text: PIM: N/A PSM: Change Location: CodeSystemCatalogHistoryServiceTypes.xsd <xs:complexType name="count"> <xs:sequence> <xs:element minOccurs="1" name="directory" type="core:CodeSystemVersionCatalogEntryDirectoryURI"/> <xs:element minOccurs="0" name="context" type="coreService:ReadContext"/> ---Added---><xs:element minOccurs="0" name="timeout" type="core:NaturalNumber"/> </xs:sequence> </xs:complexType> Change Location: CodeSystemCatalogHistoryService.wsdl ---Original---><wsdl:operation name="getLatestChangeFor"/> ---Updated---><wsdl:operation name="getLastChangeFor"> <wsdl:input name="getLastChangeFor" message="tns:getLastChangeFor"/> <wsdl:output name="getLastChangeForResponse" message="tns:getLastChangeForResponse"/> </wsdl:operation>
Actions taken:
March 24, 2014: closed issue

Issue 17175: CodeSystemCatalogQueryServices WSDL corrections (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

In the 'count' method, added a 'timeout' parameter.         Logged:  https://github.com/cts2/cts2-specification/issues/44

Resolution: PIM: N/A PSM: � In the 'count' method, added a 'timeout' parameter.
Revised Text: PIM: N/A PSM: Change Location: CodeSystemCatalogQueryServiceTypes.xsd <xs:complexType name="count"> <xs:sequence> <xs:element minOccurs="1" name="directory" type="core:CodeSystemCatalogEntryDirectoryURI"/> <xs:element minOccurs="0" name="context" type="coreService:ReadContext"/> ---Added---><xs:element minOccurs="0" name="timeout" type="core:NaturalNumber"/> </xs:sequence> </xs:complexType>
Actions taken:
February 24, 2012: received issue
February 24, 2012: received issue
July 24, 2013: closed issue
July 24, 2013: closed issue

Discussion:

Issue 17176: CodeSystemVersionCatalogReadServices WSDL corrections (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

Renamed method 'getCodeSystemVersionByExternalId' to 'getCodeSystemByVersionId'.             Renamed method 'existsExternalId' to 'existsVersionId'.         Logged:   https://github.com/cts2/cts2-specification/issues/45

Resolution: PIM: N/A PSM: � Renamed method 'getCodeSystemVersionByExternalId' to 'getCodeSystemByVersionId'. � Renamed method 'existsExternalId' to 'existsVersionId'.
Revised Text: PIM: N/A PSM: Change Location: CodeSystemVersionCatalogReadService.wsdl ---Original---><wsdl:operation name="getCodeSystemByExternalId"/> ---Updated---><wsdl:operation name="getCodeSystemByVersionId"> <wsdl:input name="getCodeSystemByVersionId" message="tns:getCodeSystemByVersionId"/> <wsdl:output name="getCodeSystemByVersionIdResponse" message="tns:getCodeSystemByVersionIdResponse"/> </wsdl:operation> ---Original---><wsdl:operation name="existsExternalId"/> ---Updated---><wsdl:operation name="existsVersionId"> <wsdl:input name="existsVersionId" message="tns:existsVersionId"/> <wsdl:output name="existsVersionIdResponse" message="tns:existsVersionIdResponse"/> </wsdl:operation>
Actions taken:
February 24, 2012: received issue
July 24, 2013: closed issue

Discussion:

Reason For Change    The methods 'getCodeSystemVersionByExternalId' and 'existsExternalId' will better align with the PIM if the naming convention 'externalId' is changed to 'versionId'. This will be clearer to implementers as to the intent of the functions, as well as bind them to the PIM.

Issue 17177: CodeSystemVersionCatalogQueryServices WSDL corrections (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: PIM: N/A PSM: � In 'count' method added 'timeout' param. � In method 'resolveAsList', rename param 'control' to 'queryControl' to match spec.
Revised Text: PIM: N/A PSM: Change Location: CodeSystemVersionCatalogQueryServiceTypes.xsd <xs:complexType name="count"> <xs:sequence> <xs:element minOccurs="1" name="directory" type="core:ConceptDomainCatalogEntryDirectoryURI"/> <xs:element minOccurs="0" name="context" type="coreService:ReadContext"/> ---Added---><xs:element minOccurs="0" name="timeout" type="core:NaturalNumber"/> </xs:sequence> </xs:complexType> <xs:complexType name="resolveAsList"> <xs:sequence> <xs:element minOccurs="1" name="directory" type="core:CodeSystemVersionCatalogEntryDirectoryURI" /> ---Original---><xs:element minOccurs="0" name="control" type="coreService:QueryControl"/> ---Updated---> <xs:element minOccurs="0" name="queryControl" type="coreService:QueryControl"/> <xs:element minOccurs="0" name="context" type="coreService:ReadContext"/> </xs:sequence> </xs:complexType>
Actions taken:
February 24, 2012: received issue
July 24, 2013: closed issue

Issue 17178: CodeSystemVersionCatalogMaintenanceServices WSDL corrections (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: 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'
Revised Text: PIM: N/A PSM: Change Location: CodeSystemCatalogVersionMaintenanceServiceTypes.xsd <xs:complexType name="putChangeSet"> <xs:sequence> <xs:element minOccurs="1" name="changeSet" type="core:ChangeSetURI"/> ---Added---><xs:element minOccurs="0" name="errorResponse" type="coreService:ErrorResponse"/> </xs:sequence> </xs:complexType> <xs:complexType name="validateChangeSet"> <xs:sequence> ---Added---><xs:element minOccurs="1" name="validationLevel" type="coreService:ValidationLevel"/> <xs:element minOccurs="1" name="changeSet" type="updates:ChangeSet"/> </xs:sequence> </xs:complexType> <xs:complexType name="deleteChangeable"> <xs:sequence> <xs:element minOccurs="1" name="changeSet" type="core:ChangeSetURI"/> ---Original---><xs:element minOccurs="1" name="target" type="core:Changeable"/> ---Updated---><xs:element minOccurs="1" name="changeableResource" type="core:Changeable"/> </xs:sequence> </xs:complexType> <xs:complexType name="readChangeSet"> <xs:sequence> <xs:element minOccurs="1" name="changeSet" type="core:ChangeSetURI"/> ---Added---><xs:element minOccurs="0" name="queryControl" type="coreService:QueryControl"/> </xs:sequence> </xs:complexType> <xs:complexType name="updateChangeableMetadata"> <xs:sequence> <xs:element minOccurs="1" name="changeSet" type="core:ChangeSetURI"/> ---Added---><xs:element minOccurs="1" name="entryID" type="core:PersistentURI"/> <xs:element minOccurs="0" name="status" type="coreService:NameOrURI"/> <xs:element minOccurs="0" name="entryState" type="core:EntryState"/> </xs:sequence> </xs:complexType> <xs:complexType name="updateChangeSetMetadata"> <xs:sequence> <xs:element minOccurs="1" name="changeSet" type="core:ChangeSetURI"/> <xs:element minOccurs="0" name="creator" type="core:SourceReference"/> <xs:element minOccurs="0" name="changeInstructions" type="core:OpaqueData"/> ---Added---><xs:element minOccurs="0" name="officialEffectiveDate" type="core:DateAndTime"/> </xs:sequence> </xs:complexType>
Actions taken:
February 24, 2012: received issue
July 24, 2013: closed issue

Issue 17179: CodeSystemVersionCatalogHistoryServices WSDL corrections (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: 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'
Revised Text: PIM: N/A PSM: Change Location: CodeSystemVersionCatalogHistoryService.wsdl ---Original---><wsdl:operation name="getLatestChangeFor"> ---Updated---><wsdl:operation name="getLastChangeFor"> <wsdl:input name="getLastChangeFor" message="tns:getLastChangeFor"/> <wsdl:output name="getLastChangeForResponse" message="tns:getLastChangeForResponse"/> </wsdl:operation> Change Location: CodeSystemVersionCatalogHistoryServiceTypes.xsd <xs:complexType name="count"> <xs:sequence> <xs:element minOccurs="1" name="directory" type="core:CodeSystemVersionCatalogEntryDirectoryURI"/> <xs:element minOccurs="0" name="context" type="coreService:ReadContext"/> ---Added---><xs:element minOccurs="0" name="timeout" type="core:NaturalNumber"/> </xs:sequence> </xs:complexType> <xs:complexType name="getEarliestChangeFor"> <xs:sequence> ---Original---><xs:element minOccurs="1" name="codeSystem" type="coreService:NameOrURI"/> ---Updated---><xs:element minOccurs="1" name="codeSystemVersion" type="coreService:NameOrURI" /> </xs:sequence> </xs:complexType> <xs:complexType name="getChangeHistoryFor"> <xs:sequence> ---Original---><xs:element minOccurs="1" name="codeSystem" type="coreService:NameOrURI"/> ---Updated---><xs:element minOccurs="1" name="codeSystemVersion" type="coreService:NameOrURI"/> <xs:element minOccurs="0" name="fromDate" type="core:DateAndTime"/> <xs:element minOccurs="0" name="toDate" type="core:DateAndTime"/> </xs:sequence> </xs:complexType>
Actions taken:
February 24, 2012: received issue
July 24, 2013: closed issue

Discussion:

Issue 17180: EntityDescriptionReadServices WSDL corrections (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

Rename method 'getKnownCodeSystems' to 'getKnownCodeSystem'.             Rename method 'getKnownCodeSystemVersions' to 'getKnownCodeSystemVersion'.             Rename method 'getSupportedVersionTags' to 'getSupportedVersionTag'.         Logged:  https://github.com/cts2/cts2-specification/issues/49

Resolution: PIM: N/A PSM: � Rename method 'getKnownCodeSystems' to 'getKnownCodeSystem'. � Rename method 'getKnownCodeSystemVersions' to 'getKnownCodeSystemVersion'. � Rename method 'getSupportedVersionTags' to 'getSupportedVersionTag'
Revised Text: PIM: N/A PSM: Change Location: EntityDescriptionReadService.wsdl ---Original---><wsdl:operation name="getKnownCodeSystems"/> ---Updated---><wsdl:operation name="getKnownCodeSystem"> <wsdl:input name="getKnownCodeSystem" message="tns:getKnownCodeSystem"/> <wsdl:output name="getKnownCodeSystemResponse" message="tns:getKnownCodeSystemResponse"/> </wsdl:operation> ---Original---><wsdl:operation name="getKnownCodeSystemVersions"/> ---Updated---><wsdl:operation name="getKnownCodeSystemVersion"> <wsdl:input name="getKnownCodeSystemVersion" message="tns:getKnownCodeSystemVersion"/> <wsdl:output name="getKnownCodeSystemVersionResponse" message="tns:getKnownCodeSystemVersionResponse"/> </wsdl:operation> ---Original---><wsdl:operation name="getSupportedVersionTags"/> ---Updated---><wsdl:operation name="getSupportedVersionTag"> <wsdl:input name="getSupportedVersionTag" message="tns:getSupportedVersionTag"/> <wsdl:output name="getSupportedVersionTagResponse" message="tns:getSupportedVersionTagResponse"/> </wsdl:operation>
Actions taken:
February 24, 2012: received issue
July 24, 2013: closed issue

Discussion:

Issue 17182: AdvancedAssociationQueryServices WSDL corrections (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: 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
Revised Text: PIM: N/A PSM: Change Location: AdvancedAssociationQueryService.wsdl ---Original---><wsdl:operation name="getKnownCodeSystems"/> ---Updated---><wsdl:operation name="getKnownCodeSystem"> <wsdl:input name="getKnownCodeSystem" message="tns:getKnownCodeSystem"/> <wsdl:output name="getKnownCodeSystemResponse" message="tns:getKnownCodeSystemResponse"/> </wsdl:operation> ---Original---><wsdl:operation name="getKnownCodeSystemVersions"/> ---Updated---><wsdl:operation name="getKnownCodeSystemVersion"> <wsdl:input name="getKnownCodeSystemVersion" message="tns:getKnownCodeSystemVersion"/> <wsdl:output name="getKnownCodeSystemVersionResponse" message="tns:getKnownCodeSystemVersionResponse"/> </wsdl:operation> Change Location: AdvancedAssociationQueryServiceTypes.xsd <xs:complexType name="count"> <xs:sequence> <xs:element minOccurs="1" name="directory" type="core:EntityDirectoryURI"/> <xs:element minOccurs="0" name="context" type="coreService:ReadContext"/> ---Added---><xs:element minOccurs="0" name="timeout" type="core:NaturalNumber"/> </xs:sequence> </xs:complexType> <xs:complexType name="restrict"> <xs:sequence> ---Original---><xs:element minOccurs="0" name="directory" type="core:AssociationDirectoryURI"/> ---Updated---><xs:element minOccurs="1" name="directory" type="core:DirectoryURI"/> <xs:element minOccurs="0" name="filter" type="core:Filter" /> </xs:sequence> </xs:complexType> <xs:complexType name="restrictToTargetExpression"> <xs:sequence> <xs:element minOccurs="0" name="directory" type="core:AssociationDirectoryURI"/> ---Original---><xs:element minOccurs="0" name="target" type="association:AssociationRendering"/> ---Updated---><xs:element minOccurs="1" name="target" type="core:EntityExpression"/> </xs:sequence> </xs:complexType> <xs:complexType name="restrictToTargetLiteral"> <xs:sequence> <xs:element minOccurs="0" name="directory" type="core:AssociationDirectoryURI"/> ---Original---><xs:element minOccurs="0" name="target" type="core:URI"/> ---Updated---><xs:element minOccurs="1" name="target" type="core:String"/> </xs:sequence> </xs:complexType>
Actions taken:
February 24, 2012: received issue
July 24, 2013: closed issue

Issue 17183: AssociationReadServices WSDL corrections (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: 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
Revised Text: PIM: N/A PSM: Change Location: AssociationReadServicesTypes.xsd <xs:complexType name="read"> <xs:sequence> ---Original---><xs:element minOccurs="0" name="entryID" type="core:String"/> ---Updated---><xs:element minOccurs="1" name="associationID" type="core:URI"/> <xs:element minOccurs="0" name="queryControl" type="coreService:QueryControl"/> <xs:element minOccurs="0" name="context" type="coreService:ReadContext"/> </xs:sequence> </xs:complexType> <xs:complexType name="exists"> <xs:sequence> ---Original---> <xs:element minOccurs="0" name="entryID" type="core:String"/> ---Updated---> <xs:element minOccurs="1" name="associationID" type="core:URI"/> <xs:element minOccurs="0" name="context" type="coreService:ReadContext"/> </xs:sequence> </xs:complexType> <xs:complexType name="existsByExternalStatementId"> <xs:sequence> ---Original---><xs:element minOccurs="0" name="assertingCodeSystemVersion" type="coreService:NameOrURI"/> ---Updated---><xs:element minOccurs="1" name="scopingNamespace" type="coreService:NameOrURI"/> <xs:element minOccurs="0" name="externalStatementId" type="core:String"/> <xs:element minOccurs="0" name="context" type="coreService:ReadContext"/> </xs:sequence> </xs:complexType> <xs:complexType name="readByExternalStatementId"> <xs:sequence> <xs:element minOccurs="1" name="externalStatementId" type="core:String"/> ---Original---><xs:element minOccurs="0" name="assertingCodeSystemVersion" type="coreService:NameOrURI"/> ---Updated---><xs:element minOccurs="1" name="scopingNamespace" type="coreService:NameOrURI"/> <xs:element minOccurs="0" name="queryControl" type="coreService:QueryControl"/> <xs:element minOccurs="0" name="context" type="coreService:ReadContext"/> </xs:sequence> </xs:complexType>
Actions taken:
February 24, 2012: received issue
July 24, 2013: closed issue

Issue 17184: AssociationHistoryServices WSDL corrections (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: 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'
Revised Text: PIM: N/A PSM: Change Location: AssociationHistoryServiceTypes.xsd <xs:complexType name="getLatestChangeFor"> <xs:sequence> ---Original---><xs:element minOccurs="0" name="association" type="coreService:NameOrURI"/> ---Updated---><xs:element minOccurs="1" name="association" type="core:URI"/> </xs:sequence> </xs:complexType> <xs:complexType name="getEarliestChangeFor"> <xs:sequence> ---Original---><xs:element minOccurs="0" name="association" type="coreService:NameOrURI"/> ---Updated---><xs:element minOccurs="1" name="association" type="core:URI"/> </xs:sequence> </xs:complexType> <xs:complexType name="getChangeHistoryFor"> <xs:sequence> ---Original---><xs:element minOccurs="0" name="association" type="coreService:NameOrURI"/> ---Updated---> <xs:element minOccurs="1" name="association" type="core:URI"/> <xs:element minOccurs="0" name="fromDate" type="core:DateAndTime"/> <xs:element minOccurs="0" name="toDate" type="core:DateAndTime"/> </xs:sequence> </xs:complexType> Change Location: AssociationHistoryService.wsdl Note: All below are additions <wsdl:operation name="getLatestServiceChangeFor"> <wsdl:input name="getLatestServiceChangeFor" message="tns:getLatestServiceChangeFor"/> <wsdl:output name="getLatestServiceChangeForResponse" message="tns:getLatestServiceChangeForResponse"/> </wsdl:operation> <wsdl:operation name="getServiceHistoryFor"> <wsdl:input name="getServiceHistoryFor" message="tns:getServiceHistoryFor"/> <wsdl:output name="getServiceHistoryForResponse" message="tns:getServiceHistoryForResponse"/> </wsdl:operation> <wsdl:operation name="getEarliestServiceChangeFor"> <wsdl:input name="getEarliestServiceChangeFor" message="tns:getEarliestServiceChangeFor"/> <wsdl:output name="getEarliestServiceChangeForResponse" message="tns:getEarliestServiceChangeForResponse"/> </wsdl:operation>
Actions taken:
February 24, 2012: received issue
July 24, 2013: closed issue

Issue 17185: AssociationMaintenanceServices WSDL corrections (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: 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
Revised Text: PIM: N/A PSM: Change Location: AssociationTransformService.wsdl ---Added----> <wsdl:message name="addAssociation"> <wsdl:part name="parameters" element="tns:addAssociation"/> </wsdl:message> <wsdl:message name="addAssociationResponse"> <wsdl:part name="parameters" element="tns:addAssociationResponse"/> </wsdl:message> ---End Added----> ---Removed----> <wsdl:message name="createAssociationFromExpressionResponse"> <wsdl:part name="parameters" element="tns:createAssociationFromExpressionResponse"/> </wsdl:message> <wsdl:message name="createAssociationsFromExpressionResponse"> <wsdl:part name="parameters" element="tns:createAssociationsFromExpressionResponse"/> </wsdl:message> <wsdl:message name="createAssociationFromExpression"> <wsdl:part name="parameters" element="tns:createAssociationFromExpression"/> </wsdl:message> <wsdl:message name="createAssociationsFromExpression"> <wsdl:part name="parameters" element="tns:createAssociationsFromExpression"/> </wsdl:message> ---End Removed----> Change Location: AssociationTransformServiceTypes.xsd <xs:complexType name="putChangeSet"> <xs:sequence> <xs:element minOccurs="1" name="changeSet" type="core:ChangeSetURI"/> ---Added---><xs:element minOccurs="0" name="errorResponse" type="coreService:ErrorResponse"/> </xs:sequence> </xs:complexType> <xs:complexType name="validateChangeSet"> <xs:sequence> ---Added---><xs:element minOccurs="1" name="validationLevel" type="coreService:ValidationLevel"/> <xs:element minOccurs="1" name="changeSet" type="updates:ChangeSet"/> </xs:sequence> </xs:complexType> <xs:complexType name="updateChangeSetMetadata"> <xs:sequence> <xs:element minOccurs="1" name="changeSet" type="core:ChangeSetURI"/> <xs:element minOccurs="0" name="creator" type="core:SourceReference"/> <xs:element minOccurs="0" name="changeInstructions" type="core:OpaqueData"/> ---Added---><xs:element minOccurs="0" name="officialEffectiveDate" type="core:DateAndTime"/> </xs:sequence> </xs:complexType> <xs:complexType name="updateChangeableMetadata"> <xs:sequence> <xs:element minOccurs="1" name="changeSet" type="core:ChangeSetURI"/> ---Added---><xs:element minOccurs="1" name="entryID" type="core:PersistentURI" /> <xs:element minOccurs="0" name="status" type="coreService:NameOrURI"/> <xs:element minOccurs="0" name="entryState" type="core:EntryState"/> </xs:sequence> </xs:complexType> <xs:complexType name="updateAssociation"> <xs:sequence> <xs:element minOccurs="1" name="changeSet" type="core:ChangeSetURI"/> <xs:element minOccurs="1" name="assertingCodeSystemVersion" type="coreService:NameOrURI"/> <xs:element minOccurs="1" name="subject" type="coreService:EntityNameOrURI"/> ---Added---><xs:element minOccurs="1" name="predicate" type="coreService:EntityNameOrURI"/> ---Added---><xs:element minOccurs="1" name="target" type="core:StatementTarget"/> ---Added---><xs:element minOccurs="0" name="externalStatementId" type="core:String"/> </xs:sequence> </xs:complexType>
Actions taken:
February 24, 2012: received issue
July 24, 2013: closed issue

Issue 17186: AssociationTransformServices WSDL corrections (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

Removed method 'getSupportedVersionTags' and 'fromEntityDirectory'             In method 'toAssociationFormat' changed type of param 'codeSystemVersion' to 'CodeSystemVersionReference'              Logged:  https://github.com/cts2/cts2-specification/issues/55

Resolution: 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
Revised Text: PIM: N/A PSM: Change Location: AssociationTransformServiceTypes.xsd NOTE: (for removes see below) <xs:complexType name="toAssociationFormat"> <xs:sequence> <xs:element minOccurs="1" name="entityExpression" type="core:EntityExpression"/> ---Modified---><xs:element minOccurs="1" name="codeSystemVersion" type="coreService:NameOrURI" /> </xs:sequence> ... </xs:complexType> Change Location: AssociationTransformService.wsdl Note: elements in this section have been removed from the original. ---Remove---><wsdl:message name="getSupportedVersionTags"> <wsdl:part name="parameters" element="tns:getSupportedVersionTags"/> </wsdl:message> <wsdl:message name="getSupportedVersionTagsResponse"> <wsdl:part name="parameters" element="tns:getSupportedVersionTagsResponse"/> </wsdl:message> ---End Remove--> ---Remove---><wsdl:operation name="getSupportedVersionTags"> <wsdl:input name="getSupportedVersionTags" message="tns:getSupportedVersionTags"/> <wsdl:output name="getSupportedVersionTagsResponse" message="tns:getSupportedVersionTagsResponse"/> </wsdl:operation> ---End Remove--> ---Remove---><wsdl:operation name="getSupportedVersionTags"> <documentation xmlns="http://schemas.xmlsoap.org/wsdl/"/> <soap:operation soapAction="" style="document"/> <wsdl:input name="getSupportedVersionTags"> <soap:body use="literal"/> </wsdl:input> <wsdl:output name="getSupportedVersionTagsResponse"> <soap:body use="literal"/> </wsdl:output> </wsdl:operation> ---End Remove-->
Actions taken:
February 24, 2012: received issue
July 24, 2013: closed issue

Issue 17187: BaseImport/ExportServices WSDL correction (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

Changed all URI param types from String to LocalURI or DocumentURI         Logged:  https://github.com/cts2/cts2-specification/issues/56

Resolution: PIM: N/A PSM: Changed all URI param types from String to LocalURI or DocumentURI
Revised Text: PIM: N/A PSM: Change Location: BaseImportServiceTypes.xsd, BaseExportService.wsdl,BaseExportServiceTypes.xsd <xs:complexType name="getLog"> <xs:sequence> <xs:element minOccurs="0" name="level" type="coreService:LoggingLevel"/> <xs:element minOccurs="0" name="processId" type="core:LocalURI"/> </xs:sequence> </xs:complexType> <xs:complexType name="clearLog"> <xs:sequence> ---Original---><xs:element minOccurs="0" name="processId" type="core:String"/> ---Updated---><xs:element minOccurs="0" name="processId" type="core:LocalURI"/> </xs:sequence> </xs:complexType> <xs:complexType name="getStatus"> <xs:sequence> ---Original---><xs:element minOccurs="1" name="processId" type="core:String"/> ---Updated---><xs:element minOccurs="1" name="processId" type="core:LocalURI"/> </xs:sequence> </xs:complexType>
Actions taken:
February 24, 2012: received issue
July 24, 2013: closed issue

Issue 17188: ConceptDomainBindingQueryServices WSDL corrections (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

In method 'count' add a 'timeout' param.         Logged:  https://github.com/cts2/cts2-specification/issues/57

Resolution: PIM: N/A PSM: In 'count' method added 'timeout' param.
Revised Text: PIM: N/A PSM: Change Location: ConceptDomainBindingQueryServiceTypes.xsd <xs:complexType name="count"> <xs:sequence> <xs:element minOccurs="1" name="directory" type="core:ConceptDomainBindingDirectoryURI"/> <xs:element minOccurs="0" name="context" type="coreService:ReadContext"/> ---Added---><xs:element minOccurs="0" name="timeout" type="core:NaturalNumber"/> </xs:sequence> </xs:complexType>
Actions taken:
February 24, 2012: received issue
July 24, 2013: closed issue

Issue 17189: ConceptDomainBindingMaintenanceServices WSDL corrections (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: 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'
Revised Text: PIM: N/A PSM: Change Location: ConceptDomainBindingMaintenanceServiceTypes.xsd <xs:complexType name="putChangeSet"> <xs:sequence> <xs:element minOccurs="1" name="changeSet" type="core:ChangeSetURI"/> ---Added---><xs:element minOccurs="0" name="errorResponse" type="coreService:ErrorResponse"/> </xs:sequence> </xs:complexType> <xs:complexType name="validateChangeSet"> <xs:sequence> ---Added---><xs:element minOccurs="1" name="validationLevel" type="coreService:ValidationLevel"/> <xs:element minOccurs="1" name="changeSet" type="updates:ChangeSet"/> </xs:sequence> </xs:complexType> <xs:complexType name="updateChangeSetMetadata"> <xs:sequence> <xs:element minOccurs="1" name="changeSet" type="core:ChangeSetURI"/> <xs:element minOccurs="0" name="creator" type="core:SourceReference"/> <xs:element minOccurs="0" name="changeInstructions" type="core:OpaqueData"/> ---Added---><xs:element minOccurs="0" name="officialEffectiveDate" type="core:DateAndTime"/> </xs:sequence> </xs:complexType> <xs:complexType name="updateChangeableMetadata"> <xs:sequence> <xs:element minOccurs="1" name="changeSet" type="core:ChangeSetURI"/> ---Added---><xs:element minOccurs="1" name="entryID" type="core:PersistentURI"/> <xs:element minOccurs="0" name="status" type="coreService:NameOrURI"/> <xs:element minOccurs="0" name="entryState" type="core:EntryState"/> </xs:sequence> </xs:complexType> <xs:complexType name="updateConceptDomainBinding"> <xs:sequence> <xs:element minOccurs="1" name="changeSet" type="core:ChangeSetURI"/> ---Original---><xs:element minOccurs="1" name="conceptDomain" type="core:DocumentURI"/> ---Updated---><xs:element minOccurs="1" name="conceptDomainBinding" type="core:DocumentURI"/> <xs:element minOccurs="1" ref="conceptDomainBindingService:UpdateConceptDomainBindingRequest" /> </xs:sequence> </xs:complexType> <xs:complexType name="newProperty"> <xs:sequence> ---Added---><xs:element minOccurs="1" name="predicate" type="coreService:EntityNameOrURI"/> ---Removed---><xs:element minOccurs="0" name="entity" type="coreService:EntityNameOrURI"/> <xs:element minOccurs="1" name="value" type="core:StatementTarget"/> <xs:element minOccurs="0" name="externalIdentifier" type="core:String"/> </xs:sequence> </xs:complexType> <xs:complexType name="readChangeSet"> <xs:sequence> <xs:element minOccurs="1" name="changeSet" type="core:ChangeSetURI"/> ---Added---><xs:element minOccurs="0" name="queryControl" type="coreService:QueryControl"/> </xs:sequence> </xs:complexType>
Actions taken:
February 24, 2012: received issue
July 24, 2013: closed issue

Issue 17190: ConceptDomainCatalogQueryServices WSDL corrections (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

In method 'count' added a 'timeout' param         Logged:  https://github.com/cts2/cts2-specification/issues/59

Resolution: PIM: N/A PSM: In 'count' method added 'timeout' param.
Revised Text: PIM: N/A PSM: Change Location: ConceptDomainCatalogQueryServiceTypes.xsd <xs:complexType name="count"> <xs:sequence> <xs:element minOccurs="1" name="directory" type="core:ConceptDomainCatalogEntryDirectoryURI"/> <xs:element minOccurs="0" name="context" type="coreService:ReadContext"/> ---Added---><xs:element minOccurs="0" name="timeout" type="core:NaturalNumber"/> </xs:sequence> </xs:complexType>
Actions taken:
February 24, 2012: received issue
July 24, 2013: closed issue

Issue 17191: ConceptDomainCatalogHistoryServices WSDL corrections (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

In method 'count' added a 'timeout' param             In method 'readChangeSet' renamed param 'URI' to 'changeSetURI'         Logged:  https://github.com/cts2/cts2-specification/issues/60

Resolution: PIM: N/A PSM: � In 'count' method added 'timeout' param. � In method 'readChangeSet' renamed param 'URI' to 'changeSetURI'
Revised Text: PIM: N/A PSM: Change Location: ConceptDomainCatalogHistoryServiceTypes.xsd <xs:complexType name="count"> <xs:sequence> <xs:element minOccurs="1" name="directory" type="core:CodeSystemVersionCatalogEntryDirectoryURI"/> <xs:element minOccurs="0" name="context" type="coreService:ReadContext"/> ---Added---><xs:element minOccurs="0" name="timeout" type="core:NaturalNumber"/> </xs:sequence> </xs:complexType> <xs:complexType name="readChangeSet"> <xs:sequence> ---Original---><xs:element minOccurs="1" name="URI" type="core:ChangeSetURI"/> ---Updated--><xs:element minOccurs="1" name="changeSetURI" type="core:ChangeSetURI"/> </xs:sequence> </xs:complexType>
Actions taken:
February 24, 2012: received issue
July 24, 2013: closed issue

Issue 17192: EntityDescriptionTransformService WSDL corrections (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

Renamed method 'getKnownCodeSystems' to 'getKnownCodeSystemVersion'             Removed method 'getSupportedVersionTags'         Logged:  https://github.com/cts2/cts2-specification/issues/61

Resolution: PIM: N/A PSM: Renamed method 'getKnownCodeSystems' to 'getKnownCodeSystemVersion'
Revised Text: PIM: N/A PSM: Change Location: EntityDescriptionTransformService.wsdl ---Original---><wsdl:operation name="getKnownCodeSystems"/> ---Updated--><wsdl:operation name="getKnownCodeSystemVersion"> <wsdl:input name="getKnownCodeSystemVersion" message="tns:getKnownCodeSystemVersion"/> <wsdl:output name="getKnownCodeSystemVersionResponse" message="tns:getKnownCodeSystemVersionResponse"/> </wsdl:operation>
Actions taken:
February 24, 2012: received issue
July 24, 2013: closed issue

Issue 17193: EntityDescriptionQueryServices WSDL corrections (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: 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'
Revised Text: PIM: N/A PSM: Change Location: EntityDescriptionMaintenanceServices.wsdl <xs:complexType name="count"> <xs:sequence> <xs:element minOccurs="1" name="directory" type="core:EntityDirectoryURI"/> <xs:element minOccurs="0" name="context" type="coreService:ReadContext"/> ---Added---><xs:element minOccurs="0" name="timeout" type="core:NaturalNumber"/> </xs:sequence> </xs:complexType> Change Location: EntityDescriptionMaintenanceServices.wsdl ---Original---><wsdl:operation name="restrictToCodeSystemVersions"/> ---Updated--><wsdl:operation name="restrictToCodeSystemVersion"> <wsdl:input name="restrictToCodeSystemVersion" message="tns:restrictToCodeSystemVersion"/> <wsdl:output name="restrictToCodeSystemVersionResponse" message="tns:restrictToCodeSystemVersionResponse"/> </wsdl:operation> ---Original---><wsdl:operation name="restrictToCodeSystems"/> ---Updated--><wsdl:operation name="restrictToCodeSystem"> <wsdl:input name="restrictToCodeSystem" message="tns:restrictToCodeSystem"/> <wsdl:output name="restrictToCodeSystemResponse" message="tns:restrictToCodeSystemResponse"/> </wsdl:operation> (added) <wsdl:operation name="isEntityInSet"> <wsdl:input name="isEntityInSet" message="tns:isEntityInSet"/> <wsdl:output name="isEntityInSetResponse" message="tns:isEntityInSetResponse"/> </wsdl:operation> (added) <wsdl:operation name="restrictToEntities"> <wsdl:input name="restrictToEntities" message="tns:restrictToEntities"/> <wsdl:output name="restrictToEntitiesResponse" message="tns:restrictToEntitiesResponse"/> </wsdl:operation> (added) <wsdl:operation name="intersectEntityList"> <wsdl:input name="intersectEntityList" message="tns:intersectEntityList"/> <wsdl:output name="intersectEntityListResponse" message="tns:intersectEntityListResponse"/> </wsdl:operation>
Actions taken:
February 24, 2012: received issue
July 24, 2013: closed issue

Issue 17194: EntityDescriptionMaintenanceServices WSDL changes (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: PIM: N/A PSM: � In method 'readChangeSet' add param 'queryControl' � In method 'updateChangeSetMetadata added param 'officialEffectiveDate' � In method putChangeSet change return type to ProcessStatus'
Revised Text: PIM: N/A PSM: Change Location: EntityDescriptionMaintenanceServicesTypes.xsd <xs:complexType name="readChangeSet"> <xs:sequence> <xs:element minOccurs="1" name="changeSet" type="core:ChangeSetURI"/> ---Added---><xs:element minOccurs="0" name="queryControl" type="coreService:QueryControl"/> </xs:sequence> </xs:complexType> <xs:complexType name="updateChangeSetMetadata"> <xs:sequence> <xs:element minOccurs="1" name="changeSet" type="core:ChangeSetURI"/> <xs:element minOccurs="0" name="creator" type="core:SourceReference"/> <xs:element minOccurs="0" name="changeInstructions" type="core:OpaqueData"/> ---Added---><xs:element minOccurs="0" name="officialEffectiveDate" type="core:DateAndTime"/> </xs:sequence> </xs:complexType> <xs:complexType name="putChangeSetResponse"> <xs:sequence> ---Removed---><xs:element name="return" type="coreService:SuccessIndicator"/> ---Added---><xs:element name="return" type="coreService:ProcessStatus"/> </xs:sequence> </xs:complexType>
Actions taken:
February 24, 2012: received issue
July 24, 2013: closed issue

Issue 17317: CTS2: ScopedEntityName.name type is too strong (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: PIM: N/A PSM: Changed the 'name' element from 'LocalIdentifier' to 'String.'
Revised Text: PIM: N/A PSM: Change Location: Core.xsd <xs:complexType name="ScopedEntityName"> <xs:annotation> <xs:documentation>The combination of a namespace identifier and a local name. Scoped entity names are not portable - they only work within the context of a single service instance, as different services may assign different namespace identifiers to the same namespace and different services may make different choices of the appropriate local identifier to use to represent an entity. As an example, one service may choose to use the entity code while a second may use another designation that is known to be unique.</xs:documentation> </xs:annotation> <xs:sequence> <xs:element name="namespace" type="NamespaceIdentifier" minOccurs="1"> <xs:annotation> <xs:documentation>an identifier that references a unique namespace URI within the context of the service</xs:documentation> </xs:annotation> </xs:element> ---Original---><xs:element name="name" type="LocalIdentifier" minOccurs="1"> ---Updated---> <xs:element name="name" type="String" minOccurs="1"> <xs:annotation> <xs:documentation>the local entity name within the context of the namespace. What is chosen for the entity name is service specific</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType>
Actions taken:
April 20, 2012: received issue
July 24, 2013: closed issue

Issue 17319: CTS2: currentVersion not typed in MapCatalogEntry (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

Map.xsd MapCatalogEntry currentVersion does not have an XSD type. Should be MapVersionReference...         Logged:  https://github.com/cts2/cts2-specification/issues/89

Resolution: 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">
Revised Text: PIM: N/A PSM: Change Location: Core.xsd <xs:complexType name="MapCatalogEntry"> <xs:annotation> <xs:documentation>An entry in a catalog of maps - organized collections of rules that describe how information encoded using one set of value meanings can be transformed into a second, related set of meanings. A map catalog contains information about who is responsible for creating and distributing the rules, the source code system or value set, the target code system or value set, how often the rules are updated, how they are distributed, etc.</xs:documentation> </xs:annotation> <xs:complexContent> <xs:extension base="core:AbstractResourceDescription"> <xs:sequence> <xs:element name="fromCodeSystem" type="core:CodeSystemReference" minOccurs="0"> <xs:annotation> <xs:documentation>the CodeSystem from which the source codes in the Map are drawn. Note that the source codes may be drawn from either a CodeSystem or a ValueSet, but not both.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="fromValueSet" type="core:ValueSetReference" minOccurs="0"> <xs:annotation> <xs:documentation>the ValueSet from which the source codes in the Map are drawn. Note that the source codes may be drawn from either a CodeSystem or a ValueSet, but not both.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="toCodeSystem" type="core:CodeSystemReference" minOccurs="0"> <xs:annotation> <xs:documentation>the CodeSystem from which the target codes in the Map are drawn. Note that the target codes may be drawn from either a CodeSystem or a ValueSet, but not both.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="toValueSet" type="core:ValueSetReference" minOccurs="0"> <xs:annotation> <xs:documentation>the ValueSet from which the source codes in the Map are drawn. Note that the target codes may be drawn from either a CodeSystem or a ValueSet, but not both.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="versions" type="core:MapVersionDirectoryURI" minOccurs="0"> <xs:annotation> <xs:documentation>a URI that, when resolved, returns the known versions of the containing Map</xs:documentation> </xs:annotation> </xs:element> ------Original-----><xs:element name="currentVersion" minOccurs="0"> ------Updated----><xs:element name="currentVersion" type="core:MapVersionReference" minOccurs="0"> <xs:annotation> <xs:documentation>The map version associated with this catalog entry that has been assigned the CURRENT tag, if any</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> <xs:attribute name="mapName" type="core:MapName" use="required"> <xs:annotation> <xs:documentation>the name by which the map is known within the context of the CTS2 service instance. mapName must uniquely designate a single, abstract Map within the context of all maps known to the instance of the service. Note that mapName is not necessarily globally unique and the about URI should be used whenever communication information about the Map across time or service instances.</xs:documentation> </xs:annotation> </xs:attribute> </xs:extension> </xs:complexContent> </xs:complexType>
Actions taken:
April 20, 2012: received issue
July 24, 2013: closed issue

Issue 17320: CTS2: Inconsistent element/complexType declarations (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: 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>
Revised Text: PIM: N/A PSM: Change Location: All schemas Apply the above pattern to all XSD Elements in all XSDs.
Actions taken:
April 20, 2012: received issue
July 24, 2013: closed issue

Issue 17321: CTS2: Message Header Documentation Missing (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: PIM: N/A PSM: Added in documentation to the 'RestResource' type as described in the updated xml below.
Revised Text: PIM: N/A PSM: Change Location: Core.xsd <xs:element name="resourceURI" type="RenderingURI"> <xs:annotation> <xs:documentation>The 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:appinfo>PSM</xs:appinfo> </xs:annotation> </xs:element> <xs:element name="parameter" type="Parameter" minOccurs="0" maxOccurs="unbounded"> <xs:annotation> <xs:documentation>The 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:appinfo>PSM</xs:appinfo> </xs:annotation> </xs:element> <xs:element name="accessDate" type="DateAndTime"> <xs:annotation> <xs:documentation>The date and time that the resource was accessed.</xs:documentation> <xs:appinfo>PSM</xs:appinfo> </xs:annotation> </xs:element>
Actions taken:
April 20, 2012: received issue
July 24, 2013: closed issue

Issue 17322: CTS2: StructuralProfile - Statement and/or MapEntry (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: 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 Map_Entry profile represents individual entries in a Map_Version</xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="SP_STATEMENT"> <xs:annotation> <xs:documentation>The Statement profile provides a bridge between the CTS2 model structure and the underlying RDF/XML/etc.</xs:documentation> </xs:annotation> </xs:enumeration>
Revised Text: PIM: N/A PSM: Change Location: CoreService.xsd <xs:simpleType name="StructuralProfile"> <xs:annotation> <xs:documentation>The CTS2 specification defines eleven distinct structural profiles. CTS2 compliant implementations may elect to implement any combination of these profiles to meet their individual requirements and use cases.</xs:documentation> </xs:annotation> <xs:restriction base="xs:string"> <xs:enumeration value="SP_CODE_SYSTEM"> <xs:annotation> <xs:documentation>The CODE_SYSTEM profile provides a catalog of classification systems, code systems, ontologies, thesauri, etc. known to the service and may also carry information about their publisher, release cycles, purpose, etc.</xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="SP_CODE_SYSTEM_VERSION"> <xs:annotation> <xs:documentation>The CODE_SYSTEM_VERSION profile carries information about the various versions of a code system, including when the release date, release format, contact information, etc.</xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="SP_ENTITY_DESCRIPTION"> <xs:annotation> <xs:documentation>The ENTITY DESCRIPTION profile provides a representation of a collection of descriptions about classes, roles or individuals along with links to the code system version(s) in which these descriptions originate. An entity description provides the "lexical" or "non-semantic" components of a description, while the ASSOCIATION profile provides the logic-based "semantic" counterpart.The service supports the EntityDescription structural model, which means that it can represent sets of lexical assertions about classes, roles and/or individuals as asserted by a specific code system version</xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="SP_ASSOCIATION"> <xs:annotation> <xs:documentation>The ASSOCIATION profile represents a collection of structured, "semantic" assertions about classes, roles and/or individuals along with links to the code system version(s) that were the source of these assertions.The service supports the Association structural model, which means that it can represent sets of semantic assertions about classes, roles and/or individuals as asserted by a specific code system version</xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="SP_VALUE_SET"> <xs:annotation> <xs:documentation>The VALUE_SET profile provides a catalog of value sets that are known to the service along with information about their publisher, release cycles, purpose, etc. Note that "Value Set" in this context represents an abstraction (e.g. the HL7 Administrative Gender Value Set, the SNOMED-CT core anatomic types) that may be coupled with different sets of possible values at different periods in time.</xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="SP_VALUE_SET_DEFINITION"> <xs:annotation> <xs:documentation>The VALUE_SET_DEFINITION structural profile provides definitions that, when interpreted using specified code system versions, result in a set of entity descriptions. Definitions are associated with value sets and can vary and evolve over time.</xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="SP_VALUE_SET_RESOLUTION"> <xs:annotation> <xs:documentation>The VALUE_SET_RESOLUTION profile describes rules for ordering and associating additional properties with the result of interpreting a value set definition. VALUE_SET_RESOLUTION allows resolved definitions to be rendered in a given language and context, sorted and filtered.</xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="SP_CONCEPT_DOMAIN"> <xs:annotation> <xs:documentation>A CONCEPT_DOMAIN profile describes the equivalent of a 11179 Data Element Concept. It identifies an abstract unit of information that can appear on a message, form or database along with metadata about its use, author, purpose, etc.</xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="SP_CONCEPT_DOMAIN_BINDING"> <xs:annotation> <xs:documentation>A CONCEPT_DOMAIN_BINDING profile describes the equivalent of the 11179 Data Element, associating a CONCEPT_DOMAIN with a value set and describing the context and rules where the association applies.</xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="SP_MAP"> <xs:annotation> <xs:documentation>The MAP profile defines collections of rules for transforming information represented using one code system into information represented in a section. MAP describes abstract collections such as "The SNOMED-CT to ICD-10 map", along with the creators, intended use, code systems involved, etc.</xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="SP_MAP_VERSION"> <xs:annotation> <xs:documentation>The MAP_VERSION profile represents the actual content of a MAP at a given point in time. It carries the from and to components as well as a representation of the rules and process for the conversion</xs:documentation> </xs:annotation> </xs:enumeration> ---Start-Added---> <xs:enumeration value="SP_MAP_ENTRY"> <xs:annotation> <xs:documentation>The Map_Entry profile represents individual entries in a Map_Version</xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="SP_STATEMENT"> <xs:annotation> <xs:documentation>The Statement profile provides a bridge between the CTS2 model structure and the underlying RDF/XML/etc.</xs:documentation> </xs:annotation> </xs:enumeration> ---End-Added---> </xs:restriction> </xs:simpleType>
Actions taken:
April 20, 2012: received issue
July 24, 2013: closed issue

Issue 17323: Create/Update in WADL use the wrong HTTP methods (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: PIM: N/A PSM: Change all creates to an HTTP 'POST' and all updates to an HTTP 'PUT'.
Revised Text: PIM: N/A PSM: Change Location: cts2.wadl CodeSystem (Added) <resource path="codesystem"> <method name="POST"> <doc title="CodeSystemCatalogMaintenanceService:createCodeSystem" >Create a new entry in the code system catalog</doc> <request> <param name="changeseturi" required="true" type="xsd:string" style="query"> <doc title="ChangeSetURI">the unique identifier of a set of change instructions that can potentially transform the contents of CTS2 service instance from one state to another. </doc> </param> <representation element="codeSystem:CodeSystemCatalogEntry"/> </request> <response status="201"/> </method> </resource> <resource path="codesystem/{codesystemid}"> <param name="codesystemid" type="xsd:string" style="template"/> <method name="PUT"> <doc title="CodeSystemCatalogMaintenanceService:updateCodeSystem" >Update the contents of an existing catalog entry.</doc> <request> <representation element="codeSystem:CodeSystemCatalogEntry" > </representation> </request> </method> </resource> CodeSystemVersion (Added) <resource path="codesystemversion"> <method name="POST"> <doc title="CodeSystemVersionCatalogMaintenanceService:createCodeSystemVersion"/> <request> <param name="changeseturi" required="true" type="xsd:string" style="query"> <doc title="ChangeSetURI">the unique identifier of a set of change instructions that can potentially transform the contents of CTS2 service instance from one state to another. </doc> </param> <representation element="codeSystemVersion:CodeSystemVersionCatalogEntry"> <doc xmlns="http://www.w3.org/2001/XMLSchema" title="Representation Type"/> </representation> </request> <response status="201"/> </method> </resource> <method name="PUT"> <doc title="CodeSystemVersionCatalogMaintenanceService:updateCodeSystemVersion"/> <request> <param name="changeseturi" required="true" type="xsd:string" style="query"> <doc title="ChangeSetURI">the unique identifier of a set of change instructions that can potentially transform the contents of CTS2 service instance from one state to another. </doc> </param> <representation element="codeSystemVersion:CodeSystemVersionCatalogEntry"> <doc xmlns="http://www.w3.org/2001/XMLSchema" title="Representation Type"/> </representation> </request> </method> ValueSetDefinition (Added) <resource path="valuesetdefinition"> <method name="POST"> <doc title="ValueSetDefinitionMaintenanceService:createValueSetDefinition"/> <request> <param name="changeseturi" required="true" type="xsd:string" style="query"> <doc title="ChangeSetURI">the unique identifier of a set of change instructions that can potentially transform the contents of CTS2 service instance from one state to another. </doc> </param> <representation element="valueSetDefinition:ValueSetDefinition"> <doc xmlns="http://www.w3.org/2001/XMLSchema" title="Representation Type"/> </representation> </request> </method> </resource> <method name="PUT"> <doc title="ValueSetDefinitionMaintenanceService:update*/create*/add*"/> <request> <representation element="valueSetDefinition:ValueSetDefinition" > </representation> </request> </method> MapVersion (Added) <resource path="mapversion"> <method name="POST"> <doc title="MapVersionMaintenanceService:createMapVersion" >Create a new map version entry.</doc> <request> <param name="changeseturi" required="true" type="xsd:string" style="query"> <doc title="ChangeSetURI">the unique identifier of a set of change instructions that can potentially transform the contents of CTS2 service instance from one state to another. </doc> </param> <representation element="mapVersion:MapVersion"> <doc xmlns="http://www.w3.org/2001/XMLSchema" title="Representation Type">A specific version of a Map. MapVersion is bound to specific code system versions and/or value set versions and references a set of mapping entries (mapSet) that, if the resource is FINAL, are fixed with respect to this version.</doc> </representation> </request> <response status="201"/> </method> </resource> <method name="PUT"> <doc title="MapVersionMaintenanceService:updateMapVersion" >Update an existing entry in the map version</doc> <request> <representation element="mapVersion:MapVersion"> <doc xmlns="http://www.w3.org/2001/XMLSchema" title="Representation Type"/> </representation> </request> <response status="201"> </response> </method> Association (Added) <resource path="association"> <method name="POST"> <doc title="AssociationMaintenanceService:createAssociation" >Create a new Association</doc> <request> <param name="changeseturi" required="true" type="xsd:string" style="query"> <doc title="ChangeSetURI">the unique identifier of a set of change instructions that can potentially transform the contents of CTS2 service instance from one state to another. </doc> </param> <representation element="association:Association" > </representation> </request> <response status="201"/> </method> </resource> <method name="PUT"> <doc title="AssociationMaintenanceService:updateAssociation" >Update an existing Association resource</doc> <request> <param name="changeseturi" type="xsd:string" style="query"> <doc title="ChangeSetURI">the unique identifier of a set of change instructions that can potentially transform the contents of CTS2 service instance from one state to another. </doc> </param> <representation element="association:Association" > </representation> </request> </method> Concept Domain (Added) <resource path="conceptdomain"> <method name="POST"> <doc title="ConceptDomainCatalogMaintenanceService:createConceptDomain" >Create a new concept domain</doc> <request> <param name="changeseturi" required="true" type="xsd:string" style="query"/> <representation element="conceptDomain:ConceptDomain"> <doc xmlns="http://www.w3.org/2001/XMLSchema" title="Representation Type"/> </representation> </request> <response status="201"/> </method> </resource> <method name="PUT"> <doc title="ConceptDomainCatalogMaintenanceService:updateConceptDomain" >Update the contents of an concept domain catalog entry.</doc> <request> <representation element="conceptDomain:ConceptDomainCatalogEntry" > </representation> </request> </method> Concept Domaing Binding (Added) <resource path="conceptdomainbinding"> <method name="POST"> <doc title="ConceptDomainBindingMaintenanceService:createConceptDomainBinding" >Create a new concept domain binding</doc> <request> <param name="changeseturi" required="true" type="xsd:string" style="query"/> <representation element="conceptDomainBinding:ConceptDomainBinding"> <doc xmlns="http://www.w3.org/2001/XMLSchema" title="Representation Type"/> </representation> </request> <response status="201"/> </method> </resource> <method name="PUT"> <doc title="ConceptDomainBindingMaintenanceService:updateConceptDomainBinding" >Change one or more elements in the named concept domain binding and return the result of the change</doc> <request> <param name="changeseturi" required="true" type="xsd:string" style="query"/> <representation element="conceptDomainBindingService:UpdateConceptDomainBindingRequest"> <doc xmlns="http://www.w3.org/2001/XMLSchema" title="Representation Type"/> </representation> </request> </method> Map (Added) <resource path="map"> <method name="POST"> <doc title="MapCatalogMaintenanceService:createMapCatalogEntry" >Create a new entry in the map catalog</doc> <request> <param name="changeseturi" required="true" type="xsd:string" style="query"> <doc title="ChangeSetURI">the unique identifier of a set of change instructions that can potentially transform the contents of CTS2 service instance from one state to another. </doc> </param> <representation element="map:MapCatalogEntry"> <doc xmlns="http://www.w3.org/2001/XMLSchema" title="Representation Type">An entry in a catalog of maps - organized collections of rules that describe how information encoded using one set of value meanings can be transformed into a second, related set of meanings. A map catalog contains information about who is responsible for creating and distributing the rules, the source code system or value set, the target code system or value set, how often the rules are updated, how they are distributed, etc.</doc> </representation> </request> <response status="201"/> </method> </resource> <method name="PUT"> <doc title="MapCatalogMaintenanceService:updateMap">Update an existing entry in the map catalog</doc> <request> <representation element="map:MapCatalogEntry"> <doc xmlns="http://www.w3.org/2001/XMLSchema" title="Representation Type"/> </representation> </request> </method> Map Entry <resource path="mapentry"> <method name="POST"> <doc title="MapEntryMaintenanceService:createMapEntry" >Create a new map entry</doc> <request> <param name="changeseturi" required="true" type="xsd:string" style="query"> <doc title="ChangeSetURI">the unique identifier of a set of change instructions that can potentially transform the contents of CTS2 service instance from one state to another. </doc> </param> <representation element="mapVersion:MapEntryMsg"/> </request> <response status="201"> </response> </method> </resource> <method name="PUT"> <doc title="MapEntryMaintenanceService:updateMapEntry">Update the attributes of the supplied map entry and return the result of the change</doc> <request> <param name="changeseturi" required="true" type="xsd:string" style="query"> <doc title="ChangeSetURI">the unique identifier of a set of change instructions that can potentially transform the contents of CTS2 service instance from one state to another. </doc> </param> <representation element="mapEntryService:UpdateMapEntryRequest"> <doc xmlns="http://www.w3.org/2001/XMLSchema" title="Representation Type">The set of parameters that can be updated in a map entry.</doc> </representation> </request> </method> Value Set <resource path="valueset"> <method name="POST"> <doc title="ValueSetCatalogMaintenanceService:createValueSet" >Create a new ValueSetCatalogEntry</doc> <request> <param name="changeseturi" required="true" type="xsd:string" style="query"> <doc title="ChangeSetURI">the unique identifier of a set of change instructions that can potentially transform the contents of CTS2 service instance from one state to another. </doc> </param> <representation element="valueSet:ValueSetCatalogEntry"> <doc xmlns="http://www.w3.org/2001/XMLSchema" title="Representation Type">An entry in a value set catalog that describes the purpose, use, etc. of a value set.</doc> </representation> </request> <response status="201"> </response> </method> </resource> <method name="PUT"> <doc title="ValueSetCatalogMaintenanceService:updateValueSet" >Update an existing ValueSetCatalogEntry</doc> <request> <representation element="valueSet:ValueSetCatalogEntry"> <doc xmlns="http://www.w3.org/2001/XMLSchema" title="Representation Type">An entry in a value set catalog that describes the purpose, use, etc. of a value set.</doc> </representation> </request> <response status="200"/> </method>
Actions taken:
April 20, 2012: received issue
July 24, 2013: closed issue

Issue 17324: CTS2: AssociationQueryService 'getAllSourceAndTargetEntities' wrong input parameter (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: PIM: N/A In the AssociationQueryService - method 'getAllSourceAndTargetEntities', change the parameter 'directory' to type 'AssociationDirectoryURI.' PSM: N/A
Revised Text: PIM: Updated Diagram (Figure 5.1: Association Query Service. Association, Page 54.)
Actions taken:
April 20, 2012: received issue
July 24, 2013: closed issue

Issue 17325: CTS2: ConceptDomainBindingReadService QueryControl parameters (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

The QueryControl parameter was omitted from the read and readByURI operations in ConceptDomainBindingService.         Logged:  https://github.com/cts2/cts2-specification/issues/81

Resolution: 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" />
Revised Text: PIM: Updated Diagram (Figure 4.1: Concept Domain Binding Read. Concept Domain Binding, Page 20.) PSM: Change Location: Core.xsd <xs:element name="readByURI" type="tns:readByURI"/> <xs:complexType name="readByURI"> <xs:sequence> <xs:element minOccurs="1" name="uri" type="core:DocumentURI"/> ---Added---><xs:element minOccurs="0" name="queryControl" type="coreService:QueryControl"/> </xs:sequence> </xs:complexType> <xs:element name="read" type="tns:read"/> <xs:complexType name="read"> <xs:sequence> <xs:element minOccurs="1" name="conceptDomain" type="coreService:NameOrURI"/> <xs:element minOccurs="1" name="valueSet" type="coreService:NameOrURI"/> <xs:element minOccurs="0" name="applicableContext" type="coreService:NameOrURI"/> <xs:element minOccurs="0" name="bindingQualifier" type="coreService:NameOrURI"/> ---Added---> <xs:element minOccurs="0" name="queryControl" type="coreService:QueryControl"/> </xs:sequence> </xs:complexType>
Actions taken:
April 20, 2012: received issue
July 24, 2013: closed issue

Issue 17326: CTS2: AssociationQueryServices WSDL corrections (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: 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
Revised Text: PIM: N/A PSM: Change Location: AssociationQueryService.wsdl,AssociationQueryServiceTypes.xsd ---Original---> <wsdl:operation name="getKnownCodeSystems"/> ---Updated---> <wsdl:operation name="getKnownCodeSystem"> <wsdl:input name="getKnownCodeSystem" message="tns:getKnownCodeSystem"/> <wsdl:output name="getKnownCodeSystemResponse" message="tns:getKnownCodeSystemResponse"/> </wsdl:operation> ---Original---> <wsdl:operation name="getKnownCodeSystemVersions"/> ---Updated---> <wsdl:operation name="getKnownCodeSystemVersion"> <wsdl:input name="getKnownCodeSystemVersion" message="tns:getKnownCodeSystemVersion"/> <wsdl:output name="getKnownCodeSystemVersionResponse" message="tns:getKnownCodeSystemVersionResponse"/> </wsdl:operation> <xs:complexType name="count"> <xs:sequence> <xs:element minOccurs="1" name="directory" type="core:EntityDirectoryURI"/> <xs:element minOccurs="0" name="context" type="coreService:ReadContext"/> ---Added---> <xs:element minOccurs="0" name="timeout" type="core:NaturalNumber"/> </xs:sequence> </xs:complexType> <xs:complexType name="restrict"> <xs:sequence> ---Original---> <xs:element minOccurs="0" name="directory" type="core:AssociationDirectoryURI"/> ---Updated---> <xs:element minOccurs="1" name="directory" type="core:DirectoryURI"/> <xs:element minOccurs="0" name="filter" type="core:Filter" /> </xs:sequence> </xs:complexType> <xs:complexType name="restrictToTargetExpression"> <xs:sequence> <xs:element minOccurs="0" name="directory" type="core:AssociationDirectoryURI"/> ---Original---> <xs:element minOccurs="0" name="target" type="association:AssociationRendering"/> ---Updated---> <xs:element minOccurs="1" name="target" type="core:EntityExpression"/> </xs:sequence> </xs:complexType> <xs:complexType name="restrictToTargetLiteral"> <xs:sequence> <xs:element minOccurs="0" name="directory" type="core:AssociationDirectoryURI"/> ---Original---> <xs:element minOccurs="0" name="target" type="core:URI"/> ---Updated---> <xs:element minOccurs="1" name="target" type="core:String"/> </xs:sequence> </xs:complexType>
Actions taken:
April 20, 2012: received issue
July 24, 2013: closed issue

Issue 17327: CTS2: Service map catalog typo (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: PIM: Update PIM text PSM: N/A
Revised Text: PIM: Change Location: Value Set Services, Page 6. Change text: The ValueSetCatalogReadService provides direct access to the service map catalog. ... to: The ValueSetCatalogReadService provides direct access to the service value set catalog. ... PSM: N/A
Actions taken:
April 20, 2012: received issue
July 24, 2013: closed issue

Issue 17330: CTS2: Concept Domain Catalog Query Service missing description (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: PIM: N/A PSM: N/A After review, the existing text is correct, and the change should not be applied to the PIM.
Revised Text: PIM: N/A PSM: N/A N\A - No Change Necessary Disposition: Closed No Change
Actions taken:
April 23, 2012: received issue
July 24, 2013: closed issue

Issue 17331: CTS2: section 1.1.2.1 Class CodeSystemCatalogEntryDirectory typo (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: PIM: N/A PSM: N/A After review, the existing text is correct, and the change should not be applied to the PIM.
Revised Text:
Actions taken:
April 23, 2012: received issue
October 9, 2012: closed issue

Issue 17332: CTS2: Change cardinality of defaultLanguage from [0..1] to [0..*] (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: 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</xs:documentation> </xs:annotation> </xs:element>
Revised Text: PIM: Change Location: Diagram (Figure 3.1: Code System Version, Page 19.) PSM: Change Location: CodeSystemVersion.xsd <xs:complexType name="CodeSystemVersionCatalogEntry"> <xs:annotation> <xs:documentation>CodeSystemVersion is a collection of assertions about one or more entities. If the state of a CodeSystemVersion is Final the set of assertions made the resource is fixed, meaning that if one knows the documentURI assigned to the version and the specific sourceAndNotation from which the version instance was derived, the set of assertions is known as well.</xs:documentation> </xs:annotation> <xs:complexContent> <xs:extension base="core:ResourceVersionDescription"> <xs:sequence> <xs:element name="versionOf" type="core:CodeSystemReference" minOccurs="1"> <xs:annotation> <xs:documentation>the name, URI and, if supported by the service, link to the code system that this version represents.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="imports" type="core:CodeSystemVersionReference" minOccurs="0" maxOccurs="unbounded"> <xs:annotation> <xs:documentation>a reference to a code system version whose assertions are included as part this code system version. </xs:documentation> </xs:annotation> </xs:element> <xs:element name="defaultLanguage" type="core:LanguageReference" minOccurs="0"> <xs:annotation> <xs:documentation>the default spoken or written language used in this version</xs:documentation> </xs:annotation> </xs:element> ---Start-Added---><xs:element name="supportedLanguage" type="core:LanguageReference" minOccurs="0" maxOccurs="unbounded"> <xs:annotation> <xs:documentation>all languages recognized by this particular code system version</xs:documentation> </xs:annotation> </xs:element> ---End-Added---><xs:element name="entityDescriptions" type="core:EntityDirectoryURI" minOccurs="0"> <xs:annotation> <xs:documentation>a DirectoryURI that resolves to the set of all entities and their descriptions asserted by this code system version. This attribute will only be present if and only if the service implementation supports the EntityQuery service profile.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="associations" type="core:AssociationDirectoryURI" minOccurs="0"> <xs:annotation> <xs:documentation>a DirectoryURI that,resolves to a a list of all associations asserted by this particular code system version</xs:documentation> </xs:annotation> </xs:element> <xs:element name="classes" type="core:EntityDirectoryURI" minOccurs="0"> <xs:annotation> <xs:documentation>a DirectoryURI that resolves to the set of EntityDescriptions that are of type owl:Class within this code system. Will only be present in code systems that represent ontologies.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="roles" type="core:EntityDirectoryURI" minOccurs="0"> <xs:annotation> <xs:documentation>a DirectoryURI that resolves to the set of EntityDescriptions that are of type owl:ObjectProperty or owl:DataProperty within this code system. Will only be present in code systems that represent ontologies.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="individuals" type="core:EntityDirectoryURI" minOccurs="0"> <xs:annotation> <xs:documentation>a DirectoryURI that resolves to the set of EntityDescriptions that are of type owl:Individual within this code system. Will only be present in code systems that represent ontologies.</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> <xs:attribute name="codeSystemVersionName" type="core:CodeSystemVersionName" use="required"> <xs:annotation> <xs:documentation>an identifier that uniquely names this particular code system version within the context of the CTS2 service instance.</xs:documentation> </xs:annotation> </xs:attribute> </xs:extension> </xs:complexContent> </xs:complexType>
Actions taken:
April 23, 2012: received issue
July 24, 2013: closed issue

Issue 17350: Missing documentation on StatementSubject (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

subjectType is not documented on page 3 of the Statement Information Model         Logged:  https://github.com/cts2/cts2-specification/issues/92

Resolution: PIM: Update PIM text PSM: N/A
Revised Text: PIM: Change Location: Statement Information Model, Page 3. Description: Add the following documentation for the 'subjectType' attribute of the 'StatementSubject' class: A discriminant that determines the statement subject type. PSM's that support string typing systems may implement this through the built-in-type system rather than providing a specific element.
Actions taken:
May 4, 2012: received issue
July 24, 2013: closed issue

Issue 17351: Introduction section about conventions and notation needs to be in all modules (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: PIM: Update PIM text PSM: N/A
Revised Text: PIM: Change Location: All modules. Description: Add the following introduction section to all modules: Conventions The CTS2 specification was developed using a combination of UML and Z notation. The classes, attributes, method signatures and relationships were modeled using UML class diagrams, while the invariants, preconditions and post-conditions are written in Z. The specification can be published using UML notation with the invariants expressed informally or in Z notation, where the model can be formally validated using the FUZZ type checker. This, along with additional issues that may well reflect the authors� lack of understanding of some of the subtleties of UML modeling have led to a number of conventions. Notation Model elements are referenced using Typewriter font. Implementation profiles are referenced using BOLD Identifiers � Class names are capitalized camel case (CodeSystemCatalog, String) � Attribute and role names are lower camel case (version, sourceAndRole) � Enumeration values are all capital letters with undescores (� �) introduced as needed for clarity. (EMPTY, STOP ON ERROR) � Method names are lowerCamelCase Stereotypes The following stereotypes are used throughout the model: � dataType - UML dataType semantics � enumeration - UML enumeration semantics � interface - UML interface semantics � mixin - a class that provides a certain functionality to be inherited by a subclass, while not meant for instantiation � opt - an optional parameter in a method call. This stereotype should always be accompanied by a 0..1 cardinality and is provided to make optionality visible in the modeling tool � optparam - an optional attribute in a class instance. This indicates that an implementation must be able to distinguish three alternatives: (1) add or change the attribute to whatever is in the class, (2) remove the attribute if its minimum cardinality is zero and (3) leave the attribute unchanged. CHAPTER 1. INTRODUCTION 3 � delta - a method call that changes the state of the service. Note that the semantics of this stereotype is the inverse of the is query model attribute. � exception - an exception � exceptionSet - a set of exceptions, the members of which are represented by aggregation Read Only Attributes The CTS2 PIM is based on a RESTful architectural style. Resources can be created, updated, read and/or deleted, and every resource has one or more immutable characteristics - characteristics that, if changed, would change the identity of the resource itself. In the information model we distinguish these characteristics from those that can be modified by declaring the identifying characteristics as ReadOnly. The computational model utilizes a pattern based on this information where the create operation(s) supply the identifying characteristics plus any of the non-optional mutable characteristics. The update operations then supply a unique identifier and a set of one or more mutable characteristics to be changed.
Actions taken:
May 4, 2012: received issue
July 24, 2013: closed issue

Issue 17352: EntityDescriptionQueryService knownCodeSystem type is incorrect (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: 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"/>
Revised Text: PIM: Change Location: Diagram (Figure 3.2: Entity Description Query Service) PSM: Change Location: CoreService.xsd <xs:element name="EntityDescriptionReadService" type="EntityDescriptionReadService"/> <xs:complexType name="EntityDescriptionReadService"> <xs:complexContent> <xs:extension base="coreservice:BaseReadService"> <xs:sequence> ---Original---> <xs:element name="knownCodeSystem" type="core:CodeSystemVersionReference" minOccurs="0" maxOccurs="unbounded"/> ---Updated---> <xs:element name="knownCodeSystem" type="core:CodeSystemReference" 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"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:element name="EntityDescriptionQueryService" type="EntityDescriptionQueryService"/> <xs:complexType name="EntityDescriptionQueryService"> <xs:complexContent> <xs:extension base="coreservice:BaseQueryService"> <xs:sequence> ---Original---> <xs:element name="knownCodeSystem" type="core:CodeSystemVersionReference" minOccurs="0" maxOccurs="unbounded"/> ---Updated---> <xs:element name="knownCodeSystem" type="core:CodeSystemReference" 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"/> </xs:sequence> <xs:attribute name="entities" type="core:EntityDirectoryURI" use="required"/> </xs:extension> </xs:complexContent> </xs:complexType>
Actions taken:
May 4, 2012: received issue
July 24, 2013: closed issue

Issue 17353: Exception listed twice in EntityDescriptionQueryService (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

restrictToCodeSystem lists InvalidDirectoryType twice in the exception list.         Logged:  https://github.com/cts2/cts2-specification/issues/95

Resolution: PIM: Update PIM text PSM: N/A
Revised Text: PIM: Change Location: Entity Description, Page 24. Remove one of the duplicate 'InvalidDirectoryType' exceptions from the 'InvalidDirectoryType' method. PIM: N/A
Actions taken:
May 4, 2012: received issue
July 24, 2013: closed issue

Issue 17434: CTS2: Delta stereotype is opposite of isQuery (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: PIM: Update PIM text PSM: N/A
Revised Text: Added "isQuery='true'" to all non-delta operations, which changes all interface diagrams containing methods to include "{query}" after the method description. Added the line "This operation may alter the state of the service." immediately after the method description for all delta methods to help people remember what "delta" means. Added "This operation may alter the state of the service." in the following locations: CodeSystems.pdf 3.4.1 3.4.1.2 5.4.1.1 5.4.1.2 ConceptDomain.pdf 3.4.1.1 3.4.1.2 Core.pdf 3.3.4.2 3.3.4.5 3.3.4.6 3.3.4.7 3.3.4.8 3.3.4.9 3.4.2.2 3.2.4.10 3.4.2.15 3.4.3.5 Entity.pdf 3.4.1.1 3.4.1.2 3.4.1.3 3.4.1.4 3.4.1.5 3.4.1.6 3.4.1.7 3.4.1.8 3.4.1.9 3.4.1.10 5.1.4.2 5.1.4.3 5.1.4.4 Map.pdf 3.4.1.1 3.4.1.2 5.4.2.2 5.4.2.3 6.4.1.1 6.4.1.2 6.4.1.3 6.4.1.4 6.4.1.5 6.4.1.6 6.4.1.7 ValueSet.pdf 3.4.2.1 3.4.2.2 5.4.1.1 5.4.1.2 5.4.1.3 5.4.1.4 5.4.1.5 5.4.1.6 5.4.1.7 5.4.1.8 5.4.1.9 5.4.1.10 5.4.1.11 5.4.1.12 5.4.1.13 7.1.1.1 7.1.1.2 7.1.1.3 7.1.1.4 7.2.1.1 7.2.1.2 7.3.1.1 7.3.1.2 7.3.1.3 7.3.1.4 7.3.1.5 7.3.1.6
Actions taken:
June 20, 2012: received issue
July 24, 2013: closed issue

Issue 17435: String is a UML dataType and cannot be included as part of the model data types (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: PIM: Update PIM text PSM: N/A
Revised Text: PIM: Remove the String datatype out of the core module. Document: Core.pdf Page 4, remove text "String - a non-empty sequence of characters. As terminological resources are often multilingual, it is expected that most CTS2 Platform Specific Models (PSMs) will require that the String implementation support international character sets." Page 3, Figure 2.1, remove String.
Actions taken:
June 20, 2012: received issue
July 24, 2013: closed issue

Issue 17436: Missing ValidationResponse class (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

ValidationResponse was missing in final model.         Logged:  https://github.com/cts2/cts2-specification/issues/115

Resolution: PIM: Update PIM text PSM: N/A
Revised Text: PIM: Update to the MiscInterface package in the Computational Model to include ValidationResponse. Core.pdf Added "Class ValidationResponse" after section 3.1.1.6. 3.1.1.7 Class ValidationResponse The result of a change set validation call. Attributes � message - The output of the validation process � validationStatus - an indicator whether the validation succeeded
Actions taken:
June 20, 2012: received issue
July 24, 2013: closed issue

Issue 17437: Boolean is a UML data type and shouldn't be part of the model (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: PIM: Update PIM text PSM: N/A
Revised Text: PIM: Removed "Boolean" as a data type from the InterfaceTypes diagram. Core.pdf Remove Section 3.1.1.9
Actions taken:
June 20, 2012: received issue
July 24, 2013: closed issue

Issue 17438: MatchValueFormatException missing from documentation (cts2-ftf)

Click here for this issue's archive.
Source: Mayo Clinic (Mr. Craig Stancl, stancl.craig(at)mayo.edu)
Nature: Uncategorized Issue
Severity:
Summary:

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

Resolution: PIM: Update PIM text PSM: Change the MatchValueFormatException type to 'exception.'
Revised Text: PIM: Added "MatchValueFormatException - The match value does not meet the format or syntax required or the supplied match algorithm." to Exceptions in each of these sections: CodeSystem.pdf 3.1.1.2 3.2.1.1 3.2.1.2 5.1.1.2 5.1.1.4 5.2.1.1 5.2.1.3 Concept.pdf 3.1.1.2 3.1.1.4 3.2.1.1 3.2.1.2 5.1.1.2 5.1.1.4 5.2.1.4 5.2.1.5 Core.pdf 3.3.2.2 3.3.3.3 3.3.4.3 3.3.4.4 Entity.pdf 3.1.1.4 3.1.1.5 3.1.1.6 3.2.1.4 3.2.1.5 3.2.1.6 5.1.1.2 5.1.1.4 5.1.2.2 5.1.2.11 5.1.2.12 5.1.2.13 5.1.2.14 5.1.2.15 5.1.2.16 5.2.1.1 Map.pdf 3.1.1.2 3.2.1.3 3.2.1.4 5.1.1.2 5.1.1.4 5.2.1.4 5.2.1.5 5.2.1.7 Statement.pdf 3.1.1.2 3.2.1.7 3.2.1.8 Value.pdf 3.1.1.2 3.2.1.5 3.2.1.6 5.1.1.2 5.4.1.7 5.4.1.8 6.1.1.1 6.1.1.2 6.1.1.4 7.1.1.1 7.1.1.2 7.1.1.4 PSM: <xs:element name="MatchValueFormatException"> <xs:complexType> <xs:annotation> <xs:documentation>The match value does not meet the format or syntax required or the supplied match algorithm. </xs:documentation> </xs:annotation> <xs:complexContent> <xs:extension base="CTS2Exception"> <xs:sequence /> </xs:extension> </xs:complexContent> </xs:complexType> </xs:element>
Actions taken:
June 20, 2012: received issue
July 24, 2013: closed issue