provides a status property for CreativeWork

[philbarker]

Closes #987

@RichardWallis I had problems getting pending/issue-987.rdfa to be included in draft website build. couldn't get buildTermConfig.sh to work. Fixed by editing sdoconfigTermsData.json by hand. Any advice about this in the future?

[RichardWallis]

@philbarker No problem manually editing sdoconfigTermsData.json as it gets overwritten by buildTermConfig.sh at version release time. Remember to do it for rdfa files and examples.txt files

buildTermConfig.sh is a shell script that is run from the root directory of a local repo (./scripts/buildTermConfig.sh) on a Mac or Linux system, and potentially a Windows system with the appropriate dev environment.

[danbri]

I'm ok with putting this into Pending to see if it flushes out some interesting usage or consensus about property values. The analogy with Event status isn't 100% compelling, there's stronger consensus about those enumerations as they're tied to fairly stereotypical transactions (ticket buying etc.), similar with payments, reservations, orders cited in #987. Document-like-things stand in all kinds of complex workflow states.

Is anyone currently planning to build something with this property?

[philbarker]

@danbri Credential Engine record the status of EducationalOccupationalCredentials (so a subtype of CreativeWork) and would like to publish it as schema.org. Seemed to make sense as a property of CreativeWork, e.g for research papers, but I understand your concerns.