Skip to content

Commit

Permalink
Releasing SDMX-JSON 2.0.0 for SDMX 3.0.0 (#113)
Browse files Browse the repository at this point in the history
* Create browse-by-topic.md

* Initial release of the browse-by-topic requirement

* Update browse-by-topic.md

* Minor edits

* Fixed typo

* Sample file for step 1 of browse-by-topic use case

* Sample for step 1 of browse-by-topic - hateoas

* Made URLs generic & added reference resolution

* Changed images alt text

* Added list of matching series

* Reviewed format for step 1

* Added sample file for step 2

* Minor formatting changes

* Changed message IDs

* Add large sample for step 3.

* References now handled as HATEOAS links

* References to DSDs now handled as HATEOAS links

* Moved to a two-queries approach

* Explain why categorisations are not used

* Minor edits

* Artefacts resolution now taken into account

* Update step1.json

* Update step1.json

* Create 0-status.md (#20)

* first Jens test

* Update Json Message for Hierarchy of Categories (#42)

* Update step1.json

* Remove inappropriate link in the header

* Doc/jens (#43)

* New field guide for SDMX JSON structure message format.
* Reference document for SDMX JSON structure message format.

* Corrected small grammatical errors.

* adding missing properties (#45)

* Updated structure content description

* Update README.md

* Update README.md

* Update README.md

* Update step1-hateoas.json

* Update step1.json

* Update step2.json

* Update step3.json

* Update 1-sdmx-json-field-guide.md

Corrected a formatting glitch.

* Update 1-sdmx-json-field-guide.md

Shortened field guide structure and further developed explanations to facilitate comprehension.
Fixed issue #8 (Allow links also in components)

* Update 1-sdmx-json-field-guide.md

Corrected newly introduced errors in document bookmarks.
Fixed issue #33 (SDMX-Json data messages DataStructure/Dataflow reference/URN).
Added "hreflang" name to link object as response to issue #40 (properties for language used in structure and possibly data SDMX JSON messages) .

* Update 1-sdmx-json-field-guide.md

Correction in example text formatting.

* Update 1-sdmx-json-field-guide.md

Include changes for issue #38 for attachment of annotations to observations, components and component values

* Update 1-sdmx-json-field-guide.md

Update for #8 adding links for component values, and replacing uri by standard links mechanism in annotations

* Update 1-sdmx-json-field-guide.md

Implemented agreed improvement related to issue #38: Highlight sentence explaining the constraint for positions of attributes when including annotations for observations.

* #8 support for links in Component (#51)

Changed schema in order to allow links in Component
(Partly) update schema for issue #8

* Update sdmx-json-data-schema.json

Completed update of schema for issue #8

* Update 1-sdmx-json-field-guide.md

Highlighted recommendation for issue #33.

* #33 links in examples (#49)

Updated examples for issue #33

* Update 1-sdmx-json-field-guide.md

Updated inline examples with annotations for issue #38. Complemented/corrected descriptions related to annotations.

* Update 3-full-example-with-comments.md

Updates for issue #38 "Attachment of annotations"

* Update sdmx-json-data-schema.json

Updated schema for issue #38 (Attachment of annotations)

* Update exr-cross-section.json

Updated example for issue #38 (Attachment of annotations)

* Update exr-flat.json

Updated example for issue #38 (Attachment of annotations)

* Update exr-time-series.json

Updated example for issue #38 (Attachment of annotations)

* Update 1-sdmx-json-field-guide.md (#52)

* Update 1-sdmx-json-field-guide.md

Proposal to not include SDMX-JSON version as mandatory but a recommendation should be made to add information of the SDMX-JSON version as done by other standards (e.g. html). Do this by aligning with JSON-API standard with:
-	new optional top-level meta tag replacing the current header tag to specify SDMX-JSON schema, which contains the SDMX-JSON format version number
-	new top-level data tag under which the current structure and dataSets tags are grouped
-	the already existing top-level errors tag is updated

* Update sdmx-json-data-schema.json

Changed to align with SDMX-API spec (linked to implementation for #37)

* Update 1-sdmx-json-field-guide.md

#46 : Make keyPosition mandatory for dimensions.

* Update sdmx-json-data-schema.json

#46 and other bug corrections

* Update 2-references.md

Align to SDMX-API specification

* Update 1-sdmx-json-field-guide.md

Implement solution for #40

* Update sdmx-json-data-schema.json

Implementation of solution for #40

* Update 3-full-example-with-comments.md

Implement solution for #40

* Update exr-action-delete.json

Implementation of solution of #40

* Update exr-cross-section.json

Implementation of solution of #40

* Update exr-flat.json

Implementation of solution of #40

* Update exr-time-series.json

Implementation of solution of #40

* Update sdmx-json-data-schema.json

First changes for #30

* Update and rename data-message/tools/schemas/sdmx-json-data-schema.json to data-message/tools/schemas/1.0/sdmx-json-data-schema.json

Implementation of solution for #30 (regular expression validation)
Also corrected bugs

* Update exr-action-delete.json

Bug correction for #46

* Update exr-cross-section.json

Bug correction for #46

* Update exr-flat.json

Bug correction for #46

* Update exr-time-series.json

Bug correction for #46

* Update 3-full-example-with-comments.md

Corrected bug for #46

* Update sdmx-json-data-schema.json

Corrected bug that prevented following feature:
An attribute value of "null" can be used to reduce the message size by using the index of the attribute value in the data part of the message (instead of "null").

* Update sdmx-json-data-schema.json

Undo previous change as it wasn't correct.

* Update 3-full-example-with-comments.md

Bug correction for attribute value specification

* Update 1-sdmx-json-field-guide.md

Replaced resources and references with properties of one single Data object, one for each returned artefact. This will allow for a more in-depth content validation with a JSON schema. Using multiple languages. Changes not yet finished.

* Update 1-sdmx-json-field-guide.md

More changes: Changed "nullable" to "optional"

* Create sdmx-json-structure-schema.json

First version, more changes to come

* Update sdmx-json-structure-schema.json

More changes, and more still to come

* Update 1-sdmx-json-field-guide.md

More changes, and more to come...

* Update 1-sdmx-json-field-guide.md

Changes to align with structure message (in progress) and simplify use and specs for languages.

* Update sdmx-json-structure-schema.json

* Update sdmx-json-data-schema.json

Changes to align with structure message (in progress) and simplify use and specs for languages.

* Update exr-action-delete.json

Changes to align with structure message (in progress) and simplify use and specs for languages.

* Update exr-cross-section.json

Changes to align with structure message (in progress) and simplify use and specs for languages.

* Update exr-flat.json

Changes to align with structure message (in progress) and simplify use and specs for languages.

* Update exr-time-series.json

Changes to align with structure message (in progress) and simplify use and specs for languages.

* Update sdmx-json-data-schema.json

Correction for content-language because RFC standard doesn't include q weights. Therefore simplification of language specification without weights.

* Update 1-sdmx-json-field-guide.md

Correction for content-language because RFC standard doesn't include q weights. Therefore simplification of language specification without weights.

* Update 3-full-example-with-comments.md

Correction for content-language because RFC standard doesn't include q weights. Therefore simplification of language specification without weights.

* Update exr-action-delete.json

Correction for content-language because RFC standard doesn't include q weights. Therefore simplification of language specification without weights.

* Update exr-cross-section.json

Correction for content-language because RFC standard doesn't include q weights. Therefore simplification of language specification without weights.

* Update exr-flat.json

Correction for content-language because RFC standard doesn't include q weights. Therefore simplification of language specification without weights.

* Update exr-time-series.json

Correction for content-language because RFC standard doesn't include q weights. Therefore simplification of language specification without weights.

* Update 1-sdmx-json-field-guide.md

Correction for content-language because RFC standard doesn't include q weights. Therefore simplification of language specification without weights.

* Update sdmx-json-structure-schema.json

Work ongoing...

* Update 1-sdmx-json-field-guide.md

Work ongoing...

* Update 1-sdmx-json-field-guide.md

Correction for annotation title

* Update 1-sdmx-json-field-guide.md

Added possibility to include parent and order number for component values to allow for reconstructing component value hierarchies.

* Update 3-full-example-with-comments.md

Added possibility to include parent and order number for component values to allow for reconstructing component value hierarchies.

* Update sdmx-json-data-schema.json

Added possibility to include parent and order number for component values to allow for reconstructing component value hierarchies.

* Update exr-flat.json

Added possibility to include parent and order number for component values to allow for reconstructing component value hierarchies.

* Update exr-time-series.json

Added possibility to include parent and order number for component values to allow for reconstructing component value hierarchies.

* Update exr-action-delete.json

Added possibility to include parent and order number for component values to allow for reconstructing component value hierarchies.

* Update exr-cross-section.json

Added possibility to include parent and order number for component values to allow for reconstructing component value hierarchies.

* Update sdmx-json-structure-schema.json

Added codelist, categoryscheme and conceptscheme

* Update 1-sdmx-json-field-guide.md

Added codelist, categoryscheme and conceptscheme.
Treating urn and uri inside the links objects including one link for "self".

* Update 1-sdmx-json-field-guide.md

Some corrections.

* Update sdmx-json-structure-schema.json

Some corrections.

* Update 1-sdmx-json-field-guide.md

Replace component value's parent property object by string, to be consistent with SDMX-JSON structure message.

* Update 1-sdmx-json-field-guide.md

Completed with most frequent artefact types. 
Remaining artefacts are defined in schema: metadataStructures, hierarchicalCodelists, dataProviderSchemes, dataConsumerSchemes, organisationUnitSchemes, metadataflows, reportingTaxonomies, provisionAgreements, structureSets, processes

* Update 1-sdmx-json-field-guide.md

Formatting corrections

* Update sdmx-json-structure-schema.json

Completed schema for all structural artefact types.

* Update sdmx-json-structure-schema.json

Formatting correction

* Create generated-sample.json

Sample generated automatically from json schema.

* Update sdmx-json-data-schema.json

Correction to parent item specification.

* Create 1-sdmx-json-field-guide.md

First draft

* Update 1-sdmx-json-field-guide.md

Small corrections/improvements

* Update 1-sdmx-json-field-guide.md

Alignment with structure and metadata messages on management of human-readable localised names

* Update 1-sdmx-json-field-guide.md

Correction

* Update 1-sdmx-json-field-guide.md

Correction

* Update sdmx-json-data-schema.json

Make data message consistent with structure and metadata message for human-readable names

* Update 1-sdmx-json-field-guide.md

Correction

* Update sdmx-json-data-schema.json

Complement links

* Update sdmx-json-structure-schema.json

* Create sdmx-json-metadata-schema.json

* Update sdmx-json-data-schema.json

* Update sdmx-json-structure-schema.json

Simplified groupDimensions to simply array of dimension IDs.
Href not mandatory in links anymore, but links to have at least href or urn.

* Create constructed-sample

* Create constructed-sample.json

* Delete constructed-sample

* Update 1-sdmx-json-field-guide.md

Corrections/additions to ItemScheme/Item documentation.

* Update constructed-sample.json

Correction

* Update sdmx-json-structure-schema.json

Removed "id", "version" and "agencyID" properties from “ConceptRepresentation” type used for Concept definitions (because its “enumeration” property already contains the URN which holds the same information). Consistently, the SDMX-JSON format only uses URNs for referencing other artefacts rather than separate "id", "version" and "agencyID" properties.
Removed the “ISOConceptReferenceType” type. The “isoConceptReference” property of the “ConceptType” type is thus now taking just a simple URN rather than that “ISOConceptReferenceType” object.

* Update 1-sdmx-json-field-guide.md

* Create constructed-sample2

* Update sdmx-json-metadata-schema.json

* Update constructed-sample2

* Create constructed-sample

* Create generated-sample

* Update sdmx-json-metadata-schema.json

* format alignment for localised strings, added attribute relationship (#56)

* Update 1-sdmx-json-field-guide.md

Proposal to not include SDMX-JSON version as mandatory but a recommendation should be made to add information of the SDMX-JSON version as done by other standards (e.g. html). Do this by aligning with JSON-API standard with:
-	new optional top-level meta tag to specify SDMX-JSON version, this tag can contain the SDMX-JSON version number
-	new top-level data tag under which the current header, structure and dataSets tags should be grouped
-	the already existing top-level errors tag would need to be updated

* Update 1-sdmx-json-field-guide.md

* Update 1-sdmx-json-field-guide.md

* Update 1-sdmx-json-field-guide.md

* Update 3-full-example-with-comments.md

* Update sdmx-json-data-schema.json

* Rename data-message/tools/schemas/sdmx-json-data-schema.json to data-message/tools/schemas/1.0/sdmx-json-data-schema.json

* Update exr-action-delete.json

* Update exr-cross-section.json

* Update exr-action-delete.json

* Update 3-full-example-with-comments.md

* Update exr-flat.json

* Update exr-time-series.json

* Create agri.json

* Update 1-sdmx-json-field-guide.md

* Added attribute relationship and structure format changes (#57)

* Update sdmx-json-data-schema.json

Added AttributeRelationship (by copying similar structure construct from new SDMX-JSON structure message draft but removing all group references - this means groups should already be resolved into a list of dimensions by the server for the client)

* Update sdmx-json-structure-schema.json

Simplified groupDimensions to simply array of dimension IDs.
Href not mandatory in links anymore, but links to have at least href or urn.

* Update 1-sdmx-json-field-guide.md

* Update sdmx-json-data-schema.json

* Update sdmx-json-data-schema.json

* Update 1-sdmx-json-field-guide.md

* Update sdmx-json-structure-schema.json

* Update 1-sdmx-json-field-guide.md

* Update sdmx-json-data-schema.json

* Update sdmx-json-metadata-schema.json

* Update README.md

* Update README.md

* Update 1-sdmx-json-field-guide.md

Corrected formatting and writing mistakes

* Update 1-sdmx-json-field-guide.md

* Update 1-sdmx-json-field-guide.md

* first full release

* Add type prop to contentconstraint (#60)

* Corrected generated example for contentconstraint definition and other bugs

* Finished contentconstraint correction #59

* Corrected content constraint type #59, other small bugs and cleaning of unused definitions

* Corrected contentconstraints #59

* Corrected contentconstraint #59

* Still #59

* Generic language management (#62)

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Delete TODO.md

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Delete step1-hateoas.json

* Delete step1.json

* Delete step2.json

* Delete step3.json

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Added mention of metadata message

* Update sdmx-json-structure-schema.json (#68)

Fix for #66

* Patch for 72 for structures (merge into dev branch since structures are not yet released) (#79)

* Correct inconsistency in 'attributeRelationship' definition in structure message

Solves #72

* Correct conceptRoles

* Update sdmx-json-structure-schema.json

Fixing #72

* Sdmx3.0.0 (#102)

* Release 1.0 of data message (#65)

* Create browse-by-topic.md

* Initial release of the browse-by-topic requirement

* Update browse-by-topic.md

* Minor edits

* Fixed typo

* Sample file for step 1 of browse-by-topic use case

* Sample for step 1 of browse-by-topic - hateoas

* Made URLs generic & added reference resolution

* Changed images alt text

* Added list of matching series

* Reviewed format for step 1

* Added sample file for step 2

* Minor formatting changes

* Changed message IDs

* Add large sample for step 3.

* References now handled as HATEOAS links

* References to DSDs now handled as HATEOAS links

* Moved to a two-queries approach

* Explain why categorisations are not used

* Minor edits

* Artefacts resolution now taken into account

* Update step1.json

* Update step1.json

* Create 0-status.md (#20)

* first Jens test

* Update Json Message for Hierarchy of Categories (#42)

* Update step1.json

* Remove inappropriate link in the header

* Doc/jens (#43)

* New field guide for SDMX JSON structure message format.
* Reference document for SDMX JSON structure message format.

* Corrected small grammatical errors.

* adding missing properties (#45)

* Updated structure content description

* Update README.md

* Update README.md

* Update README.md

* Update step1-hateoas.json

* Update step1.json

* Update step2.json

* Update step3.json

* Update 1-sdmx-json-field-guide.md

Corrected a formatting glitch.

* Update 1-sdmx-json-field-guide.md

Shortened field guide structure and further developed explanations to facilitate comprehension.
Fixed issue #8 (Allow links also in components)

* Update 1-sdmx-json-field-guide.md

Corrected newly introduced errors in document bookmarks.
Fixed issue #33 (SDMX-Json data messages DataStructure/Dataflow reference/URN).
Added "hreflang" name to link object as response to issue #40 (properties for language used in structure and possibly data SDMX JSON messages) .

* Update 1-sdmx-json-field-guide.md

Correction in example text formatting.

* Update 1-sdmx-json-field-guide.md

Include changes for issue #38 for attachment of annotations to observations, components and component values

* Update 1-sdmx-json-field-guide.md

Update for #8 adding links for component values, and replacing uri by standard links mechanism in annotations

* Update 1-sdmx-json-field-guide.md

Implemented agreed improvement related to issue #38: Highlight sentence explaining the constraint for positions of attributes when including annotations for observations.

* #8 support for links in Component (#51)

Changed schema in order to allow links in Component
(Partly) update schema for issue #8

* Update sdmx-json-data-schema.json

Completed update of schema for issue #8

* Update 1-sdmx-json-field-guide.md

Highlighted recommendation for issue #33.

* #33 links in examples (#49)

Updated examples for issue #33

* Update 1-sdmx-json-field-guide.md

Updated inline examples with annotations for issue #38. Complemented/corrected descriptions related to annotations.

* Update 3-full-example-with-comments.md

Updates for issue #38 "Attachment of annotations"

* Update sdmx-json-data-schema.json

Updated schema for issue #38 (Attachment of annotations)

* Update exr-cross-section.json

Updated example for issue #38 (Attachment of annotations)

* Update exr-flat.json

Updated example for issue #38 (Attachment of annotations)

* Update exr-time-series.json

Updated example for issue #38 (Attachment of annotations)

* Update 1-sdmx-json-field-guide.md (#52)

* Update 1-sdmx-json-field-guide.md

Proposal to not include SDMX-JSON version as mandatory but a recommendation should be made to add information of the SDMX-JSON version as done by other standards (e.g. html). Do this by aligning with JSON-API standard with:
-	new optional top-level meta tag replacing the current header tag to specify SDMX-JSON schema, which contains the SDMX-JSON format version number
-	new top-level data tag under which the current structure and dataSets tags are grouped
-	the already existing top-level errors tag is updated

* Update sdmx-json-data-schema.json

Changed to align with SDMX-API spec (linked to implementation for #37)

* Update 1-sdmx-json-field-guide.md

#46 : Make keyPosition mandatory for dimensions.

* Update sdmx-json-data-schema.json

#46 and other bug corrections

* Update 2-references.md

Align to SDMX-API specification

* Update 1-sdmx-json-field-guide.md

Implement solution for #40

* Update sdmx-json-data-schema.json

Implementation of solution for #40

* Update 3-full-example-with-comments.md

Implement solution for #40

* Update exr-action-delete.json

Implementation of solution of #40

* Update exr-cross-section.json

Implementation of solution of #40

* Update exr-flat.json

Implementation of solution of #40

* Update exr-time-series.json

Implementation of solution of #40

* Update sdmx-json-data-schema.json

First changes for #30

* Update and rename data-message/tools/schemas/sdmx-json-data-schema.json to data-message/tools/schemas/1.0/sdmx-json-data-schema.json

Implementation of solution for #30 (regular expression validation)
Also corrected bugs

* Update exr-action-delete.json

Bug correction for #46

* Update exr-cross-section.json

Bug correction for #46

* Update exr-flat.json

Bug correction for #46

* Update exr-time-series.json

Bug correction for #46

* Update 3-full-example-with-comments.md

Corrected bug for #46

* Update sdmx-json-data-schema.json

Corrected bug that prevented following feature:
An attribute value of "null" can be used to reduce the message size by using the index of the attribute value in the data part of the message (instead of "null").

* Update sdmx-json-data-schema.json

Undo previous change as it wasn't correct.

* Update 3-full-example-with-comments.md

Bug correction for attribute value specification

* Update 1-sdmx-json-field-guide.md

Replaced resources and references with properties of one single Data object, one for each returned artefact. This will allow for a more in-depth content validation with a JSON schema. Using multiple languages. Changes not yet finished.

* Update 1-sdmx-json-field-guide.md

More changes: Changed "nullable" to "optional"

* Create sdmx-json-structure-schema.json

First version, more changes to come

* Update sdmx-json-structure-schema.json

More changes, and more still to come

* Update 1-sdmx-json-field-guide.md

More changes, and more to come...

* Update 1-sdmx-json-field-guide.md

Changes to align with structure message (in progress) and simplify use and specs for languages.

* Update sdmx-json-structure-schema.json

* Update sdmx-json-data-schema.json

Changes to align with structure message (in progress) and simplify use and specs for languages.

* Update exr-action-delete.json

Changes to align with structure message (in progress) and simplify use and specs for languages.

* Update exr-cross-section.json

Changes to align with structure message (in progress) and simplify use and specs for languages.

* Update exr-flat.json

Changes to align with structure message (in progress) and simplify use and specs for languages.

* Update exr-time-series.json

Changes to align with structure message (in progress) and simplify use and specs for languages.

* Update sdmx-json-data-schema.json

Correction for content-language because RFC standard doesn't include q weights. Therefore simplification of language specification without weights.

* Update 1-sdmx-json-field-guide.md

Correction for content-language because RFC standard doesn't include q weights. Therefore simplification of language specification without weights.

* Update 3-full-example-with-comments.md

Correction for content-language because RFC standard doesn't include q weights. Therefore simplification of language specification without weights.

* Update exr-action-delete.json

Correction for content-language because RFC standard doesn't include q weights. Therefore simplification of language specification without weights.

* Update exr-cross-section.json

Correction for content-language because RFC standard doesn't include q weights. Therefore simplification of language specification without weights.

* Update exr-flat.json

Correction for content-language because RFC standard doesn't include q weights. Therefore simplification of language specification without weights.

* Update exr-time-series.json

Correction for content-language because RFC standard doesn't include q weights. Therefore simplification of language specification without weights.

* Update 1-sdmx-json-field-guide.md

Correction for content-language because RFC standard doesn't include q weights. Therefore simplification of language specification without weights.

* Update sdmx-json-structure-schema.json

Work ongoing...

* Update 1-sdmx-json-field-guide.md

Work ongoing...

* Update 1-sdmx-json-field-guide.md

Correction for annotation title

* Update 1-sdmx-json-field-guide.md

Added possibility to include parent and order number for component values to allow for reconstructing component value hierarchies.

* Update 3-full-example-with-comments.md

Added possibility to include parent and order number for component values to allow for reconstructing component value hierarchies.

* Update sdmx-json-data-schema.json

Added possibility to include parent and order number for component values to allow for reconstructing component value hierarchies.

* Update exr-flat.json

Added possibility to include parent and order number for component values to allow for reconstructing component value hierarchies.

* Update exr-time-series.json

Added possibility to include parent and order number for component values to allow for reconstructing component value hierarchies.

* Update exr-action-delete.json

Added possibility to include parent and order number for component values to allow for reconstructing component value hierarchies.

* Update exr-cross-section.json

Added possibility to include parent and order number for component values to allow for reconstructing component value hierarchies.

* Update sdmx-json-structure-schema.json

Added codelist, categoryscheme and conceptscheme

* Update 1-sdmx-json-field-guide.md

Added codelist, categoryscheme and conceptscheme.
Treating urn and uri inside the links objects including one link for "self".

* Update 1-sdmx-json-field-guide.md

Some corrections.

* Update sdmx-json-structure-schema.json

Some corrections.

* Update 1-sdmx-json-field-guide.md

Replace component value's parent property object by string, to be consistent with SDMX-JSON structure message.

* Update 1-sdmx-json-field-guide.md

Completed with most frequent artefact types. 
Remaining artefacts are defined in schema: metadataStructures, hierarchicalCodelists, dataProviderSchemes, dataConsumerSchemes, organisationUnitSchemes, metadataflows, reportingTaxonomies, provisionAgreements, structureSets, processes

* Update 1-sdmx-json-field-guide.md

Formatting corrections

* Update sdmx-json-structure-schema.json

Completed schema for all structural artefact types.

* Update sdmx-json-structure-schema.json

Formatting correction

* Create generated-sample.json

Sample generated automatically from json schema.

* Update sdmx-json-data-schema.json

Correction to parent item specification.

* Create 1-sdmx-json-field-guide.md

First draft

* Update 1-sdmx-json-field-guide.md

Small corrections/improvements

* Update 1-sdmx-json-field-guide.md

Alignment with structure and metadata messages on management of human-readable localised names

* Update 1-sdmx-json-field-guide.md

Correction

* Update 1-sdmx-json-field-guide.md

Correction

* Update sdmx-json-data-schema.json

Make data message consistent with structure and metadata message for human-readable names

* Update 1-sdmx-json-field-guide.md

Correction

* Update sdmx-json-data-schema.json

Complement links

* Update sdmx-json-structure-schema.json

* Create sdmx-json-metadata-schema.json

* Update sdmx-json-data-schema.json

* Update sdmx-json-structure-schema.json

Simplified groupDimensions to simply array of dimension IDs.
Href not mandatory in links anymore, but links to have at least href or urn.

* Create constructed-sample

* Create constructed-sample.json

* Delete constructed-sample

* Update 1-sdmx-json-field-guide.md

Corrections/additions to ItemScheme/Item documentation.

* Update constructed-sample.json

Correction

* Update sdmx-json-structure-schema.json

Removed "id", "version" and "agencyID" properties from “ConceptRepresentation” type used for Concept definitions (because its “enumeration” property already contains the URN which holds the same information). Consistently, the SDMX-JSON format only uses URNs for referencing other artefacts rather than separate "id", "version" and "agencyID" properties.
Removed the “ISOConceptReferenceType” type. The “isoConceptReference” property of the “ConceptType” type is thus now taking just a simple URN rather than that “ISOConceptReferenceType” object.

* Update 1-sdmx-json-field-guide.md

* Create constructed-sample2

* Update sdmx-json-metadata-schema.json

* Update constructed-sample2

* Create constructed-sample

* Create generated-sample

* Update sdmx-json-metadata-schema.json

* format alignment for localised strings, added attribute relationship (#56)

* Update 1-sdmx-json-field-guide.md

Proposal to not include SDMX-JSON version as mandatory but a recommendation should be made to add information of the SDMX-JSON version as done by other standards (e.g. html). Do this by aligning with JSON-API standard with:
-	new optional top-level meta tag to specify SDMX-JSON version, this tag can contain the SDMX-JSON version number
-	new top-level data tag under which the current header, structure and dataSets tags should be grouped
-	the already existing top-level errors tag would need to be updated

* Update 1-sdmx-json-field-guide.md

* Update 1-sdmx-json-field-guide.md

* Update 1-sdmx-json-field-guide.md

* Update 3-full-example-with-comments.md

* Update sdmx-json-data-schema.json

* Rename data-message/tools/schemas/sdmx-json-data-schema.json to data-message/tools/schemas/1.0/sdmx-json-data-schema.json

* Update exr-action-delete.json

* Update exr-cross-section.json

* Update exr-action-delete.json

* Update 3-full-example-with-comments.md

* Update exr-flat.json

* Update exr-time-series.json

* Create agri.json

* Update 1-sdmx-json-field-guide.md

* Added attribute relationship and structure format changes (#57)

* Update sdmx-json-data-schema.json

Added AttributeRelationship (by copying similar structure construct from new SDMX-JSON structure message draft but removing all group references - this means groups should already be resolved into a list of dimensions by the server for the client)

* Update sdmx-json-structure-schema.json

Simplified groupDimensions to simply array of dimension IDs.
Href not mandatory in links anymore, but links to have at least href or urn.

* Update 1-sdmx-json-field-guide.md

* Update sdmx-json-data-schema.json

* Update sdmx-json-data-schema.json

* Update 1-sdmx-json-field-guide.md

* Update sdmx-json-structure-schema.json

* Update 1-sdmx-json-field-guide.md

* Update sdmx-json-data-schema.json

* Update sdmx-json-metadata-schema.json

* Update README.md

* Update README.md

* Update 1-sdmx-json-field-guide.md

Corrected formatting and writing mistakes

* Update 1-sdmx-json-field-guide.md

* Update 1-sdmx-json-field-guide.md

* first full release

* Add type prop to contentconstraint (#60)

* Corrected generated example for contentconstraint definition and other bugs

* Finished contentconstraint correction #59

* Corrected content constraint type #59, other small bugs and cleaning of unused definitions

* Corrected contentconstraints #59

* Corrected contentconstraint #59

* Still #59

* Generic language management (#62)

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Delete TODO.md

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Delete step1-hateoas.json

* Delete step1.json

* Delete step2.json

* Delete step3.json

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Generic language approach

as agreed by SDMX-TWG TF3 to fully respond to #40

* Added mention of metadata message

* Delete sdmx-json-metadata-schema.json

* Delete constructed-sample

* Delete constructed-sample2

* Delete generated-sample

* Delete 1-sdmx-json-field-guide.md

* Delete 0-status.md

* Delete 1-sdmx-json-field-guide.md

* Delete 2-references.md

* Delete cs-list.png

* Delete cs-treeview.png

* Delete df-filters.png

* Delete df-list.png

* Delete series-list.png

* Delete browse-by-topic.md

* Delete sdmx-json-structure-schema.json

* Delete constructed-sample.json

* Delete generated-sample.json

* Update README.md

* Update README.md

* Update README.md

* Update sdmx-json-data-schema.json (#67)

Fix 1 for #66

* Fix minor typos (#70)

* Patch for 72 for data (merge into master branch since data are already released) (#80)

* Update 1-sdmx-json-field-guide.md

Fixing #72 for data

* Update sdmx-json-data-schema.json

Fixing #72 for data

* Update sdmx-json-data-schema.json

Fixing #72 for data

* Update 1-sdmx-json-field-guide.md

Fixing #72 for data

* Patch for 75 (#81)

* Update sdmx-json-data-schema.json

Fixing #75

* Update 1-sdmx-json-field-guide.md

Fixing #75

* Patch for #76 (#77)

* Update sdmx-json-data-schema.json

Fixing #76

* Update 1-sdmx-json-field-guide.md

Fixing #76

* Structure message release (#84)

* Update README.md
* Create sdmx-json-structure-schema.json
* Create generated-sample.json
* Create constructed-sample.json
* Create browse-by-topic.md
* Delete cs-list[1].png
* Add files via upload
* Create 0-status.md
* Create 1-sdmx-json-field-guide.md
* Create 2-references.md

Correction for content constraint type and uri/urn
Removed incorrect start and end properties from 'Item' artefact.

* Create 1-sdmx-json-field-guide.md

* Update 1-sdmx-json-field-guide.md

* Create sdmx-json-metadata-schema.json

* Update 1-sdmx-json-field-guide.md

* Update sdmx-json-metadata-schema.json

* Update sdmx-json-metadata-schema.json

* Update 1-sdmx-json-field-guide.md

* Update 1-sdmx-json-field-guide.md

WIP

* Update sdmx-json-metadata-schema.json

* Update sdmx-json-metadata-schema.json

* Update sdmx-json-data-schema.json

* Update 1-sdmx-json-field-guide.md

* Update 1-sdmx-json-field-guide.md

* Update sdmx-json-data-schema.json

* Update sdmx-json-data-schema.json

* Update 1-sdmx-json-field-guide.md

* Update 1-sdmx-json-field-guide.md

* Update sdmx-json-data-schema.json

* Update 0-status.md

* Update 2-references.md

* Create generated-sample.json

* Delete 3-full-example-with-comments.md

* Create constructed-sample-full.json

* Update sdmx-json-data-schema.json

* Update constructed-sample-full.json

* Update 1-sdmx-json-field-guide.md

* Update constructed-sample-full.json

* Update generated-sample.json

* Update sdmx-json-data-schema.json

* Update sdmx-json-data-schema.json

* Update agri.json

* Update exr-action-delete.json

* Update exr-cross-section.json

* Update exr-flat.json

* Update exr-time-series.json

* Delete TODO.md

* Create constructed-sample.json

* Update constructed-sample.json

* Create constructed-sample2.json

* Update sdmx-json-metadata-schema.json

* Create constructed-sample2.json

* Delete constructed-sample2.json

* Create generated-sample.json

* Update 1-sdmx-json-field-guide.md

#101

* Update generated-sample.json

* Update constructed-sample-full.json

* Update agri.json

* Update constructed-sample-full.json

* Update generated-sample.json

* Update exr-action-delete.json

* Update agri.json

* Update exr-cross-section.json

* Update exr-flat.json

* Update exr-time-series.json

* Update sdmx-json-data-schema.json

* Update 1-sdmx-json-field-guide.md

* Update 1-sdmx-json-field-guide.md

* Update sdmx-json-data-schema.json

* Update README.md

* Create README.md

* Update README.md

* Update 1-sdmx-json-field-guide.md

* Update 1-sdmx-json-field-guide.md

* Update 1-sdmx-json-field-guide.md

Updated list of artefacts. Updated dataStructure (without link to MSD).

* Add MSD link to DSD

* Updated MSD

* DSD dimensonlist not optional

* Update 1-sdmx-json-field-guide.md

* MetadataStructure corrections

* Create sdmx-json-structure-schema.json

Version 2.0.0 draft

* Update sdmx-json-structure-schema.json

Changed assignmentstatus to isMandatory boolean property for attributes and added isMandatory boolean property for measures.

* Update sdmx-json-structure-schema.json

Removed unused abstract TextFormatType

* Update sdmx-json-structure-schema.json

Completing "isMandatory" for ReportingYearStartDayType

* Update 1-sdmx-json-field-guide.md

corrections

* Update sdmx-json-structure-schema.json

maxOcccurs/minOccurs corrections/improvements

* Update sdmx-json-structure-schema.json

Attribute maxOccurs corrections

* Update sdmx-json-structure-schema.json

Bug corrections (constraint roles, typo)

* Update browse-by-topic.md

resolves #86

* Update 1-sdmx-json-field-guide.md

bug corrections for constraints

* Update README.md

* Update 1-sdmx-json-field-guide.md

Typo correction

* Update sdmx-json-structure-schema.json

Corrected SimpleComponentTextFormatType (removed isMultiLingual)
Corrected regex for timeInterval (duration)

* Update sdmx-json-data-schema.json

Corrected "format" for all components  
Corrected regex for timeInterval (duration)

* Update sdmx-json-data-schema.json

Corrections for representations

* Update sdmx-json-structure-schema.json

Corrections in representations

* Update 1-sdmx-json-field-guide.md

Corrections for representations

* Update 1-sdmx-json-field-guide.md

Corrections for representations

* Update sdmx-json-data-schema.json

Corrected allowed data types: added boolean and integer.

* Create sdmx-json-data-schema.json

Moved versioned schema file to new version directory

* Update sdmx-json-data-schema.json

Revert schema 1.0 to current master version, since each version has its own folder.

* Update 1-sdmx-json-field-guide.md

Implementation of agreed solution for https://github.com/sdmx3mdt/public-consultation/issues/14

* Update sdmx-json-data-schema.json

Implementation of agreed solution for sdmx3mdt/public-consultation#14

* Update sdmx-json-metadata-schema.json

Implementation of agreed solution for sdmx3mdt/public-consultation#14 (harmonisation with data message)

* Update 1-sdmx-json-field-guide.md

Implementation of agreed solution for sdmx3mdt/public-consultation#14 (harmonisation with data message)

* Update 1-sdmx-json-field-guide.md

Implementation of agreed solution for sdmx3mdt/public-consultation#14 (harmonisation with data message)

* Update generated-sample.json

Implementation of agreed solution for sdmx3mdt/public-consultation#14

* Update constructed-sample.json

Implementation of agreed solution for sdmx3mdt/public-consultation#14

* Update constructed-sample2.json

Implementation of agreed solution for sdmx3mdt/public-consultation#14

* Update 1-sdmx-json-field-guide.md

URN example correction

* Update sdmx-json-metadata-schema.json

Implementation of agreed solution for sdmx3mdt/public-consultation#34

* Update 1-sdmx-json-field-guide.md

Implementation of agreed solution for sdmx3mdt/public-consultation#34

* Update 1-sdmx-json-field-guide.md

Implementation of agreed solution for sdmx3mdt/public-consultation#34

* Update sdmx-json-data-schema.json

Implementation of agreed solution for sdmx3mdt/public-consultation#34

* Update 1-sdmx-json-field-guide.md

Implementation of agreed solution for sdmx3mdt/public-consultation#34

* Update sdmx-json-structure-schema.json

Implementation of agreed solution for sdmx3mdt/public-consultation#34

* Update sdmx-json-structure-schema.json

Implementation of solution for https://github.com/sdmx3mdt/public-consultation/issues/36

* Update 1-sdmx-json-field-guide.md

Implementation of solution for https://github.com/sdmx3mdt/public-consultation/issues/36

* Update 1-sdmx-json-field-guide.md

https://github.com/sdmx3mdt/public-consultation/issues/15

Change attribute relationship `none` to `dataflow`

* Update sdmx-json-data-schema.json

https://github.com/sdmx3mdt/public-consultation/issues/15

Change attribute relationship `none` to `dataflow`

* Update exr-action-delete.json

https://github.com/sdmx3mdt/public-consultation/issues/15

Change attribute relationship `none` to `dataflow`

* Update exr-cross-section.json

https://github.com/sdmx3mdt/public-consultation/issues/15

Change attribute relationship `none` to `dataflow`

* Update exr-flat.json

https://github.com/sdmx3mdt/public-consultation/issues/15

Change attribute relationship `none` to `dataflow`

* Update exr-time-series.json

https://github.com/sdmx3mdt/public-consultation/issues/15

Change attribute relationship `none` to `dataflow`

* Update agri.json

https://github.com/sdmx3mdt/public-consultation/issues/15

Change attribute relationship `none` to `dataflow`

* Update constructed-sample-full.json

https://github.com/sdmx3mdt/public-consultation/issues/15

Change attribute relationship `none` to `dataflow`

* Update generated-sample.json

https://github.com/sdmx3mdt/public-consultation/issues/15

Change attribute relationship `none` to `dataflow`

* Update 1-sdmx-json-field-guide.md

https://github.com/sdmx3mdt/public-consultation/issues/15

Change attribute relationship `none` to `dataflow`

* Update sdmx-json-structure-schema.json

https://github.com/sdmx3mdt/public-consultation/issues/15

Change attribute relationship `none` to `dataflow`

* Update 1-sdmx-json-field-guide.md

https://github.com/sdmx3mdt/public-consultation/issues/36

Clarification for separate time dimension

* Update 1-sdmx-json-field-guide.md

https://github.com/sdmx3mdt/public-consultation/issues/58

Remove ReportingYearStartDay

* Update sdmx-json-structure-schema.json

https://github.com/sdmx3mdt/public-consultation/issues/58

Remove ReportingYearStartDay

* Update sdmx-json-structure-schema.json

Corrects versionless URN for DataProvider and MetadataProvider references.

Link issue: https://github.com/sdmx-twg/sdmx-json/issues/106

* Update 1-sdmx-json-field-guide.md

https://github.com/sdmx3mdt/public-consultation/issues/38

* Update sdmx-json-structure-schema.json

* Update sdmx-json-structure-schema.json

Reverting changes for non-versioned artefacts

* Update sdmx-json-structure-schema.json

* Update sdmx-json-structure-schema.json

Implemented changes to Constraints

https://github.com/sdmx3mdt/public-consultation/issues/46

* Update sdmx-json-structure-schema.json

Bug corrections

* Update 1-sdmx-json-field-guide.md

Corrections for constraints

* Update sdmx-json-structure-schema.json

Corrections for constraints

* Update sdmx-json-structure-schema.json

corrections to mappings

* Update sdmx-json-structure-schema.json

Corrections

* Update 1-sdmx-json-field-guide.md

corrections and alignment with updated schema

* Update 1-sdmx-json-field-guide.md

header display corrections

* Update sdmx-json-structure-schema.json

Reformatted json layout

* Update sdmx-json-structure-schema.json

Changed name of DateMap property to align with proposal in https://github.com/sdmx3mdt/public-consultation/issues/53

* Update sdmx-json-structure-schema.json

Correction for https://github.com/glennmdt/sdmx-ml/issues/93

* Update sdmx-json-structure-schema.json

According to https://github.com/glennmdt/sdmx-ml/issues/94 removed all non-stub properties from the required property list of all maintainable artefacts.

* Update 1-sdmx-json-field-guide.md

Corrects for https://github.com/glennmdt/sdmx-ml/issues/97

* Update sdmx-json-structure-schema.json

Corrects for https://github.com/glennmdt/sdmx-ml/issues/97

* Update sdmx-json-structure-schema.json

https://github.com/glennmdt/sdmx-ml/issues/102

* Update 1-sdmx-json-field-guide.md

https://github.com/glennmdt/sdmx-ml/issues/102

* Update constructed-sample-full.json

Additional examples and simplifications

* Update generated-sample.json

Corrections

* Update sdmx-json-structure-schema.json

Correction for code parent type

* Update constructed-sample.json

Updated example for SDMX-JSON 2.0.0

* Update generated-sample.json

Corrected generated example to validate against schema

* Update 1-sdmx-json-field-guide.md

correction of examples

* Update 1-sdmx-json-field-guide.md

Corrections for annotations at dimensionGroup level

* Update sdmx-json-metadata-schema.json

Minor typo fix

* Update sdmx-json-data-schema.json (#105) (#108)

corrects for #104

* Update sdmx-json-structure-schema.json

Bug correction in SingleValueMappingType

* Update sdmx-json-structure-schema.json

Correction of plural form of RepresentationMapType source/target object properties

* Update sdmx-json-structure-schema.json

Bug corrections for CodeSelectionType and CascadeSelectionType

* Update generated-sample.json

Example updated to conform to SDMX-JSON 2.0.0

* Update generated-sample.json

Added "value" to "Annotations"

Co-authored-by: Xiaodong <xd_deng@hotmail.com>
Co-authored-by: Stratos Nikoloutsos <stratos.nikoloutsos@bis.org>

* SDMX 3.0.0 develop branch conflict resolution (#109)

* Release 1.0 of data message (#65)

* Create browse-by-topic.md

* Initial release of the browse-by-topic requirement

* Update browse-by-topic.md

* Minor edits

* Fixed typo

* Sample file for step 1 of browse-by-topic use case

* Sample for step 1 of browse-by-topic - hateoas

* Made URLs generic & added reference resolution

* Changed images alt text

* Added list of matching series

* Reviewed format for step 1

* Added sample file for step 2

* Minor formatting changes

* Changed message IDs

* Add large sample for step 3.

* References now handled as HATEOAS links

* References to DSDs now handled as HATEOAS links

* Moved to a two-queries approach

* Explain why categorisations are not used

* Minor edits

* Artefacts resolution now taken into account

* Update step1.json

* Update step1.json

* Create 0-status.md (#20)

* first Jens test

* Update Json Message for Hierarchy of Categories (#42)

* Update step1.json

* Remove inappropriate link in the header

* Doc/jens (#43)

* New field guide for SDMX JSON structure message format.
* Reference document for SDMX JSON structure message format.

* Corrected small grammatical errors.

* adding missing properties (#45)

* Updated structure content description

* Update README.md

* Update README.md

* Update README.md

* Update step1-hateoas.json

* Update step1.json

* Update step2.json

* Update step3.json

* Update 1-sdmx-json-field-guide.md

Corrected a formatting glitch.

* Update 1-sdmx-json-field-guide.md

Shortened field guide structure and further developed explanations to facilitate comprehension.
Fixed issue #8 (Allow links also in components)

* Update 1-sdmx-json-field-guide.md

Corrected newly introduced errors in document bookmarks.
Fixed issue #33 (SDMX-Json data messages DataStructure/Dataflow reference/URN).
Added "hreflang" name to link object as response to issue #40 (properties for language used in structure and possibly data SDMX JSON messages) .

* Update 1-sdmx-json-field-guide.md

Correction in example text formatting.

* Update 1-sdmx-json-field-guide.md

Include changes for issue #38 for attachment of annotations to observations, components and component values

* Update 1-sdmx-json-field-guide.md

Update for #8 adding links for component values, and replacing uri by standard links mechanism in annotations

* Update 1-sdmx-json-field-guide.md

Implemented agreed improvement related to issue #38: Highlight sentence explaining the constraint for positions of attributes when including annotations for observations.

* #8 support for links in Component (#51)

Changed schema in order to allow links in Component
(Partly) update schema for issue #8

* Update sdmx-json-data-schema.json

Completed update of schema for issue #8

* Update 1-sdmx-json-field-guide.md

Highlighted recommendation for issue #33.

* #33 links in examples (#49)

Updated examples for issue #33

* Update 1-sdmx-json-field-guide.md

Updated inline examples with annotations for issue #38. Complemented/corrected descriptions related to annotations.

* Update 3-full-example-with-comments.md

Updates for issue #38 "Attachment of annotations"

* Update sdmx-json-data-schema.json

Updated schema for issue #38 (Attachment of annotations)

* Update exr-cross-section.json

Updated example for issue #38 (Attachment of annotations)

* Update exr-flat.json

Updated example for issue #38 (Attachment of annotations)

* Update exr-time-series.json

Updated example for issue #38 (Attachment of annotations)

* Update 1-sdmx-json-field-guide.md (#52)

* Update 1-sdmx-json-field-guide.md

Proposal to not include SDMX-JSON version as mandatory but a recommendation should be made to add information of the SDMX-JSON version as done by other standards (e.g. html). Do this by aligning with JSON-API standard with:
-	new optional top-level meta tag replacing the current header tag to specify SDMX-JSON schema, which contains the SDMX-JSON format version number
-	new top-level data tag under which the current structure and dataSets tags are grouped
-	the already existing top-level errors tag is updated

* Update sdmx-json-data-schema.json

Changed to align with SDMX-API spec (linked to implementation for #37)

* Update 1-sdmx-json-field-guide.md

#46 : Make keyPosition mandatory for dimensions.

* Update sdmx-json-data-schema.json

#46 and other bug corrections

* Update 2-references.md

Align to SDMX-API specification

* Update 1-sdmx-json-field-guide.md

Implement solution for #40

* Update sdmx-json-data-schema.json

Implementation of solution for #40

* Update 3-full-example-with-comments.md

Implement solution for #40

* Update exr-action-delete.json

Implementation of solution of #40

* Update exr-cross-section.json

Implementation of solution of #40

* Update exr-flat.json

Implementation of solution of #40

* Update exr-time-series.json

Implementation of solution of #40

* Update sdmx-json-data-schema.json

First changes for #30

* Update and rename data-message/tools/schemas/sdmx-json-data-schema.json to data-message/tools/schemas/1.0/sdmx-json-data-schema.json

Implementation of solution for #30 (regular expression validation)
Also corrected bugs

* Update exr-action-delete.json

Bug correction for #46

* Update exr-cross-section.json

Bug correction for #46

* Update exr-flat.json

Bug correction for #46

* Update exr-time-series.json

Bug correction for #46

* Update 3-full-example-with-comments.md

Corrected bug for #46

* Update sdmx-json-data-schema.json

Corrected bug that prevented following feature:
An attribute value of "null" can be used to reduce the message size by using the index of the attribute value in the data part of the message (instead of "null").

* Update sdmx-json-data-schema.json

Undo previous change as it wasn't correct.

* Update 3-full-example-with-comments.md

Bug correction for attribute value specification

* Update 1-sdmx-json-field-guide.md

Replaced resources and references with properties of one single Data object, one for each returned artefact. This will allow for a more in-depth content validation with a JSON schema. Using multiple languages. Changes not yet finished.

* Update 1-sdmx-json-field-guide.md

More changes: Changed "nullable" to "optional"

* Create sdmx-json-structure-schema.json

First version, more changes to come

* Update sdmx-json-structure-schema.json

More changes, and more still to come

* Update 1-sdmx-json-field-guide.md

More changes, and more to come...

* Update 1-sdmx-json-field-guide.md

Changes to align with structure message (in progress) and simplify use and specs for languages.

* Update sdmx-json-structure-schema.json

* Update sdmx-json-data-schema.json

Changes to align with structure message (in progress) and simplify use and specs for languages.

* Update exr-action-delete.json

Changes to align with structure message (in progress) and simplify use and specs for languages.

* Update exr-cross-section.json

Changes to align with structure message (in progress) and simplify use and specs for languages.

* Update exr-flat.json

Changes to align with structure message (in progress) and simplify use and specs for languages.

* Update exr-time-series.json

Changes to align with structure message (in progress) and simplify use and specs for languages.

* Update sdmx-json-data-schema.json

Correction for content-language because RFC standard doesn't include q weights. Therefore simplification of language specification without weights.

* Update 1-sdmx-json-field-guide.md

Correction for content-language because RFC standard doesn't include q weights. Therefore simplification of language specification without weights.

* Update 3-full-example-with-comments.md

Correction for content-language because RFC standard doesn't include q weights. Therefore simplification of language specification without weights.

* Update exr-action-delete.json

Correction for content-language because RFC standard doesn't include q weights. Therefore simplification of language specification without weights.

* Update exr-cross-section.json

Correction for content-language because RFC standard doesn't include q weights. Therefore simplification of language specification without weights.

* Update exr-flat.json

Correction for content-language because RFC standard doesn't include q weights. Therefore simplification of language specification without weights.

* Update exr-time-series.json

Correction for content-language because RFC standard doesn't include q weights. Therefore simplification of language specification without weights.

* Update 1-sdmx-json-field-guide.md

Correction for content-language because RFC standard doesn't include q weights. Therefore simplification of language specification without weights.

* Update sdmx-json-structure-schema.json

Work ongoing...

* Update 1-sdmx-json-field-guide.md

Work ongoing...

* Update 1-sdmx-json-field-guide.md

Correction for annotation title

* Update 1-sdmx-json-field-guide.md

Added possibility to include parent and order number for component values to allow for reconstructing component value hierarchies.

* Update 3-full-example-with-comments.md

Added possibility to include parent and order number for component values to allow for reconstructing component value hierarchies.

* Update sdmx-json-data-schema.json

Added possibility to include parent and order number for component values to allow for reconstructing component value hierarchies.

* Update exr-flat.json

Added possibility to include parent and order number for component values to allow for reconstructing component value hierarchies.

* Update exr-time-series.json

Added possibility to include parent and order number for component values to allow for reconstructing component value hierarchies.

* Update exr-action-delete.json

Added possibility to include parent and order number for component values to allow for reconstructing component value hierarchies.

* Update exr-cross-section.json

Added possibility to include parent and order number for component values to allow for reconstructing component value hierarchies.

* Update sdmx-json-structure-schema.json

Added codelist, categoryscheme and conceptscheme

* Update 1-sdmx-json-field-guide.md

Added codelist, categoryscheme and conceptscheme.
Treating urn and uri inside the links objects including one link for "self".

* Update 1-sdmx-json-field-guide.md

Some corrections.

* Update sdmx-json-structure-schema.json

Some corrections.

* Update 1-sdmx-json-field-guide.md

Replace component value's parent property object by string, to be consistent with SDMX-JSON structure message.

* Update 1-sdmx-json-field-guide.md

Completed with most frequent artefact types. 
Remaining artefacts are defined in schema: metadataStructures, hierarchicalCodelists, dataProviderSchemes, dataConsumerSchemes, organisationUnitSchemes, metadataflows, reportingTaxonomies, provisionAgreements, structureSets, processes

* Update 1-sdmx-json-field-guide.md

Formatting corrections

* Update sdmx-json-structure-schema.json

Completed schema for all structural artefact types.

* Update sdmx-json-structure-schema.json

Formatting correction

* Create generated-sample.json

Sample generated automatically from json schema.

* Update sdmx-json-data-schema.json

Correction to parent item specification.

* Create 1-sdmx-json-field-guide.md

First draft

* Update 1-sdmx-json-field-guide.md

Small corrections/improvements

* Update 1-sdmx-json-field-guide.md

Alignment with structure and metadata messages on management of human-readable localised names

* Update 1-sdmx-json-field-guide.md

Correction

* Update 1-sdmx-json-field-guide.md

Correction

* Update sdmx-json-data-schema.json

Make data message consistent with structure and metadata message for human-readable names

* Update 1-sdmx-json-field-guide.md

Correction

* Update sdmx-json-data-schema.json

Complement links

* Update sdmx-json-structure-schema.json

* Create sdmx-json-metadata-schema.json

* Update sdmx-json-data-schema.json

* Update sdmx-json-structure-schema.json

Simplified groupDimensions to simply array of dimension IDs.
Href not mandatory in links anymore, but links to have at least href or urn.

* Create constructed-sample

* Create constructed-sample.json

* Delete constructed-sample

* Update 1-sdmx-json-field-guide.md

Corrections/additions to ItemScheme/Item documentation.

* Update constructed-sample.json

Correction

* Update sdmx-json-structure-schema.json

Removed "id", "version" and "agencyID" properties from “ConceptRepresentation” type used for Concept definitions (because its “enumeration” property already contains the URN which holds the same information). Consistently, the SDMX-JSON format only uses URNs for referencing other artefacts rather than separate "id", "version" and "agencyID" properties.
Removed the “ISOConceptReferenceType” type. The “isoConceptReference” property of the “ConceptType” type is thus now taking just a simple URN rather than that “ISOConceptReferenceType” object.

* Update 1-sdmx-json-field-guide.md

* Create constructed-sample2

* Update sdmx-json-metadata-schema.json

* Update constructed-sample2

* Create constructed-sample

* Create generated-sample

* Update sdmx-json-metadata-schema.json

* format alignment for localised strings, added attribute relationship (#56)

* Update 1-sdmx-json-field-guide.md

Proposal to not include SDMX-JSON version as mandatory but a recommendation should be made to add information of the SDMX-JSON version as done by other standards (e.g. html). Do this by aligning with JSON-API standard with:
-	new optional top-level meta tag to specify SDMX-JSON version, this tag can contain the SDMX-JSON version number
-	new top-level data tag under which the current he…
  • Loading branch information
9 people authored Oct 29, 2021
1 parent d2bf3f7 commit 30de0ba
Show file tree
Hide file tree
Showing 31 changed files with 22,710 additions and 6,055 deletions.
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ This repository is used for maintaining the SDMX-JSON messages specifications.

This includes:

- Normative documentation, samples and tools for the SDMX-JSON data message format.
- Normative documentation and samples for the SDMX-JSON structure message format.
- Prototype for the SDMX-JSON metadata message format. (see develop branch)
- Normative documentation and samples for the SDMX-JSON structure message format
- Normative documentation and samples for the SDMX-JSON data message format
- Normative documentation and samples for the SDMX-JSON metadata message format
- [Wiki](https://github.com/sdmx-twg/sdmx-json/wiki) for additional information
5 changes: 3 additions & 2 deletions data-message/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,8 +14,9 @@ parsing. The format may be used in a wide variety of programming languages
and application programs. Testing and development of the format has focused
on JavaScript applications running in web browsers.

The SDMX-JSON Data Message format supports the SDMX 2.1 Information Model
and works together with the SDMX 2.1 RESTful Web Services API for data queries.
The current SDMX-JSON Data Message format 2.0.0 supports the SDMX 3.0 Information Model
and works together with the SDMX 3.0 RESTful Web Services API for data queries.

The SDMX-JSON format is streamable from a supporting web service in order to
limit the amount of server resources.

Expand Down
5 changes: 0 additions & 5 deletions data-message/TODO.md

This file was deleted.

7 changes: 2 additions & 5 deletions data-message/docs/0-status.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,15 +3,12 @@
*This section describes the status of this document at the time of its publication.
Other documents may supersede this document.*

This is the released SDMX Technical Standard for SDMX-JSON Data Message.
This is the released SDMX Technical Standard for SDMX-JSON Data Message, version 2.0.0.

This document has been produced by the SDMX-TWG. The authors of this document
are the members of the SDMX-TWG. Different parts of this specification have
different editors.

----

\null
\vfill

© SDMX 2014-2019 http://www.sdmx.org/
© SDMX 2014-2021 http://www.sdmx.org/
1,093 changes: 724 additions & 369 deletions data-message/docs/1-sdmx-json-field-guide.md

Large diffs are not rendered by default.

6 changes: 3 additions & 3 deletions data-message/docs/2-references.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,10 +9,10 @@ interchange — Representation of dates and times*, ISO, 2004
[json] *The JSON Data Interchange Format*, Standard ECMA-404, ECMA International,
October 2013

[sdmxim21] *Section 2: Information Model: UML Conceptual Design*, SDMX Standards 2.1,
SDMX, April 2011
[sdmx-im] *SDMX Information Model v3.0.0*, https://github.com/sdmx-twg/sdmx-im,
SDMX, September 2021

[sdmxws21] *Section 7: Guidelines for the Use of Web Services*, SDMX Standards 2.1,
[sdmx-rest] *SDMX RESTful Web Services Specification v2.0.0*, https://github.com/sdmx-twg/sdmx-rest,
SDMX, April 2011

[json api 1.0] *A specification for building APIs in Json*, http://jsonapi.org/, 2015
492 changes: 0 additions & 492 deletions data-message/docs/3-full-example-with-comments.md

This file was deleted.

Loading

0 comments on commit 30de0ba

Please sign in to comment.