- From: Dan Connolly <connolly@w3.org>
- Date: 08 Jul 2002 10:50:19 -0500
- To: "Smith, Michael K" <michael.smith@eds.com>
- Cc: webont <www-webont-wg@w3.org>
On Mon, 2002-07-08 at 10:22, Smith, Michael K wrote: [...] > - Introduction > - Why (steal from other docs or maybe just point to them) > - Some indication of the kinds of things you can expect to be able > to express in OWL. Perhaps some specific indications of what > you cannot. > - Brief history - RDF, RDFS, DAML+OIL (steal or point to) > - Background - URI's, XML, ... (steal) I suggest moving that stuff to later in the document, as much as possible. Don't make them learn anything before they get their first bit of immediate gratification. I'd like to see the first (or: one of the first) section headings relate to our use cases... ala: - Finding the needle in a multimedia haystack wherein, using a pre-existing ontology, the reader can construct queries on a multimedia collection using part-whole relationships and such. Something like: "I know some part of a collection edited by Sholz has a sonata performed by Pinkerton... tell me the title of that part and all the names of the performers? result(?Title, ?PerformerName) :- mm:part(?Collection, ?Part), mm:editor(?Part, ?Sholz), mm:familyName(?Sholz, "Sholz"), dc:type(?Part, mm:Sonata), mm:performer(?Part, ?Pinkerton), mm:familyName(?Pinkerton, "Pinkerton"), dc:title(?Part, ?Title), mm:performer(?Part, ?Performer), mm:familyName(?Performer, ?PerformerName). cf http://www.w3.org/TR/webont-req/#usecase-multimedia There are a number of tools that can handle this sort of query... we can publish some sample data as part of the tech report (or put it in our test repository). > - Housekeeping > - Setting up namespaces > - Ontology headers > - Importing ontologies (w/ forward pointer to Ontology Mapping) > - Dublin Core metadata (????) > - Simple Classes and Individuals > - Defining simple hierarchical named classes (class, subClassOf) > - Defining individuals (individual) > - Datatypes (user-defined XML Schema datatypes) > - Simple Properties > - Defining properties (property, subPropertyOf, domain, range) > - Part-whole relations (????) > - Property axioms (characteristics and restrictions) > - transitive, symmetric, functional > - isTheOnlyOne, eachValueFrom, someValueFrom > - simple cardinality > - Ontology mapping > - sameClassAs, samePropertyAs > - sameIndividualAs, differentIndividualFrom > - Complex Classes (axioms and constructive classes) > - Class relations - oneOf (enumerated classes) > - Class relations - disjoint classes > - Class relations - sameClassAs, subClassOf applied to class expressions > - unionOf, intersectionOf, complementOf > - Complex Property axioms > - Full cardinality > - Defining property attributes (transitive, ...) > - Defining property restrictions > - Idioms (????) > How to assert commonly desired relations whose expression in OWL > may not be obvious. > - Entailments (????) > E.g. how to ask questions of a KB. > Is this too implementation specific? Not all OWL implementations > will support full OWL reasoning. > - Questions about classes (all x: C(x) -> P(x,b)) > - Questions about individuals (C(a), P(a,b)) > - Retrieveal of sets of individuals ({x : C(x)}, {x : P(x,b)}) > - ... > > plus references and some appendices: > > - OWL, DAML+OIL and RDF Schema (issues involved in transitioning) > ... > > > Michael K. Smith > EDS - Austin Innovation Centre > 98 San Jacinto, #500 > Austin, TX 78701 > > * phone: +01-512-404-6683 > * mailto:michael.smith@eds.com > www.eds.com -- Dan Connolly, W3C http://www.w3.org/People/Connolly/
Received on Monday, 8 July 2002 11:49:31 UTC