W3C home > Mailing lists > Public > public-schemaorg@w3.org > June 2015

Re: Support for URLs per language or region in schema.org

From: Aaron Bradley <aaranged@gmail.com>
Date: Thu, 4 Jun 2015 10:06:29 -0700
Message-ID: <CAMbipBvHE0w+16yoanZ4RcFViwi-MHwyqoH=RT9ucSA6XaSWQg@mail.gmail.com>
To: Vicki Tardif Holland <vtardif@google.com>
Cc: "mfhepp@gmail.com" <mfhepp@gmail.com>, "schema.org Mailing List" <public-schemaorg@w3.org>
Excuse me if I'm being dense, but could either of you provide an example of
how that might work?  Say, if I wanted to declare the URL and name of the
World Bank in English and Spanish (i.e. same entity, different annotations
per language).

World Bank Group
http://www.worldbank.org/

El Grupo del Banco Mundial
http://www.bancomundial.org/

And is there a method by which one might be able to do so now?  This is the
best I've been able to do:

<script type='application/ld+json'>
{
  "@context": "http://schema.org",
  "@type": "Organization",
  "name": [
    {
      "@language": "en",
      "@value": "World Bank Group"
    },
    {
      "@language": "es",
      "@value": "El Grupo del Banco Mundial"
    }
  ],
  "contactPoint": [
    {
  "@type" : "ContactPoint",
      "url" : "http://www.worldbank.org/",
      "availableLanguage" : "en"
    },
{
  "@type" : "ContactPoint",
      "url" : "http://www.bancomundial.org/",
      "availableLanguage" : "es"
    }
  ]
}
</script>

But this seems terribly hack-y, and has also sorts of issues (the name
isn't mapped to the equivalent URL for example), and FWIW Google requires
the use of "contactType" for each ContactPoint instance and, ironically,
demands a url be declared for Organization.  The desired outcome is
actually to be able to say the equivalent of "OrganizationX has url X
inLanguage en, and url Y inLanguage es."

On Thu, Jun 4, 2015 at 8:41 AM, Vicki Tardif Holland <vtardif@google.com>
wrote:

>
> On Thu, Jun 4, 2015 at 6:41 AM, mfhepp@gmail.com <mfhepp@gmail.com> wrote:
>
>> We could simply add schema:WebPage (or schema:Thing) to the range of all
>> (or most) properties that  accept schema:URL as a datatype. Then, you can
>> model different values for different languages or devices by simply adding
>> an additional schema:WebPage node instead of the raw URL, which can hold
>> the language and other meta-data.
>
>
> It seems that EntryPoint would be a better type than WebPage.
> Increasingly, URLs are for mobile apps and there is no "page" on the other
> end.
>
> - Vicki
>
> Vicki Tardif Holland | Ontologist | vtardif@google.com
>
>
Received on Thursday, 4 June 2015 17:06:58 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 4 June 2015 17:06:58 UTC