-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
0011 book 3 behavior #198
0011 book 3 behavior #198
Conversation
Establishing link with issue #11 |
Cookbook editor comments: The cookbook editors note this recipes contains two use cases in one and this may come up in the TRC although the editors are happy to approve it as all use cases match the feature described. In use case
In Restrictions
in Related recipes:
The cookbook editors are happy to approve the recipe with the changes above. |
Thank you for the feedback. I'm happy to make the changes above, but have a question about the use case. In discussing the use cases for this recipe, we decided to only include continuous and individuals because the recipe was for behavior variations for book objects. Unordered doesn't fit this use case, so we left it out. I think we'd need to change the focus of the recipe overall to include unordered. I'm happy to do so, but want to make sure this is the intention. Alternatively, I could create a new issue/recipe that focuses on behavior for something like an archival folder. |
Thats a good point. The thing that came up in the meeting was that |
Issue passed in TRC with no changes requested so I am merging. |
No description provided.