-
Notifications
You must be signed in to change notification settings - Fork 826
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposal to add support for Amazon's ASIN product identifier #3123
Comments
This is a no-brainer, imho. We should also have a general construct so the longer tail of IDs can be represented more explicitly, but that shouldn't block supporting something as widely used as asin. |
I disagree and believe this will further enable monopolization from Amazon. Giving Amazon identifiers special treatment seems unfair in the grand scheme of things. |
This is not true what you just said.
The EWS is specifically put into dataset to mimick a human closet and
demonizing automation services is "Anti-trust" however, you just marked
"Anti-Commerce".
This is the last thing we need as freelance open source. The more
financially sound your bot reliance is, the healthier your online
entrepreneurship as presence takes presidencies.
…On Tue, Jun 21, 2022, 6:36 PM RHEV ***@***.***> wrote:
I disagree and believe this will further enable monopolization from
Amazon. Giving Amazon identifiers special treatment seems unfair in the
grand scheme of things.
—
Reply to this email directly, view it on GitHub
<#3123 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADFVNUWOPQYSGJC4M5NPLH3VQJGYFANCNFSM5YNZWRMA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Sounds smart indeed. We could add support to Yoast WooCommerce SEO for this easily and quickly. |
Thanks all
I will go ahead and code this up for the Pending area (where as usual it will remain until we have evidence it is being consumed). I believe the most typical values will be strings but we should also anticipate the use of URIs/URLs as property values, similar to GS1's move towards Digital Link with /gtin /cc @philarcher. During Pending review we should also solicit Amazon (/cc @Savas) for their perspective. |
Could do with input on specifics - I found it hard to find the right spec so have referenced Wikipedia for now. For #3123
@danbri unfortunately, we/Yoast can't add support for ASIN until this gets merged, as the Schema validator will throw errors for it, causing a barrage of emails to our support team usually :) |
Released in 15.0 |
Context - This is a proposal from Google based on our experience consuming schema.org Product markup and working with similar data from online merchants. If it were accepted, it would make it easier for us and others to identify products sold online.
Proposal - Schema.org supports a variety of industry-standard product identifiers, for example gtin, mpn, and nsn. We propose to add a new property asin of type Text for use on Product, representing the Amazon Standard Identification Number. Given its common and broad use in the industry it would be beneficial to allow products to be identified with their corresponding ASIN code in structured data.
Alternatives - An alternative option would be supporting ASIN through the existing productID property. However, given the broad usage of ASIN, support as a first-class property seems more appropriate.
The text was updated successfully, but these errors were encountered: