Richard Wallis

I agree that there is some confusion in the identifying of expected types for Date and DateTime properties. Symptomatic perhaps of a community based process that takes input from many...

@VladimirAlexiev I suppose marking the description of such properties with an equivalent XSD type may help with human comprehension, but the guidance to use a [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) formatted string is...

@chicco785 Thanks for sharing this. Taking a quick (airport gate) scan of the GSMA [harmonized data models work](http://www.gsma.com/connectedliving/wp-content/uploads/2016/11/CLP.26-v1.0.pdf) document from a Schema.org point of view I have an immediate suggestion...

See issue schemaorg/suggestions-questions-brainstorming#7 for the context of the move from the main Schema.org [issue tracker](https://github.com/schemaorg/schemaorg/issues) to this repository.

I would suggest an option 4. Propose a new property **developmentStatus** - a sub-property of **creativeWorkStatus** - with a domainIncludes of **SoftwareSourceCode**

Getting ```creativeWorkStatus``` renamed **would be** a difficult sell, due to the broad coverage of CreativeWork and its many sub-types. Reference to the _repostatus.org_ vocabulary highlights another potential option. If there...

Implemented in PR #2725

+1 for deleting them

Following the merge of [schemaorg PR #3182](https://github.com/schemaorg/schemaorg/pull/3182) the output from the [shex_shacl_shapes_exporter.py](https://github.com/schemaorg/schemaorg/blob/main/software/scripts/shex_shacl_shapes_exporter.py) script will be produced when the site is built. On the release of a schema version (next one...

Schemaorg [6fcbc1b](https://github.com/schemaorg/schemaorg/commit/6fcbc1bd7f9bb601ee4b06c950d06905ef4db67e) implements @danbri's suggestion.