Drivers: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
|ComponentCode=D | |ComponentCode=D | ||
|IMAGEComponent=Agriculture and land use; | |IMAGEComponent=Agriculture and land use; | ||
|Reference=Ten Brink et al., 2010; OECD, 2008a; OECD, 2012; UNEP, 2011; Westhoek et al., 2011; | |Reference=Ten Brink et al., 2010; OECD, 2008a; OECD, 2012; UNEP, 2011; Westhoek et al., 2011; | ||
|FrameworkElementType=driver | |FrameworkElementType=driver | ||
|Description===Introduction== | |Description===Introduction== | ||
| Line 43: | Line 43: | ||
Relations between scenario drivers | Relations between scenario drivers | ||
As mentioned in the descriptions of the six scenario drivers, assumptions for each tend to depend to a lesser or greater extent on what is assumed for one or several of the other scenario drivers. Plausibility of the set of drivers, over and above the plausibility of each driver in its own right, therefore hinges on a careful consideration of the nature and direction of these relationships. An overarching story or narrative is proven to be helpful in choosing meaningful combinations across each of the six domains (IPCC, 2000); (Millennium_Ecosystem_Assessment, 2006). | As mentioned in the descriptions of the six scenario drivers, assumptions for each tend to depend to a lesser or greater extent on what is assumed for one or several of the other scenario drivers. Plausibility of the set of drivers, over and above the plausibility of each driver in its own right, therefore hinges on a careful consideration of the nature and direction of these relationships. An overarching story or narrative is proven to be helpful in choosing meaningful combinations across each of the six domains (IPCC, 2000); (Millennium_Ecosystem_Assessment, 2006). | ||
}} | }} | ||
Revision as of 15:57, 31 July 2013
| Projects/Applications |
| Models/Databases |
| Relevant overviews |
| Key publications |
Introduction
"driver" is not in the list (driver component, pressure component, interaction component, state component, impact component, response component) of allowed values for the "FrameworkElementType" property.