DARPA Agent Markup Language (DAML) Details

(vs. database, base XML, etc.)

URI-based naming
- "Cardinals" vs.
  - http://www.mlb.com/teams/2001#cardinals
  - http://www.audubon.org/birds#cardinal
  - http://www.stanford.edu/athletics#cardinal (color)
- drill down
adding properties to someone else's objects
- Goodyear Blimp pilot needs lat/lon for Busch Stadium rather than street address
- aggregation

expressive power

class expressions

<daml:Class rdf:ID="Southpaw">
  <daml:sameClassAs>
    <daml:Restriction>
      <daml:onProperty rdf:resource="#position">
      <daml:hasValue rdf:resource="#Pitcher">
    </daml:Restriction>
    <daml:Restriction>
      <daml:onProperty rdf:resource="#throws">
      <daml:hasValue rdf:resource="#Left">
    </daml:Restriction>
  <daml:sameClassAs>
</daml:Class>

subproperties

<rdf:Property rdf:ID="father">
  <rdf:subPropertyOf rdf:resource="#parent"/>
<rdf:Property>

data distributed over multiple sites
fine-grained filtering of individual facts rather than pages

Why DAML?