text: If you click on the Manager individual, you will see that he has a constraint violation because his phone 
  number is not in the proper format. Waiter1 has a similar problem. Waiter2 has missing data. Her 
  hasPhone and ssn data properties both must have values but don’t. 
  
  If you move your focus to the Customer class, you can see the remaining 3 constraint violations. 
  Customer10’s hasDiscount property is greater than 1 which is not allowed. This is defined by the 
  CustomerShape in the hasDiscount node with sh:minInclusive 0.0 and sh:maxInclusive 
  1.0. This is the way you define a minimum and maximum value for a numeric property (note: this 
  applies to the value not to the number of values). Customer2 also has a hasPhone value that doesn’t match 
  the defined format and finally Customer3 does not have a value for hasPhone when at least one is 
  required. 
  
  Recall that the SHACL constraints themselves are essentially RDF graphs. Figures 11.3 and 11.4 
  illustrate the Employee shape and the Customer shape used in the above example as graphed in the 
  Gruff tool from AllegroGraph. 