Re: yehuda

They're identifiers, and the comparison is string equality based. So `http://schema.org/InStock` doesn't equal `https://schema.org/InStock` (any more than it would be equivalent to `http://schema.org/InStock?` (or similar).

I'd highly recommend fixing the data to use the correct identifiers. The FAQ says you can use either, but practically the `http://schema.org/`-based identifiers are much more prevalent. So, while they're conceptually equivalent, they are "practically" not equivalent. Link to the FAQ: https://schema.org/docs/faq.html#19

Additionally, since it looks like you're using the JSON-LD expression of Schema.org, you should have a `@context` setup, and that would allow you to change the value for `"availability"` from `"http://schema.org/InStock"` to simply `"InStock"` since the context file will take care of the rest. You can test this approach out using the example from schema.org and Google's Structured Data Testing Tool: https://search.google.com/structured-data/testing-tool

Hope that helps!
Benjamin

--

http://bigbluehat.com/

http://linkedin.com/in/benjaminyoung

________________________________
From: Yehuda Clinton <yehudaclinton@gmail.com>
Sent: Monday, March 18, 2019 2:46 PM
To: public-schemaorg@w3.org
Subject: yehuda

im getting G search console error
Invalid value type for field "availability"
for
    "availability": "https://schema.org/InStock",

I understand that the issue is that there shouldn't be a https

My question why can't accept both as valid?

This would save a lot of headache from having to manually change them all.

cheers