[
https://issues.apache.org/jira/browse/AVRO-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Cutting updated AVRO-153:
------------------------------
Component/s: spec
We currently define identifiers with:
{quote}
Record, field and enum names must:
- start with [A-Za-z_]
- subsequently contain only [A-Za-z0-9_]
{quote}
We however don't say anything about namespaces. I propose that namespaces must
be a series of dot-delimited identifiers as defined above.
As for encouraged naming conventions, I'd opt for Java's:
- namespaces are hierarchical, with the root at left, starting with a reversed
domain name.
- namespace elements are lowercase
- record and enum names are capitalized CamelCase
- field and message names are uncapitalized camelCase
- enum symbols are all-cap
- acronyms embeeded in names are capitalized, e.g., Md5Hash, BaseUrl, etc.
> Naming conventions for avro records and protocols
> -------------------------------------------------
>
> Key: AVRO-153
> URL: https://issues.apache.org/jira/browse/AVRO-153
> Project: Avro
> Issue Type: Improvement
> Components: spec
> Reporter: Philip Zeyliger
>
> It would be nice to add a few paragraphs to the spec with suggested naming
> conventions. I'm ambivalent as to what they actually are, but while the
> paint hasn't fully settled, it might be nice to lead the project in one
> direction or another.
> Any thoughts on what the best style here is?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
