google-cloud-document_ai-v1 1.11.0 → 1.12.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -24,14 +24,17 @@ module Google
24
24
  # date is relative to the Gregorian Calendar. This can represent one of the
25
25
  # following:
26
26
  #
27
- # * A full date, with non-zero year, month, and day values
28
- # * A month and day value, with a zero year, such as an anniversary
29
- # * A year on its own, with zero month and day values
30
- # * A year and month value, with a zero day, such as a credit card expiration
31
- # date
27
+ # * A full date, with non-zero year, month, and day values.
28
+ # * A month and day, with a zero year (for example, an anniversary).
29
+ # * A year on its own, with a zero month and a zero day.
30
+ # * A year and month, with a zero day (for example, a credit card expiration
31
+ # date).
32
32
  #
33
- # Related types are [google.type.TimeOfDay][google.type.TimeOfDay] and
34
- # `google.protobuf.Timestamp`.
33
+ # Related types:
34
+ #
35
+ # * [google.type.TimeOfDay][google.type.TimeOfDay]
36
+ # * {::Google::Type::DateTime google.type.DateTime}
37
+ # * {::Google::Protobuf::Timestamp google.protobuf.Timestamp}
35
38
  # @!attribute [rw] year
36
39
  # @return [::Integer]
37
40
  # Year of the date. Must be from 1 to 9999, or 0 to specify a date without
@@ -32,8 +32,8 @@ module Google
32
32
  #
33
33
  # The date is relative to the Proleptic Gregorian Calendar.
34
34
  #
35
- # If year is 0, the DateTime is considered not to have a specific year. month
36
- # and day must have valid, non-zero values.
35
+ # If year, month, or day are 0, the DateTime is considered not to have a
36
+ # specific year, month, or day respectively.
37
37
  #
38
38
  # This type may also be used to represent a physical time if all the date and
39
39
  # time fields are set and either case of the `time_offset` oneof is set.
@@ -49,27 +49,28 @@ module Google
49
49
  # datetime without a year.
50
50
  # @!attribute [rw] month
51
51
  # @return [::Integer]
52
- # Required. Month of year. Must be from 1 to 12.
52
+ # Optional. Month of year. Must be from 1 to 12, or 0 if specifying a
53
+ # datetime without a month.
53
54
  # @!attribute [rw] day
54
55
  # @return [::Integer]
55
- # Required. Day of month. Must be from 1 to 31 and valid for the year and
56
- # month.
56
+ # Optional. Day of month. Must be from 1 to 31 and valid for the year and
57
+ # month, or 0 if specifying a datetime without a day.
57
58
  # @!attribute [rw] hours
58
59
  # @return [::Integer]
59
- # Required. Hours of day in 24 hour format. Should be from 0 to 23. An API
60
- # may choose to allow the value "24:00:00" for scenarios like business
61
- # closing time.
60
+ # Optional. Hours of day in 24 hour format. Should be from 0 to 23, defaults
61
+ # to 0 (midnight). An API may choose to allow the value "24:00:00" for
62
+ # scenarios like business closing time.
62
63
  # @!attribute [rw] minutes
63
64
  # @return [::Integer]
64
- # Required. Minutes of hour of day. Must be from 0 to 59.
65
+ # Optional. Minutes of hour of day. Must be from 0 to 59, defaults to 0.
65
66
  # @!attribute [rw] seconds
66
67
  # @return [::Integer]
67
- # Required. Seconds of minutes of the time. Must normally be from 0 to 59. An
68
- # API may allow the value 60 if it allows leap-seconds.
68
+ # Optional. Seconds of minutes of the time. Must normally be from 0 to 59,
69
+ # defaults to 0. An API may allow the value 60 if it allows leap-seconds.
69
70
  # @!attribute [rw] nanos
70
71
  # @return [::Integer]
71
- # Required. Fractions of seconds in nanoseconds. Must be from 0 to
72
- # 999,999,999.
72
+ # Optional. Fractions of seconds in nanoseconds. Must be from 0 to
73
+ # 999,999,999, defaults to 0.
73
74
  # @!attribute [rw] utc_offset
74
75
  # @return [::Google::Protobuf::Duration]
75
76
  # UTC offset. Must be whole seconds, between -18 hours and +18 hours.
@@ -91,10 +92,10 @@ module Google
91
92
  # [IANA Time Zone Database](https://www.iana.org/time-zones).
92
93
  # @!attribute [rw] id
93
94
  # @return [::String]
94
- # IANA Time Zone Database time zone, e.g. "America/New_York".
95
+ # IANA Time Zone Database time zone. For example "America/New_York".
95
96
  # @!attribute [rw] version
96
97
  # @return [::String]
97
- # Optional. IANA Time Zone Database version number, e.g. "2019a".
98
+ # Optional. IANA Time Zone Database version number. For example "2019a".
98
99
  class TimeZone
99
100
  include ::Google::Protobuf::MessageExts
100
101
  extend ::Google::Protobuf::MessageExts::ClassMethods
@@ -19,23 +19,23 @@
19
19
 
20
20
  module Google
21
21
  module Type
22
- # Represents a postal address, e.g. for postal delivery or payments addresses.
23
- # Given a postal address, a postal service can deliver items to a premise, P.O.
24
- # Box or similar.
25
- # It is not intended to model geographical locations (roads, towns,
26
- # mountains).
22
+ # Represents a postal address, such as for postal delivery or payments
23
+ # addresses. With a postal address, a postal service can deliver items to a
24
+ # premise, P.O. box, or similar. A postal address is not intended to model
25
+ # geographical locations like roads, towns, or mountains.
27
26
  #
28
- # In typical usage an address would be created via user input or from importing
27
+ # In typical usage, an address would be created by user input or from importing
29
28
  # existing data, depending on the type of process.
30
29
  #
31
- # Advice on address input / editing:
32
- # - Use an i18n-ready address widget such as
33
- # https://github.com/google/libaddressinput)
34
- # - Users should not be presented with UI elements for input or editing of
35
- # fields outside countries where that field is used.
30
+ # Advice on address input or editing:
36
31
  #
37
- # For more guidance on how to use this schema, please see:
38
- # https://support.google.com/business/answer/6397478
32
+ # - Use an internationalization-ready address widget such as
33
+ # https://github.com/google/libaddressinput.
34
+ # - Users should not be presented with UI elements for input or editing of
35
+ # fields outside countries where that field is used.
36
+ #
37
+ # For more guidance on how to use this schema, see:
38
+ # https://support.google.com/business/answer/6397478.
39
39
  # @!attribute [rw] revision
40
40
  # @return [::Integer]
41
41
  # The schema revision of the `PostalAddress`. This must be set to 0, which is
@@ -46,8 +46,8 @@ module Google
46
46
  # @return [::String]
47
47
  # Required. CLDR region code of the country/region of the address. This
48
48
  # is never inferred and it is up to the user to ensure the value is
49
- # correct. See http://cldr.unicode.org/ and
50
- # http://www.unicode.org/cldr/charts/30/supplemental/territory_information.html
49
+ # correct. See https://cldr.unicode.org/ and
50
+ # https://www.unicode.org/cldr/charts/30/supplemental/territory_information.html
51
51
  # for details. Example: "CH" for Switzerland.
52
52
  # @!attribute [rw] language_code
53
53
  # @return [::String]
@@ -67,55 +67,56 @@ module Google
67
67
  # @return [::String]
68
68
  # Optional. Postal code of the address. Not all countries use or require
69
69
  # postal codes to be present, but where they are used, they may trigger
70
- # additional validation with other parts of the address (e.g. state/zip
71
- # validation in the U.S.A.).
70
+ # additional validation with other parts of the address (for example,
71
+ # state or zip code validation in the United States).
72
72
  # @!attribute [rw] sorting_code
73
73
  # @return [::String]
74
74
  # Optional. Additional, country-specific, sorting code. This is not used
75
75
  # in most regions. Where it is used, the value is either a string like
76
- # "CEDEX", optionally followed by a number (e.g. "CEDEX 7"), or just a number
77
- # alone, representing the "sector code" (Jamaica), "delivery area indicator"
78
- # (Malawi) or "post office indicator" (e.g. Côte d'Ivoire).
76
+ # "CEDEX", optionally followed by a number (for example, "CEDEX 7"), or just
77
+ # a number alone, representing the "sector code" (Jamaica), "delivery area
78
+ # indicator" (Malawi) or "post office indicator" (Côte d'Ivoire).
79
79
  # @!attribute [rw] administrative_area
80
80
  # @return [::String]
81
81
  # Optional. Highest administrative subdivision which is used for postal
82
82
  # addresses of a country or region.
83
83
  # For example, this can be a state, a province, an oblast, or a prefecture.
84
- # Specifically, for Spain this is the province and not the autonomous
85
- # community (e.g. "Barcelona" and not "Catalonia").
86
- # Many countries don't use an administrative area in postal addresses. E.g.
87
- # in Switzerland this should be left unpopulated.
84
+ # For Spain, this is the province and not the autonomous
85
+ # community (for example, "Barcelona" and not "Catalonia").
86
+ # Many countries don't use an administrative area in postal addresses. For
87
+ # example, in Switzerland, this should be left unpopulated.
88
88
  # @!attribute [rw] locality
89
89
  # @return [::String]
90
- # Optional. Generally refers to the city/town portion of the address.
90
+ # Optional. Generally refers to the city or town portion of the address.
91
91
  # Examples: US city, IT comune, UK post town.
92
92
  # In regions of the world where localities are not well defined or do not fit
93
- # into this structure well, leave locality empty and use address_lines.
93
+ # into this structure well, leave `locality` empty and use `address_lines`.
94
94
  # @!attribute [rw] sublocality
95
95
  # @return [::String]
96
96
  # Optional. Sublocality of the address.
97
- # For example, this can be neighborhoods, boroughs, districts.
97
+ # For example, this can be a neighborhood, borough, or district.
98
98
  # @!attribute [rw] address_lines
99
99
  # @return [::Array<::String>]
100
100
  # Unstructured address lines describing the lower levels of an address.
101
101
  #
102
- # Because values in address_lines do not have type information and may
103
- # sometimes contain multiple values in a single field (e.g.
102
+ # Because values in `address_lines` do not have type information and may
103
+ # sometimes contain multiple values in a single field (for example,
104
104
  # "Austin, TX"), it is important that the line order is clear. The order of
105
- # address lines should be "envelope order" for the country/region of the
106
- # address. In places where this can vary (e.g. Japan), address_language is
107
- # used to make it explicit (e.g. "ja" for large-to-small ordering and
108
- # "ja-Latn" or "en" for small-to-large). This way, the most specific line of
109
- # an address can be selected based on the language.
105
+ # address lines should be "envelope order" for the country or region of the
106
+ # address. In places where this can vary (for example, Japan),
107
+ # `address_language` is used to make it explicit (for example, "ja" for
108
+ # large-to-small ordering and "ja-Latn" or "en" for small-to-large). In this
109
+ # way, the most specific line of an address can be selected based on the
110
+ # language.
110
111
  #
111
112
  # The minimum permitted structural representation of an address consists
112
- # of a region_code with all remaining information placed in the
113
- # address_lines. It would be possible to format such an address very
113
+ # of a `region_code` with all remaining information placed in the
114
+ # `address_lines`. It would be possible to format such an address very
114
115
  # approximately without geocoding, but no semantic reasoning could be
115
116
  # made about any of the address components until it was at least
116
117
  # partially resolved.
117
118
  #
118
- # Creating an address only containing a region_code and address_lines, and
119
+ # Creating an address only containing a `region_code` and `address_lines` and
119
120
  # then geocoding is the recommended way to handle completely unstructured
120
121
  # addresses (as opposed to guessing which parts of the address should be
121
122
  # localities or administrative areas).
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: google-cloud-document_ai-v1
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.11.0
4
+ version: 1.12.1
5
5
  platform: ruby
6
6
  authors:
7
7
  - Google LLC
@@ -129,7 +129,7 @@ required_ruby_version: !ruby/object:Gem::Requirement
129
129
  requirements:
130
130
  - - ">="
131
131
  - !ruby/object:Gem::Version
132
- version: '3.1'
132
+ version: '3.2'
133
133
  required_rubygems_version: !ruby/object:Gem::Requirement
134
134
  requirements:
135
135
  - - ">="