Re: Proposal for “OrganicCertification” Schema in Product Listings

The schema is very flexible and imo you wouldn't need a type for organic
certification. If you imagine that every certification would have its own
type the schema would be unnecessarily large as it retains flexibility to
shape most use cases currently.

Consider this example:
{
  "@context": "https://schema.org",
  "@type": "Certification",
  "name": "Organic Certification",
  "description": "Certification ensuring compliance with organic farming
and production standards.",
  "certificationIdentification": {
    "@type": "DefinedTerm",
    "name": "USDA Organic",
    "termCode": "ORG-001",
    "url": "https://example.org/usda-organic-certification"
  },
  "provider": {
    "@type": "Organization",
    "name": "Organic Standards Agency",
    "url": "https://example.org/organic-standards"
  },
  "validFrom": "2024-11-19",
  "expires": "2026-11-18",
  "url": "https://example.org/organic-certification-details"
}

Gives all the information necessary and moving into the age of LLMs, think
they'd be able to understand the structure quite well. Try asking an LLM
for examples and you can use the above example in your prompt.

On Tue, Nov 19, 2024 at 12:38 PM Marie Seshat Landry <
marielandryceo@gmail.com> wrote:

> Subject: Proposal for “OrganicCertification” Schema in Product Listings
>
> Dear Public Schema.org Community,
>
> I would like to bring attention to an important GitHub issue discussing
> the proposal of adding an “OrganicCertification” as a subtype under
> “Certifications” in the Product schema. This proposal aims to improve how
> search engines can identify and prioritize certified organic products,
> enhancing transparency and promoting eco-friendly practices.
>
> For more details, please review the full discussion here: GitHub Issue
> #4290 <https://github.com/schemaorg/schemaorg/issues/4290>.
>
> Best regards,
>
> Marie Seshat Landry
>
>
>
>
>