issues
search
cts2
/
cts2-specification
The CTS2 OMG Specification
http://informatics.mayo.edu/cts2
11
stars
2
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Updates namespace to CTS2 version 1.2 uri
#186
ghost
closed
8 years ago
0
Resolves bad faults in the WSDLs, updates operations to 1.2 & namespace uri to 1.3
#185
ghost
closed
2 years ago
0
ValueSetDefinition needs to include resolution info
#184
hsolbrig
opened
9 years ago
0
ValueSetCatalogEntry should list code systems
#183
hsolbrig
opened
9 years ago
0
Need to know the code system version(s) used to create SpecificEntityList in ValueSetDefinition
#182
hsolbrig
opened
10 years ago
1
ValueSetResolution service name is inconsistent
#181
hsolbrig
opened
10 years ago
1
changeDate should be optional in Core.xsd ChangeDescription
#180
hsolbrig
opened
10 years ago
0
CTS2 needs formal mime types for different versions.
#179
hsolbrig
opened
10 years ago
0
Comment on Clause 7 regarding how the FTF will be conducted.
#178
cendle
opened
11 years ago
1
Table row 13: I am not sure this rule is fully specified, with respect to the second and third paragraphs.
#177
cendle
opened
11 years ago
1
Table row 12: I am not sure the rules for escaping are fully specified.
#176
cendle
opened
11 years ago
1
Table row 10: What happens if there are two elements having the same name, but in different namespaces, within a single parent element?
#175
cendle
opened
11 years ago
1
Table row 9: The example shows the element before the attributes.
#174
cendle
opened
11 years ago
1
Table row 7: The meaning of "Order will be preserved within the JSONArray, but not in the dictionaries." is unclear.
#173
cendle
opened
11 years ago
1
What conformance levels for CTS2 are required to be able to conform to this new conformance point?
#172
cendle
opened
11 years ago
1
Will the FTF beta document comprise the additions from this RFC integrated with the existing CTS2 spec?
#171
cendle
opened
11 years ago
1
Will the conformance clause of CTS2 spec be modified after this RFC is finalized?
#170
cendle
opened
11 years ago
1
Terms and Definitions: will any of these terms be added to the CTS2 spec after this RFC is finalized?
#169
cendle
opened
11 years ago
1
Normative References: add reference to XML specification.
#168
cendle
opened
11 years ago
1
OMG Issue 18871: SpecificEntityList description is incorrect
#167
hsolbrig
opened
11 years ago
0
OMG Issue 18872: Documentation is incorrect in SpecificEntityList class
#166
hsolbrig
opened
11 years ago
0
OMG Issue 18866: Children / Descendants use inconsistent with Value Set Definition
#165
hsolbrig
opened
11 years ago
0
OMG Issue 18867: ConceptDomain Binding has no property attribute
#164
hsolbrig
opened
11 years ago
0
OMG Issue 18868: EntityDescription lacks workflow status entry
#163
hsolbrig
opened
11 years ago
0
OMG Issue 18851: ValueSetDefinitionListEntry in ValueSetDefinition.xsd has wrong cardinality
#162
kevinpeterson
opened
11 years ago
0
OMG Issue 18853: ResourceList entries have double "entry" items
#161
hsolbrig
opened
11 years ago
0
OMG Issue 18852: Wrong type in CompleteValueSetReference (ValueSetDefinition.xsd)
#160
kevinpeterson
opened
11 years ago
0
OMG Issue 18689: ValueSetDefinitionResolution 'resolve' method has incorrect return type.
#159
kevinpeterson
opened
11 years ago
1
OMG Issue 18682: Type of maxtoreturn is string in the WADL definitions. It should be NaturalNumber (or equiv)
#158
hsolbrig
opened
11 years ago
1
OMG Issue 18624: Association derivation should be optional and not have a default
#157
hsolbrig
opened
11 years ago
1
OMG Issue 18622: AssociationDirectory needs the derivation
#156
hsolbrig
opened
11 years ago
1
OMG Issue 18610: Resource content filtering for Query
#155
kevinpeterson
opened
11 years ago
2
OMG Issue 18562: MapTargetList and MapTargetListList need a 'Message' wrapper for REST calls
#154
kevinpeterson
opened
11 years ago
1
OMG Issue 18563: MapEntry Read and Resolution need WADL 'byURI' REST signatures
#153
kevinpeterson
opened
11 years ago
1
OMG Issue 18564: WADL Graph URLs need to change to better reflect AssociationDirectory as input.
#152
kevinpeterson
opened
11 years ago
1
OMG Issue 18541: Filter PropertyReference documentation needs clarification
#151
hsolbrig
opened
11 years ago
3
OMG Issue 18542: Cardinality of includesResolvedValueSet wrong on ResolvedValueSetHeader
#150
hsolbrig
opened
11 years ago
2
OMG Issue 18534: Complete binding operation missing from specification
#149
hsolbrig
opened
11 years ago
3
OMG Issue 18530: CTS2Exception doesn't match documentation
#148
hsolbrig
opened
11 years ago
1
OMG Issue 18531: IteratableResolvedValueSet and ResolvedValueSet have inconsistent element names
#147
hsolbrig
opened
11 years ago
1
OMG Issue 18519: Usage Context Binding Inappropriately Expressed
#146
cendle
opened
11 years ago
1
OMG Issue 18518: Using enumerations instead of using code systems
#145
cendle
opened
11 years ago
2
OMG Issue 18517: Need an optional attribute to carry the OID in addition to the URI
#144
cendle
opened
11 years ago
2
OMG Issue 18532: URIAndEntityName references should all be changed to EntitySynopsis, allowing an optional description
#143
hsolbrig
opened
11 years ago
1
OMG Issue 18469: "entityType" description text incorrect - needs to be updated
#142
hsolbrig
opened
11 years ago
2
OMG Issue 18470: referencedEntity in Value Set Definitions should include an optional description
#141
hsolbrig
opened
11 years ago
1
OMG Issue 18471: "SourceAndNotation" should be made optional in resource version
#140
hsolbrig
opened
11 years ago
1
OMG Issue 18472: "documentURI" attribute description in ResourceVersionDescription is incorrect
#139
hsolbrig
opened
11 years ago
1
OMG Issue 18473: DocumentURI shouldn't be mandatory in ResourceVersionDescription
#138
hsolbrig
opened
11 years ago
1
OMG Issue 18474: Extensible Directories - Allow directories to be extended.
#137
hsolbrig
opened
11 years ago
3
Next