You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "stephen mallette (JIRA)" <ji...@apache.org> on 2015/07/15 15:36:04 UTC

[jira] [Closed] (TINKERPOP3-610) General graph concept names in test schema

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

stephen mallette closed TINKERPOP3-610.
---------------------------------------
    Resolution: Implemented

This is implemented but it remains a "convention" - not sure how it could be made enforceable.

> 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
>    Affects Versions: 3.0.0-incubating
>            Reporter: Dan LaRocque
>            Assignee: stephen mallette
>            Priority: Minor
>             Fix For: 3.0.1-incubating
>
>
> 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)