Content deleted Content added
Jerryobject (talk | contribs) m Small WP:COPYEDITs WP:EoS WP:TERSE. WP:LINK: needless WP:PIPE > WP:NOPIPE. MOS:FIRSTABBReviation clarify, define before WP:ABBR in parentheses. Cut needless carriage return whitespace characters in sections: to standardize, aid work via small screens. WP:NAVBOX update. |
→Overview: no need for advertisement... |
||
Line 7:
Preferences can be regarded as soft constraints on a plan. The quality of a plan increases when more preferences are satisfied but it may not be possible to satisfy all preferences in one plan. This differs from hard constraints which must be satisfied in all plans produced by the planning software. These hard constraints are part of the [[___domain knowledge]] while the soft constraints (or preferences) are separately specified by the user. This allows the same ___domain knowledge to be reused for various users who may have different preferences.
The use of preferences may also increase the length of a plan in order to satisfy more preferences. For example, when planning a journey from home to school, the user may prefer to buy a cup of coffee along the way. The planning software could now plan to visit
== Planning Domain Definition Language ==
| |||