Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Describe significance of user field #274

Closed
zimeon opened this issue Nov 9, 2018 · 3 comments
Closed

Describe significance of user field #274

zimeon opened this issue Nov 9, 2018 · 3 comments
Assignees
@awoods
Labels
Editorial Editorial issues (no changes to intent) Needs Discussion
Milestone
Beta

Comments

@zimeon
Copy link
Contributor

zimeon commented Nov 9, 2018

Comment about user data split from @justinlittman #272:

  • In 3.5.3, describe the significance of the user field.
@zimeon zimeon added the Editorial Editorial issues (no changes to intent) label Nov 9, 2018
@justinlittman justinlittman mentioned this issue Nov 9, 2018
Closed
@zimeon
Copy link
Contributor Author

zimeon commented Nov 9, 2018

I agree that we do not provide sufficient motivation for the requirement of the user field (does it really justify MUST?) and its format

@rosy1280 rosy1280 added this to the Beta milestone Dec 5, 2018
@rosy1280
Copy link
Contributor

rosy1280 commented Jan 6, 2019

@zimeon would it make sense to split out the list into two sections, must and may? I can see the message being in a similar boat as user.

@awoods
Copy link
Member

awoods commented Jan 9, 2019

For keys in the OCFL Version block, I can see the following as MUST:

  • created
  • state

..and the following as SHOULD:

  • message
  • user

@awoods awoods self-assigned this Feb 6, 2019
awoods pushed a commit to awoods/spec that referenced this issue Feb 6, 2019
Describe significance of user field in Inventory
03024a4 
- Move `user` and `message` from MUST to SHOULD

Resolves: OCFL#274
@awoods awoods mentioned this issue Feb 6, 2019
Merged
ahankinson pushed a commit that referenced this issue Feb 11, 2019
@ahankinson
Describe significance of user field in Inventory (#297)
b6dad26 
- Move `user` and `message` from MUST to SHOULD

Resolves: #274
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@awoods awoods

Labels
Editorial Editorial issues (no changes to intent) Needs Discussion
Projects
None yet
Milestone
Beta
Development

No branches or pull requests
3 participants
@rosy1280 @awoods @zimeon