W3C home > Mailing lists > Public > public-vocabs@w3.org > August 2014

Re: User friendly labels for Schema.org types and properties

From: Stéphane Corlosquet <scorlosquet@gmail.com>
Date: Sat, 2 Aug 2014 18:33:09 -0400
Message-ID: <CAGR+nnFRsuu1TvqS+J6U4iFQznzGEdULq-_2UJc-w-iyFm2XjA@mail.gmail.com>
To: Gregg Kellogg <gregg@greggkellogg.net>
Cc: Martin Hepp <martin.hepp@ebusiness-unibw.org>, "Wallis,Richard" <Richard.Wallis@oclc.org>, "<public-vocabs@w3.org>" <public-vocabs@w3.org>, Sachini Herath <sachini.mc@gmail.com>
That works too. The machine name of each term used to generate each type
and property page on schema.org is simply the local name of each term (the
part that comes after ":" in turtle)

Steph.
On Aug 2, 2014 5:47 PM, "Gregg Kellogg" <gregg@greggkellogg.net> wrote:

> On Aug 2, 2014, at 1:26 PM, Stéphane Corlosquet <scorlosquet@gmail.com>
> wrote:
>
> >
> >
> >
> > On Sat, Aug 2, 2014 at 1:30 PM, Wallis,Richard <Richard.Wallis@oclc.org>
> wrote:
> > Martin is right about the rdfs:label being used to generate the
> documentation.
> >
> > However Sachini also has a point about user-friendly names.
> >
> > Potentially it would not be too difficult (without over hacking the code
> that creates the documentation) to introduce schema:name as extra triple(s)
> in the Type and property descriptions.  The display could then be enhanced
> with an extra column to display user-friendly names alongside the labels.
> >
> > This introduces the further thought of adding the capability for
> recognising language tagging of strings for descriptions and these names,
> and thus the ability to build language specific, or selectable, versions of
> the Scema.org site.
> >
> > Good ideas, Richard. I thought of adding a new schema.org property
> (along schema:domainIncludes and schema:rangeIncludes), but re-using
> schema:name sounds good too! I think the topic of translations has been
> brought on this list before, and this would be a solution to address it
> (and would allow to personalize any user interface based on schema.org as
> well into the user preferred language).
>
> I agree that we really need user friendly names for classes and
> properties, however, there's already a convention to use rdfs properties
> where it makes sense. For instance, the definition already uses
> rdfs:comment, rdfs:Class, rdfs:subClassOf, rdfs:subPropertyOf and of course
> rdf:Property. It also currently uses rdfs:label, just not using a friendly
> form. I don't know that schema:name adds anything different then
> rdfs:label, but I wouldn't mind seeing them both.
>
> A dump of one existing vocabulary term using my processor yeilds the
> following:
>
> schema:StadiumOrArena a rdfs:Class;
>    rdfs:label "StadiumOrArena";
>    rdfs:comment "A stadium.";
>    rdfs:subClassOf schema:CivicStructure,
>      schema:SportsActivityLocation .
>
> IMO, just changing rdfs:label to "Stadium or Arena" would work properly.
> Adding @en would make sense too, opening the door for alternate
> translations, or content-negotiated based on Accept-Language.
>
> Gregg
>
> > Steph.
> >
> >
> > ~Richard
> >
> > On 1 Aug 2014, at 22:30, martin.hepp@ebusiness-unibw.org wrote:
> >
> >> I think the main reason is that the labels in schema.org are used to
> generate the documentation and that the RDFa version of schema.org is not
> mainly designed as an RDF vocabulary in its own right.
> >> By the way, we had CamelCase labels in GoodRelations for long and
> changed them to more human-readable ones about two years ago. However,
> GoodRelations is an RDF/OWL vocabulary, while schema.org is something
> different ;-)
> >>
> >>
> >>
> >> On 01 Aug 2014, at 17:12, Stéphane Corlosquet <scorlosquet@gmail.com>
> wrote:
> >>
> >>> To give an example, FOAF defines user friendly labels in rdfs:label.
> Couple of examples:
> >>>
> >>> foaf:OnlineGamingAccount a rdfs:Class;
> >>>   rdfs:label "Online Gaming Account";
> >>>   rdfs:comment "An online gaming account.";
> >>>
> >>> foaf:givenName a rdf:Property;
> >>>   rdfs:label "Given name";
> >>>   rdfs:comment "The given name of some person.";
> >>>
> >>>
> >>>
> >>> On Fri, Aug 1, 2014 at 10:45 AM, Sachini Herath <sachini.mc@gmail.com>
> wrote:
> >>> I’m Sachini Herath, an undergraduate from Sri Lanka. I am working on
> building Schema.org mapping tools for Drupal 8 as my Google Summer of Code
> 2014 project, mentored by Stéphane Corlosquet. The tools would enable the
> users to map Drupal content types and fields to Schema.org types and
> properties, or to generate Content Types templates based on Schema.org.
> More details on the project can be found at
> https://groups.drupal.org/node/424838
> >>>
> >>> When developing the tool I noticed that the labels of Schema.org types
> and properties are not user-friendly. Some example would be types such as
> ProfessionalService, AutoPartsStore, BankOrCreditUnion,
> HealthAndBeautyBusiness, CollegeOrUniversity and properties such as
> postOfficeBoxNumber, primaryImageOfPage, estimatedFlightDuration. The label
> of “HealthAndBeautyBusiness” would be much easier and recognizable for the
> user as “Health and beauty business.”
> >>>
> >>> Are you aware of any similar implemantations where forms are auto
> generated based on Schema.org? I am eager to discuss how they have overcome
> similar problems.
> >>>
> >>> Thank you
> >>> --
> >>> Sachini Herath
> >>>
> >>>
> >>>
> >>> --
> >>> Steph.
> >>
> >>
> >
> >
> >
> >
> > --
> > Steph.
>
>
Received on Saturday, 2 August 2014 22:33:36 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:49:34 UTC