# Task Planning Specification questions

**Category:** [Task Planning/GDL](https://discourse.openehr.org/c/task-planning-gdl/27)
**Created:** 2020-07-13 10:35 UTC
**Views:** 615
**Replies:** 2
**URL:** https://discourse.openehr.org/t/task-planning-specification-questions/867

---

## Post #1 by @Cristiana_Neto

Hello,
During an analysis of the [TP specification](https://specifications.openehr.org/releases/PROC/latest/task_planning.html), some questions arose that I would like to discuss:
1) The class CALENDAR_ENTRY has no properties in the specification. I think it would be pertinent to specify these properties since it seems incomplete. What do you think?
2) The class M_CALLBACK is not defined in the specifications despite being defined in [JSON](https://specifications.openehr.org/releases/ITS-JSON/latest/components/PROC/latest/Materialised/M_CALLBACK.json). Is there any reason for this?

---

## Post #2 by @thomas.beale

Hi Cristiana,
Yes, the CALENDAR_ENTRY type needs a bit more work.

The M_* classes are less reliable than the main definitional classes, and we are debating about whether to even keep them in the spec. 

If you would like to follow / participate in the ongoing TP/GDL discussions, please do so on the #taskplanning channel in [openEHR specifications Slack](https://openehrspecs.slack.com), and also follow this Discourse category. More participants are very welcome.

---

## Post #3 by @Cristiana_Neto

Thank you for your reply. 
It would be great to have access to that discussion. Can you please send me an invitation (cristiana.neto@algoritmi.uminho.pt) so that I can access Slack?

---


**Canonical:** https://discourse.openehr.org/t/task-planning-specification-questions/867
**Original content:** https://discourse.openehr.org/t/task-planning-specification-questions/867