W3C home > Mailing lists > Public > public-vocabs@w3.org > March 2012

Re: Schema.org property cardinality and use of plural (WAS Re: SoftwareApplication proposal for schema.org)

From: Dan Brickley <danbri@danbri.org>
Date: Fri, 9 Mar 2012 21:34:02 +0100
Message-ID: <CAFfrAFosNKa9Ew2u9BzTPGGaCEP1a23i-Vg4A4fjmmoPLip4=w@mail.gmail.com>
To: "public-vocabs@w3.org" <public-vocabs@w3.org>
On 1 March 2012 21:49, St├ęphane Corlosquet <scorlosquet@gmail.com> wrote:
> On Thu, Mar 1, 2012 at 1:06 PM, Dan Brickley <danbri@danbri.org> wrote:
>> OK, I've written up a first cut of a proposal to create new singular
>> property names:
>> http://www.w3.org/wiki/WebSchemas/Singularity
> Some of these properties actually make sense to be kept plural. I've
> highlighted many of the them in the wiki with some rationale, but I might
> have missed some more. I've strikelined them for now while they are being
> reviewed. we can remove them once they've been approved as being correct the
> way they are (plural).

Thanks everyone for the discussion. The schema.org partners agreed
today to move ahead with this direction.

Specifically, per http://www.w3.org/wiki/WebSchemas/Singularity#Core_Proposal

* For every property name whose final 's' is due to the earlier
practice of writing plurals for property names, create a new property
with shorter, singular name
* For each previous property name, agree this it is still acceptable
(and somehow document this in schema.org for people and machines); but
the singular form is preferred

I've reflected into the wiki all the substantive points that came up
in offlist and telecon discussion. In particular, there is a new
section http://www.w3.org/wiki/WebSchemas/Singularity#RDFa_impact
which works through an RDFa 1.1 example as my schema.org colleagues
wanted to make sure that it worked OK with RDFa 1.1 too.

I have just now been continuing the work Lin and St├ęphane began, on a
final enumeration of the changes needed. Several properties that
didn't fall under the "plural to indicate repeatability" rule have
been moved out of the main list. I have also added domain/range links
to show the classes for all the property names that we'll be adding a
singular alias for.


I've closed the issue tracking this, and actioned myself to get a
detailed change proposal written up. Getting those details right will
take a bit of work, so it's important to record consensus so far,
which is that moving away from cardinality-based plural properties
makes sense.



Received on Friday, 9 March 2012 20:34:30 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:29:22 UTC