Common Terminology Services 2 Avatar
  1. OMG Specification

Common Terminology Services 2 — Closed Issues

  • Acronym: CTS2
  • Issues Count: 137
  • 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
CTS212-26 OMG Architecture Board review issues, Nov 2013 CTS2 1.1 CTS2 1.2 Resolved closed
CTS212-25 The reference in B4 should instead be added to section 3 (assuming it is normative) CTS2 1.1 CTS2 1.2 Resolved closed
CTS212-24 Rule 10 example uses xsi2:nill – I think this should be xsi2:nil (only one L) CTS2 1.1 CTS2 1.2 Resolved closed
CTS212-22 Rule 10 does not cover the case where the removal of namespaces causes names to be indistinguishable CTS2 1.1 CTS2 1.2 Resolved closed
CTS212-21 The following in rule 10 is very unclear “In certain situations, this may cause issues for opaque data” CTS2 1.1 CTS2 1.2 Resolved closed
CTS212-20 issue with rule 10 CTS2 1.1 CTS2 1.2 Resolved closed
CTS212-23 conflict between rules 10 and 13 CTS2 1.1 CTS2 1.2 Resolved closed
CTS212-19 The documents referenced in Rule 12 should appear in the normative references section CTS2 1.1 CTS2 1.2 Resolved closed
CTS212-18 B2 rule 7: I’m not aware of such a thing as an “XML array” CTS2 1.1 CTS2 1.2 Resolved closed
CTS212-17 Section 7 has the wrong document number for CTS2 – it should be formal/13-12-01 CTS2 1.1 CTS2 1.2 Resolved closed
CTS212-16 The Normative References in section 3 must be added to the Normative References section in the main CTS2 spec CTS2 1.1 CTS2 1.2 Resolved closed
CTS212-15 the “Plan” in 6.2 with the RTF working in parallel is not being followed at all CTS2 1.1 CTS2 1.2 Resolved closed
CTS212-14 No Beta document CTS2 1.1 CTS2 1.2 Resolved closed
CTS212-13 Section 1: should rephrase “this submission” – it’s now a specification CTS2 1.1 CTS2 1.2 Resolved closed
CTS2F2-82 CTS2 XML file appears to contain EA proprietary elements CTS2 1.0b1 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-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-77 CTS2: Delta stereotype is opposite of isQuery CTS2 1.0b2 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-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
CTS211-26 CTS2: Parents URI needed in EntityDescription CTS2 1.0 CTS2 1.1 Resolved closed
CTS211-25 CTS2: CodeSystemCatalogQueryService (resolve and resolveAsList) parameter 'directory' type incorrect CTS2 1.0 CTS2 1.1 Resolved closed
CTS211-31 CTS2: Complete binding operation missing from specification CTS2 1.0 CTS2 1.1 Resolved closed
CTS211-30 CTS2: URIAndEntityName references should all be changed to EntitySynopsis, allowing an optional description CTS2 1.0 CTS2 1.1 Resolved closed
CTS211-29 CTS2: IteratableResolvedValueSet and ResolvedValueSet have inconsistent element names CTS2 1.0 CTS2 1.1 Resolved closed
CTS211-28 CTS2: CTS2Exception doesn't match documentation CTS2 1.0 CTS2 1.1 Resolved closed
CTS211-27 Need an optional attribute to carry the OID in addition to the URI CTS2 1.0 CTS2 1.1 Resolved closed
CTS211-22 AssociationDirectory needs "associationID" CTS2 1.0 CTS2 1.1 Resolved closed
CTS211-21 CTS2: Make "associationID" optional CTS2 1.0 CTS2 1.1 Resolved closed
CTS211-32 CTS2: Filter PropertyReference documentation needs clarification CTS2 1.0 CTS2 1.1 Resolved closed
CTS211-20 CTS2: Include a depth indicator for AssociationGraph CTS2 1.0 CTS2 1.1 Resolved closed
CTS211-24 CTS2: ConceptDomainCatalogQueryService (resolve) parameter "directory" type incorrect CTS2 1.0 CTS2 1.1 Resolved closed
CTS211-23 CTS2: URIAndEntityName XSD representation does not match UML CTS2 1.0 CTS2 1.1 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-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-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-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-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-51 AssociationTransformServices WSDL corrections CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-55 ConceptDomainCatalogQueryServices WSDL corrections CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS211-1 CTS2: Possible issue with CTS2 URI CTS2 1.0b1 CTS2 1.1 Resolved closed
CTS211-5 CTS2: "documentURI" attribute description in ResourceVersionDescription is incorrect CTS2 1.0 CTS2 1.1 Resolved closed
CTS211-2 CTS2: "entityType" description text incorrect - needs to be updated CTS2 1.0 CTS2 1.1 Resolved closed
CTS211-4 CTS2: "SourceAndNotation" should be made optional in resource version CTS2 1.0 CTS2 1.1 Resolved closed
CTS211-3 CTS2: referencedEntity in Value Set Definitions should include an optional description CTS2 1.0 CTS2 1.1 Resolved closed
CTS211-6 CTS2: DocumentURI shouldn't be mandatory in ResourceVersionDescription CTS2 1.0 CTS2 1.1 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
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-5 CTS 2: FilterComponent is a PropertyReference and contains a MatchAlgorithm reference CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-6 AnonymousStatement target cardinality 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
CTS211-37 CTS2: Resource content filtering for Query CTS2 1.0 CTS2 1.1 Resolved closed
CTS211-36 CTS2: WADL Graph URLs need to change to better reflect AssociationDirectory as input CTS2 1.0 CTS2 1.1 Resolved closed
CTS211-34 CTS2: MapTargetList and MapTargetListList need a 'Message' wrapper for REST calls CTS2 1.0 CTS2 1.1 Resolved closed
CTS211-33 CTS2: Cardinality of includesResolvedValueSet wrong on ResolvedValueSetHeader CTS2 1.0 CTS2 1.1 Resolved closed
CTS211-41 CTS2: ValueSetDefinitionResolution 'resolve' method has incorrect return type CTS2 1.0 CTS2 1.1 Resolved closed
CTS211-39 CTS2: Association derivation should be optional and not have a default CTS2 1.0 CTS2 1.1 Resolved closed
CTS211-35 CTS2: MapEntry Read and Resolution need WADL 'byURI' REST signatures CTS2 1.0 CTS2 1.1 Resolved closed
CTS211-38 CTS2: AssociationDirectory needs the derivation CTS2 1.0 CTS2 1.1 Resolved closed
CTS211-40 Type of maxtoreturn is string in the WADL definitions. It should be NaturalNumber (or equiv) CTS2 1.0 CTS2 1.1 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-22 NamedEntityDescription and AnonymousEntityDescription incorrectly defined in schema 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-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-13 CodesystemCatalogEntry.usedOntologyEngineeringTool 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-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-17 EntityDescriptionReadService lacking local variables CTS2 1.0b1 CTS2 1.0 Resolved closed
CTS2F2-14 Entity description services p20 typo 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-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-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-25 XML Schema for BaseService has wrong type for supported Profile 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-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
CTS211-12 CTS2: Additional options needed for Entity Read Query CTS2 1.0 CTS2 1.1 Resolved closed
CTS211-11 CTS2: Format and language resolution precedence not described for REST CTS2 1.0 CTS2 1.1 Resolved closed
CTS211-8 CTS2: Include the signature for the CLONE operation in Change Set CTS2 1.0 CTS2 1.1 Resolved closed
CTS211-7 CTS2: Extensible Directories - Allow directories to be extended CTS2 1.0 CTS2 1.1 Resolved closed
CTS211-15 CTS2: Rest signatures missing for ValueSetDefinitionResolution "resolveAsCompleteSet" function CTS2 1.0 CTS2 1.1 Resolved closed
CTS211-14 CTS2: REST language signature "referencelanguage" needs to be more REST compliant CTS2 1.0 CTS2 1.1 Resolved closed
CTS211-19 CTS2: CodeSystemCatalogEntry xml schema missing "hasOntologyLanguage" and "includes" elements CTS2 1.0 CTS2 1.1 Resolved closed
CTS211-18 CTS2: Map Entry "MapFrom" and "MapTo" need optional description element CTS2 1.0 CTS2 1.1 Resolved closed
CTS211-9 CTS2: No ROA link to value set resolution of current value set CTS2 1.0 CTS2 1.1 Resolved closed
CTS211-17 CTS2: ValueSetDefinition REST signatures need to include shortcuts for tags CTS2 1.0 CTS2 1.1 Resolved closed
CTS211-16 CTS2: Documentation for value set resolution needs to be corrected. CTS2 1.0 CTS2 1.1 Resolved closed
CTS211-10 CTS2: "versiontag" has wrong type in MapVersion schema CTS2 1.0 CTS2 1.1 Resolved closed
CTS211-13 CTS2: Redirect behavior isn't clear for uri reads CTS2 1.0 CTS2 1.1 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-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-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-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-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-71 CTS2: section 1.1.2.1 Class CodeSystemCatalogEntryDirectory typo CTS2 1.0b1 CTS2 1.0 Resolved closed

Issues Descriptions

OMG Architecture Board review issues, Nov 2013

  • Key: CTS212-26
  • Legacy Issue Number: 19308
  • Status: closed  
  • Source: Object Management Group ( Andrew Watson)
  • Summary:

    This is my OMG Architecture Board review of:

    CTS2 XML to JSON Transformation Rules RFC (2nd Rdg) ad/13-09-04
    Inventory ad/13-09-05

    Here are the comments I did have - mostly minor, and all addressable during finalisation:

    1. PDF page 7. For reference, OMG's office has moved: http://www.omg.org/contact.htm

    2. Section 1 (Scope), PDF page 8. It would be useful to have definitive references to Badgerfish & Parker, the XML to JSON transformation conventions mentioned. It would also be useful to include one or two sentences explaining why they aren't thought suitable for CTS2 XML.

    3. Section 3 (Normative references), PDF page 8. We definitely need a normative reference for JSON. One possibility is IETF RFC 4627 (July 2006):

    http://www.ietf.org/rfc/rfc4627.txt

    However, it looks as though ECMA has just published a JSON specification as ECMA 404 (an amusing coincidence, no doubt):

    http://www.ecma-international.org/publications/files/ECMA-ST/ECMA-404.pdf

    Is either of these an appropriate reference?

    4. Section 6.2 (Specification adoption plan), PDF page 9.

    The FTF process is designed to accommodate a specification adopted with the intention of merging it into an existing specification, as here. We simply charter an FTF that takes as input both the newly-adopted specification (in this case, the XML to JSON mapping RFC) and the already-adopted specification with which it is being merged (the CTS2 specification), and delivers as its result the merged specification (along with a finalisation report).

    In this case, we should simply dissolve the CTS2 1.2 RTF, and charter an FTF that takes the XML/JSON RFC and CTS 1.1 as inputs, and delivers CTS 1.2 (including the JSON mapping) as its result (along with a finalisation report that tracks all the changes made to CTS 1.1 and to the RFC).

    This is basically what you have proposed with the "common convenience document", but without the complication of having a separate RTF and FTF.

    5. Section 6.4 (Patents containing essential claims). Unfortunately, we can't say that there are definitely none. The best we can say is that there are "none known to the authors". (But that's still useful to know).

    6. Section B2 (Transformation patterns and Rules). I'm not an expert, but this all looks reasonable to me. However, "shall" should be used to express the rules instead of "will". For example "Repeating XML attribute values shall be treated as a single JSONValue.", "XML comments and processing instructions shall be ignored.", "The following JSONStringCharacters shall be escaped:" It's just a style issue - the meaning is already clear, and not affected by the change.

  • Reported: CTS2 1.1 — Mon, 31 Mar 2014 04:00 GMT
  • Disposition: Resolved — CTS2 1.2
  • Disposition Summary:

    1. Address of the OMG office changed in RFC
    Delete: Section B4, which referenced the emacs document was deleted and the following normative reference:
    The JSON Data Interchange Format 1st Edition / October 2013. http://www.ecma-international.org/publications/files/ECMA-ST/ECMA-404.pdf
    Was added to section 3

  • Updated: Sat, 7 Mar 2015 03:03 GMT

The reference in B4 should instead be added to section 3 (assuming it is normative)

  • Key: CTS212-25
  • Legacy Issue Number: 19307
  • Status: closed  
  • Source: agnos.ai UK Ltd ( Pete Rivett)
  • Summary:

    The reference in B4 should instead be added to section 3 (assuming it is normative)

  • Reported: CTS2 1.1 — Mon, 24 Mar 2014 04:00 GMT
  • Disposition: Resolved — CTS2 1.2
  • Disposition Summary:

    The reference in B4 was deleted and a subsequent, normative reference was added to section 3:

  • Updated: Sat, 7 Mar 2015 03:03 GMT

Rule 10 example uses xsi2:nill – I think this should be xsi2:nil (only one L)

  • Key: CTS212-24
  • Legacy Issue Number: 19306
  • Status: closed  
  • Source: agnos.ai UK Ltd ( Pete Rivett)
  • Summary:

    Rule 10 example uses xsi2:nill – I think this should be xsi2:nil (only one L)

  • Reported: CTS2 1.1 — Mon, 24 Mar 2014 04:00 GMT
  • Disposition: Resolved — CTS2 1.2
  • Disposition Summary:

    Change "xsi:nill" to "xsi:nil" in 4 places on Rule 10

  • Updated: Sat, 7 Mar 2015 03:03 GMT

Rule 10 does not cover the case where the removal of namespaces causes names to be indistinguishable

  • Key: CTS212-22
  • Legacy Issue Number: 19304
  • Status: closed  
  • Source: agnos.ai UK Ltd ( Pete Rivett)
  • Summary:

    Rule 10 does not cover the case where the removal of namespaces causes names to be indistinguishable (that’s the point of namespaces after all). Do such now-identical names then get treated as “arrays” per Rule 7. Or is this disallowed (similar to B3 rule 2)? This needs clarifying

  • Reported: CTS2 1.1 — Mon, 24 Mar 2014 04:00 GMT
  • Disposition: Resolved — CTS2 1.2
  • Disposition Summary:

    Rule 10 included the statement “This rule is specific to the CTS2 specification. Other OMG specifications may choose the option to keep the namespace.” As, for the time being, this is a CTS2 only specification, the statement above was removed and, instead, a third B3 rule was added

  • Updated: Sat, 7 Mar 2015 03:03 GMT

The following in rule 10 is very unclear “In certain situations, this may cause issues for opaque data”

  • Key: CTS212-21
  • Legacy Issue Number: 19303
  • Status: closed  
  • Source: agnos.ai UK Ltd ( Pete Rivett)
  • Summary:

    The following in rule 10 is very unclear “In certain situations, this may cause issues for opaque data”

  • Reported: CTS2 1.1 — Mon, 24 Mar 2014 04:00 GMT
  • Disposition: Resolved — CTS2 1.2
  • Disposition Summary:

    Remove the sentence as it is already addressed in the _CDATA section

  • Updated: Sat, 7 Mar 2015 03:03 GMT

issue with rule 10

  • Key: CTS212-20
  • Legacy Issue Number: 19302
  • Status: closed  
  • Source: agnos.ai UK Ltd ( Pete Rivett)
  • Summary:

    Rule 10: it says to remove the “namespace prefixes” but the examples show removal of complete namespace declarations not just the prefix

  • Reported: CTS2 1.1 — Mon, 24 Mar 2014 04:00 GMT
  • Disposition: Resolved — CTS2 1.2
  • Disposition Summary:

    The previous sentence states “XML namespaces are removed in the JSON.” We have already added the caveat involving _CDATA (issue 19305), but do need to add one additional exception for the root namespace

  • Updated: Sat, 7 Mar 2015 03:03 GMT

conflict between rules 10 and 13

  • Key: CTS212-23
  • Legacy Issue Number: 19305
  • Status: closed  
  • Source: agnos.ai UK Ltd ( Pete Rivett)
  • Summary:

    There seems to be a conflict between rule 10 which seems to state to strip all XML namespaces, and rule 13 which says to retain them if they are in _CDATA

  • Reported: CTS2 1.1 — Mon, 24 Mar 2014 04:00 GMT
  • Disposition: Resolved — CTS2 1.2
  • Disposition Summary:

    There seems to be a conflict between rule 10 which seems to state to strip all XML namespaces, and rule 13 which says to retain them if they are in _CDATA

  • Updated: Sat, 7 Mar 2015 03:03 GMT

The documents referenced in Rule 12 should appear in the normative references section

  • Key: CTS212-19
  • Legacy Issue Number: 19301
  • Status: closed  
  • Source: agnos.ai UK Ltd ( Pete Rivett)
  • Summary:

    The documents referenced in Rule 12 should appear in the normative references section

  • Reported: CTS2 1.1 — Mon, 24 Mar 2014 04:00 GMT
  • Disposition: Resolved — CTS2 1.2
  • Disposition Summary:

    References added (the first one was already added from Issue 19306)

  • Updated: Sat, 7 Mar 2015 03:03 GMT

B2 rule 7: I’m not aware of such a thing as an “XML array”

  • Key: CTS212-18
  • Legacy Issue Number: 19300
  • Status: closed  
  • Source: agnos.ai UK Ltd ( Pete Rivett)
  • Summary:

    B2 rule 7: I’m not aware of such a thing as an “XML array”

  • Reported: CTS2 1.1 — Mon, 24 Mar 2014 04:00 GMT
  • Disposition: Resolved — CTS2 1.2
  • Disposition Summary:

    Reworded to clarify the intent

  • Updated: Sat, 7 Mar 2015 03:03 GMT

Section 7 has the wrong document number for CTS2 – it should be formal/13-12-01

  • Key: CTS212-17
  • Legacy Issue Number: 19299
  • Status: closed  
  • Source: agnos.ai UK Ltd ( Pete Rivett)
  • Summary:

    Section 7 has the wrong document number for CTS2 – it should be formal/13-12-01

  • Reported: CTS2 1.1 — Mon, 24 Mar 2014 04:00 GMT
  • Disposition: Resolved — CTS2 1.2
  • Disposition Summary:

    Fix document number

  • Updated: Sat, 7 Mar 2015 03:03 GMT

The Normative References in section 3 must be added to the Normative References section in the main CTS2 spec

  • Key: CTS212-16
  • Legacy Issue Number: 19298
  • Status: closed  
  • Source: agnos.ai UK Ltd ( Pete Rivett)
  • Summary:

    The Normative References in section 3 must be added to the Normative References section in the main CTS2 spec. However section 7 does not describe such a change

  • Reported: CTS2 1.1 — Mon, 24 Mar 2014 04:00 GMT
  • Disposition: Resolved — CTS2 1.2
  • Disposition Summary:

    Add a section to the revision document saying to add a section to the CTS2 document that contains the normative references in the annex.

  • Updated: Sat, 7 Mar 2015 03:03 GMT

the “Plan” in 6.2 with the RTF working in parallel is not being followed at all

  • Key: CTS212-15
  • Legacy Issue Number: 19297
  • Status: closed  
  • Source: agnos.ai UK Ltd ( Pete Rivett)
  • Summary:

    And in fact the “Plan” in 6.2 with the RTF working in parallel is not being followed at all. The whole section is at variance with reality and people reading this document coming out of the FTF could get very confused as to what is happening.

  • Reported: CTS2 1.1 — Mon, 24 Mar 2014 04:00 GMT
  • Disposition: Resolved — CTS2 1.2
  • Disposition Summary:

    This had been corrected as an earlier issue reported by Andrew Watson

  • Updated: Sat, 7 Mar 2015 03:03 GMT

No Beta document

  • Key: CTS212-14
  • Legacy Issue Number: 19296
  • Status: closed  
  • Source: agnos.ai UK Ltd ( Pete Rivett)
  • Summary:

    6.2 references “The FTF beta document” but this is not referenced by document number – nor does it seem to exist as per comments above

  • Reported: CTS2 1.1 — Mon, 24 Mar 2014 04:00 GMT
  • Disposition: Resolved — CTS2 1.2
  • Disposition Summary:

    Change to “this submission"

  • Updated: Sat, 7 Mar 2015 03:03 GMT

Section 1: should rephrase “this submission” – it’s now a specification

  • Key: CTS212-13
  • Legacy Issue Number: 19295
  • Status: closed  
  • Source: agnos.ai UK Ltd ( Pete Rivett)
  • Summary:

    Section 1: should rephrase “this submission” – it’s now a specification

  • Reported: CTS2 1.1 — Mon, 24 Mar 2014 04:00 GMT
  • Disposition: Resolved — CTS2 1.2
  • Disposition Summary:

    revised

  • Updated: Sat, 7 Mar 2015 03:03 GMT

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

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

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

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

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


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: Parents URI needed in EntityDescription

  • Key: CTS211-26
  • Legacy Issue Number: 18494
  • Status: closed  
  • Source: Mayo Clinic ( Cory Endle)
  • Summary:

    EntityDescription provides URI's for children, descendants and ancestors, but it only provides parents directly. While this is useful, it means that applications that are traversing graphs have to have two different mechanisms - one for the first three categories and a second for parents. We should add one more attribute, "parents" which allows parents to be accessed by URI as well.

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

  • Reported: CTS2 1.0 — Fri, 22 Feb 2013 05:00 GMT
  • Disposition: Resolved — CTS2 1.1
  • Disposition Summary:

    No Data Available

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

CTS2: CodeSystemCatalogQueryService (resolve and resolveAsList) parameter 'directory' type incorrect

  • Key: CTS211-25
  • Legacy Issue Number: 18493
  • Status: closed  
  • Source: Mayo Clinic ( Cory Endle)
  • Summary:

    Section 2.2.1.1 (Operation resolve), input parameter 'directory' is specified as type CodeSystemCatalogURI. Type should be 'CodeSystemCatalogEntryDirectoryURI'

    Section 2.2.1.2 (Operation resolveAsList), input parameter 'directory' is specified as type CodeSystemCatalogURI. Type should be 'CodeSystemCatalogEntryDirectoryURI'

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

  • Reported: CTS2 1.0 — Fri, 22 Feb 2013 05:00 GMT
  • Disposition: Resolved — CTS2 1.1
  • Disposition Summary:

    This issue does not exist in the "CTS2 - Code System and Code System Version Catalog Services, v1.0" document.
    Disposition: Closed, no change

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

CTS2: Complete binding operation missing from specification

  • Key: CTS211-31
  • Legacy Issue Number: 18534
  • Status: closed  
  • Source: Mayo Clinic ( Cory Endle)
  • Summary:

    There is no method with a signature: f(conceptDomain, context[0..*], codeSystemVersion[0..*], tag[0..1]) --> ResolvedValueSet

    (In that there is no way to say "Give me the resolved value set for this concept domain in this context")

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

  • Reported: CTS2 1.0 — Thu, 7 Mar 2013 05:00 GMT
  • Disposition: Resolved — CTS2 1.1
  • Disposition Summary:

    No Data Available

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

CTS2: URIAndEntityName references should all be changed to EntitySynopsis, allowing an optional description


CTS2: IteratableResolvedValueSet and ResolvedValueSet have inconsistent element names

  • Key: CTS211-29
  • Legacy Issue Number: 18531
  • Status: closed  
  • Source: Mayo Clinic ( Cory Endle)
  • Summary:

    ResolvedValueSet has 'member' elements while IteratableResolvedValueSet has 'entry' elements.

    Recommend moving all elements to 'entry' as that is the pattern for everything else.

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

  • Reported: CTS2 1.0 — Thu, 7 Mar 2013 05:00 GMT
  • Disposition: Resolved — CTS2 1.1
  • Disposition Summary:

    No Data Available

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

CTS2: CTS2Exception doesn't match documentation

  • Key: CTS211-28
  • Legacy Issue Number: 18530
  • Status: closed  
  • Source: Mayo Clinic ( Cory Endle)
  • Summary:

    CTS2Exception in the PIM consists of message and severity. The XML schema has an extra element that makes no sense - ExceptionType. This appears to be an artifact that was accidentally left in the UML model, but is never used in the spec itself.

    This should be removed from both places - the UML and the exception schema

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

  • Reported: CTS2 1.0 — Thu, 7 Mar 2013 05:00 GMT
  • Disposition: Resolved — CTS2 1.1
  • Disposition Summary:

    No Data Available

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

Need an optional attribute to carry the OID in addition to the URI

  • Key: CTS211-27
  • Legacy Issue Number: 18517
  • Status: closed  
  • Source: Phast ( Ana Estelrich)
  • Summary:

    In the description of the Code System Catalog Entry the identification is done via the Code System name: “codeSystemName - 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”.

    The HL7 culture is used to manage messages and documents via OIDs which. An optional attribute: CodeSystemOID is needed. The issue here is not turning an OID into a URI but having the possibility to have SIMULTANEOUSLY the URI and OID present (an additional attribute aside from about). In all IHE domains we use OIDs to identify objects. There is no strong consensus and a mechanism of sharing URI so that complete interoperability can be achieved. In this transition context we need a means to assure this transition while assuring interoperability. https://github.com/cts2/cts2-specification/issues/144

  • Reported: CTS2 1.0 — Fri, 1 Mar 2013 05:00 GMT
  • Disposition: Resolved — CTS2 1.1
  • Disposition Summary:

    No Data Available

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

AssociationDirectory needs "associationID"

  • Key: CTS211-22
  • Legacy Issue Number: 18490
  • Status: closed  
  • Source: Mayo Clinic ( Cory Endle)
  • Summary:

    In cases where the associationID is supplied, it is the ID that gets you from the directory contents to the actual association.

    This change has been added to revision 7733 in cts2/spec/submission/OMGServerMap/association/Association.xsd on 10/4/2012

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

  • Reported: CTS2 1.0 — Fri, 22 Feb 2013 05:00 GMT
  • Disposition: Resolved — CTS2 1.1
  • Disposition Summary:

    No Data Available

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

CTS2: Make "associationID" optional

  • Key: CTS211-21
  • Legacy Issue Number: 18489
  • Status: closed  
  • Source: Mayo Clinic ( Cory Endle)
  • Summary:

    Generating associationID's when none exist just produces noise. The associationID parameter should made optional in the PIM where the service doesn't support AssociationRead. This needs to be changed in the schema AND the spec.

    Schema has been updated in revision 7752 in cts2/spec/submission/OMGServerMap/association/Association.xsd

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

  • Reported: CTS2 1.0 — Fri, 22 Feb 2013 05:00 GMT
  • Disposition: Resolved — CTS2 1.1
  • Disposition Summary:

    No Data Available

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

CTS2: Filter PropertyReference documentation needs clarification

  • Key: CTS211-32
  • Legacy Issue Number: 18541
  • Status: closed  
  • Source: Mayo Clinic ( Cory Endle)
  • Summary:

    The PropertyReference class in Filter, and corresponding elements in the query signatures doesn't specify exactly how one should create a referenceTarget for references of type Attribute. As an example, how would one go about specifying the uri attribute in the source component of a sourceAndRole element? The behavior is underspecified if the reference not to a leaf (e.g. "sourceAndRole") Recommend it should specify match anything except href.

    If it is going to require URIAndEntityName (vs. 'or'), we need to clearly state what URI is used in the CTS2 spec. Otherwise we need to change the signature to allow just a name (preferred).

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

  • Reported: CTS2 1.0 — Tue, 12 Mar 2013 04:00 GMT
  • Disposition: Resolved — CTS2 1.1
  • Disposition Summary:

    No Data Available

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

CTS2: Include a depth indicator for AssociationGraph

  • Key: CTS211-20
  • Legacy Issue Number: 18488
  • Status: closed  
  • Source: Mayo Clinic ( Cory Endle)
  • Summary:

    The association graph structure is considerably easier to use if has a dept indicator. While this could be computed, it is much easier to traverse if explicitly present.

    This change has been added to Association.xsd in cts2/spec/submission/OMGServerMap/association

    Still needs to be documented and added to the spec itself

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

  • Reported: CTS2 1.0 — Fri, 22 Feb 2013 05:00 GMT
  • Disposition: Resolved — CTS2 1.1
  • Disposition Summary:

    No Data Available

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

CTS2: ConceptDomainCatalogQueryService (resolve) parameter "directory" type incorrect

  • Key: CTS211-24
  • Legacy Issue Number: 18492
  • Status: closed  
  • Source: Mayo Clinic ( Cory Endle)
  • Summary:

    Section 2.2.1.1 (Operation resolve), input parameter 'directory' is specified as type ConceptDomainDirectoryURI. Type should be 'ConceptDomainCatalogEntryDirectoryURI'

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

  • Reported: CTS2 1.0 — Fri, 22 Feb 2013 05:00 GMT
  • Disposition: Resolved — CTS2 1.1
  • Disposition Summary:

    This issue does not exist in the "CTS2 - Concept Domain and Concept Domain Binding Services, v1.0" document.
    Disposition: Closed, no change

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

CTS2: URIAndEntityName XSD representation does not match UML

  • Key: CTS211-23
  • Legacy Issue Number: 18491
  • Status: closed  
  • Source: Mayo Clinic ( Cory Endle)
  • Summary:

    URIAndEntityName does not represent what is in the UML. The UML says that the only thing that is required is the uri – the name and href are optional. The Schema says that the namespace and name is required.

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

  • Reported: CTS2 1.0 — Fri, 22 Feb 2013 05:00 GMT
  • Disposition: Resolved — CTS2 1.1
  • Disposition Summary:

    No Data Available

  • 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

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

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

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

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

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

ConceptDomainCatalogQueryServices WSDL corrections


CTS2: Possible issue with CTS2 URI

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

    Appendix 10 of the OMG "Hitchhiker's Guide" (http://www.omg.org/cgi-bin/doc?hh) specifies a directory structure for organizing submission documents. While older specifications were organized as "spec.omg.org/...", the current direction is that the documents should be organized in "www.omg.org/spec//, where version would be "Beta2", "1.0" for the base spec and "yyyymmmm" for accompanying files.

    The OMG AB believes that this set of requirements would imply that the CTS2 URIs should change from "http://spec.omg.org/cts2/1.0/" to "http://www.omg.org/spec/cts2/1.0/".

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

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

    Resolution (PIM)
    N/A

    Resolution (PSM)

    In each of the following files, all references to: "http://schema.omg.org/spec/CTS2/1.0"
    are being changed to: "http://www.omg.org/spec/CTS2/1.1".

    Change Location

    AdvancedAssociationQueryService.wsdl
    AssociationHistoryService.wsdl
    AssociationMaintenanceService.wsdl
    AssociationQueryService.wsdl
    AssociationReadService.wsdl
    AssociationTransformService.wsdl
    BaseExportService.wsdl
    BaseImportService.wsdl
    CodeSystemCatalogHistoryService.wsdl
    CodeSystemCatalogMaintenanceService.wsdl
    CodeSystemCatalogQueryService.wsdl
    CodeSystemCatalogReadService.wsdl
    CodeSystemVersionCatalogHistoryService.wsdl
    CodeSystemVersionCatalogMaintenanceService.wsdl
    CodeSystemVersionCatalogQueryService.wsdl
    CodeSystemVersionCatalogReadService.wsdl
    ConceptDomainBindingMaintenanceService.wsdl
    ConceptDomainBindingQueryService.wsdl
    ConceptDomainBindingReadService.wsdl
    ConceptDomainCatalogHistoryService.wsdl
    ConceptDomainCatalogMaintenanceService.wsdl
    ConceptDomainCatalogQueryService.wsdl
    ConceptDomainCatalogReadService.wsdl
    EntityDescriptionHistoryService.wsdl
    EntityDescriptionMaintenanceService.wsdl
    EntityDescriptionQueryService.wsdl
    EntityDescriptionReadService.wsdl
    EntityDescriptionTransformService.wsdl
    MapCatalogHistoryService.wsdl
    MapCatalogMaintenanceService.wsdl
    MapCatalogQueryService.wsdl
    MapCatalogReadService.wsdl
    MapEntryHistoryService.wsdl
    MapEntryMaintenanceService.wsdl
    MapEntryQueryService.wsdl
    MapEntryReadService.wsdl
    MapResolutionService.wsdl
    MapVersionHistoryService.wsdl
    MapVersionMaintenanceService.wsdl
    MapVersionQueryService.wsdl
    MapVersionReadService.wsdl
    ReasoningService.wsdl
    ResolvedValueSetLoader.wsdl
    ResolvedValueSetQueryService.wsdl
    ResolvedValueSetResolution.wsdl
    StatementHistoryService.wsdl
    StatementQueryService.wsdl
    StatementReadService.wsdl
    UpdateService.wsdl
    ValueSetCatalogHistoryService.wsdl
    ValueSetCatalogMaintenanceService.wsdl
    ValueSetCatalogQueryService.wsdl
    ValueSetCatalogReadService.wsdl
    ValueSetDefinitionHistoryService.wsdl
    ValueSetDefinitionMaintenanceService.wsdl
    ValueSetDefinitionQueryService.wsdl
    ValueSetDefinitionReadService.wsdl
    ValueSetDefinitionResolution.wsdl

    Change Description

    Changes to machine readable files are easily identified by Git using the color red to indicate “deletion” and green to indicate “addition.” Furthermore, the ‘-‘ minus sign is also displayed to indicate a deletion, and a “+” plus sign is displayed to indicate an addition.

    View Changes: https://github.com/cts2/cts2-specification/commit/890558063ee42dd3a21419f942abe16f0a634677

    Due to number of changes, please review the PDF.
    http://informatics.mayo.edu/svn/trunk/cts2/spec/submission/RTF_1.1/RTF_Issues/CTS2_RTF_1.1_17318.pdf

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

CTS2: "documentURI" attribute description in ResourceVersionDescription is incorrect

  • Key: CTS211-5
  • Legacy Issue Number: 18472
  • Status: closed  
  • Source: Mayo Clinic ( Cory Endle)
  • Summary:

    On page 39 of Core the description of the documentURI attribute in ResourceVersionDescription stops in mid sentence with a "100".

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

  • Reported: CTS2 1.0 — Fri, 22 Feb 2013 05:00 GMT
  • Disposition: Resolved — CTS2 1.1
  • Disposition Summary:

    Resolution (PIM)
    Location 1
    Document "CTS2 - Core Model Elements, v1.0"
    Section 2.7.1.5
    Page 39
    Change Description 1
    Change made to Attributes section.
    Old Text:
    documentURI - a URI that identifies the specific version, language, and notation of the about resource. This URI needs to be constructed in such a way that, if necessary, it will be possible to differentiate resource versions that were loaded from different document syntaxes. As an example, if an image of the wine ontology was loaded from a resource that was in Manchester Syntax, it should be given a different URI than the image loaded from the RDF/XML syntax. The reasoning behind this is, even in cases where different syntaxes are 100.
    New Text:
    documentURI - a URI that identifies the specific version, language and notation of the about resource. This URI needs to be constructed in such a way that, if necessary, it will be possible to differentiate resource versions that were loaded from different document syntaxes. As an example, if an image of a the wine ontology was loaded from a resource that was in Manchester Syntax, it should be given a different URI than the image loaded from the RDF/XML syntax. The reasoning behind this is, even in cases where different syntaxes are 100% compatible the transformation into the CTS2 model may not be identical.
    Resolution (PSM)
    Change Location
    Core.xsd
    Change Description
    Changes to machine readable files are easily identified by Git using the color red to indicate “deletion” and green to indicate “addition.” Furthermore, the ‘-‘ minus sign is also displayed to indicate a deletion, and a “+” plus sign is displayed to indicate an addition.
    View changes: https://github.com/cts2/cts2-specification/commit/138ee6180cb52fa1176ac0f3bbfd93b54de34205

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

CTS2: "entityType" description text incorrect - needs to be updated

  • Key: CTS211-2
  • Legacy Issue Number: 18469
  • Status: closed  
  • Source: Mayo Clinic ( Cory Endle)
  • Summary:

    The current description of entityType in section 2.1.1.1 of the Entity Description Services (page 6) reads:
    entityType - the set of type(s) which the entityReference is an instance of. Because this is a terminology service, entityType must include one of owl:class, owl:individual, rdf:predicate, or skos:concept, although it may carry many other types as well.

    This is incorrect - it should read:
    "... must include one of owl:Class, owl:Individual, rdf:Property or skos:Concept"

    Note that this may potentially effect some implementations that have either transcribed the information literally or have used "rdf:predicate" instead of "ref:Property"

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

  • Reported: CTS2 1.0 — Fri, 22 Feb 2013 05:00 GMT
  • Disposition: Resolved — CTS2 1.1
  • Disposition Summary:
  • Updated: Fri, 6 Mar 2015 20:58 GMT

CTS2: "SourceAndNotation" should be made optional in resource version

  • Key: CTS211-4
  • Legacy Issue Number: 18471
  • Status: closed  
  • Source: Mayo Clinic ( Cory Endle)
  • Summary:

    At the moment, SourceAndNotation is a required field. In many situations there is nothing of value that can be supplied here - it should be made optional.

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

  • Reported: CTS2 1.0 — Fri, 22 Feb 2013 05:00 GMT
  • Disposition: Resolved — CTS2 1.1
  • Disposition Summary:

    see pages 35 - 37 of prc/2013-06-02 for details

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

CTS2: referencedEntity in Value Set Definitions should include an optional description

  • Key: CTS211-3
  • Legacy Issue Number: 18470
  • Status: closed  
  • Source: Mayo Clinic ( Cory Endle)
  • Summary:

    AssociatedEntitiesReference.referencedEntity and SpecificEntityList.referencedEntity are currently of type URIAndEntityName. This does not provide any place to include a designation or description of the entity. The type should be changed to EntitySynopsis

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

  • Reported: CTS2 1.0 — Fri, 22 Feb 2013 05:00 GMT
  • Disposition: Resolved — CTS2 1.1
  • Disposition Summary:

    See issue 18532 for disposition

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

CTS2: DocumentURI shouldn't be mandatory in ResourceVersionDescription

  • Key: CTS211-6
  • Legacy Issue Number: 18473
  • Status: closed  
  • Source: Mayo Clinic ( Cory Endle)
  • Summary:

    The DocumentURI was intended to differentiate situations where there were potentially multiple sources of the same version of a resource (e.g. SNOMED CT 20120731 from RF1, RF2, RRF or Owl). This is the exception, rather than the rule, and the DocumentURI field should be made optional for clarity.

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

  • Reported: CTS2 1.0 — Fri, 22 Feb 2013 05:00 GMT
  • Disposition: Resolved — CTS2 1.1
  • Disposition Summary:

    Resolution (PIM)
    Change Location 1
    Document "CTS2 - Core Model Elements, v1.0"
    Section 2.7.2
    Page 40
    Figure 2.17
    Change Description 1
    Updated diagram in Figure 2.17
    Old Diagram:

  • 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

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

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

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

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

CTS2: Resource content filtering for Query

  • Key: CTS211-37
  • Legacy Issue Number: 18610
  • Status: closed  
  • Source: Mayo Clinic ( Cory Endle)
  • Summary:

    In each Query Service, it would be helpful for the user to be able to select certain attributes of the resource to be included (or excluded). For instance, a user may only be interested in the Definitions, or a given named property. Right now, for the Query Service, the user is limited to either 1) the directory entry, or 2) the list representation, which is the entire resource. It would be helpful to have the option of something in between.

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

  • Reported: CTS2 1.0 — Mon, 1 Apr 2013 04:00 GMT
  • Disposition: Resolved — CTS2 1.1
  • Disposition Summary:

    See OMG Issue 18474 (#137) for disposition.

    Disposition: See issue 18474 for disposition

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

CTS2: WADL Graph URLs need to change to better reflect AssociationDirectory as input

  • Key: CTS211-36
  • Legacy Issue Number: 18564
  • Status: closed  
  • Source: Mayo Clinic ( Cory Endle)
  • Summary:

    Currently, to get an association graph in REST, the graph is retrieved by:

    /codesystem/cs/version/1.0/graph

    It would be more correct to be like:

    /codesystem/cs/version/1.0/associations/graph

    to take into account the 'graph' taking in the association directory as an input. Right now, the 'graph' resource is used in place of the 'associations' resource, but this makes it very hard to do queries such as:

    /codesystem/cs/version/1.0/entity/C12345/children/graph

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

  • Reported: CTS2 1.0 — Thu, 14 Mar 2013 04:00 GMT
  • Disposition: Resolved — CTS2 1.1
  • Disposition Summary:

    No Data Available

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

CTS2: MapTargetList and MapTargetListList need a 'Message' wrapper for REST calls


CTS2: Cardinality of includesResolvedValueSet wrong on ResolvedValueSetHeader

  • Key: CTS211-33
  • Legacy Issue Number: 18542
  • Status: closed  
  • Source: Mayo Clinic ( Cory Endle)
  • Summary:

    The UML model in figure 4.4 of the ValueSet document lists the cardinality of includesResolvedValueSet as [0..1]. It should be [0..*].

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

  • Reported: CTS2 1.0 — Tue, 12 Mar 2013 04:00 GMT
  • Disposition: Resolved — CTS2 1.1
  • Disposition Summary:

    No Data Available

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

CTS2: ValueSetDefinitionResolution 'resolve' method has incorrect return type

  • Key: CTS211-41
  • Legacy Issue Number: 18689
  • Status: closed  
  • Source: Mayo Clinic ( Craig Stancl)
  • Summary:

    ValueSetDefinitionResolution 'resolve' method has incorrect return type. It should be IterableResolvedValueSet.

    6.1.1.1 Operation: resolve

    Resolve the value set definition against the supplied code system versions and/or version tags.

    ....

    Return Type: ResolvedValueSetDirectory

    should be:

    6.1.1.1 Operation: resolve

    Resolve the value set definition against the supplied code system versions and/or version tags.

    ....

    Return Type: IterableResolvedValueSet

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

  • Reported: CTS2 1.0 — Fri, 26 Apr 2013 04:00 GMT
  • Disposition: Resolved — CTS2 1.1
  • Disposition Summary:

    No Data Available

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

CTS2: Association derivation should be optional and not have a default

  • Key: CTS211-39
  • Legacy Issue Number: 18624
  • Status: closed  
  • Source: Mayo Clinic ( Cory Endle)
  • Summary:

    The specification states that derivation can be ASSERTED, INFERRED or omitted, meaning that the derivation is unknown. The UML diagram shows it as required, which is wrong. The XML Schema shows it with a default of ASSERTED, which also needs to be removed.

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

  • Reported: CTS2 1.0 — Tue, 9 Apr 2013 04:00 GMT
  • Disposition: Resolved — CTS2 1.1
  • Disposition Summary:

    see pages 258 - 260 of ptc/2013-06-02 for details

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

CTS2: MapEntry Read and Resolution need WADL 'byURI' REST signatures

  • Key: CTS211-35
  • Legacy Issue Number: 18563
  • Status: closed  
  • Source: Mayo Clinic ( Cory Endle)
  • Summary:

    In the WADL, two MapEntry URLS were omitted:
    map/

    {map}/version/{version}/entrybyuri?uri=...
    map/{map}

    /version/

    {version}

    /entrybyuri/resolution?uri=.

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

  • Reported: CTS2 1.0 — Thu, 14 Mar 2013 04:00 GMT
  • Disposition: Resolved — CTS2 1.1
  • Disposition Summary:

    No Data Available

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

CTS2: AssociationDirectory needs the derivation

  • Key: CTS211-38
  • Legacy Issue Number: 18622
  • Status: closed  
  • Source: Mayo Clinic ( Cory Endle)
  • Summary:

    The derivation attribute (INFERRED/ASSERTED) needs to be visible in an association directory, as it helps consumers understand the abstract structure.

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

  • Reported: CTS2 1.0 — Mon, 8 Apr 2013 04:00 GMT
  • Disposition: Resolved — CTS2 1.1
  • Disposition Summary:

    No Data Available

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

Type of maxtoreturn is string in the WADL definitions. It should be NaturalNumber (or equiv)


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

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

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


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

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

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

ChangeSet element doesn't have a MSG header



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


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

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

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

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

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

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

CTS2: Additional options needed for Entity Read Query

  • Key: CTS211-12
  • Legacy Issue Number: 18479
  • Status: closed  
  • Source: Mayo Clinic ( Cory Endle)
  • Summary:

    The entity and entitybyuri queries currently return an EntityReference that contains zero or more knownEntityDescriptions. They do this even if there is just one knownEntityDescription. This behavior is not what most clients desire

    Would recommend the following:
    (a) (re-)add the tag that was present in the LexGrid model that could be used to identify one of the coding systems as the "primary"
    (b) State that the default behavior of entity and entitybyuri is to redirect to the only or (when present) tagged entry in the specific codesystem version. The id is that //entity/12345 will redirect to //codesystem/

    {c}

    /version/

    {v}

    /entity/12345 if it is the only describing code system version or its code system (version?) is listed as the primary
    (c) add an additional parameter (fwd?) that, when false, says that redirection should not occur.

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

  • Reported: CTS2 1.0 — Fri, 22 Feb 2013 05:00 GMT
  • Disposition: Resolved — CTS2 1.1
  • Disposition Summary:

    No Data Available

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

CTS2: Format and language resolution precedence not described for REST

  • Key: CTS211-11
  • Legacy Issue Number: 18478
  • Status: closed  
  • Source: Mayo Clinic ( Cory Endle)
  • Summary:

    Both the format and language can be supplied as a url parameter or as part of the http header. The current specification doesn't address what to do if both are present.

    Recommendation is that the command line takes precedence over Accept and Accept-Language in the header.

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

  • Reported: CTS2 1.0 — Fri, 22 Feb 2013 05:00 GMT
  • Disposition: Resolved — CTS2 1.1
  • Disposition Summary:

    No Data Available

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

CTS2: Include the signature for the CLONE operation in Change Set

  • Key: CTS211-8
  • Legacy Issue Number: 18475
  • Status: closed  
  • Source: Mayo Clinic ( Cory Endle)
  • Summary:

    The change set includes a CLONE type, but we haven't specified a method for asking that a CLONE be performed.

    We would anticipate that the method signature would include:
    nameOrURI of the the versionable resource to be Cloned
    the new version identifier (optional - could be assigned by service or error if it doesn't)
    the new version URI (optional)
    the change set URI

    (we need to check the documentation to see whether there is anything else)

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

  • Reported: CTS2 1.0 — Fri, 22 Feb 2013 05:00 GMT
  • Disposition: Resolved — CTS2 1.1
  • Disposition Summary:

    No Data Available

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

CTS2: Extensible Directories - Allow directories to be extended

  • Key: CTS211-7
  • Legacy Issue Number: 18474
  • Status: closed  
  • Source: Mayo Clinic ( Cory Endle)
  • Summary:

    The CTS2 specification describes the minimum (and, at the moment, only) content that can be in directories of various types. Implementers are discovering that they need to add information to this to meet special use cases (e.g. ChangeSetURI and ChangeSetNotes for a special value set authoring environment). We need a way to allow directories to be extended for service specific implementations.

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

  • Reported: CTS2 1.0 — Fri, 22 Feb 2013 05:00 GMT
  • Disposition: Resolved — CTS2 1.1
  • Disposition Summary:

    No Data Available

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

CTS2: Rest signatures missing for ValueSetDefinitionResolution "resolveAsCompleteSet" function

  • Key: CTS211-15
  • Legacy Issue Number: 18483
  • Status: closed  
  • Source: Mayo Clinic ( Cory Endle)
  • Summary:

    The resolveAsCompleteSet function allows the client to ask for a ResolvedValueSet (vs. IterableResolvedValueSet). There is currently no way to do this in the REST functions.

    Would propose that we add a parameter to queryControl or update the possible values for maxToReturn so a client can indicate that they don't want an iterator, they want the whole thing. We will have to supply a new error message as well - something to the effect of "too much to return all at once"

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

  • Reported: CTS2 1.0 — Fri, 22 Feb 2013 05:00 GMT
  • Disposition: Resolved — CTS2 1.1
  • Disposition Summary:

    No Data Available

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

CTS2: REST language signature "referencelanguage" needs to be more REST compliant

  • Key: CTS211-14
  • Legacy Issue Number: 18481
  • Status: closed  
  • Source: Mayo Clinic ( Cory Endle)
  • Summary:

    The current tag, "referencelanguage" is a bit unwieldy from the REST perspective. Would recommend adding a synonym, "lang" to address this issue.

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

  • Reported: CTS2 1.0 — Fri, 22 Feb 2013 05:00 GMT
  • Disposition: Resolved — CTS2 1.1
  • Disposition Summary:

    No Data Available

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

CTS2: CodeSystemCatalogEntry xml schema missing "hasOntologyLanguage" and "includes" elements

  • Key: CTS211-19
  • Legacy Issue Number: 18487
  • Status: closed  
  • Source: Mayo Clinic ( Cory Endle)
  • Summary:

    CodeSystemCatalogEntry.xsd is missing "hasOntologyLanguage" and "includes" elements. These were added to cts2/spec/submission/OMGServerMap/codesystem/CodeSystem.xsd in revision 7641

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

  • Reported: CTS2 1.0 — Fri, 22 Feb 2013 05:00 GMT
  • Disposition: Resolved — CTS2 1.1
  • Disposition Summary:

    No Data Available

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

CTS2: Map Entry "MapFrom" and "MapTo" need optional description element

  • Key: CTS211-18
  • Legacy Issue Number: 18486
  • Status: closed  
  • Source: Mayo Clinic ( Cory Endle)
  • Summary:

    The mapFrom and mapTo elements in Map Entry are currently of type URIAndEntityName, which doesn't allow an explanatory designation to be provided, meaning that it may be necessary to resolve the returned types against a code system. This type should be changed to EntitySynopsis. Changes have been submitted to CTS2 svn repository as change 7853

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

  • Reported: CTS2 1.0 — Fri, 22 Feb 2013 05:00 GMT
  • Disposition: Resolved — CTS2 1.1
  • Disposition Summary:

    Disposition: See issue 18532 for disposition

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

CTS2: No ROA link to value set resolution of current value set

  • Key: CTS211-9
  • Legacy Issue Number: 18476
  • Status: closed  
  • Source: Mayo Clinic ( Cory Endle)
  • Summary:

    While it is possible to construct a URL that requests the resolution of the CURRENT version of a value set, there is no href in the ValueSet schema that allows this query to be performed without knowing URL construction rules. There should be another optional link called "resolution" or something similar where a service can provide an href that allows direct access to the value set resolution.

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

  • Reported: CTS2 1.0 — Fri, 22 Feb 2013 05:00 GMT
  • Disposition: Resolved — CTS2 1.1
  • Disposition Summary:

    No Data Available

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

CTS2: ValueSetDefinition REST signatures need to include shortcuts for tags

  • Key: CTS211-17
  • Legacy Issue Number: 18485
  • Status: closed  
  • Source: Mayo Clinic ( Cory Endle)
  • Summary:

    Currently there is no way to resolve a value set definition directly without knowing a specific version - it is first necessary to find the definition via query statements. The REST signatures should include:
    //valueset/resolution[?tag=

    {tag}

    ], which will resolve CURRENT or tag directly. This has already been implemented in the SVS mat implementation.

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

  • Reported: CTS2 1.0 — Fri, 22 Feb 2013 05:00 GMT
  • Disposition: Resolved — CTS2 1.1
  • Disposition Summary:

    No Data Available

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

CTS2: Documentation for value set resolution needs to be corrected.


CTS2: "versiontag" has wrong type in MapVersion schema

  • Key: CTS211-10
  • Legacy Issue Number: 18477
  • Status: closed  
  • Source: Mayo Clinic ( Cory Endle)
  • Summary:

    Line 60 in MapVersion.xsd has the wrong type for versiontag. Change:

    <xs:element name="versionTag" type="core:MapVersionReference" minOccurs="0" maxOccurs="unbounded">

    to

    <xs:element name="versionTag" type="core:VersionTagName" minOccurs="0" maxOccurs="unbounded">

    Change submitted to svn - cts2/spec/submission/OMGServerMap/mapversion/MapVersion.xsd - revision 7877

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

  • Reported: CTS2 1.0 — Fri, 22 Feb 2013 05:00 GMT
  • Disposition: Resolved — CTS2 1.1
  • Disposition Summary:

    No Data Available

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

CTS2: Redirect behavior isn't clear for uri reads

  • Key: CTS211-13
  • Legacy Issue Number: 18480
  • Status: closed  
  • Source: Mayo Clinic ( Cory Endle)
  • Summary:

    The REST specification doesn't specify what the service behavior should be on "byuri" type queries. Some implementations use a 303 to get to the base resource while others leave the URI as entered.

    Would propose that the specification say that it should always redirect.

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

  • Reported: CTS2 1.0 — Fri, 22 Feb 2013 05:00 GMT
  • Disposition: Resolved — CTS2 1.1
  • Disposition Summary:

    No Data Available

  • 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: 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

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

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