Hello, When you grab a property from a vertex, you get back an Iterator, not a List. That iterator can have 0, 1, 2, 3… etc. number of values. As such, the number of the properties for a key is variable. Sometimes its one, then you add another, now its two. Then you decide to delete one, back to one. Does the key name change as you dynamically add/remove values. ?
If a user wishes to use plural key names, they can, its just not how we promote it in TinkerPop given that TinkerPop is schema-less. Thanks, Marko. http://markorodriguez.com On Jun 29, 2015, at 12:22 PM, Bob Briody <bob.bri...@datastax.com> wrote: > +1 for plural names, because when you grab the property from the vertex you > get back a list. > > I hear "the RDF" motivation but still like plural multi-prop names better. > > Bob > > On Mon, Jun 29, 2015 at 9:34 AM, Marko A. Rodriguez (JIRA) <j...@apache.org> > wrote: > >> >> [ >> https://issues.apache.org/jira/browse/TINKERPOP3-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel >> ] >> >> Marko A. Rodriguez closed TINKERPOP3-751. >> ----------------------------------------- >> Resolution: Won't Fix >> Assignee: Marko A. Rodriguez >> >> I don't think multi-properties should have plural key names. The >> convention espoused by TinkerPop3 is taken from the RDF world. >> >> {code} >> 1--name-->marko >> 1--name-->mrodriguez >> 1--created-->2 >> 1--created-->3 >> {code} >> >> Like edges that go from vertex-to-vertex, vertex-to-literal "edges" are >> also singularly named. >> >>> Vertex property docs use singular nouns for multi-properties >>> ------------------------------------------------------------ >>> >>> Key: TINKERPOP3-751 >>> URL: >> https://issues.apache.org/jira/browse/TINKERPOP3-751 >>> Project: TinkerPop 3 >>> Issue Type: Improvement >>> Components: documentation >>> Reporter: Bryn Cooke >>> Assignee: Marko A. Rodriguez >>> Priority: Minor >>> >>> http://www.tinkerpop.com/docs/3.0.0-SNAPSHOT/#vertex-properties >>> The current docs seem to suggest folks should use singular nouns for >> properties in all circumstances. However in graph databases with schema >> this will cause issues where people will find themselves with name clashes >> between single and multi-property definitions. >>> Perhaps write a section on naming conventions. For instance labels >> should be the class of elements, properties should be singular-nouns, >> multi-properties should be plural nouns? >> >> >> >> -- >> This message was sent by Atlassian JIRA >> (v6.3.4#6332) >>
