The fully qualified name of this api, including package name followed by the api's simple name.
The methods of this api, in unspecified order.
Any metadata attached to the API.
A version string for this api. If specified, must have the form
major-version.minor-version
, as in 1.10
. If the minor version
is omitted, it defaults to zero. If the entire version field is
empty, the major version is derived from the package name, as
outlined below. If the field is not empty, the version in the
package name will be verified to be consistent with what is
provided here.
The versioning schema uses [semantic
versioning](http://semver.org) where the major version number
indicates a breaking change and the minor version an additive,
non-breaking change. Both version numbers are signals to users
what to expect from different versions, and should be carefully
chosen based on the product plan.
The major version is also reflected in the package name of the
API, which must end in v<major-version>
, as in
google.feature.v1
. For major versions 0 and 1, the suffix can
be omitted. Zero major versions must only be used for
experimental, none-GA apis.
Source context for the protocol buffer service represented by this message.
Included APIs. See [Mixin][].
The source syntax of the service.
The methods of this api, in unspecified order.
Included APIs.
Included APIs. See [Mixin][].
The fully qualified name of this api, including package name followed by the api's simple name.
Any metadata attached to the API.
Source context for the protocol buffer service represented by this message.
The source syntax of the service.
A version string for this api.
A version string for this api. If specified, must have the form
major-version.minor-version
, as in 1.10
. If the minor version
is omitted, it defaults to zero. If the entire version field is
empty, the major version is derived from the package name, as
outlined below. If the field is not empty, the version in the
package name will be verified to be consistent with what is
provided here.
The versioning schema uses [semantic
versioning](http://semver.org) where the major version number
indicates a breaking change and the minor version an additive,
non-breaking change. Both version numbers are signals to users
what to expect from different versions, and should be carefully
chosen based on the product plan.
The major version is also reflected in the package name of the
API, which must end in v<major-version>
, as in
google.feature.v1
. For major versions 0 and 1, the suffix can
be omitted. Zero major versions must only be used for
experimental, none-GA apis.
Api is a light-weight descriptor for a protocol buffer service.
The fully qualified name of this api, including package name followed by the api's simple name.
The methods of this api, in unspecified order.
Any metadata attached to the API.
A version string for this api. If specified, must have the form
major-version.minor-version
, as in1.10
. If the minor version is omitted, it defaults to zero. If the entire version field is empty, the major version is derived from the package name, as outlined below. If the field is not empty, the version in the package name will be verified to be consistent with what is provided here. The versioning schema uses [semantic versioning](http://semver.org) where the major version number indicates a breaking change and the minor version an additive, non-breaking change. Both version numbers are signals to users what to expect from different versions, and should be carefully chosen based on the product plan. The major version is also reflected in the package name of the API, which must end inv<major-version>
, as ingoogle.feature.v1
. For major versions 0 and 1, the suffix can be omitted. Zero major versions must only be used for experimental, none-GA apis.Source context for the protocol buffer service represented by this message.
Included APIs. See [Mixin][].
The source syntax of the service.