[
https://issues.apache.org/jira/browse/TINKERPOP-2969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18060588#comment-18060588
]
Ken Hu commented on TINKERPOP-2969:
-----------------------------------
1. The specification has been updated already and all current GLVs that support
GraphSON4/GraphBinary4 have this implemented.
2. This seems to not be done yet.
3. This is covered by a different jira
https://issues.apache.org/jira/browse/TINKERPOP-2063
4. This has been done and the specifications have been updated.
Since 2 is the only relevant part of this issue left, the description and title
will be updated to match.
> 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)
