Issue 16347: CTS2 XML file appears to contain EA proprietary elements
Issue 16937: CTS 2: Change 'boundValueSet' cardinality in ConceptDomainBindingDirectoryEntry (XSD) to 1..1
Issue 16938: CTS2: Move 'bindingQualifier' in ConceptDomainBinding (XSD) to an Element
Issue 16939: CTS 2: Change 'applicableContext' cardinality in ConceptDomainBinding (XSD) to 0..1
Issue 16940: CTS 2: SortCriteria contains PropertyReference
Issue 16941: CTS 2: FilterComponent is a PropertyReference and contains a MatchAlgorithm reference
Issue 17070: AnonymousStatement target cardinality
Issue 17071: AnonymousStatement typo
Issue 17072: ChangeDescription stereotypes
Issue 17073: Changeable/ChangeDescription typo
Issue 17074: BaseMaintenanceService.updateChangeableMetadata parameters
Issue 17075: Core spec typos
Issue 17076: UpdateCodesystemCatalogEntry.usedOntologyEngineeringTool optionality
Issue 17077: CodesystemCatalogEntry.usedOntologyEngineeringTool
Issue 17078: Entity description services p20 typo
Issue 17079: AssociationGraph p45 typo
Issue 17080: ChangeSet element doesn't have a MSG header
Issue 17081: EntityDescriptionReadService lacking local variables
Issue 17082: EntityDescriptionQueryService lacking supportedVersionTag
Issue 17083: UpdateEntityDescription is missing elements and does not support "optparam" semantics
Issue 17084: Designation and Note have inconsistent pattern in schema
Issue 17085: SpecificEntityList incorrectly supertyped
Issue 17086: NamedEntityDescription and AnonymousEntityDescription incorrectly defined in schema
Issue 17087: ImplementationProfiles.ProfileElement not RESTful
Issue 17088: Documentation issue on ProfileElement
Issue 17089: XML Schema for BaseService has wrong type for supported Profile
Issue 17107: Remove CONCEPT_DOMAIN_BINDING from ReferenceType
Issue 17108: EntityReferences - URIAndEntityNameList
Issue 17109: Changeable changeDescription cardinality constraint
Issue 17110: BaseQueryService filter property needs to be individualized
Issue 17111: ConceptDomainbinding needs an identifier
Issue 17112: Statement needs an identifier
Issue 17113: Typo on page 3 of Statement Information model
Issue 17114: Typo on page 11 of statement information model
Issue 17115: Association Information Model derivation and derivationReasoningAlgorithm
Issue 17116: AdvancedAssociationQuerySerivce not in WADL (REST PSM)
Issue 17117: ResolvedValueSetDirectory misnamed and mistyped
Issue 17118: ResolvedValueSetReadService and QueryService omitted from spec
Issue 17119: Refactor inline XSD types from WSDLs (SOAP PSM)
Issue 17173: CodeSystemCatalogMaintenanceServices WSDL corrections
Issue 17174: CodeSystemCatalogHistoryServices WSDL corrections
Issue 17175: CodeSystemCatalogQueryServices WSDL corrections
Issue 17176: CodeSystemVersionCatalogReadServices WSDL corrections
Issue 17177: CodeSystemVersionCatalogQueryServices WSDL corrections
Issue 17178: CodeSystemVersionCatalogMaintenanceServices WSDL corrections
Issue 17179: CodeSystemVersionCatalogHistoryServices WSDL corrections
Issue 17180: EntityDescriptionReadServices WSDL corrections
Issue 17181: AssociationQueryServices WSDL corrections
Issue 17182: AdvancedAssociationQueryServices WSDL corrections
Issue 17183: AssociationReadServices WSDL corrections
Issue 17184: AssociationHistoryServices WSDL corrections
Issue 17185: AssociationMaintenanceServices WSDL corrections
Issue 17186: AssociationTransformServices WSDL corrections
Issue 17187: BaseImport/ExportServices WSDL correction
Issue 17188: ConceptDomainBindingQueryServices WSDL corrections
Issue 17189: ConceptDomainBindingMaintenanceServices WSDL corrections
Issue 17190: ConceptDomainCatalogQueryServices WSDL corrections
Issue 17191: ConceptDomainCatalogHistoryServices WSDL corrections
Issue 17192: EntityDescriptionTransformService WSDL corrections
Issue 17193: EntityDescriptionQueryServices WSDL corrections
Issue 17194: EntityDescriptionMaintenanceServices WSDL changes
Issue 17317: CTS2: ScopedEntityName.name type is too strong
Issue 17318: CTS2: Possible issue with CTS2 URI
Issue 17319: CTS2: currentVersion not typed in MapCatalogEntry
Issue 17320: CTS2: Inconsistent element/complexType declarations
Issue 17321: CTS2: Message Header Documentation Missing
Issue 17322: CTS2: StructuralProfile - Statement and/or MapEntry
Issue 17323: Create/Update in WADL use the wrong HTTP methods
Issue 17324: CTS2: AssociationQueryService 'getAllSourceAndTargetEntities' wrong input parameter
Issue 17325: CTS2: ConceptDomainBindingReadService QueryControl parameters
Issue 17326: CTS2: AssociationQueryServices WSDL corrections
Issue 17327: CTS2: Service map catalog typo
Issue 17330: CTS2: Concept Domain Catalog Query Service missing description
Issue 17331: CTS2: section 1.1.2.1 Class CodeSystemCatalogEntryDirectory typo
Issue 17332: CTS2: Change cardinality of defaultLanguage from [0..1] to [0..*]
Issue 17350: Missing documentation on StatementSubject
Issue 17351: Introduction section about conventions and notation needs to be in all modules
Issue 17352: EntityDescriptionQueryService knownCodeSystem type is incorrect
Issue 17353: Exception listed twice in EntityDescriptionQueryService
Issue 16347: CTS2 XML file appears to contain EA proprietary elements (cts2-ftf)
Click here for this issue's archive.
Source: Microsoft (Mr. Steve Cook, stcook(at)microsoft.com)
Nature: Uncategorized Issue
Severity:
Summary:
Looking at 11-06-20.xml, I see elements such as <thecustomprofile:interface base_Class="EAID_F37A3B0D_CFE6_448a_A95F_26FDC113F2A2"/>, which are EA-specific representations. This needs to be fixed to be properly XMI compliant.
'boundValueSet' cardinality in ConceptDomainBindingDirectoryEntry (XSD) needs to change from 0..* to to 1..1 Logged: https://github.com/cts2/cts2-specification/issues/2
'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
'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
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
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
Target cardinalityTarget should be 1..* to allow things like unionof(a,b,c...). Need to change spec and schema
StatmentQualifier -> statementQualifier Logged: https://github.com/cts2/cts2-specification/issues/8
ChangeType, committed, containingChangeSet, prevChangeSet, changeDate and clonedResource should be ReadOnly Logged: https://github.com/cts2/cts2-specification/issues/9
Changeable/ChangeDescription typo
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
CTS2: Core spec p57 typo Createchangeset condition 8 https://github.com/cts2/cts2-specification/issues/12 Core spec p62 typo AbstractResourc.... Goes off page Logged: https://github.com/cts2/cts2-specification/issues/13 CTS2: Core spec p75 typo ExportStatus missing documentation Logged: https://github.com/cts2/cts2-specification/issues/14
Should be 0..* Logged: https://github.com/cts2/cts2-specification/issues/15
Type should be OntologyEngineeringToolReference... Check omv for "used" vs. "uses" Logged: https://github.com/cts2/cts2-specification/issues/16
Last line is "tetrieve" Logged: https://github.com/cts2/cts2-specification/issues/17
"To accomplish this, every EntityDescription ..." -> EntitySynopsis Logged: https://github.com/cts2/cts2-specification/issues/18
The ChangeSet element in the Updates schematic doesnt have the message header. https://github.com/cts2/cts2-specification/issues/19
EntityDescriptionServices.xsd doesn't have knownCodeSystem, knownCodeSystemVersion or supportedVersionTag in the schema. Logged: https://github.com/cts2/cts2-specification/issues/20
EntityDescriptionServices.xsd doesn't have suppportedVersionTag in the query service Logged: https://github.com/cts2/cts2-specification/issues/21
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
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
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
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
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
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
The type of SupportedProfile should be ProfileElement, not StructuralProfile Logged: https://github.com/cts2/cts2-specification/issues/28
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
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
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
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
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
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
subject - ahe subject Logged: https://github.com/cts2/cts2-specification/issues/35
blank exceptions entry Logged: https://github.com/cts2/cts2-specification/issues/36
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
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
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
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
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
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
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
In the 'count' method, added a 'timeout' parameter. Logged: https://github.com/cts2/cts2-specification/issues/44
Renamed method 'getCodeSystemVersionByExternalId' to 'getCodeSystemByVersionId'.
Renamed method 'existsExternalId' to 'existsVersionId'.
Logged: https://github.com/cts2/cts2-specification/issues/45
Reason For Change The methods 'getCodeSystemVersionByExternalId' and 'existsExternalId' will better align with the PIM if the naming convention 'externalId' is changed to 'versionId'. This will be clearer to implementers as to the intent of the functions, as well as bind them to the PIM.
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
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
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
Rename method 'getKnownCodeSystems' to 'getKnownCodeSystem'.
Rename method 'getKnownCodeSystemVersions' to 'getKnownCodeSystemVersion'.
Rename method 'getSupportedVersionTags' to 'getSupportedVersionTag'.
Logged: https://github.com/cts2/cts2-specification/issues/49
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/50
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
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
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
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
Removed method 'getSupportedVersionTags' and 'fromEntityDirectory'
In method 'toAssociationFormat' changed type of param 'codeSystemVersion' to 'CodeSystemVersionReference'
Logged: https://github.com/cts2/cts2-specification/issues/55
Changed all URI param types from String to LocalURI or DocumentURI Logged: https://github.com/cts2/cts2-specification/issues/56
In method 'count' add a 'timeout' param. Logged: https://github.com/cts2/cts2-specification/issues/57
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
In method 'count' added a 'timeout' param Logged: https://github.com/cts2/cts2-specification/issues/59
In method 'count' added a 'timeout' param
In method 'readChangeSet' renamed param 'URI' to 'changeSetURI'
Logged: https://github.com/cts2/cts2-specification/issues/60
Renamed method 'getKnownCodeSystems' to 'getKnownCodeSystemVersion'
Removed method 'getSupportedVersionTags'
Logged: https://github.com/cts2/cts2-specification/issues/61
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
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
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
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
Map.xsd MapCatalogEntry currentVersion does not have an XSD type. Should be MapVersionReference... Logged: https://github.com/cts2/cts2-specification/issues/89
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
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
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
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
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
The QueryControl parameter was omitted from the read and readByURI operations in ConceptDomainBindingService. Logged: https://github.com/cts2/cts2-specification/issues/81
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
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
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
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
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
subjectType is not documented on page 3 of the Statement Information Model Logged: https://github.com/cts2/cts2-specification/issues/92
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
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
restrictToCodeSystem lists InvalidDirectoryType twice in the exception list. Logged: https://github.com/cts2/cts2-specification/issues/95