AssessAction entity names - should they include statuses?

[beforan]

Looking at the example in draft 0.4 of a Disclosure Phase AssessAction:

{  
  "@id": "#disclosure-b16c1f0a-ae7f-4582-9b28-7d9df3313e27",
  "type": "AssessAction",
  "name": "Disclosure check of workflow results: pending (estimate: 1 week)",
  // ...
  "actionStatus": "http://schema.org/PotentialActionStatus"
}

Here the name property includes commentary on the status: pending (estimate: 1 week).

• Is it useful or appropriate to put this status information here?
  • the actual action status has its own well defined property actionStatus
• If so, is it appropriate or problematic to be updating the entity name when status changes?
  • e.g. to Disclosure check of workflow results: completed
  • I realise the id is unchanging and is the canonical unique identifier for the entity, so perhaps changing the name is acceptable, but it seems odd
• Should/Can the additional status commentary such as estimates of assessment duration in a pending state be recorded in a well defined property instead?
  • I don't know if this is useful or overkill, but if modifying the name is deemed undesirable, then doing this will be necessary to retain the pending estimate, or other status information such as reasons for disclosure check failure.

Happy to hear thoughts :)

[stain]

Agree now, might be more consistent to not reflect the status in name. It could be misleading if they are not matching after an update. Perhaps status can be detailed in description textually (which may be a multi-line log) but that the normative status is in the actionStatus.

Also if there is some detail report of the action (e.g. programmatic validation log file, or manual checklist) then perhaps that needs to be associated as a separate CreativeWork entity from the action's subjectOf -- not sure if we should recommend that or leave it open.

[stain]

https://schema.org/startTime includes "The startTime of something. For a reserved event or service (e.g. FoodEstablishmentReservation), the time that it is expected to start. For actions that span a period of time, when the action was performed" and vice versa for https://schema.org/endTime -- so that was my thinking to only include predicted startTime for a scheduled or in progress event, and only add endTime if it is completed or failed.