Writing Conventions for GQL
This document is stale and needs review.
These are documented as we go and in general try to follow SQL unless there is
a strong reason to not do so.
- Never capitalize after an acronym, e.g. use
GQL-procedure
but don't use GQL-Procedure
Procedure Terminology
- Available in any form (written in GQL or provided via the catalog):
GQL-procedure, GQL-query, GQL-function
- Written in GQL: procedure, query, function
- External: external procedure, external query, external function
- Prefixed by side-effect: catalog procedure, session procedure, data procedure
- Production rules: as is, e.g. , ,
- In rules: specification function
- Prefix GQL-: Related to top-level constructs like the request
Catalog Terminology
- Catalog root
- Catalog entry
- Catalog directory
- Catalog object
- Catalog alias
Execution context
Graph Terminology
- Preferred: Node
- Preferred: Edge
Type Terminology
- every value has a data type [top most concept]
- ( predefined types, constructed types ) as in SQL + auxiliary types + null type that is
a predefined type
- atomic type / composite type
- collection types
- broad categorizations by context:
direct data type, indirect data type
property data type, binding data type, data object type, component type
- super type and subtype
- union type
- type union
- type intersection
This file: Copyright © 2021 Editors of ISO/IEC JTC 1/SC 32/WG 3:
Jim Melton, Stephen Cannan, Jörn Bartels, Stefan Plantikow