You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tinkerpop.apache.org by GitBox <gi...@apache.org> on 2021/10/20 12:15:57 UTC
[GitHub] [tinkerpop] krlawrence edited a comment on pull request #1485: TINKERPOP-848 draft implementation to support default value
krlawrence edited a comment on pull request #1485:
URL: https://github.com/apache/tinkerpop/pull/1485#issuecomment-947604873
I think part of the challenge here is the GraphML spec. There is solid normative guidance for the allowed schema but there seems to be very little in the way of normative guidance regarding the processing model. The Primer itself is not normative and does not cover all possible cases where the schema allows a `<default>` value. The ambiguity comes from a document such as this one:
```
<graphml xmlns='http://graphml.graphdrawing.org/xmlns'>
<key id='code' for='node' attr.name='code' attr.type='string'><default>LHR</default></key>
<key id='city' for='node' attr.name='city' attr.type='string'><default>London></default></key>
<graph id='routes' edgedefault='directed'>
<node id='0' label='n1'>
<data key='city'/>
</node>
</graph>
</graphml>
```
When `n1` is created should it have both properties for `code` and `city` created using the default values? The spec provides no guidance (that I can find). I tested using Gephi which is a popular tool for working with various graph file formats. The results from Gephi yield a node with both properties. In the absence of normative guidance from the GraphML spec itself I would propose we be consistent with Gephi if we add support for default values to help with interchange between other tools, like Gephi, and TinkerPop.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@tinkerpop.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org