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.

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

Upper and lower case in English learning goal names #55

Open
StefanZoerner opened this issue Jan 19, 2025 · 2 comments
Open

Upper and lower case in English learning goal names #55

StefanZoerner opened this issue Jan 19, 2025 · 2 comments
Assignees
Labels
question Further information is requested

Comments

@StefanZoerner
Copy link

The learning goals in the English version are written like chapter headings, for example

LG 6-1: Understand the API Lifecycle
LG 6-2: Manage APIs as Products
LG 6-3: Know API Lifecycle Tooling

This looks reasonable in the chapters, but not in the list of learning objectives at the beginning, where they are simply placed one below the other. I would therefore write them with small letters at the beginning of the words.

LG 6-1: Understand the API lifecycle
LG 6-2: Manage APIs as products
LG 6-3: Know API lifecycle tooling

At least that's how we did it in the SOFT translation. But perhaps it's also a matter of taste and definitely not super important.

@dret
Copy link
Contributor

dret commented Jan 20, 2025

Since I was the one writing those my vote clearly is for title case. But whether these are titles or not certainly is up for discussion. I'll defer to the majority opinion on that one.

Weirdly, GitHub issues cannot have polls, but discussions can. Should I create a poll in a discussion and link it from here?

@dret dret self-assigned this Jan 20, 2025
@sippsack
Copy link
Contributor

sippsack commented Feb 17, 2025

There was no discussion and would suggest to keep it as it is in the moment. I checked some other curriculums:

  • CPSA-F als uses upper cases
  • FLEX sometimes does and sometimes not

Maybe we should decide an unique style for iSAQB in general. What do you think, @programming-wolf?

Therefore we will leave it for the first release but maybe change it later.

@sippsack sippsack added the question Further information is requested label Feb 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants