CAMP PDP sketching after v4 and before the fruits

1 vitaminder (based on mine, gil's, derek's, then mine again)

name: VitaMinder
artifacts:
  -  
    name: VitaMinder WAR
    type: com.example.java:WAR
    content: { href: vitaminder.war }
    requirements:
      -  
        type: HostedOn
        fulfillment: id:as
      -
        type: JDBC
        fulfillment: id.db  # or service-spec here directly
      # We still can use component-specific in-line requirements
      -  
        type: com.example:SomeJEEFeature
        mode: session
  -  
    name: VitaMinder SQL
    type: com.example.sql:SqlScript
    content: { href: vitaminder.sql }
    requirements:
      -  
        type: ExecuteAt
        fulfillment: id:db
services:   //modulo the name of this (PCTish)
  -  
    name: VitaMinder DB 
    id: db 
    requirements:  //modulo the name of this (capability?)
      -  
        type: com.example.db:RDBM
      -  
        type: com.exampl.db:Replication
        replicas: 2
        strategy: com.example.db:Optimistic
      -  
        type: com.example.db:SQL
        version: SQL:2008
  -  
    name: App Server
    id: as
    requirements:
      -
     	  type: com.example:WebContainer
        javaVersion: [1.6,)
      - 
        type: com.example.java:JDBC
        version: 4.0
        injectionMode: CDI

2 similar thing, using syntax overloading ("short-form syntax") to make more readable

name: VitaMinder
components:
  war:
    name: VitaMinder WAR
    type: com.example.java:WAR
    content: VitaMinder.war
    requirements:
      com.example:HostedOn: { javaVersion: [1.6,) }
      com.example.java:JdbcDependency: 
        injectionMode: CDI
        fulfillment: db
  sql:
    name: VitaMinder SQL
    type: com.example.sql:SqlScript
    content: vitaminder.sql
    requirements:
      com.example.db:RunAt: db
  db:
    name: VitaMinder DB
    requirements:
      - com.example.db:ODBC
      - com.example.db:redundancy: { mode: synchronous, replicas: 2 }