[
https://issues.apache.org/jira/browse/TINKERPOP3-610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14625185#comment-14625185
]
stephen mallette commented on TINKERPOP3-610:
---------------------------------------------
Looked into this issue - didn't seem to be as big a deal as I thought it would
be as we hadn't used many of the keys you'd like to see reserved in the first
place (just a handful of tests had to change). I still don't have an approach
to ensure we don't backslide into using them again, so at this time "reserving"
will remain a convention for test developers to follow.
> General graph concept names in test schema
> ------------------------------------------
>
> Key: TINKERPOP3-610
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-610
> Project: TinkerPop 3
> Issue Type: Improvement
> Components: test-suite
> Reporter: Dan LaRocque
> Priority: Minor
>
> The TP3 test suite uses the abstract names of graph concepts for some schema
> definitions, for example defining an edge label named "label".
> Implementations may want to reserve names like these for internal use, but
> they have no way to tell the tests which names to avoid.
> Ideally, the tests would either forego names that would plausibly be
> interesting to implementations, or provide some annotation or other mechanism
> for impls to tweak the default names.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
