W3C home > Mailing lists > Public > public-schemaorg@w3.org > March 2016

Re: Question on expressing translations of terms

From: Richard Wallis <richard.wallis@dataliberate.com>
Date: Thu, 17 Mar 2016 13:08:31 +0000
Message-ID: <CAD47Kz5k40q-V1=+1evymy5O92nnUdqB4xBLXn9nA5QedyY7_g@mail.gmail.com>
To: Thomas Francart <thomas.francart@sparna.fr>
Cc: Dan Brickley <danbri@google.com>, Felix Sasaki <fsasaki@w3.org>, "schema.org Mailing List" <public-schemaorg@w3.org>
I think you will find Dan’s use of schema.org term definition RDFa was just
to show syntax for multiple language, not to narrow the discussion to that
topic.  My earlier example demonstrates the same for a more generic Thing.

As to proposing a general purpose term definition / relationship structure
such as you describe, I can see the need for such a capability but wonder
if in most cases SKOS-like existing solutions would suffice for detailed
description.  Whereas I would require some convincing as to the potential
take up in a broad general purpose vocabulary such as Schema.org.

~Richard.

Richard Wallis
Founder, Data Liberate
http://dataliberate.com
Linkedin: http://www.linkedin.com/in/richardwallis
Twitter: @rjw

On 17 March 2016 at 12:56, Thomas Francart <thomas.francart@sparna.fr>
wrote:

> I don't think the original question was about translating the terms of
> schema.org itself (classes and properties); it was about the possibility
> to describe terms/words, similar to what SKOS-XL proposes.
> For me the original proposition makes sense, it would allow to state
> things like "this term/word A is used for a large public", "that other
> word/term B is used by the scientific community" "the words/terms A and B
> are both used to refer to concept C", "word/term A is an acronym of
> word/term B", "word/term D is slang, while word/term E is formal language",
> etc.
>
> Thomas
>
> 2016-03-17 13:38 GMT+01:00 Dan Brickley <danbri@google.com>:
>
>> Yes, I tend to agree with Chaals & Richard here: for translated labels
>> of structured data vocabulary terms (schema.org's and others), we
>> should look towards the underlying W3C standards: RDF/S and perhaps
>> sometimes SKOS, SKOS-XL. It is usual to stick to a single URL for
>> types and properties rather than proliferate them by having different
>> URLs for each language.
>>
>>
>> Here is an example btw of RDFa+RDFS definitions that do this, from
>>
>> https://github.com/schemaorg/schemaorg/blob/sdo-deimos/data/l10n/zh-cn/schema_org_zhcn.html
>>
>> <div typeof="rdfs:Class" resource="http://schema.org/Audience">
>> <span class="h" property="rdfs:label">Audience</span>
>> <span class="h" property="rdfs:label" xml:lang="zh-cn">听众</span>
>> <span property="rdfs:comment">Intended audience for an item, i.e. the
>> group for whom the item was created.</span>
>> <span property="rdfs:comment" xml:lang="zh-cn">听众,观众, 读者</span>
>> <span>Subclass of: <a property="rdfs:subClassOf"
>> href="http://schema.org/Intangible">Intangible</a></span>
>> </div>
>>
>> Does this approach do what you have in mind, Felix?
>>
>> Dan
>>
>> On 17 March 2016 at 10:56, Richard Wallis
>> <richard.wallis@dataliberate.com> wrote:
>> > Not sure I understand your definition of a term, but the ability to
>> handle
>> > names, or any other text based properties, of things in multiple
>> languages
>> > is already possible:
>> >
>> > {
>> >
>> >   "@context": “http://schema.org/”,
>> >
>> >   "@id": "http://example.com/my-term-data-base-entry-1",
>> >
>> >   "@type": "schema:Thing",
>> >
>> >   "schema:name": [
>> >
>> >     {
>> >
>> >       "@language": "en",
>> >
>> >       "@value": "screwdriver"
>> >
>> >     },
>> >
>> >     {
>> >
>> >       "@language": "de",
>> >
>> >       "@value": "schraubendreher"
>> >
>> >     }
>> >
>> >   ]
>> >
>> > }
>> >
>> >
>> > or in RDFa:
>> >
>> >
>> >  <div typeof="schema:Thing"
>> > about="http://example.com/my-term-data-base-entry-1">
>> >     <div property="schema:name" xml:lang="en"
>> content="screwdriver"></div>
>> >     <div property="schema:name" xml:lang="de"
>> > content="schraubendreher"></div>
>> >   </div>
>> >
>> >
>> > ~Richard
>> >
>> > Richard Wallis
>> > Founder, Data Liberate
>> > http://dataliberate.com
>> > Linkedin: http://www.linkedin.com/in/richardwallis
>> > Twitter: @rjw
>> >
>> > On 17 March 2016 at 09:04, Felix Sasaki <fsasaki@w3.org> wrote:
>> >>
>> >> Hi all,
>> >>
>> >> It seems that schema.org as of writing would not allow to express the
>> >> relation for terms „A is a translation from B“ or „A is an
>> abbreviation from
>> >> B“. It is already possible to express that A is translation of B, see
>> >>
>> >> http://bib.schema.org/translationOfWork
>> >>
>> >> but this is specific to works, not translated terms. Would the below
>> make
>> >> sense? It is adapted from
>> >> https://schema.org/translator
>> >>
>> >> note: schema:Term and schema:translation do not exist in schema.org, I
>> >> made them up for the example.
>> >>
>> >> {
>> >>   "@id": "http://example.com/my-term-data-base-entry-1",
>> >>   "@type": "schema:Term",
>> >>   "schema:inLanguage": "en",
>> >>   "schema:name": "screwdriver",
>> >>   "schema:translation": {
>> >>     "@id": "http://example.com/my-term-data-base-entry-2",
>> >>     "schema:inLanguage": "de",
>> >>     "schema:name": "schraubendreher"
>> >>   }
>> >> }
>> >>
>> >> - Felix
>> >
>> >
>>
>>
>
>
> --
>
> *Thomas Francart* -* SPARNA*
> Web de *données* | Architecture de l'*information* | Accès aux
> *connaissances*
> blog : blog.sparna.fr, site : sparna.fr, linkedin :
> fr.linkedin.com/in/thomasfrancart
> tel :  +33 (0)6.71.11.25.97, skype : francartthomas
>
Received on Thursday, 17 March 2016 13:09:01 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:12:24 UTC