anchor.diff:              section(data-markdown)
                   h2 Domain can refer to  
                   ul
  -                  li the entire domain of the business, 
  -                  li as well as just one core or supporting area of it
  +                  li.fragment the entire domain of the business, 
  +                  li.fragment as well as just one core or supporting area of it
               section
  -                h2 Should we 
  -                p  create a single, cohesive, all-inclusive models
  -                   of an organization's entire business domain?
  +                p Should we create a 
  +                ul
  +                  li single,
  +                  li cohesive,
  +                  li all-inclusive models
  +                p of an organization's entire business domain?
               section
                   h2 DDD places the emphasis on just the opposite 
               section
  
positive.code:                 h2 Example of an Inventory System
                  ul
                    li An Inventory System is about managing goods (items).
                    li Yet, there's no guarantee that it has a completely clean model, 
                       possessing wholly unambiguous domain linguistics.
              section
                  h2 an Item
                  ul
                    li on order that is yet available for sale Back-Ordered Item
                    li being received - Goods received
                    li in stock - Stock Item
              section
                  h2 an Item (cont.)
                  ul
                    li being consumed - Item Leaving Inventory
                    li and, an Inventoried Item that becomes broken - Wasted Inventory Item
              section
                  h1 Ubiquitious Language
                  ul
                    li Ubiquitious means "found everywhere"
                    li The use of the word is not an attempt to describe some kind 
                       of enterprise-wide, company-wide, or universal domain language 
                    li There is one Ubiquitious Language per Bounded Context
  
           section
              section
  
negative.code:                    the Ubiquitious Language have specific meaning, and the model reflects 
                     the Language with exactness.
               section
                   h2 Bounded Contexts and Context Map
                   ul
                     li On a single project that develops a single
                        Bounded Context, there are always one or more additional
                        isolated Bounded Context with which it integrates using
                        Context Map.
                     li.fragment Each of the multiple Bounded Contexts that
                        integrate has its own Ubiquitious Language, even though
                        some terms of each may overlap.
               section
                   h2 Blended core concepts with generic ones
                   img(src="img/blended-core-concepts-with-generic-ones.jpg")
  