Frédéric Julien

At the risk of oversimplifying things, it would also be possible to state the DOI with a `sameAs` attribute value pair. Since the DOI is a persistent identifier expressed as...

I'm highly supportive of this proposal. Many performing arts organization would like to represent live performances at a more granular level than the Event type. However, the Schema's current Event...

@MatthiasWiesmann A pull request is in progress. If we would like to provide several examples, should we submit them within the same .txt file or as distinct files? And is...

@gmackenz @MatthiasWiesmann Should our files go straight in data or should we first create them under data/ext/pending? If the former, should we also edit the schema.ttl file or do we...

@MatthiasWiesmann What's the typical deployment timeline for a new class? We have a few use cases in which we could promote adoption, and I would like to know whether I...

> there's no point in theoretically slightly cleaner data if it is too hard for non-rdf nerds to understand. I can't speak for the rest of the world, but I...

> That said I think we do have an issue to clarify the examples for wikidata here Thanks in advance for accepting to implement this minor update.

I am supportive of this proposal. I think the performing arts sector sorely needs a concept describing the "work" that is presented to an audience during a performance. This work...

@gmackenz > Would some of the subtypes of CreativeWork be moved to be subtypes of PerformanceWork (such as @WeaverStever mentioning above about Play). No. Some existing subtypes of CreativeWork can...

@RichardWallis > However some thought needs to be applied to which already defined subclasses of CreativeWork, such as [Play](https://schema.org/Play) and possibly [TVEpisode](https://schema.org/TVEpisode) & [RadioEpisode](https://schema.org/RadioEpisode), would be better relocated to become...