Common Terminology Services 2 Avatar
  1. OMG Specification

Common Terminology Services 2 — Closed Issues

  • Acronym: CTS2
  • Issues Count: 82
  • Description: Issues resolved by a task force and approved by Board
Closed All
Issues resolved by a task force and approved by Board

Issues Summary

Key Issue Reported Fixed Disposition Status
CTS2F2-82 CTS2 XML file appears to contain EA proprietary elements CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-81 MatchValueFormatException missing from documentation CTS2 1.0b2 CTS2 1.0 Resolved closed
CTS2F2-80 Boolean is a UML data type and shouldn't be part of the model CTS2 1.0b2 CTS2 1.0 Resolved closed
CTS2F2-79 Missing ValidationResponse class CTS2 1.0b2 CTS2 1.0 Resolved closed
CTS2F2-78 String is a UML dataType and cannot be included as part of the model data types CTS2 1.0b2 CTS2 1.0 Resolved closed
CTS2F2-77 CTS2: Delta stereotype is opposite of isQuery CTS2 1.0b2 CTS2 1.0 Resolved closed
CTS2F2-76 Exception listed twice in EntityDescriptionQueryService CTS2 1.0b2 CTS2 1.0 Resolved closed
CTS2F2-75 EntityDescriptionQueryService knownCodeSystem type is incorrect CTS2 1.0b2 CTS2 1.0 Resolved closed
CTS2F2-74 Introduction section about conventions and notation needs to be in all modules CTS2 1.0b2 CTS2 1.0 Resolved closed
CTS2F2-73 Missing documentation on StatementSubject CTS2 1.0b2 CTS2 1.0 Resolved closed
CTS2F2-72 CTS2: Change cardinality of defaultLanguage from [0..1] to [0..*] CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-71 CTS2: section 1.1.2.1 Class CodeSystemCatalogEntryDirectory typo CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-70 CTS2: Concept Domain Catalog Query Service missing description CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-69 CTS2: Service map catalog typo CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-68 CTS2: AssociationQueryServices WSDL corrections CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-67 CTS2: ConceptDomainBindingReadService QueryControl parameters CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-66 CTS2: AssociationQueryService 'getAllSourceAndTargetEntities' wrong input parameter CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-65 Create/Update in WADL use the wrong HTTP methods CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-64 CTS2: StructuralProfile - Statement and/or MapEntry CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-63 CTS2: Message Header Documentation Missing CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-62 CTS2: Inconsistent element/complexType declarations CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-61 CTS2: currentVersion not typed in MapCatalogEntry CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-60 CTS2: ScopedEntityName.name type is too strong CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-59 EntityDescriptionMaintenanceServices WSDL changes CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-58 EntityDescriptionQueryServices WSDL corrections CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-57 EntityDescriptionTransformService WSDL corrections CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-56 ConceptDomainCatalogHistoryServices WSDL corrections CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-55 ConceptDomainCatalogQueryServices WSDL corrections CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-54 ConceptDomainBindingMaintenanceServices WSDL corrections CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-53 ConceptDomainBindingQueryServices WSDL corrections CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-52 BaseImport/ExportServices WSDL correction CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-51 AssociationTransformServices WSDL corrections CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-50 AssociationMaintenanceServices WSDL corrections CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-49 AssociationHistoryServices WSDL corrections CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-48 AssociationReadServices WSDL corrections CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-47 AdvancedAssociationQueryServices WSDL corrections CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-46 EntityDescriptionReadServices WSDL corrections CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-45 CodeSystemVersionCatalogHistoryServices WSDL corrections CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-44 CodeSystemVersionCatalogMaintenanceServices WSDL corrections CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-43 CodeSystemVersionCatalogQueryServices WSDL corrections CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-42 CodeSystemVersionCatalogReadServices WSDL corrections CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-41 CodeSystemCatalogQueryServices WSDL corrections CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-40 CodeSystemCatalogHistoryServices WSDL corrections CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-39 CodeSystemCatalogMaintenanceServices WSDL corrections CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-38 Refactor inline XSD types from WSDLs (SOAP PSM) CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-37 ResolvedValueSetReadService and QueryService omitted from spec CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-36 ResolvedValueSetDirectory misnamed and mistyped CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-35 AdvancedAssociationQuerySerivce not in WADL (REST PSM) CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-34 Association Information Model derivation and derivationReasoningAlgorithm CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-33 Typo on page 11 of statement information model CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-32 Typo on page 3 of Statement Information model CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-31 Statement needs an identifier CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-30 ConceptDomainbinding needs an identifier CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-29 BaseQueryService filter property needs to be individualized CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-28 Changeable changeDescription cardinality constraint CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-27 EntityReferences - URIAndEntityNameList CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-26 Remove CONCEPT_DOMAIN_BINDING from ReferenceType CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-25 XML Schema for BaseService has wrong type for supported Profile CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-24 Documentation issue on ProfileElement CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-23 ImplementationProfiles.ProfileElement not RESTful CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-22 NamedEntityDescription and AnonymousEntityDescription incorrectly defined in schema CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-21 SpecificEntityList incorrectly supertyped CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-20 Designation and Note have inconsistent pattern in schema CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-19 UpdateEntityDescription is missing elements and does not support "optparam" semantics CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-18 EntityDescriptionQueryService lacking supportedVersionTag CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-17 EntityDescriptionReadService lacking local variables CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-16 ChangeSet element doesn't have a MSG header CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-15 AssociationGraph p45 typo CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-14 Entity description services p20 typo CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-13 CodesystemCatalogEntry.usedOntologyEngineeringTool CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-12 UpdateCodesystemCatalogEntry.usedOntologyEngineeringTool optionality CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-11 Core spec typos CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-10 BaseMaintenanceService.updateChangeableMetadata parameters CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-9 Changeable/ChangeDescription typo CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-8 ChangeDescription stereotypes CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-7 AnonymousStatement typo CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-6 AnonymousStatement target cardinality CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-5 CTS 2: FilterComponent is a PropertyReference and contains a MatchAlgorithm reference CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-4 CTS 2: SortCriteria contains PropertyReference CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-3 CTS 2: Change 'applicableContext' cardinality in ConceptDomainBinding (XSD) to 0..1 CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-2 CTS2: Move 'bindingQualifier' in ConceptDomainBinding (XSD) to an Element CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-1 CTS 2: Change 'boundValueSet' cardinality in ConceptDomainBindingDirectoryEntry (XSD) to 1..1 CTS2 1.0b1 CTS2 1.0 Resolved closed

Issues Descriptions

CTS2 XML file appears to contain EA proprietary elements

  • Key: CTS2F2-82
  • Legacy Issue Number: 16347
  • Status: closed  
  • Source: Model Driven Solutions ( Steve Cook)
  • 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.

  • Reported: CTS2 1.0b1 — Thu, 23 Jun 2011 04:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

    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

  • Updated: Fri, 6 Mar 2015 20:58 GMT

MatchValueFormatException missing from documentation

  • Key: CTS2F2-81
  • Legacy Issue Number: 17438
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b2 — Wed, 20 Jun 2012 04:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

    PIM: Update PIM text

    PSM: Change the MatchValueFormatException type to 'exception.'

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Boolean is a UML data type and shouldn't be part of the model

  • Key: CTS2F2-80
  • Legacy Issue Number: 17437
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b2 — Wed, 20 Jun 2012 04:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

    PIM: Update PIM text
    PSM: N/A

  • Updated: Fri, 6 Mar 2015 20:58 GMT


String is a UML dataType and cannot be included as part of the model data types


CTS2: Delta stereotype is opposite of isQuery

  • Key: CTS2F2-77
  • Legacy Issue Number: 17434
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b2 — Wed, 20 Jun 2012 04:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

    PIM: Update PIM text
    PSM: N/A

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Exception listed twice in EntityDescriptionQueryService


EntityDescriptionQueryService knownCodeSystem type is incorrect

  • Key: CTS2F2-75
  • Legacy Issue Number: 17352
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b2 — Fri, 4 May 2012 04:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

    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"/>

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Introduction section about conventions and notation needs to be in all modules

  • Key: CTS2F2-74
  • Legacy Issue Number: 17351
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b2 — Fri, 4 May 2012 04:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

    PIM: Update PIM text
    PSM: N/A

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Missing documentation on StatementSubject


CTS2: Change cardinality of defaultLanguage from [0..1] to [0..*]

  • Key: CTS2F2-72
  • Legacy Issue Number: 17332
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Mon, 23 Apr 2012 04:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

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

  • Updated: Fri, 6 Mar 2015 20:58 GMT

CTS2: section 1.1.2.1 Class CodeSystemCatalogEntryDirectory typo

  • Key: CTS2F2-71
  • Legacy Issue Number: 17331
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Mon, 23 Apr 2012 04:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

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

  • Updated: Fri, 6 Mar 2015 20:58 GMT

CTS2: Concept Domain Catalog Query Service missing description

  • Key: CTS2F2-70
  • Legacy Issue Number: 17330
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Mon, 23 Apr 2012 04:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

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

  • Updated: Fri, 6 Mar 2015 20:58 GMT

CTS2: Service map catalog typo

  • Key: CTS2F2-69
  • Legacy Issue Number: 17327
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Fri, 20 Apr 2012 04:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

    PIM: Update PIM text
    PSM: N/A

  • Updated: Fri, 6 Mar 2015 20:58 GMT

CTS2: AssociationQueryServices WSDL corrections

  • Key: CTS2F2-68
  • Legacy Issue Number: 17326
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Fri, 20 Apr 2012 04:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

    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

  • Updated: Fri, 6 Mar 2015 20:58 GMT

CTS2: ConceptDomainBindingReadService QueryControl parameters

  • Key: CTS2F2-67
  • Legacy Issue Number: 17325
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • Summary:

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

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

  • Reported: CTS2 1.0b1 — Fri, 20 Apr 2012 04:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

    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" />

  • Updated: Fri, 6 Mar 2015 20:58 GMT

CTS2: AssociationQueryService 'getAllSourceAndTargetEntities' wrong input parameter

  • Key: CTS2F2-66
  • Legacy Issue Number: 17324
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Fri, 20 Apr 2012 04:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

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

    PSM: N/A

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Create/Update in WADL use the wrong HTTP methods

  • Key: CTS2F2-65
  • Legacy Issue Number: 17323
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Fri, 20 Apr 2012 04:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

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

  • Updated: Fri, 6 Mar 2015 20:58 GMT

CTS2: StructuralProfile - Statement and/or MapEntry

  • Key: CTS2F2-64
  • Legacy Issue Number: 17322
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Fri, 20 Apr 2012 04:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

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

  • Updated: Fri, 6 Mar 2015 20:58 GMT

CTS2: Message Header Documentation Missing

  • Key: CTS2F2-63
  • Legacy Issue Number: 17321
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Fri, 20 Apr 2012 04:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

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

  • Updated: Fri, 6 Mar 2015 20:58 GMT

CTS2: Inconsistent element/complexType declarations

  • Key: CTS2F2-62
  • Legacy Issue Number: 17320
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Fri, 20 Apr 2012 04:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

    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>

  • Updated: Fri, 6 Mar 2015 20:58 GMT

CTS2: currentVersion not typed in MapCatalogEntry

  • Key: CTS2F2-61
  • Legacy Issue Number: 17319
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • Summary:

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

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

  • Reported: CTS2 1.0b1 — Fri, 20 Apr 2012 04:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

    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">

  • Updated: Fri, 6 Mar 2015 20:58 GMT

CTS2: ScopedEntityName.name type is too strong

  • Key: CTS2F2-60
  • Legacy Issue Number: 17317
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Fri, 20 Apr 2012 04:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

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

  • Updated: Fri, 6 Mar 2015 20:58 GMT

EntityDescriptionMaintenanceServices WSDL changes

  • Key: CTS2F2-59
  • Legacy Issue Number: 17194
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Fri, 24 Feb 2012 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

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

  • Updated: Fri, 6 Mar 2015 20:58 GMT

EntityDescriptionQueryServices WSDL corrections

  • Key: CTS2F2-58
  • Legacy Issue Number: 17193
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Fri, 24 Feb 2012 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

    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'

  • Updated: Fri, 6 Mar 2015 20:58 GMT

EntityDescriptionTransformService WSDL corrections

  • Key: CTS2F2-57
  • Legacy Issue Number: 17192
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • Summary:

    Renamed method 'getKnownCodeSystems' to 'getKnownCodeSystemVersion'

    Removed method 'getSupportedVersionTags'

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

  • Reported: CTS2 1.0b1 — Fri, 24 Feb 2012 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

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

  • Updated: Fri, 6 Mar 2015 20:58 GMT

ConceptDomainCatalogHistoryServices WSDL corrections

  • Key: CTS2F2-56
  • Legacy Issue Number: 17191
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Fri, 24 Feb 2012 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

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

  • Updated: Fri, 6 Mar 2015 20:58 GMT

ConceptDomainCatalogQueryServices WSDL corrections


ConceptDomainBindingMaintenanceServices WSDL corrections

  • Key: CTS2F2-54
  • Legacy Issue Number: 17189
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Fri, 24 Feb 2012 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

    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'

  • Updated: Fri, 6 Mar 2015 20:58 GMT

ConceptDomainBindingQueryServices WSDL corrections


BaseImport/ExportServices WSDL correction

  • Key: CTS2F2-52
  • Legacy Issue Number: 17187
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • Summary:

    Changed all URI param types from String to LocalURI or DocumentURI

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

  • Reported: CTS2 1.0b1 — Fri, 24 Feb 2012 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

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

  • Updated: Fri, 6 Mar 2015 20:58 GMT

AssociationTransformServices WSDL corrections

  • Key: CTS2F2-51
  • Legacy Issue Number: 17186
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Fri, 24 Feb 2012 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

    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

  • Updated: Fri, 6 Mar 2015 20:58 GMT

AssociationMaintenanceServices WSDL corrections

  • Key: CTS2F2-50
  • Legacy Issue Number: 17185
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Fri, 24 Feb 2012 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

    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

  • Updated: Fri, 6 Mar 2015 20:58 GMT

AssociationHistoryServices WSDL corrections

  • Key: CTS2F2-49
  • Legacy Issue Number: 17184
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Fri, 24 Feb 2012 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

    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'

  • Updated: Fri, 6 Mar 2015 20:58 GMT

AssociationReadServices WSDL corrections

  • Key: CTS2F2-48
  • Legacy Issue Number: 17183
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Fri, 24 Feb 2012 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

    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

  • Updated: Fri, 6 Mar 2015 20:58 GMT

AdvancedAssociationQueryServices WSDL corrections

  • Key: CTS2F2-47
  • Legacy Issue Number: 17182
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Fri, 24 Feb 2012 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

    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

  • Updated: Fri, 6 Mar 2015 20:58 GMT

EntityDescriptionReadServices WSDL corrections

  • Key: CTS2F2-46
  • Legacy Issue Number: 17180
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Fri, 24 Feb 2012 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

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

  • Updated: Fri, 6 Mar 2015 20:58 GMT

CodeSystemVersionCatalogHistoryServices WSDL corrections

  • Key: CTS2F2-45
  • Legacy Issue Number: 17179
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Fri, 24 Feb 2012 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

    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'

  • Updated: Fri, 6 Mar 2015 20:58 GMT

CodeSystemVersionCatalogMaintenanceServices WSDL corrections

  • Key: CTS2F2-44
  • Legacy Issue Number: 17178
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Fri, 24 Feb 2012 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

    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'

  • Updated: Fri, 6 Mar 2015 20:58 GMT

CodeSystemVersionCatalogQueryServices WSDL corrections

  • Key: CTS2F2-43
  • Legacy Issue Number: 17177
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Fri, 24 Feb 2012 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

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

  • Updated: Fri, 6 Mar 2015 20:58 GMT

CodeSystemVersionCatalogReadServices WSDL corrections

  • Key: CTS2F2-42
  • Legacy Issue Number: 17176
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • Summary:

    Renamed method 'getCodeSystemVersionByExternalId' to 'getCodeSystemByVersionId'.

    Renamed method 'existsExternalId' to 'existsVersionId'.

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

  • Reported: CTS2 1.0b1 — Fri, 24 Feb 2012 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

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

  • Updated: Fri, 6 Mar 2015 20:58 GMT

CodeSystemCatalogQueryServices WSDL corrections


CodeSystemCatalogHistoryServices WSDL corrections

  • Key: CTS2F2-40
  • Legacy Issue Number: 17174
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Tue, 1 May 2012 04:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

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

  • Updated: Fri, 6 Mar 2015 20:58 GMT

CodeSystemCatalogMaintenanceServices WSDL corrections

  • Key: CTS2F2-39
  • Legacy Issue Number: 17173
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Fri, 24 Feb 2012 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

    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'

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Refactor inline XSD types from WSDLs (SOAP PSM)

  • Key: CTS2F2-38
  • Legacy Issue Number: 17119
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Thu, 9 Feb 2012 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

    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.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

ResolvedValueSetReadService and QueryService omitted from spec

  • Key: CTS2F2-37
  • Legacy Issue Number: 17118
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Thu, 9 Feb 2012 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

    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.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

ResolvedValueSetDirectory misnamed and mistyped

  • Key: CTS2F2-36
  • Legacy Issue Number: 17117
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Thu, 9 Feb 2012 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

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

  • Updated: Fri, 6 Mar 2015 20:58 GMT

AdvancedAssociationQuerySerivce not in WADL (REST PSM)

  • Key: CTS2F2-35
  • Legacy Issue Number: 17116
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Thu, 9 Feb 2012 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

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

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Association Information Model derivation and derivationReasoningAlgorithm

  • Key: CTS2F2-34
  • Legacy Issue Number: 17115
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Thu, 9 Feb 2012 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

    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>

  • Updated: Fri, 6 Mar 2015 20:58 GMT



Statement needs an identifier

  • Key: CTS2F2-31
  • Legacy Issue Number: 17112
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Thu, 9 Feb 2012 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

    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>

  • Updated: Fri, 6 Mar 2015 20:58 GMT

ConceptDomainbinding needs an identifier

  • Key: CTS2F2-30
  • Legacy Issue Number: 17111
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Thu, 9 Feb 2012 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

    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>

  • Updated: Fri, 6 Mar 2015 20:58 GMT

BaseQueryService filter property needs to be individualized

  • Key: CTS2F2-29
  • Legacy Issue Number: 17110
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Thu, 9 Feb 2012 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

    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>

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Changeable changeDescription cardinality constraint

  • Key: CTS2F2-28
  • Legacy Issue Number: 17109
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Thu, 9 Feb 2012 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

    PIM: Update PIM text
    PSM: N/A

  • Updated: Fri, 6 Mar 2015 20:58 GMT

EntityReferences - URIAndEntityNameList

  • Key: CTS2F2-27
  • Legacy Issue Number: 17108
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Thu, 9 Feb 2012 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

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

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Remove CONCEPT_DOMAIN_BINDING from ReferenceType

  • Key: CTS2F2-26
  • Legacy Issue Number: 17107
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Thu, 9 Feb 2012 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

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

    PSM:
    N/A

  • Updated: Fri, 6 Mar 2015 20:58 GMT

XML Schema for BaseService has wrong type for supported Profile

  • Key: CTS2F2-25
  • Legacy Issue Number: 17089
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • Summary:

    The type of SupportedProfile should be ProfileElement, not StructuralProfile

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

  • Reported: CTS2 1.0b1 — Mon, 30 Jan 2012 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

    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">

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Documentation issue on ProfileElement

  • Key: CTS2F2-24
  • Legacy Issue Number: 17088
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Mon, 30 Jan 2012 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

    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

  • Updated: Fri, 6 Mar 2015 20:58 GMT

ImplementationProfiles.ProfileElement not RESTful

  • Key: CTS2F2-23
  • Legacy Issue Number: 17087
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Mon, 30 Jan 2012 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

    PIM:
    N/A

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

  • Updated: Fri, 6 Mar 2015 20:58 GMT

NamedEntityDescription and AnonymousEntityDescription incorrectly defined in schema

  • Key: CTS2F2-22
  • Legacy Issue Number: 17086
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Mon, 30 Jan 2012 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

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

  • Updated: Fri, 6 Mar 2015 20:58 GMT

SpecificEntityList incorrectly supertyped

  • Key: CTS2F2-21
  • Legacy Issue Number: 17085
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Mon, 30 Jan 2012 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

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

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Designation and Note have inconsistent pattern in schema

  • Key: CTS2F2-20
  • Legacy Issue Number: 17084
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Mon, 30 Jan 2012 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

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

  • Updated: Fri, 6 Mar 2015 20:58 GMT

UpdateEntityDescription is missing elements and does not support "optparam" semantics

  • Key: CTS2F2-19
  • Legacy Issue Number: 17083
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Mon, 30 Jan 2012 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

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

  • Updated: Fri, 6 Mar 2015 20:58 GMT

EntityDescriptionQueryService lacking supportedVersionTag

  • Key: CTS2F2-18
  • Legacy Issue Number: 17082
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • Summary:

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

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

  • Reported: CTS2 1.0b1 — Mon, 30 Jan 2012 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

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

  • Updated: Fri, 6 Mar 2015 20:58 GMT

EntityDescriptionReadService lacking local variables

  • Key: CTS2F2-17
  • Legacy Issue Number: 17081
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • Summary:

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

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

  • Reported: CTS2 1.0b1 — Mon, 30 Jan 2012 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

    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"/>

  • Updated: Fri, 6 Mar 2015 20:58 GMT

ChangeSet element doesn't have a MSG header




CodesystemCatalogEntry.usedOntologyEngineeringTool

  • Key: CTS2F2-13
  • Legacy Issue Number: 17077
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • Summary:

    Type should be OntologyEngineeringToolReference...

    Check omv for "used" vs. "uses"

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

  • Reported: CTS2 1.0b1 — Mon, 30 Jan 2012 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

    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>

  • Updated: Fri, 6 Mar 2015 20:58 GMT

UpdateCodesystemCatalogEntry.usedOntologyEngineeringTool optionality

  • Key: CTS2F2-12
  • Legacy Issue Number: 17076
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • Reported: CTS2 1.0b1 — Mon, 30 Jan 2012 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

    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>

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Core spec typos


BaseMaintenanceService.updateChangeableMetadata parameters

  • Key: CTS2F2-10
  • Legacy Issue Number: 17074
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Mon, 30 Jan 2012 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

    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>

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Changeable/ChangeDescription typo

  • Key: CTS2F2-9
  • Legacy Issue Number: 17073
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • Summary:

    Changeable/ChangeDescription typo

  • Reported: CTS2 1.0b1 — Mon, 30 Jan 2012 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

    PIM: Update PIM text
    PSM: N/A

  • Updated: Fri, 6 Mar 2015 20:58 GMT

ChangeDescription stereotypes

  • Key: CTS2F2-8
  • Legacy Issue Number: 17072
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • Summary:

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

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

  • Reported: CTS2 1.0b1 — Mon, 30 Jan 2012 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

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

  • Updated: Fri, 6 Mar 2015 20:58 GMT

AnonymousStatement typo

  • Key: CTS2F2-7
  • Legacy Issue Number: 17071
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • Summary:

    StatmentQualifier -> statementQualifier

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

  • Reported: CTS2 1.0b1 — Mon, 30 Jan 2012 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

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

    PSM: N/A

  • Updated: Fri, 6 Mar 2015 20:58 GMT

AnonymousStatement target cardinality

  • Key: CTS2F2-6
  • Legacy Issue Number: 17070
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • Summary:

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

  • Reported: CTS2 1.0b1 — Mon, 30 Jan 2012 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

    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">

  • Updated: Fri, 6 Mar 2015 20:58 GMT

CTS 2: FilterComponent is a PropertyReference and contains a MatchAlgorithm reference

  • Key: CTS2F2-5
  • Legacy Issue Number: 16941
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Fri, 30 Dec 2011 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

    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.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

CTS 2: SortCriteria contains PropertyReference

  • Key: CTS2F2-4
  • Legacy Issue Number: 16940
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Fri, 30 Dec 2011 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

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

  • Updated: Fri, 6 Mar 2015 20:58 GMT

CTS 2: Change 'applicableContext' cardinality in ConceptDomainBinding (XSD) to 0..1

  • Key: CTS2F2-3
  • Legacy Issue Number: 16939
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Fri, 30 Dec 2011 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

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

  • Updated: Fri, 6 Mar 2015 20:58 GMT

CTS2: Move 'bindingQualifier' in ConceptDomainBinding (XSD) to an Element

  • Key: CTS2F2-2
  • Legacy Issue Number: 16938
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • 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

  • Reported: CTS2 1.0b1 — Fri, 30 Dec 2011 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

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

  • Updated: Fri, 6 Mar 2015 20:58 GMT

CTS 2: Change 'boundValueSet' cardinality in ConceptDomainBindingDirectoryEntry (XSD) to 1..1

  • Key: CTS2F2-1
  • Legacy Issue Number: 16937
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • Summary:

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

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

  • Reported: CTS2 1.0b1 — Fri, 30 Dec 2011 05:00 GMT
  • Disposition: Resolved — CTS2 1.0
  • Disposition Summary:

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

  • Updated: Fri, 6 Mar 2015 20:58 GMT