-
Notifications
You must be signed in to change notification settings - Fork 7
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #354 from vtl-sdmx-task-force/revert-348-patch-3
Revert "Patch 3"
- Loading branch information
Showing
5 changed files
with
1,657 additions
and
1,299 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,6 @@ | ||
# SDMX-VTL | ||
VTL is a standard language for defining **validation** and **transformation** rules (set of operators, their syntax and semantics) for any kind of statistical data. VTL builds on the Transformation section of the SDMX information model, by taking the common parts of GSIM, SDMX and DDI as for the representation of concepts and data. The assumption is that such a logical formalization of validation and transformation rules will provide a "technology-neutral" expression at business level of the processing taking place, against which various implementations and specific programming languages can be mapped. The specifications for exchanging VTL validation rules in SDMX messages, for storing rules and for requesting validation rules from web services will be provided in a specific update to the SDMX Technical Standards on which the SDMX Technical Working Group is working on. The VTL 1.1 (currently under [public review](https://sdmx.org/?page_id=5096)) package includes: | ||
VTL is a standard language for defining **validation** and **transformation** rules (set of operators, their syntax and semantics) for any kind of statistical data. VTL builds on the Transformation section of the SDMX information model, by taking the common parts of GSIM, SDMX and DDI as for the representation of concepts and data. The assumption is that such a logical formalization of validation and transformation rules will provide a "technology-neutral" expression at business level of the processing taking place, against which various implementations and specific programming languages can be mapped. The specifications for exchanging VTL validation rules in SDMX messages, for storing rules and for requesting validation rules from web services will be provided in a specific update to the SDMX Technical Standards on which the SDMX Technical Working Group is working on. The VTL 1.0 package includes: | ||
|
||
* [Part 1](https://sdmx.org/wp-content/uploads/VTL-1-1-review-User-Manual-20161017-final.pdf), highlighting the main characteristics of VTL, its core assumptions and the information model the language is based on; | ||
* [Part 2](https://sdmx.org/wp-content/uploads/VTL-1-1-review-Reference-Manual-20161017-final.pdf), containing the full library of operators ordered by category, including examples; this first version can support validation and basic compilation needs. Future versions, whose design is already in progress, will include more features related to transformation of data; | ||
* EBNF notation (Extended Backus-Naur Form) which is the technical notation to be used as a test bed for all the examples throughout the document: files [Vtl.g4](https://github.com/sdmx-twg/sdmx-vtl/blob/v1.1.0/Vtl.g4) & [VtlTokens.g4](https://github.com/sdmx-twg/sdmx-vtl/blob/v1.1.0/VtlTokens.g4) | ||
* [Part 1](https://sdmx.org/wp-content/uploads/VTL1_2015_part1_general_final.pdf), highlighting the main characteristics of VTL, its core assumptions and the information model the language is based on; | ||
* [Part 2](https://sdmx.org/wp-content/uploads/VTL1_2015_part2_operators_final.pdf), containing the full library of operators ordered by category, including examples; this first version can support validation and basic compilation needs. Future versions, whose design is already in progress, will include more features related to transformation of data; | ||
* EBNF notation (Extended Backus-Naur Form) which is the technical notation to be used as a test bed for all the examples throughout the document. |
Oops, something went wrong.