deploy: c532b8b

Author: copybara-service[bot]

index.xml

@@ -90,7 +90,7 @@ Lexical Elements Letters and Digits letter = "A" ... "Z&
 | alternation () grouping [] option (zero or one time) {} repetition (any number of times) Lexical Elements Letters and Digits letter = &amp;#34;A&amp;#34; ... &amp;#34;Z&amp;#34; | &amp;#34;a&amp;#34; ... &amp;#34;z&amp;#34; capitalLetter = &amp;#34;A&amp;#34; ... &amp;#34;Z&amp;#34; decimalDigit = &amp;#34;0&amp;#34; ... &amp;#34;9&amp;#34; octalDigit = &amp;#34;0&amp;#34; ... &amp;#34;7&amp;#34; hexDigit = &amp;#34;0&amp;#34; ... &amp;#34;9&amp;#34; | &amp;#34;A&amp;#34; ... &amp;#34;F&amp;#34; | &amp;#34;a&amp;#34; ... &amp;#34;f&amp;#34; Identifiers ident = letter { letter | decimalDigit | &amp;#34;_&amp;#34; } fullIdent = ident { &amp;#34;.</description></item><item><title>Protocol Buffers Language Specification (Proto3)</title><link>https://protobuf.dev/reference/protobuf/proto3-spec/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/reference/protobuf/proto3-spec/</guid><description>The syntax is specified using Extended Backus-Naur Form (EBNF):
 | alternation () grouping [] option (zero or one time) {} repetition (any number of times) For more information about using proto3, see the language guide.
 Lexical Elements Letters and Digits letter = &amp;#34;A&amp;#34; ... &amp;#34;Z&amp;#34; | &amp;#34;a&amp;#34; ... &amp;#34;z&amp;#34; decimalDigit = &amp;#34;0&amp;#34; ... &amp;#34;9&amp;#34; octalDigit = &amp;#34;0&amp;#34; ... &amp;#34;7&amp;#34; hexDigit = &amp;#34;0&amp;#34; ... &amp;#34;9&amp;#34; | &amp;#34;A&amp;#34; ... &amp;#34;F&amp;#34; | &amp;#34;a&amp;#34; .</description></item><item><title>Text Format Language Specification</title><link>https://protobuf.dev/reference/protobuf/textformat-spec/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/reference/protobuf/textformat-spec/</guid><description>This format is distinct from the format of text within a .proto schema, for example. This document contains reference documentation using the syntax specified in ISO/IEC 14977 EBNF.
-Note This is a draft spec reverse-engineered from the C++ text format implementation and may change based on further discussion and review. While an effort has been made to keep text formats consistent across supported languages, incompatibilities are likely to exist. Example convolution_benchmark { label: &amp;#34;NHWC_128x20x20x56x160&amp;#34; input { dimension: [128, 56, 20, 20] data_type: DATA_HALF format: TENSOR_NHWC } } Parsing Overview The language elements in this spec are split into lexical and syntactic categories.</description></item><item><title>Protocol Buffer MIME Types</title><link>https://protobuf.dev/reference/protobuf/mime-types/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/reference/protobuf/mime-types/</guid><description>All Protobuf documents should have the MIME type application and the subtype protobuf, with the suffix +json for JSON encodings according to the standard, followed by the following parameters:
+Note This is a draft spec originally reverse-engineered from the C++ text format implementation It has evolved and may change further based on discussion and review. While an effort has been made to keep text formats consistent across supported languages, incompatibilities are likely to exist.</description></item><item><title>Protocol Buffer MIME Types</title><link>https://protobuf.dev/reference/protobuf/mime-types/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/reference/protobuf/mime-types/</guid><description>All Protobuf documents should have the MIME type application and the subtype protobuf, with the suffix +json for JSON encodings according to the standard, followed by the following parameters:
 encoding should be set only to binary, or json, denoting those respective formats. With subtype protobuf+json, encoding has the default json and cannot be set to binary. With subtype protobuf (without +json), encoding has the default binary and cannot be set to json.</description></item><item><title>Protocol Buffers Well-Known Types</title><link>https://protobuf.dev/reference/protobuf/google.protobuf/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/reference/protobuf/google.protobuf/</guid><description>Index Any (message) Api (message) BoolValue (message) BytesValue (message) DoubleValue (message) Duration (message) Empty (message) Enum (message) EnumValue (message) Field (message) Field.Cardinality (enum) Field.Kind (enum) FieldMask (message) FloatValue (message) Int32Value (message) Int64Value (message) ListValue (message) Method (message) Mixin (message) NullValue (enum) Option (message) SourceContext (message) StringValue (message) Struct (message) Syntax (enum) Timestamp (message) Type (message) UInt32Value (message) UInt64Value (message) Value (message) Well-Known Types that end in &amp;ldquo;Value&amp;rdquo; are wrapper messages for other types, such as BoolValue and EnumValue.</description></item><item><title>Other Languages</title><link>https://protobuf.dev/reference/other/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/reference/other/</guid><description>While the current release includes compilers and APIs for C++, Java, Go, Ruby, C#, and Python, the compiler code is designed so that it&amp;rsquo;s easy to add support for other languages. There are several ongoing projects to add new language implementations to Protocol Buffers, including C, Haskell, Perl, Rust, and more.
 For a list of links to projects we know about, see the third-party add-ons wiki page.
 Compiler Plugins protoc, the Protocol Buffers Compiler, can be extended to support new languages via plugins.</description></item><item><title>Version Support</title><link>https://protobuf.dev/support/version-support/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/support/version-support/</guid><description>Support windows for protoc and the various languages are covered in the tables later in this topic. Version numbers throughout this topic use SemVer conventions; in the version &amp;ldquo;3.21.7,&amp;rdquo; we say that &amp;ldquo;3&amp;rdquo; is the major version, &amp;ldquo;21&amp;rdquo; is the minor version, and &amp;ldquo;7&amp;rdquo; is the micro or patch number.

reference/protobuf/index.xml

@@ -5,5 +5,5 @@ Lexical Elements Letters and Digits letter = "A" ... "Z&
 | alternation () grouping [] option (zero or one time) {} repetition (any number of times) Lexical Elements Letters and Digits letter = &amp;#34;A&amp;#34; ... &amp;#34;Z&amp;#34; | &amp;#34;a&amp;#34; ... &amp;#34;z&amp;#34; capitalLetter = &amp;#34;A&amp;#34; ... &amp;#34;Z&amp;#34; decimalDigit = &amp;#34;0&amp;#34; ... &amp;#34;9&amp;#34; octalDigit = &amp;#34;0&amp;#34; ... &amp;#34;7&amp;#34; hexDigit = &amp;#34;0&amp;#34; ... &amp;#34;9&amp;#34; | &amp;#34;A&amp;#34; ... &amp;#34;F&amp;#34; | &amp;#34;a&amp;#34; ... &amp;#34;f&amp;#34; Identifiers ident = letter { letter | decimalDigit | &amp;#34;_&amp;#34; } fullIdent = ident { &amp;#34;.</description></item><item><title>Protocol Buffers Language Specification (Proto3)</title><link>https://protobuf.dev/reference/protobuf/proto3-spec/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/reference/protobuf/proto3-spec/</guid><description>The syntax is specified using Extended Backus-Naur Form (EBNF):
 | alternation () grouping [] option (zero or one time) {} repetition (any number of times) For more information about using proto3, see the language guide.
 Lexical Elements Letters and Digits letter = &amp;#34;A&amp;#34; ... &amp;#34;Z&amp;#34; | &amp;#34;a&amp;#34; ... &amp;#34;z&amp;#34; decimalDigit = &amp;#34;0&amp;#34; ... &amp;#34;9&amp;#34; octalDigit = &amp;#34;0&amp;#34; ... &amp;#34;7&amp;#34; hexDigit = &amp;#34;0&amp;#34; ... &amp;#34;9&amp;#34; | &amp;#34;A&amp;#34; ... &amp;#34;F&amp;#34; | &amp;#34;a&amp;#34; .</description></item><item><title>Text Format Language Specification</title><link>https://protobuf.dev/reference/protobuf/textformat-spec/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/reference/protobuf/textformat-spec/</guid><description>This format is distinct from the format of text within a .proto schema, for example. This document contains reference documentation using the syntax specified in ISO/IEC 14977 EBNF.
-Note This is a draft spec reverse-engineered from the C++ text format implementation and may change based on further discussion and review. While an effort has been made to keep text formats consistent across supported languages, incompatibilities are likely to exist. Example convolution_benchmark { label: &amp;#34;NHWC_128x20x20x56x160&amp;#34; input { dimension: [128, 56, 20, 20] data_type: DATA_HALF format: TENSOR_NHWC } } Parsing Overview The language elements in this spec are split into lexical and syntactic categories.</description></item><item><title>Protocol Buffer MIME Types</title><link>https://protobuf.dev/reference/protobuf/mime-types/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/reference/protobuf/mime-types/</guid><description>All Protobuf documents should have the MIME type application and the subtype protobuf, with the suffix +json for JSON encodings according to the standard, followed by the following parameters:
+Note This is a draft spec originally reverse-engineered from the C++ text format implementation It has evolved and may change further based on discussion and review. While an effort has been made to keep text formats consistent across supported languages, incompatibilities are likely to exist.</description></item><item><title>Protocol Buffer MIME Types</title><link>https://protobuf.dev/reference/protobuf/mime-types/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/reference/protobuf/mime-types/</guid><description>All Protobuf documents should have the MIME type application and the subtype protobuf, with the suffix +json for JSON encodings according to the standard, followed by the following parameters:
 encoding should be set only to binary, or json, denoting those respective formats. With subtype protobuf+json, encoding has the default json and cannot be set to binary. With subtype protobuf (without +json), encoding has the default binary and cannot be set to json.</description></item><item><title>Protocol Buffers Well-Known Types</title><link>https://protobuf.dev/reference/protobuf/google.protobuf/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://protobuf.dev/reference/protobuf/google.protobuf/</guid><description>Index Any (message) Api (message) BoolValue (message) BytesValue (message) DoubleValue (message) Duration (message) Empty (message) Enum (message) EnumValue (message) Field (message) Field.Cardinality (enum) Field.Kind (enum) FieldMask (message) FloatValue (message) Int32Value (message) Int64Value (message) ListValue (message) Method (message) Mixin (message) NullValue (enum) Option (message) SourceContext (message) StringValue (message) Struct (message) Syntax (enum) Timestamp (message) Type (message) UInt32Value (message) UInt64Value (message) Value (message) Well-Known Types that end in &amp;ldquo;Value&amp;rdquo; are wrapper messages for other types, such as BoolValue and EnumValue.</description></item></channel></rss>