You have a translation error there.
Wikipedia about such a law:
It is only named for its origin in the Demeter Project, an adaptive programming and aspect-oriented programming effort. The project was named in honor of Demeter, "distribution-mother" and the Greek god dess of agriculture.
It is the name of the Goddess Demeter, or Demetra.
Otherwise, such a law says that a unit of code must know and communicate only with the units closest to it and directly related to it. New from the wiki:
When object-oriented programs (...) an object A request to service (call a method) of an object instance B, but object A should not "reach through" object B to access yet another object
"When applied to OO (...) an object A can request a service (call a method) from an instance of object B, but object A can not" traverse "object B to access a third object. "
In his case, the "m" method can access his father (type "O"), his brothers (other members of "O"), his own parameters etc. The law is violated if "m" accesses other objects that have been created by other methods, ie D alternative.