# Paralink Query Language
Paralink data requests can be made via PQL definitions, which are JSON based descriptions of ETL (Extract, Transform & Load) jobs. PQL queries are done via SQL like interface which generalizes over common data structures (JSON, XML, SQL), and includes basic post processing utilities such as math functions and type casting.
The data collected from multiple sources and aggregated with a function like
mean, validated using
validation conditions and then returned to the caller's smart contract of choice via the
# Example definition
Note: PQL is not finalized yet, and subject to change in future revisions.
IPFS is used to immutably store the job definition and provide an addressable content hash. The hash is only 32 bytes long, which is significantly shorter than the job definition itself, making it suitable for request signalling on resource constrained chains such as Ethereum.
# Private Datasets
While it is possible to connect to private databases and API's that require credentials - both supported by Paralink Node & PQL - we do not want to expose those credentials on the public blockchain(s). Furthermore, the owner of the proprietary dataset may want to charge for access. Paralink addresses both use cases with Trusted Ingress solution, where reputable data providers sell their cryptographically signed data feeds.