RE: Leaping aliases or Property aliases in Schema.org

This is part of a larger problem: schema.org doesn’t distinguish between the abstract creative work and the physical realization of it. We’d like to say that the physical work comprises the cover (which has an artist) and the abstract text (which has an author).

Similarly, the novel “To Kill a Mockingbird” has a length, an author, a copyright date, etc., but it doesn’t have a cover picture, a publisher, or an ISBN. A particular edition of “To Kill a Mockingbird” has a publisher, a publication date, a number of pages, and contents. The contents include the novel but also likely include an introduction by someone other than Harper Lee and might include study materials as well. It would be nice to separate the descriptions of the cover, the introduction, and the novel text from the description of the physical volume that combines them.

The same problem occurs when trying to describe an anthology. It’s a book with no author but each story in it has an author. Magazines sort of work, via publication issue, but that’s a ad hoc solution to a more general problem.

In general, I wish Schema.org made a distinction between a WrittenWork and a PublishedWork.

WrittenWork would have a title, author, length in words (not pages), copyright date (not publication date), optionally might have editor, translator, translationOf, revisionOf

PublishedWork would have an editor (but not an author), a length in pages, a publication date, a publisher, contents (creative works), and optionally might include illustrations, a volume number, etc.

A WrittenWork might be part of a series. (E.g. “The Fellowship of the Ring” is part of “The Lord of the Rings.”) A PublishedWork might be part of a set. (E.g. Volume I and Volume II would be part of the same set.)

It might be nice to have a “publishedAs” field in WrittenWork to allow enumeration of places the work was published.

--Greg

Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10

From: Stian Soiland-Reyes<mailto:soiland-reyes@cs.manchester.ac.uk>
Sent: Saturday, October 22, 2016 5:48 AM
To: Thad Guidry<mailto:thadguidry@gmail.com>
Cc: schema.org Mailing List<mailto:public-schemaorg@w3.org>
Subject: Re: Leaping aliases or Property aliases in Schema.org


Perhaps you could amend with some owl:equivalentProperty rule. (Assuming you mean the "artist" of a CoverArt must be a "cover artist".)

But would not the cover artist property go from the Work (e.g. a book or music album) rather than from the CoverArt itself?

On 20 Oct 2016 2:14 am, "Thad Guidry" <thadguidry@gmail.com<mailto:thadguidry@gmail.com>> wrote:
So...There's this...
https://bib.schema.org/CoverArt
that has an 'artist' property.

That 'artist' property in actuality could be a 'cover artist' that could be mapped to https://www.wikidata.org/wiki/Property:P736

But I have no reliable way to do that because we don't have Aliases at a Type/Property level.  Bummer.

How do we fix or solve this ?