The logically redundant Sibling activity element (related-activity type="3") may be useful in some circumstances but in a database context, the need is much less , since navigation to a sibling via a parent and child relationships would probably be sufficient. IF not the relationship can be computed on the fly.
Activities are frequently bloated with these elements. eg. SIDA such as
The logically redundant Sibling activity element (related-activity type="3") may be useful in some circumstances but in a database context, the need is much less , since navigation to a sibling via a parent and child relationships would probably be sufficient. IF not the relationship can be computed on the fly.
Activities are frequently bloated with these elements. eg. SIDA such as
http://data.aidinfolabs.org/admin/corpus/main/Publisher/sida/set/sida-189/activity/SE-6-5204017401-189ANO-72010
Ignoring all sibling elements on load would be one solution - better to drop this redundant element entirely.