; > approach or another, first decide what we are trying to achieve in
> > the first place.
> >
>
>
> +1
>
>
> > Here goes my understanding of what we are trying to achieve.
> >
> > 1: A property graph meta model. To describe exactly what kin
not even be considered. i.e. 99%
> backward compatibility should be guaranteed at all times.
>
I think you can do what you are proposing with no changes at all to the
Gremlin language.
Josh
>
>
> On Tue, 2022-01-11 at 10:47 -0800, Joshua Shinavier wrote:
>
> Hey Pieter,
>
ponses inline.
>
>
> On Sun, Jan 9, 2022 at 4:28 AM pieter gmail
> wrote:
> > Hi,
> >
> > I have done some work on defining a meta model for Gremlin's
> > property graph. I am using the approach used in the modelling
> > world, in particular as done b
"weight", "type", GremlinDataType.INTEGER.name());
knows.addEdge("properties", knowsWeightVertexProperty);
Vertex created = modernModelGraph.addVertex(T.label, "EdgeLabel",
"label", "created");
Vertex createdWeightVertexProperty =
moder
Hey Pieter,
Good to see some more motion on this front. Responses inline.
On Sun, Jan 9, 2022 at 4:28 AM pieter gmail wrote:
> Hi,
>
> I have done some work on defining a meta model for Gremlin's property
> graph. I am using the approach used in the modelling world, in partic
hi Pieter, the dev list isn't so good with embedded attachments so your
images are missing. Perhaps you could make those available some other way?
On Sun, Jan 9, 2022 at 7:28 AM pieter gmail wrote:
> Hi,
>
> I have done some work on defining a meta model for Gremlin's pro
Hi,
I have done some work on defining a meta model for Gremlin's property
graph. I am using the approach used in the modelling world, in
particular as done by the OMG group when defining their various meta
models and specifications.
However where OMG uses a subset of the UML to define their
