How to model a parent-child relation between TODO items correctly

[Cyber1000]

I've proprietary task (from another system) and want them to convert to Todos according to RFC 5545.

I've parent/child relationships between tasks and startet to create them here with parentTodo.Children.Add(todo), but now I'm not sure if using Children/Parent from CalendarObject is the right way to do. RFC 5545 defines RELTYPE (3.2.15) and RELATED-TO (3.8.4.5)

I've found that RecurringComponent.RelatedComponents implements the RELATED-TO Property, but only as IList and RELTYPE seems to be still a TODO in UniqueComponent (comment "Add AddRelationship() public method").

So what's the right method? Use Children/Parent from CalendarObject? Use RelatedComponents (what's the string, the UId of the other component?), but without defining the type of the relation?

Thanks for any help!

[axunonb]

The standard way to represent parent-child relationships between to-dos in iCalendar is to use the “RELATED-TO” property in the child component, where the value is the UID of the parent component, and set the “RELTYPE” parameter to “PARENT” (or omit it, since PARENT is the default)

Alternatively, you could use the “RELATED-TO” property in the parent component and set the “RELTYPE” parameter to “CHILD”, where the value is the UID of the child component.

[axunonb]

@Cyber1000 How did you finally solve the relations?

[Cyber1000]

Sorry to come back here that late, I finally used your proposal with RELTYPE PARENT. It was a little bit confusing that a CalendarObject (where TODO inherits from) has a Parent and a List of children. My first guess was that this will be internally converted into a reltype on serialization. What's the usecase of parent/child her (I assume it makes sense for some other subclass, but not todo)?