RE: Suggestion for new category

Take a look at www.Eidr.org – in addition to a shared identification system for digital assets, they’ve got a pretty well thought out approach to handling things like movie trailers, different language versions, etc.  and other concepts that will be related.

Bill Nichols
Acting Associate Director
Strategic Data Services
Office of Financial Research
US Department of the Treasury

Bill.Nichols@ofr.treasury.gov<mailto:Bill.Nichols@ofr.treasury.gov>
+1 202.622.2780 (o)
+1 202.262.5623 (c)

Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain information that is privileged, confidential, or otherwise protected from disclosure. If you have received this message in error, please delete this message and any attachments, and notify the sender immediately.  If you are not the intended recipient, you are hereby notified that the disclosure, copying, or distribution of the contents of this transmission is strictly prohibited.  An inadvertent disclosure is not intended to waive any privileges.


From: Richard Wallis [mailto:richard.wallis@dataliberate.com]
Sent: Thursday, March 03, 2016 9:48 AM
To: Jacob Jett
Cc: public-schemaorg@w3.org
Subject: Re: Suggestion for new category

Not wishing to overload CreativeWork in the subtypes department, but ‘Play’ does seem to be an obvious missing candidate.

I don’t really think the ’Stage’ qualification is necessary. Most of the properties you reference would be inherited from CreativeWork.  The exceptions being some of the more specific contributors such as StageDesigner and WadrobeKeeper.   These could be handled as per some of the roles in the movie industry are - using the Role<http://schema.org/Role> construct.

You could then connect the individual performances to the Play using TheaterEvent if appropriate using the workPerformed property.

On 3 March 2016 at 14:27, Jacob Jett <jjett2@illinois.edu<mailto:jjett2@illinois.edu>> wrote:
We have a similar use case but also need to account for things like costume sketches and photographs (and same for storyboards, set designs, etc.). Should we just extend the TheaterEvent with new predicates?

Most if not all of those things would be CreativeWorks or subtypes thereof, in their own right and could be considered ‘isPartOf’ of the play.

~Richard

On Thu, Mar 3, 2016 at 8:17 AM, Tim Turner <tturner@flumc.org<mailto:tturner@flumc.org>> wrote:
There is a TheaterEvent that could be expanded from this list.
https://schema.org/TheaterEvent


From: Webmestre Globetrottoirs [mailto:webmaster@globetrottoirs.com<mailto:webmaster@globetrottoirs.com>]
Sent: Wednesday, March 02, 2016 1:05 PM
To: public-schemaorg@w3.org<mailto:public-schemaorg@w3.org>
Subject: Suggestion for new category

Hello,

I am working on a theater group website.

When trying to code micro-data, I felt that the following schema is missing.

In the “Creativework” schema, could we add “TheaterPlay”, which would have the following properties :

Name – expected type : text – description : the name of the play
Author – expected type : text – description : the author of the play
Director – expected type : text – description : the person who directed the play
Actor – expected type : text – description : the actors of the play
Character – expected type : text – description : the characters of the play
Composer – expected type : text – description : the composer of the music used in the play
Genre – expected type : text – description : the genre of the play (eg : musical theatre, gesture theatre, pantomime, …)
StageDesigner – expected type : text – description : the person who designed the settings
WardrobeKeeper – expected type : text – description : the person who designed or created the wardrobe.

It could be also usefull to create schema related to dance or mime, etc…

Do you think it is possible to do this ?

Thank you for your answer.

Sincerely.

Stéphane Reboul


________________________________
Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain information that is privileged, confidential, or otherwise protected from disclosure. If you have received this message in error, please delete this message and any attachments, and notify the sender immediately. If you are not the intended recipient, you are hereby notified that the disclosure, copying, or distribution of the contents of this transmission is strictly prohibited. An inadvertent disclosure is not intended to waive any privileges.
FinancialResearch.gov<http://www.financialresearch.gov/>