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

STU4B#125: Updated text and chose first option (even though) #12

Merged
merged 1 commit into from
May 29, 2019
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion spec/01-introduction.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -127,7 +127,7 @@ The specification is written with the following major roles in mind:

Table 1‑B

Note that even the material in Chapter 2 is somewhat technical in nature, and that Authors will benefit from some familiarity with and/or training in basic computer language and database language topics.
Note that even though the material in Chapter 2 is somewhat technical in nature, and that Authors will benefit from some familiarity with and/or training in basic computer language and database language topics.

In general, each of these roles will benefit from focusing on different aspects of the specification. In particular, the Author role will be primarily interested in Chapter 2, the Language Guide for the high-level CQL syntax; the Developer role will be primarily interested in Chapters 2 & 3; the Integrator role will be primarily interested in Chapter 4, the formal description of the logical model; and the Implementer role will be primarily interested in Chapters 5, 6, and 7, which discuss the intended execution semantics, translation semantics, and physical representation, respectively, as well as Chapter 9 - Appendix B, and ELM UML model artifacts.

Expand Down