You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Yang Xia (Jira)" <ji...@apache.org> on 2024/05/21 18:28:00 UTC

[jira] [Updated] (TINKERPOP-2969) Introduce GraphSON 4.0 and GraphBinary 4.0

     [ https://issues.apache.org/jira/browse/TINKERPOP-2969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yang Xia updated TINKERPOP-2969:
--------------------------------
    Summary: Introduce GraphSON 4.0 and GraphBinary 4.0  (was: Introduce GraphSON 4.0 and GraphBinary 2.0)

> Introduce GraphSON 4.0 and GraphBinary 4.0
> ------------------------------------------
>
>                 Key: TINKERPOP-2969
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2969
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: io
>    Affects Versions: 3.6.4
>            Reporter: Stephen Mallette
>            Priority: Major
>
> Now that we have untyped GraphSON consistently implemented, there are a few things we could do to improve the untyped version and to adjust a thing or two in the typed version. Also, if we make some of these changes to GraphSON they should also apply to GraphBinary.
> 1. allow for multi-label on vertices as more graphs are allowing that these
> days.
> 2. in GraphSON untyped use our "~" prefix for any structural/reserved keys like T.label or T.id
> 3. get the {{Tree}} right for GraphSON
> {code}
> {
> "node": {},
> "children": [{
> "node": {},
> "children": []
> },
> {
> "node": {},
> "children": []
> },
> {
> "node": {},
> "children": [{
> "node": {},
> "children": []
> }]
> }]
> }
> {code}
> 4. Drop extended types from GraphBinary and GraphSON and any types that might be considered JVM oriented.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)