Comments (7)
I agree with you that deletions are a "sub-optimal". This topics links also to the discussions on handling of missing/not-provided values in SDMX-ML/JSON messages with actions "REPLACE" and "INFO", as well as in SDMX-CSV messages.
Supporting different schema types might not be sufficient to solve this for generic SDMX-ML messages, because a message can contain several datasets with each a different action (e.g. as a result of includeHistory). Another solution would be to be less strict with the presence of values (as done for structure-specific messages).
from sdmx-ml.
Thanks, @dosse!
I believe that having multiple datasets in the response will not be a problem. The issue is similar with dimensionAtObservation: There as a well, the schema will vary depending on how the data are packaged (as time series, flat or cross-sectional messages).
The way this was addressed for dimensionAtObservation was to make the "packaging information" part of the URN, for example:
urn:sdmx:org.sdmx.infomodel.datastructure.DataStructure=ESTAT:NA_MAIN(1.10):ObsLevelDim:TIME_PERIOD
The URN is used as key to the schema and so, multiple datasets (in the same message) may very well reference different schemas.
The same could be achieved in this case, as long as the action is made part of the URN.
What do you think?
from sdmx-ml.
@sosna Sounds good!
from sdmx-ml.
Hi @sosna, since the generic message type has been deprecated, can we now close this ticket?
from sdmx-ml.
Hi @sosna, could we now close this ticket, please?
from sdmx-ml.
This is either a change to the technical notes on how to generate a schema (allow empty values) - however it would be inconsistent with the behavior of CSV which requires a value.
Alternatively this could be coupled with the ticket on reporting null values:
sdmx-twg/sdmx-csv#27
If a definition was defined in all formats which is the same - then the schema can allow this for attributes in addition to the standard list of allowable content - and the generated schema does not have to be action dependent.
The benefit of using a reserved term for missing is that the user does not need to process the data to discover the action in order to generate the correct schema.
from sdmx-ml.
@dosse: Sorry, I just saw your question about closing the ticket now :(.
And I'm not sure I understand the request to close the ticket actually. Yes, the examples use the Generic format, a now deprecated format. But these were just examples and the issue still remains with the other formats?
from sdmx-ml.
Related Issues (20)
- SDMX 3.0: implement "feature 005 Codelist extension / composition" for SDMX-ML messages HOT 2
- SDMX 3.0: implement "feature 006 Discriminated union of codelists" for SDMX-ML messages HOT 1
- SDMX 3.0: implement "feature 008 Enhance the constraints artefacts" for SDMX-ML messages HOT 1
- SDMX 3.0: implement "feature 010 Improve mapping by enhancing the Structure Set artefact" for SDMX-ML messages HOT 2
- SDMX 3.0: implement "feature 012 Referencing of hierarchical codelists" for SDMX-ML messages HOT 1
- SDMX 3.0: implement "feature 014 Schema attribute attachment at series and group level" for SDMX-ML messages HOT 2
- SDMX 3.0: implement "feature 013 Reorganising constraints" for SDMX-ML messages HOT 5
- SDMX 3.0: implement "feature 002 Support reference metadata in the Restful APIs" for SDMX-ML messages HOT 12
- SDMX 3.0: implement "feature 029 Improving API data queries" for SDMX-ML messages HOT 2
- Geo component and concept role name HOT 4
- GeospatialInformation and WKT question HOT 2
- Metadata in Dataset question HOT 2
- Possibly bug/breaking change in parent items regular expression HOT 5
- Data message to fully replace data
- Handling of missing values
- Review isMultiLingual default in Data attributes/measures HOT 2
- Schema Typo HOT 3
- Reference Metadata attributes may only have one single value HOT 1
- Harmonize indenting across XSD files HOT 1
- Merge SDMXMessageFooter.xsd and SDMXMessage.xsd 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-ml.