[
https://issues.apache.org/jira/browse/TINKERPOP3-610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14394719#comment-14394719
]
stephen mallette commented on TINKERPOP3-610:
---------------------------------------------
I like the idea of standardizing the schema names used in the test-suite a bit.
I'm not sure how advanced an implementation is required, but it would be nice
if we had something that didn't let test writers backslide into using "edge",
"label", etc. again. At one point I toyed with the idea of defining "schema"
as part of annotations on tests, but that got a bit complicated when I tried to
put it in place. Would be interested to hear ideas in this area.
> 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)
