Implementation details with LEX YAML alignment

[yangxk1]

We recently held in-depth discussions with the LDBC LEX (LDBC Extended GQL
Schema) team. Based on these conversations, we propose making adjustments
to Graphar’s current Schema YAML format and would like to solicit your
feedback.

LEX, which is part of the GDC (Graph Data Council) Text2GraphQuery project
focused on property graphs, is a proposed strict superset of GQL graph
types and as a proposal to WG3 for possible future standardization. LEX
includes many of the same players as the WG3 international and INCITS U.S.
national standards bodies.

LEX has expressed strong interest in Graphar’s current approach of using
YAML to represent graph schemas, and we have already engaged in several
productive discussions on this topic.

Given the strong alignment between LEX’s goals for graph storage
standardization and Graphar’s own mission, we believe this presents a
valuable opportunity for collaboration. To better integrate with the LEX
ecosystem, we plan to adapt Graphar’s YAML format to conform as closely as
possible to LEX’s proposed syntax, this may require changes to our current
YAML structure.

We can discuss some details here

[SemyonSinchenko]

If this is only about changing logical schema and we are not changing physical layer I'm for it. We just need to think a clear migration plan and also we should provide a converter from old GAR to LEX.

That is the example of LEX yaml: https://github.com/alastai/grasch-lex/blob/main/snb-lex-2026.0.0-schema.yaml

[yangxk1]

If this is only about changing logical schema and we are not changing physical layer I'm for it.

This work only involves changes to the yaml schema.

I think the best way currently is to support parsing of both LEX schema YAML and current Schema YAML.