Organiza tus páginas con colecciones
Guarda y categoriza el contenido según tus preferencias.
Cada declaración está diseñada con un consumidor en mente; el consumidor del resumen es el que lee y verifica una declaración realizada por un principal y, luego, toma medidas en función de esa declaración. Más específicamente, un consumidor realiza estos pasos básicos:
Solicita la lista de declaraciones de una principal específica
Verifica si la lista contiene una sentencia dada en comparación con un objetivo determinado.
Valida que el objetivo de la instrucción sea el objetivo (sitio web o aplicación) que crees que es
Realizar la acción especificada en la instrucción, si así lo deseas
Muchos casos de uso consumen sentencias detrás de escena. Por ejemplo, Android App Linking consume declaraciones de permisos de vínculos realizadas por un sitio web para habilitar vínculos directamente a una app. Una app indica que acepta ser un objetivo para cualquiera de esas declaraciones agregando un código especial (un controlador de intents) en su manifiesto.
Puedes realizar los pasos 1 y 2 anteriores (solicitar y validar una declaración) de dos maneras: usando nuestra API o manualmente (con tu propia implementación).
Cómo consumir declaraciones con la API de Vínculos de recursos digitales
La API de Vínculos de recursos digitales admite dos métodos, Check() y List(), para encontrar o validar declaraciones:
Check() toma una fuente, un destino y una relación, y verifica que la fuente realice la declaración enviada sobre el destino.
List() enumera todas las declaraciones de una fuente determinada.
Consumo manual de instrucciones
El protocolo de Vínculos de recursos digitales es abierto, por lo que puedes crear una implementación por tu cuenta.
Para consumir las declaraciones de sitios web, puedes realizar una solicitud GET de HTTP para la lista de instrucciones correspondiente y analizarla tú mismo. Por ejemplo, la lista de sentencias correspondiente para el sitio web http://example.digitalassetlinks.org se encuentra en http://example.digitalassetlinks.org/.well-known/assetlinks.json.
Para consumir las declaraciones realizadas por apps para Android, debes acceder al manifiesto del paquete de APK correspondiente. En dispositivos Android, esto se puede lograr con la interfaz PackageManager.
Presta especial atención a los significados específicos de las declaraciones de Vínculos de recursos digitales. Consulta la especificación de los vínculos de recursos si tienes dudas.
[[["Fácil de comprender","easyToUnderstand","thumb-up"],["Resolvió mi problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Falta la información que necesito","missingTheInformationINeed","thumb-down"],["Muy complicado o demasiados pasos","tooComplicatedTooManySteps","thumb-down"],["Desactualizado","outOfDate","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Problema con las muestras o los códigos","samplesCodeIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 2024-06-26 (UTC)"],[[["\u003cp\u003eDigital Asset Links enable websites and apps to make statements about their relationships, which other apps and services can then verify and act upon.\u003c/p\u003e\n"],["\u003cp\u003eYou can consume these statements using the Digital Asset Links API (\u003ccode\u003eCheck()\u003c/code\u003e and \u003ccode\u003eList()\u003c/code\u003e methods) or manually by retrieving and parsing the statement list.\u003c/p\u003e\n"],["\u003cp\u003eBefore implementing your own solution, check if existing mechanisms like Android App Linking already handle your desired scenario.\u003c/p\u003e\n"],["\u003cp\u003eWebsites publish their statements in a JSON file located at \u003ccode\u003e.well-known/assetlinks.json\u003c/code\u003e, while Android app statements are found within their manifest file.\u003c/p\u003e\n"],["\u003cp\u003eFor a deeper understanding of statement meanings and the underlying protocol, refer to the Asset Links Specification.\u003c/p\u003e\n"]]],[],null,["# Consuming a statement\n\nEvery statement is designed with a *consumer* in mind; the statement consumer is the one who reads and verifies a statement made by a principal, then takes action based on that statement. More specifically, a consumer performs these basic steps:\n\n1. Request the statement list from a specific principal\n2. Check to see if the list contains a given statement against a given target\n3. Validate that the target in the statement is the target (website or app) that you think it is\n4. Perform the action specified by the statement, if you choose to\n\n[Many use cases](/digital-asset-links/v1/using) consume statements for you behind the scenes. For example, Android App Linking consumes link permission statements made by a website to enable links directly into an app. An app indicates that it agrees to be a target to any such statements by adding special code (an intent handler) in its manifest.\n| Be sure to check that your scenario doesn't have a special mechanism for consuming or implementing a statement before handling it manually.\n\nYou can perform steps 1 and 2 above --- requesting and validating a statement --- in two ways: using our API or manually (using your own implementation).\n\nConsuming statements using the Digital Asset Links API\n------------------------------------------------------\n\n**The Digital Asset Links API** supports two methods: `Check()` and `List()` to find or validate statements:\n\n- [Check()](/digital-asset-links/reference/rest) takes a source, target, and relationship and verifies that the source makes the submitted statement about the target.\n- [List()](/digital-asset-links/reference/rest) lists all statements made by a given source.\n\n| In order to use the API, you need an [API key](https://support.google.com/googleapi/answer/6158862) and you must first activate the API for your project. To do that, follow these steps:\n|\n| 1. Go to the [Google Developers Console](https://console.developers.google.com/project/_/apiui/apiview/digitalassetlinks/overview).\n|\n| The console might require you to sign in first.\n| 2. Select or create a project.If you have multiple projects, make sure that you are in the project for which you want to activate the Digital Asset Links API and click **Continue** . Or, if you do not have a project, select **Create a new project** and click **Create**.\n|\n| 3. In the Digital Asset Links API overview, click **Enable API** .\n|\n| If the API is already enabled for your project, you will see **Disable API**.\n| 4. In the left-hand menu, click on **Credentials** and either select or create an API key.\n|\n| [More information about creating API keys](https://support.google.com/googleapi/answer/6158862).\n\nConsuming statements manually\n-----------------------------\n\nThe Digital Asset Links protocol is open, so you can create an implementation of it for yourself.\n\nTo consume statements made by **web sites** , you can make an HTTP GET request for the corresponding statement list and parse it yourself. For example, the corresponding statement list for the web site `http://example.digitalassetlinks.org` is at `http://example.digitalassetlinks.org/.well-known/assetlinks.json`.\n\nTo consume statements made by **Android apps** , you need to access the manifest of the corresponding APK package. On Android devices, this can be accomplished using the [PackageManager](http://developer.android.com/reference/android/content/pm/PackageManager.html) interface.\n\nPlease pay special attention to the specific meanings of Digital Asset Links statements. Refer to the [Asset Links Specification](https://github.com/google/digitalassetlinks/blob/master/well-known/details.md) if you are unsure."]]
