Comments (3)
In general, the SDMX-ML schema is meant to be a "master" IM implementation. In many aspects, it is more precise. However, each issue need to be looked at separately, as bugs could also happen here.
from sdmx-json.
Hello @buhaiovos, thanks for reporting this. It highlights an inconsistency in the documentation between the IM and the message format implementations (SDMX-ML and SDMX-JSON). Indeed, when constructing the message formats, sometimes some changes are made to generalise the approach and make it more coherent. Certain aspects may not have been seen when writing the IM document. The SDMX-JSON represents a translation of structures in SDMX-ML,.
You can see here how the maxOccurs and minOccurs parameters were moved from the component definitions into the RepresentationType, thus into CoreRepresentation (inside concepts) and LocalRepresentation (inside the component definitions in the DSD). The same was done in SDMX-JSON.
In conclusion, it would seem to me that this feedback should be addressed by updating the IM document. I opened sdmx-twg/sdmx-im#27 for this.
from sdmx-json.
@dosse, thanks for the response.
So, basically, if we're dealing with such kind of issues (when something between infomodel and XML(JSON) doesn't match) - we consider message formats more relevant?
from sdmx-json.
Related Issues (20)
- Proposal to reference DSD from data message via `agencyID` and `version` HOT 4
- Coded TIME_PERIOD?
- `contentLanguages` disallows most non-lowercase language identifiers HOT 1
- `timeDimension.localRepresentation` should be optional
- `name` and `description` on `$.data.structures[*]`
- `valueArray` schema requires `oneOf` `integer` xor `number`
- Bad schema for `dimValues` HOT 1
- Invalid regex pattern for `StandardTimePeriodType`
- Use `$defs` instead of `$.definitions` in JSON Schemas.
- Unclear representation of metadata in data messages
- Attribute relationship vs attachment level
- Dimension group relationships no longer resolved
- Confusing ID inheritance remark
- Missing `validFrom`/`validTo` properties on `TimeRangeValue`
- How are `s:GenericDataflow` elements represented?
- Deprecate using artefact types as link relations
- Time and time zone requirements vs SDMX-ML
- `meta` and `errors` should be annotable
- If `data` and `errors` are mutually exclusive, then where do warnings go?
- Possible inconsistency regarding coded attributes/measures with array values HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from sdmx-json.