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

Inconsistencies between motivations types (list, string) in Content State API #2313

Open
giacomomarchioro opened this issue Aug 30, 2024 · 1 comment · May be fixed by #2325
Open

Inconsistencies between motivations types (list, string) in Content State API #2313

giacomomarchioro opened this issue Aug 30, 2024 · 1 comment · May be fixed by #2325

Comments

@giacomomarchioro
Copy link

Hi all,
Although in https://www.w3.org/TR/annotation-model/ motivation is always followed by a string in Content State API it is always a list, except for the Multiple targets section where motivation value is a string e.g.:

"motivation": "contentState", instead of "motivation": ["contentState"],

Should they be uniformed?
@markpbaggett
Copy link

Just noticed this as well. It seems like the example should be "motivation": ["contentState"].

@glenrobson glenrobson linked a pull request Dec 3, 2024 that will close this issue
Motivation should be Array, not String #2325
Open
@glenrobson glenrobson mentioned this issue Dec 3, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Motivation should be Array, not String cubap/api
2 participants
@markpbaggett @giacomomarchioro