Re: VideoGames

Looking good!  A number of comments on specific types and properties.

>  elf Pavlik via
> What do you think about
> adding schema:GameCharacter extending schema:Person

+1 for some version of this (I would opt for the Game property "character"
which would have the expected type "Person").

Without this we'd have the Game property "characterAttribute" but,
counter-intuitively, not have a "character" property available.


Great to see this has incorporated Martin's proposal to collapse the
previously-proposed  minNumberOfPlayer/maxNumberOfPlayer properties into
this single one and use QuantitativeValue.  However, I would also use his
nomenclature for this property, namely the plural (and the corrected
initial case):

One would never say "number of player" even when the value of number of
players was one.

While uses the singular form for single nouns, it uses plurals
as appropriate for compound structures.  E.g. for CreativeWork we have the



Why is the expected value for these "CreativeWork"?  Doesn't "text" make
more sense here (I could perhaps see the case for using CreativeWork for
"tip" because that might point to a URI, but not for "cheatCode")?

For "tip" specifically, regardless of the expected type, I think that the
property description:
"Links to tips, tactics, etc"
Should be amended to read:
"Tips, tactics, etc."

A "tip" may not always be a link - it can also be an inline property of a
VideoGame resource.  This is analogous to the existing SoftwareApplication
property "help", which also has an expected type of "CreativeWork".  There
the description is - quite properly:
"Software application help"
Not the more constrictive:
"Links to software application help"


Proposed enumeration members are:

No other enumeration member, type or property contains a dash.
 This is true even of situations where a dash would normally be called for,
as in the enumeration members for ContactPointOption, which are:
Rather than:

Accordingly, I think these members should be:


This should be extended so that one of the types on which this can be used
is VideoGame.

I raised this before in the context of VideoGameSeries.  If we end up with
this, then it should be extended to VideoGameSeries, but if not it should
at least be extended to include VideoGame.

Almost any video game produced these days features a trailer, and these
trailers are almost certainly the the most-consumed creative work
associated with a video game (e.g. [1]).


On Tue, Jul 8, 2014 at 2:02 PM, ☮ elf Pavlik ☮ <> wrote:

> What do you think about
> * adding schema:GameCharacter extending schema:Person
> * creating schema:Quest which schema:quest would expect
> * reusing schema:location where Place would provide support for URL
> ("@id"), maybe also schema:VirtualPlace extending schema:Place
> * schema:characterAttribute could extend something also relevant for
> schema:Person,  myself I would find it interesting possibility to import
> some concepts from especially with
> projects like popping up.
> Also somehow schema:NumberOfPlayer shows instead of schema:numberOfPlayers
> I also notice possible mistakes in examples
> * schema:employee and schema:founder expect schema:Person
> * schema:publisher expects schema:Organization
> * schema:copyrightHolder expects schema:Organization or schema:Person
> * schema:availability expects schema:ItemAvailability
> relevant in all those cases:
> Looks to me like a good work, especially with decent amount of examples!
> //
> side note: 243KB attachment sent to a mailing list -> maybe just a hyper
> link to it in a future? ;)
> On 07/08/2014 08:16 PM, Yuliya Tikhokhod wrote:
> > Hi,
> >
> > This is intended to be a final or near final version of Video Game
> > proposal.
> >
> > Here are test build
> >
> >
> >
> >
> >
> > PDF version is attached
> >
> > Please let me know if you have any comments
> >
> > --
> > Yuliya Tikhokhod
> >
> > Yandex
> >

Received on Wednesday, 9 July 2014 00:09:12 UTC