The Author Online Book Forums are Moving

The Author Online Book Forums will soon redirect to Manning's liveBook and liveVideo. All book forum content will migrate to liveBook's discussion forum and all video forum content will migrate to liveVideo. Log in to liveBook or liveVideo with your Manning credentials to join the discussion!

Thank you for your engagement in the AoF over the years! We look forward to offering you a more enhanced forum experience.

335250 (2) [Avatar] Offline
#1
Everything within the context adheres to the semantics of the model, but outside the boundary the same concept may have a different meaning
.

The focus of this section is a few abstract concepts that are relatively high-falutin' for most programmers. This is therefore an area where precision is critical to avoid losing the reader. The words "concept" and "meaning" have the same, well, meaning. Nothing is done to relieve the confusion of the reader who thinks "a concept is the meaning of a symbol, so what can it mean to say that a concept has a different meaning?".

Given that the first clause relates a language-category entity ("context") to a model-category entity ("semantics"), I suggest that it would be clearest if the second clause were written in the same style, e.g "outside the boundary the same term may have different semantics". Repetition be damned; this is instruction, not rhetoric.
Daniel Deogun (5) [Avatar] Offline
#2
Good point – thanks! I'll make sure to clarify this in the next revision of chapter 3.