Content deleted Content added
Added CAPS/Morpheus description; link GQL EWD from SC32 public repository |
Add references |
||
Line 9:
==Managed alongside SQL by JTC 1/SC32 Working Group 3 (WG3) ==
The GQL project has a four-year timespan. Seven national standards bodies (those of the United States, China, Korea, the Netherlands, the United Kingdom, Denmark and Sweden) have nominated national subject-matter experts to work on the project, which is conducted by Working Group 3 (Database Languages) of ISO/IEC JTC 1's Subcommittee 32 (Data Management and Interchange), usually abbreviated as ISO/IEC JTC 1/SC 32 WG3, or just "WG3" for short. WG3 (and its direct predecessor committees within JTC 1) has been responsible for the SQL standard since 1987.<ref name="SC32 and WG3 history">{{cite web|url=https://jtc1info.org/sd_2-history_of_jtc1/jtc1-subcommittees/sc-32/|title=JTC 1/SC 32 Data Management and Interchange|last=|first=|date=|website=|publisher=ISO/IEC JTC1|accessdate=October 6, 2019}}</ref><ref name="1987 scope of SQL">{{cite web|url=https://isotc.iso.org/livelink/livelink?func=ll&objId=19733701&objAction=Open/|title=''Scope from the original standard, ISO 9075-1987, Database Language SQL''|last=|first=|date=|website=|publisher=ISO/IEC JTC1|accessdate=November 9, 2019}}</ref>
A working proposal for the scope and features of GQL [REF NEO4J TIGERGRAPH] was put forward by expert contributors from Sweden, the United Kingdom and the United States in the query languages standards teams at Neo4j Inc. and TigerGraph Inc. in September 2019, following the start of the project. This proposal, along with supplementary material detailing transaction demarcation semantics and syntax, and an approach to transaction isolation that would allow implementers to include isolation levels additional to those in the SQL standard, were agreed at the meeting of WG3 that took place in the same month in Arusha, Tanzania.
| |||