Cole-Greer commented on code in PR #3523: URL: https://github.com/apache/tinkerpop/pull/3523#discussion_r3605935837
########## docs/src/dev/provider/index.asciidoc: ########## @@ -192,12 +192,52 @@ The following bullets provide some tips to consider when implementing the struct `Graph open(Configuration)` method where the `Configuration` is an Apache Commons class of that name. Alternatively, the `Graph` implementation can have the `GraphFactoryClass` annotation which specifies a class with that static `Graph open(Configuration)` method. +* `Vertex` +** By default a vertex has exactly one immutable label. Graphs that want to support multiple, mutable, or zero +labels should follow the <<multi-label-support,Multi-Label Support>> section below. * `VertexProperty` ** This interface is both a `Property` and an `Element` as `VertexProperty` is a first-class graph element in that it can have its own properties (i.e. meta-properties). Even if the implementation does not intend to support meta-properties, the `VertexProperty` needs to be implemented as an `Element`. `VertexProperty` should return empty iterable for properties if meta-properties is not supported. +[[multi-label-support]] +==== Multi-Label Support + +By default a vertex has exactly one immutable label, matching the 3.x behavior. Providers that want to support Review Comment: I think we should be careful with using the word default here, we don't want to imply that that any choice is "more correct" than the other. TinkerGraph defaults to a cardinality of ONE, but TinkerPop itself shouldn't have any bias towards any of the choices. The [reference docs](https://github.com/apache/tinkerpop/blob/19112cc479f332ce352b77df36cbac120fb7a451/docs/src/reference/the-graph.asciidoc?plain=1#L192-L240) were carefully structured to avoid calling it the default. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
