You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It doesn't make sense to have a cycle in supplements / replaces relationships, since they are apparently causally ordered.
Since $tag-rel-type-choice is extensible by profiles, do we say that only cycles involving supplements/replaces are invalid and leave the validity of cycles to a profile that extends the relationship enum to decide? Or just disallow cycles entirely?
The text was updated successfully, but these errors were encountered:
It's hard to get your mind around a legitimate use case that results in a cycle. I'm OK with languagee that rejects cycles until a use case is identified that needs it.
It doesn't make sense to have a cycle in supplements / replaces relationships, since they are apparently causally ordered.
Since
$tag-rel-type-choice
is extensible by profiles, do we say that only cycles involving supplements/replaces are invalid and leave the validity of cycles to a profile that extends the relationship enum to decide? Or just disallow cycles entirely?The text was updated successfully, but these errors were encountered: