View Source API Reference google_api_content_warehouse v0.6.0

API client metadata for GoogleApi.ContentWarehouse.V1.

API calls for all endpoints tagged Projects.

Handle Tesla connections for GoogleApi.ContentWarehouse.V1.

The identity to configure a CloudSQL instance provisioned via SLM Terraform.

The identity to configure a GCS bucket.

The dynamic IAM bindings to be granted after tenant projects are created.

The configuration for a spanner database provisioning. Next ID: 8

The options to create a spanner database. KMS key access audit logging and AxT logging will be associated with the given resource name, resource type and service name. Please ensure to give right options to enable correct audit logging and AxT logging.

The identity to configure a service account.

The identity to configure a tenant project.

The tenant project and tenant resources. Next ID: 10

A collection of tenant resources.

The identity of service accounts that have been explicitly created under tenant projects.

Describes the billing configuration for a new tenant project.

Translates to IAM Policy bindings (without auditing at this level)

Represents the action responsible for access control list management operations.

Represents the action triggered by Rule Engine when the rule is true.

Represents the output of the Action Executor.

Represents the result of executing an action.

Represents the action responsible for adding document under a folder.

Request Option for processing Cloud AI Document in CW Document.

Request message for DocumentLinkService.CreateDocumentLink.

Metadata object for CreateDocument request (currently empty).

Request message for DocumentService.CreateDocument.

Response message for DocumentService.CreateDocument.

To support the custom weighting across document schemas.

Represents the action responsible for properties update operations.

Represents the action responsible for data validation operations.

DateTime values.

Configurations for a date time property.

Represents the action responsible for deleting the document.

Request message for DocumentLinkService.DeleteDocumentLink.

Request message for DocumentService.DeleteDocument.

Defines the structure for content warehouse document proto.

A document-link between source and target document.

Attributes

• customPropertyFilter (type: String.t, default: nil) - This filter specifies a structured syntax to match against the [PropertyDefinition].is_filterable marked as true. The syntax for this expression is a subset of SQL syntax. Supported operators are: =, !=, <, <=, >, and >= where the left of the operator is a property name and the right of the operator is a number or a quoted string. You must escape backslash (\) and quote (\") characters. Supported functions are LOWER([property_name]) to perform a case insensitive match and EMPTY([property_name]) to filter on the existence of a key. Boolean expressions (AND/OR/NOT) are supported up to 3 levels of nesting (for example, "((A AND B AND C) OR NOT D) AND E"), a maximum of 100 comparisons or functions are allowed in the expression. The expression must be < 6000 bytes in length. Sample Query: (LOWER(driving_license)="class \"a\"" OR EMPTY(driving_license)) AND driving_years > 10
• customWeightsMetadata (type: GoogleApi.ContentWarehouse.V1.Model.GoogleCloudContentwarehouseV1CustomWeightsMetadata.t, default: nil) - To support the custom weighting across document schemas, customers need to provide the properties to be used to boost the ranking in the search request. For a search query with CustomWeightsMetadata specified, only the RetrievalImportance for the properties in the CustomWeightsMetadata will be honored.
• documentCreatorFilter (type: list(String.t), default: nil) - The exact creator(s) of the documents to search against. If a value isn't specified, documents within the search results are associated with any creator. If multiple values are specified, documents within the search results may be associated with any of the specified creators.
• documentNameFilter (type: list(String.t), default: nil) - Search the documents in the list. Format: projects/{project_number}/locations/{location}/documents/{document_id}.
• documentSchemaNames (type: list(String.t), default: nil) - This filter specifies the exact document schema Document.document_schema_name of the documents to search against. If a value isn't specified, documents within the search results are associated with any schema. If multiple values are specified, documents within the search results may be associated with any of the specified schemas. At most 20 document schema names are allowed.
• fileTypeFilter (type: GoogleApi.ContentWarehouse.V1.Model.GoogleCloudContentwarehouseV1FileTypeFilter.t, default: nil) - This filter specifies the types of files to return: ALL, FOLDER, or FILE. If FOLDER or FILE is specified, then only either folders or files will be returned, respectively. If ALL is specified, both folders and files will be returned. If no value is specified, ALL files will be returned.
• folderNameFilter (type: String.t, default: nil) - Search all the documents under this specified folder. Format: projects/{project_number}/locations/{location}/documents/{document_id}.
• isNlQuery (type: boolean(), default: nil) - Experimental, do not use. If the query is a natural language question. False by default. If true, then the question-answering feature will be used instead of search, and result_count in SearchDocumentsRequest must be set. In addition, all other input fields related to search (pagination, histograms, etc.) will be ignored.
• propertyFilter (type: list(GoogleApi.ContentWarehouse.V1.Model.GoogleCloudContentwarehouseV1PropertyFilter.t), default: nil) - This filter specifies a structured syntax to match against the PropertyDefinition.is_filterable marked as true. The relationship between the PropertyFilters is OR.
• query (type: String.t, default: nil) - The query string that matches against the full text of the document and the searchable properties. The query partially supports Google AIP style syntax. Specifically, the query supports literals, logical operators, negation operators, comparison operators, and functions. Literals: A bare literal value (examples: "42", "Hugo") is a value to be matched against. It searches over the full text of the document and the searchable properties. Logical operators: "AND", "and", "OR", and "or" are binary logical operators (example: "engineer OR developer"). Negation operators: "NOT" and "!" are negation operators (example: "NOT software"). Comparison operators: support the binary comparison operators =, !=, <, >, <= and >= for string, numeric, enum, boolean. Also support like operator ~~ for string. It provides semantic search functionality by parsing, stemming and doing synonyms expansion against the input query. To specify a property in the query, the left hand side expression in the comparison must be the property ID including the parent. The right hand side must be literals. For example: "\"projects/123/locations/us\".property_a < 1" matches results whose "property_a" is less than 1 in project 123 and us location. The literals and comparison expression can be connected in a single query (example: "software engineer \"projects/123/locations/us\".salary > 100"). Functions: supported functions are LOWER([property_name]) to perform a case insensitive match and EMPTY([property_name]) to filter on the existence of a key. Support nested expressions connected using parenthesis and logical operators. The default logical operators is AND if there is no operators between expressions. The query can be used with other filters e.g. time_filters and folder_name_filter. They are connected with AND operator under the hood. The maximum number of allowed characters is 255.
• queryContext (type: list(String.t), default: nil) - For custom synonyms. Customers provide the synonyms based on context. One customer can provide multiple set of synonyms based on different context. The search query will be expanded based on the custom synonyms of the query context set. By default, no custom synonyms wll be applied if no query context is provided. It is not supported for CMEK compliant deployment.
• timeFilters (type: list(GoogleApi.ContentWarehouse.V1.Model.GoogleCloudContentwarehouseV1TimeFilter.t), default: nil) - Documents created/updated within a range specified by this filter are searched against.

References to the documents.

A document schema used to define document structure.

Enum values.

Configurations for an enum/categorical property.

Represents the string value of the enum field.

The configuration of exporting documents from the Document Warehouse to CDW pipeline.

Request message for DocumentService.FetchAcl

Response message for DocumentService.FetchAcl.

Filter for the specific types of documents returned.

Float values.

Configurations for a float property.

The configuration of the Cloud Storage Ingestion pipeline.

The configuration of the Cloud Storage Ingestion with DocAI Processors pipeline.

Request message for DocumentService.GetDocument.

The histogram request.

Attributes

• documentSchemas (type: list(String.t), default: nil) - This filter specifies the exact document schema(s) Document.document_schema_name to run histogram query against. It is optional. It will perform histogram for property names for all the document schemas if it is not set. At most 10 document schema names are allowed. Format: projects/{project_number}/locations/{location}/documentSchemas/{document_schema_id}.
• propertyNames (type: list(String.t), default: nil) - It is optional. It will perform histogram for all the property names if it is not set. The properties need to be defined with the is_filterable flag set to true and the name of the property should be in the format: "schemaId.propertyName". The property needs to be defined in the schema. Example: the schema id is abc. Then the name of property for property MORTGAGE_TYPE will be "abc.MORTGAGE_TYPE".
• yAxis (type: String.t, default: nil) - By default, the y_axis is HISTOGRAM_YAXIS_DOCUMENT if this field is not set.

Histogram result that matches HistogramQuery specified in searches.

The ingestion pipeline config.

Request message for projectService.InitializeProject

Response message for projectService.InitializeProject

Integer values.

Configurations for an integer property.

A triggered rule that failed the validation check(s) after parsing.

Response message for DocumentSchemaService.ListDocumentSchemas.

Response message for DocumentLinkService.ListLinkedSources.

Response message for DocumentLinkService.ListLinkedSources.

Request message for DocumentLinkService.ListLinkedTargets.

Response message for DocumentLinkService.ListLinkedTargets.

Response message for RuleSetService.ListRuleSets.

Response message for SynonymSetService.ListSynonymSets.

Request message for DocumentService.LockDocument.

Map property value. Represents a structured entries of key value pairs, consisting of field names which map to dynamically typed values.

Configurations for a Map property.

Options for merging updated fields.

The configuration of processing documents in Document Warehouse with DocAi processors pipeline.

The DocAI processor information.

Status of a project, including the project state, dbType, aclMode and etc.

Property of a document.

Property values.

Defines the metadata for a schema property.

The schema source information.

Attributes

• condition (type: String.t, default: nil) - The filter condition. The syntax for this expression is a subset of SQL syntax. Supported operators are: =, !=, <, <=, >, >=, and ~~ where the left of the operator is a property name and the right of the operator is a number or a quoted string. You must escape backslash (\) and quote (\") characters. ~~ is the LIKE operator. The right of the operator must be a string. The only supported property data type for LIKE is text_values. It provides semantic search functionality by parsing, stemming and doing synonyms expansion against the input query. It matches if the property contains semantic similar content to the query. It is not regex matching or wildcard matching. For example, "property.company ~~ \"google\"" will match records whose property property.compnay have values like "Google Inc.", "Google LLC" or "Google Company". Supported functions are LOWER([property_name]) to perform a case insensitive match and EMPTY([property_name]) to filter on the existence of a key. Boolean expressions (AND/OR/NOT) are supported up to 3 levels of nesting (for example, "((A AND B AND C) OR NOT D) AND E"), a maximum of 100 comparisons or functions are allowed in the expression. The expression must be < 6000 bytes in length. Only properties that are marked filterable are allowed (PropertyDefinition.is_filterable). Property names do not need to be prefixed by the document schema id (as is the case with histograms), however property names will need to be prefixed by its parent hierarchy, if any. For example: top_property_name.sub_property_name. Sample Query: (LOWER(driving_license)="class \"a\"" OR EMPTY(driving_license)) AND driving_years > 10 CMEK compliant deployment only supports: Operators: =, <, <=, >, and >=. Boolean expressions: AND and OR.
• documentSchemaName (type: String.t, default: nil) - The Document schema name Document.document_schema_name. Format: projects/{project_number}/locations/{location}/documentSchemas/{document_schema_id}.

Configurations for a nested structured data property.

Represents the action responsible for publishing messages to a Pub/Sub topic.

Additional result info for the question-answering feature.

A text span in the search text snippet that represents a highlighted section (answer context, highly relevant sentence, etc.).

Represents the action responsible for remove a document from a specific folder.

Meta information is used to improve the performance of the service.

Additional information returned to client, such as debugging information.

Represents the rule for a content warehouse trigger.

Represents a rule and outputs of associated actions.

Records the output of Rule Engine including rule evaluation and actions result.

Represents the output of the Rule Evaluator.

Represents a set of rules from a single customer.

Metadata message of RunPipeline method.

The metadata message for Export-to-CDW pipeline.

The metadata message for GcsIngest pipeline.

The status of processing a document.

The metadata message for Process-with-DocAi pipeline.

Request message for DocumentService.RunPipeline.

Request message for DocumentService.SearchDocuments.

Response message for DocumentService.SearchDocuments.

Document entry with metadata inside SearchDocumentsResponse

Request message for DocumentService.SetAcl.

Response message for DocumentService.SetAcl.

Represents a list of synonyms for a given context. For example a context "sales" could contain: Synonym 1: sale, invoice, bill, order Synonym 2: money, credit, finance, payment Synonym 3: shipping, freight, transport Each SynonymSets should be disjoint

Represents a list of words given by the customer All these words are synonyms of each other.

String/text values.

Configurations for a text property.

Filter on create timestamp or update timestamp of documents.

Timestamp values.

Configurations for a timestamp property.

Timestamp value type.

Metadata object for UpdateDocument request (currently empty).

Request message for DocumentService.UpdateDocument.

Response message for DocumentService.UpdateDocument.

Request message for DocumentSchemaService.UpdateDocumentSchema.

Options for Update operations.

Request message for RuleSetService.UpdateRuleSet.

The user information.

Value represents a dynamically typed value which can be either be a float, a integer, a string, or a datetime value. A producer of value is expected to set one of these variants. Absence of any variant indicates an error.

Specifies the schema property name.

Metadata object for CreateDocument request (currently empty).

Response message for projectService.InitializeProject

Metadata object for UpdateDocument request (currently empty).

Encodes the detailed information of a barcode.

A bounding polygon for the detected image annotation.

Document represents the canonical document resource in Document AI. It is an interchange format that provides insights into documents and allows for collaboration between users and Document AI to iterate and optimize for quality.

Represents the chunks that the document is divided into.

Represents a chunk.

Represents the page footer associated with the chunk.

Represents the page header associated with the chunk.

Represents where the chunk starts and ends in the document.

Represents the parsed layout of a document as a collection of blocks that the document is divided into.

Represents a block. A block could be one of the various types (text, table, list) supported.

Represents a list type block.

Represents an entry in the list.

Represents where the block starts and ends in the document.

Represents a table type block.

Represents a cell in a table row.

Represents a row in a table.

Represents a text type block.

An entity that could be a phrase in the text or a property that belongs to the document. It is a known entity type, such as a person, an organization, or location.

Parsed and normalized entity value.

Relationship between Entities.

A page in a Document.

Referencing the visual context of the entity in the Document.pages. Page anchors can be cross-page, consist of multiple bounding polygons and optionally reference specific layout element types.

Represents a weak reference to a page element within a document.

A block has a set of lines (collected into paragraphs) that have a common line-spacing and orientation.

A detected barcode.

Detected language for a structural component.

Dimension for the page.

A form field detected on the page.

Rendered image contents for this page.

Image quality scores for the page image.

Image Quality Defects

Visual element describing a layout unit on a page.

A collection of tokens that a human would perceive as a line. Does not cross column boundaries, can be horizontal, vertical, etc.

Representation for transformation matrix, intended to be compatible and used with OpenCV format for image manipulation.

A collection of lines that a human would perceive as a paragraph.

A detected symbol.

A table representation similar to HTML table structure.

A cell representation inside the table.

A row of table cells.

A detected token.

Detected break at the end of a Token.

Font and other text style attributes.

Detected non-text visual elements e.g. checkbox, signature etc. on the page.

Structure to identify provenance relationships between annotations in different revisions.

The parent element the current element is based on. Used for referencing/aligning, removal and replacement operations.

Contains past or forward revisions of this document.

Human Review information of the document.

For a large document, sharding may be performed to produce several document shards. Each document shard contains this field to detail which shard it is.

Annotation for common text style attributes. This adheres to CSS conventions as much as possible.

Font size with unit.

Text reference indexing into the Document.text.

A text segment in the Document.text. The indices may be out of bounds which indicate that the text extends into another document shard for large sharded documents. See ShardInfo.text_offset

This message is used for text changes aka. OCR corrections.

A vertex represents a 2D point in the image. NOTE: the normalized vertex coordinates are relative to the original image and range from 0 to 1.

A vertex represents a 2D point in the image. NOTE: the vertex coordinates are in the same scale as the original image.

Specifies the audit configuration for a service. The configuration determines which permission types are logged, and what identities, if any, are exempted from logging. An AuditConfig must have one or more AuditLogConfigs. If there are AuditConfigs for both allServices and a specific service, the union of the two AuditConfigs is used for that service: the log_types specified in each AuditConfig are enabled, and the exempted_members in each AuditLogConfig are exempted. Example Policy with multiple AuditConfigs: { "audit_configs": [ { "service": "allServices", "audit_log_configs": [ { "log_type": "DATA_READ", "exempted_members": [ "user:jose@example.com" ] }, { "log_type": "DATA_WRITE" }, { "log_type": "ADMIN_READ" } ] }, { "service": "sampleservice.googleapis.com", "audit_log_configs": [ { "log_type": "DATA_READ" }, { "log_type": "DATA_WRITE", "exempted_members": [ "user:aliya@example.com" ] } ] } ] } For sampleservice, this policy enables DATA_READ, DATA_WRITE and ADMIN_READ logging. It also exempts jose@example.com from DATA_READ logging, and aliya@example.com from DATA_WRITE logging.

Provides the configuration for logging a type of permissions. Example: { "audit_log_configs": [ { "log_type": "DATA_READ", "exempted_members": [ "user:jose@example.com" ] }, { "log_type": "DATA_WRITE" } ] } This enables 'DATA_READ' and 'DATA_WRITE' logging, while exempting jose@example.com from DATA_READ logging.

Associates members, or principals, with a role.

An Identity and Access Management (IAM) policy, which specifies access controls for Google Cloud resources. A Policy is a collection of bindings. A binding binds one or more members, or principals, to a single role. Principals can be user accounts, service accounts, Google groups, and domains (such as G Suite). A role is a named list of permissions; each role can be an IAM predefined role or a user-created custom role. For some types of Google Cloud resources, a binding can also specify a condition, which is a logical expression that allows access to a resource only if the expression evaluates to true. A condition can add constraints based on attributes of the request, the resource, or both. To learn which resources support conditions in their IAM policies, see the IAM documentation. JSON example: { "bindings": [ { "role": "roles/resourcemanager.organizationAdmin", "members": [ "user:mike@example.com", "group:admins@example.com", "domain:google.com", "serviceAccount:my-project-id@appspot.gserviceaccount.com" ] }, { "role": "roles/resourcemanager.organizationViewer", "members": [ "user:eve@example.com" ], "condition": { "title": "expirable access", "description": "Does not grant access after Sep 2020", "expression": "request.time < timestamp('2020-10-01T00:00:00.000Z')", } } ], "etag": "BwWWja0YfJA=", "version": 3 } YAML example: bindings: - members: - user:mike@example.com - group:admins@example.com - domain:google.com - serviceAccount:my-project-id@appspot.gserviceaccount.com role: roles/resourcemanager.organizationAdmin - members: - user:eve@example.com role: roles/resourcemanager.organizationViewer condition: title: expirable access description: Does not grant access after Sep 2020 expression: request.time < timestamp('2020-10-01T00:00:00.000Z') etag: BwWWja0YfJA= version: 3 For a description of IAM and its features, see the IAM documentation.

This resource represents a long-running operation that is the result of a network API call.

A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance: service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); }

The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.

Represents a color in the RGBA color space. This representation is designed for simplicity of conversion to and from color representations in various languages over compactness. For example, the fields of this representation can be trivially provided to the constructor of java.awt.Color in Java; it can also be trivially provided to UIColor's +colorWithRed:green:blue:alpha method in iOS; and, with just a little work, it can be easily formatted into a CSS rgba() string in JavaScript. This reference page doesn't have information about the absolute color space that should be used to interpret the RGB value—for example, sRGB, Adobe RGB, DCI-P3, and BT.2020. By default, applications should assume the sRGB color space. When color equality needs to be decided, implementations, unless documented otherwise, treat two colors as equal if all their red, green, blue, and alpha values each differ by at most 1e-5. Example (Java): import com.google.type.Color; // ... public static java.awt.Color fromProto(Color protocolor) { float alpha = protocolor.hasAlpha() ? protocolor.getAlpha().getValue() : 1.0; return new java.awt.Color( protocolor.getRed(), protocolor.getGreen(), protocolor.getBlue(), alpha); } public static Color toProto(java.awt.Color color) { float red = (float) color.getRed(); float green = (float) color.getGreen(); float blue = (float) color.getBlue(); float denominator = 255.0; Color.Builder resultBuilder = Color .newBuilder() .setRed(red / denominator) .setGreen(green / denominator) .setBlue(blue / denominator); int alpha = color.getAlpha(); if (alpha != 255) { result.setAlpha( FloatValue .newBuilder() .setValue(((float) alpha) / denominator) .build()); } return resultBuilder.build(); } // ... Example (iOS / Obj-C): // ... static UIColor fromProto(Color protocolor) { float red = [protocolor red]; float green = [protocolor green]; float blue = [protocolor blue]; FloatValue alpha_wrapper = [protocolor alpha]; float alpha = 1.0; if (alpha_wrapper != nil) { alpha = [alpha_wrapper value]; } return [UIColor colorWithRed:red green:green blue:blue alpha:alpha]; } static Color toProto(UIColor color) { CGFloat red, green, blue, alpha; if (![color getRed:&red green:&green blue:&blue alpha:&alpha]) { return nil; } Color result = [[Color alloc] init]; [result setRed:red]; [result setGreen:green]; [result setBlue:blue]; if (alpha <= 0.9999) { [result setAlpha:floatWrapperWithValue(alpha)]; } [result autorelease]; return result; } // ... Example (JavaScript): // ... var protoToCssColor = function(rgb_color) { var redFrac = rgb_color.red || 0.0; var greenFrac = rgb_color.green || 0.0; var blueFrac = rgb_color.blue || 0.0; var red = Math.floor(redFrac 255); var green = Math.floor(greenFrac 255); var blue = Math.floor(blueFrac * 255); if (!('alpha' in rgb_color)) { return rgbToCssColor(red, green, blue); } var alphaFrac = rgb_color.alpha.value || 0.0; var rgbParams = [red, green, blue].join(','); return ['rgba(', rgbParams, ',', alphaFrac, ')'].join(''); }; var rgbToCssColor = function(red, green, blue) { var rgbNumber = new Number((red << 16) | (green << 8) | blue); var hexString = rgbNumber.toString(16); var missingZeros = 6 - hexString.length; var resultBuilder = ['#']; for (var i = 0; i < missingZeros; i++) { resultBuilder.push('0'); } resultBuilder.push(hexString); return resultBuilder.join(''); }; // ...

Represents a whole or partial calendar date, such as a birthday. The time of day and time zone are either specified elsewhere or are insignificant. The date is relative to the Gregorian Calendar. This can represent one of the following: A full date, with non-zero year, month, and day values. A month and day, with a zero year (for example, an anniversary). A year on its own, with a zero month and a zero day. A year and month, with a zero day (for example, a credit card expiration date). Related types: google.type.TimeOfDay google.type.DateTime * google.protobuf.Timestamp

Represents civil time (or occasionally physical time). This type can represent a civil time in one of a few possible ways: When utc_offset is set and time_zone is unset: a civil time on a calendar day with a particular offset from UTC. When time_zone is set and utc_offset is unset: a civil time on a calendar day in a particular time zone. * When neither time_zone nor utc_offset is set: a civil time on a calendar day in local time. The date is relative to the Proleptic Gregorian Calendar. If year, month, or day are 0, the DateTime is considered not to have a specific year, month, or day respectively. This type may also be used to represent a physical time if all the date and time fields are set and either case of the time_offset oneof is set. Consider using Timestamp message for physical time instead. If your use case also would like to store the user's timezone, that can be done in another field. This type is more flexible than some applications may want. Make sure to document and validate your application's limitations.

Represents a textual expression in the Common Expression Language (CEL) syntax. CEL is a C-like expression language. The syntax and semantics of CEL are documented at https://github.com/google/cel-spec. Example (Comparison): title: "Summary size limit" description: "Determines if a summary is less than 100 chars" expression: "document.summary.size() < 100" Example (Equality): title: "Requestor is owner" description: "Determines if requestor is the document owner" expression: "document.owner == request.auth.claims.email" Example (Logic): title: "Public documents" description: "Determine whether the document should be publicly visible" expression: "document.type != 'private' && document.type != 'internal'" Example (Data Manipulation): title: "Notification string" description: "Create a notification string with a timestamp." expression: "'New message received at ' + string(document.create_time)" The exact variables and functions that may be referenced within an expression are determined by the service that evaluates it. See the service documentation for additional information.

Represents a time interval, encoded as a Timestamp start (inclusive) and a Timestamp end (exclusive). The start must be less than or equal to the end. When the start equals the end, the interval is empty (matches no time). When both start and end are unspecified, the interval matches any time.

Represents an amount of money with its currency type.

Represents a postal address, e.g. for postal delivery or payments addresses. Given a postal address, a postal service can deliver items to a premise, P.O. Box or similar. It is not intended to model geographical locations (roads, towns, mountains). In typical usage an address would be created via user input or from importing existing data, depending on the type of process. Advice on address input / editing: - Use an internationalization-ready address widget such as https://github.com/google/libaddressinput) - Users should not be presented with UI elements for input or editing of fields outside countries where that field is used. For more guidance on how to use this schema, please see: https://support.google.com/business/answer/6397478

Represents a time zone from the IANA Time Zone Database.