sdmx-twg/sdmx-json

Issues

• Possible inconsistency regarding coded attributes/measures with array values

  #164 opened 4 months ago by achronis
  1

• Time and time zone requirements vs SDMX-ML

  #161 opened 4 months ago by hoehrmann
  0

• If `data` and `errors` are mutually exclusive, then where do warnings go?

  #163 opened 4 months ago by hoehrmann
  0

• `meta` and `errors` should be annotable

  #162 opened 4 months ago by hoehrmann
  0

• Deprecate using artefact types as link relations

  #160 opened 4 months ago by hoehrmann
  0

• How are `s:GenericDataflow` elements represented?

  #159 opened 5 months ago by hoehrmann
  0

• Missing `validFrom`/`validTo` properties on `TimeRangeValue`

  #158 opened 5 months ago by hoehrmann
  0

• Confusing ID inheritance remark

  #157 opened 5 months ago by hoehrmann
  0

• Dimension group relationships no longer resolved

  #156 opened 5 months ago by hoehrmann
  0

• Unclear representation of metadata in data messages

  #154 opened 5 months ago by hoehrmann
  0

• Attribute relationship vs attachment level

  #155 opened 5 months ago by hoehrmann
  0

• Use `$defs` instead of `$.definitions` in JSON Schemas.

  #153 opened 5 months ago by hoehrmann
  0

• Bad schema for `dimValues`

  #151 opened 5 months ago by hoehrmann
  1

• Invalid regex pattern for `StandardTimePeriodType`

  #152 opened 5 months ago by hoehrmann
  0

• `valueArray` schema requires `oneOf` `integer` xor `number`

  #150 opened 5 months ago by hoehrmann
  0

• `name` and `description` on `$.data.structures[*]`

  #149 opened 5 months ago by hoehrmann
  0

• Proposal to reference DSD from data message via `agencyID` and `version`

  #145 opened 5 months ago by hoehrmann
  4

• `timeDimension.localRepresentation` should be optional

  #148 opened 5 months ago by hoehrmann
  0

• `contentLanguages` disallows most non-lowercase language identifiers

  #147 opened 5 months ago by hoehrmann
  1

• Coded TIME_PERIOD?

  #146 opened 5 months ago by hoehrmann
  0

• Attribute `attributeRelationship` cannot be required for MSD attributes

  #144 opened 5 months ago by hoehrmann
  0

• `conceptScheme` `parent` is ID reference, but text says URN

  #143 opened 5 months ago by hoehrmann
  0

• Implementation considerations for datatype handling

  #142 opened 6 months ago by hoehrmann
  0

• Revisit decision to make `keyPosition` mandatory for dimensions

  #141 opened 6 months ago by hoehrmann
  0

• Proposal: Enhance Annotation Referencing in SDMX-JSON Data Messages

  #140 opened 6 months ago by hoehrmann
  0

• `annotation.value` vs. `annotation.text`

  #139 opened 6 months ago by hoehrmann
  0

• Weird bit of text at the end of `dataType` definition

  #138 opened 6 months ago by hoehrmann
  0

• Are `minOccurs != 1`, `maxOccurs != 1` measures and attributes always arrays?

  #136 opened 6 months ago by hoehrmann
  2

• SDMX Registry types (or entire specification for registry messages) missing.

  #137 opened 6 months ago by hoehrmann
  0

• Use root-level `$schema` instead of `meta.schema`

  #135 opened 6 months ago by hoehrmann
  0

• Language identifier information loss converting SDMX-JSON to SDMX-ML

  #134 opened 6 months ago by hoehrmann
  0

• Schema incorrectly requires `name` property on items / ItemScheme artefacts

  #133 opened 6 months ago by hoehrmann
  0

• Missing definition of `isConceptRole`

  #132 opened 6 months ago by hoehrmann
  0

• `AttributeRelationshipType` `oneOf` lacks `measures`

  #131 opened 6 months ago by hoehrmann
  0

• Bad definition of `primaryMeasure`

  #130 opened 6 months ago by hoehrmann
  0

• Bad description of uri data type in schema

  #129 opened 6 months ago by hoehrmann
  0

• Misleading definition of required properties on links

  #128 opened 6 months ago by hoehrmann
  0

• SDMX-JSON schema erroneously requires `meta` property

  #127 opened 6 months ago by hoehrmann
  0

• Proposal to make Sender Metadata Field optional

  #126 opened 6 months ago by hoehrmann
  0

• SDMX-JSON v2.0.0 data message schema erroneously requires `data.dataSets.[*].links`

  #125 opened 6 months ago by hoehrmann
  0

• Reference Metadata attributeType - value discrepency with XML Schema

  #123 opened a year ago by agent96
  3

• Handling of missing values

  #122 opened 3 years ago by dosse
  0

• Bug in structure-message/samples/generated-sample.json: incorrect textFormat property

  #121 opened 3 years ago by dosse
  1

• Correct referential metadata samples

  #120 opened 3 years ago by dosse
  0

• Clarify error codes to be used

  #117 opened 3 years ago by dosse
  0

• Issues in json formats

  #116 opened 3 years ago by dosse
  0

• Unclear source of min/maxOccurs property present in JSON schema of ConceptRepresentationType

  #124 opened a year ago by buhaiovos
  3

• SDMX-JSON 1.0 data message schema misses boolean and integer data types

  #104 opened 3 years ago by dosse
  1

• SDMX 3.0 question about versioning, urn in OrganisationScheme family of artefacts

  #106 opened 3 years ago by achronis
  4

• SDMX 3.0.0 / SDMX JSON 2.0.0 possible inconsistency in CodelistExtension

  #107 opened 3 years ago by achronis
  3