I) Suggested Structure for the tutorial:

Unit 1: ASP Basics:

-Responsible: Thomas , Axel+Roman (examples)

- Organization: (90min)

• 45, maximum 60 slides (Optimal: 35 slides basics, plus maybe 20 practical examples?)

- Key issues in this part:

1. Short intro to the demos and intro (where participants find what!)
   • (we should ideally have a tutorial website with the example files, questions and solutionsfor hands-on session and a link to the the Web interface to DLV)
2. Basic notions and intuitive semantics of ASP
3. How to represent rules, queries, constraints in ASP?
4. Distinct features: strong negations and nonmonotonic negation,
   • disjunction/non-determinism, constraints.
5. Demonstrate the ASP basics and paradigm on familiar semantic Web examples.

- Message to convey: ASP is not Prolog, ASP is problem solutions as models

Roman: Explaining the (historically grown) difference between "ASP" and "Stable Model Semantics" could be quite interesting, since this question comes up often, and its answer is insightful.

- Hands-on Examples: "Webbish" Example suggestions: e.g.

• variations of the reviewer selection example.
• a scheduling problem using iCal RDF data.
• (we could extend the movie example from my scoped negation paper.)
• (some easy things on OWL Wine Ontology - ideas?)
• (TODO: Axel to work out some of these examples, maybe Roman wants to join?)

- Material:

• courses for ASP, knowledge representation, wissensmodellierung: Thomas:
• Modelling, ASP, course (Dresden)
• Declarative Wissensrepraesentation/Wissensverarbeitung (Viena)

Unit 2, ASP Extensions:

-Responsible: GB , Axel+Roman (examples)

- Organization (60min)

• max 30 slides (4 times 7-8 slides)

- Key issues in this part:

• Weak constraints! (5)
• Aggregates: DLV and smodels versions or only DLV? (10)
• Rule templates? (8)
• External function calls (7): Shall we introduce the API to add external functions?
• What about APIs? I think this is important!

- Message to convey: ASP is not Prolog, ASP is problem solutions as models

- Hands-on Examples:

• - Weak constraints can be added easily to the rewiewer selection example. - Aggregates: probably fits nicely with reviewers and also time scheduling examples. - Rule templates: Examples transitive closure, etc. - External functions: Point out usefulness for built-ins in order to implement XML
  • datatypes and predicates e.g. the ones allowed in XQuery, demonstrate one or two such examples?
  - APIs: DLV Java- Wrapper, Smodels API ?

Roman: also dlvhex-API, since it is very powerful (imho).

- Message: Extensions address useful features, especially in querying, etc.

Unit 3, ASP State of the Art and realworld showcases:

-Responsible: GB

- Organization:

• (30 min), max 20 Slides

- Key issues in this part: demonstrate "real world" large use cases!

• WASP showcase
• Security (Trento)
• Information Integration (Infomix, GB)
• (TODO: Who has slides here? check also on WASP Website!)

- No Hands-on Examples in this session

Unit 4: Contribution of ASP to SW:

-Responsible: Axel

Organization: (45 min) max 30 slides

Key aspect: Classify and briefly introduce related appoaches to bring ASP to SW:

• reductions from DL to ASP (Swift; Baral; Motik, Sattler)
• Approaches to mix ASP with SW: (Rosati; Eiter,et al.)
• Maybe also: TRIPLE, Description Logic Programs (Decker; Grosof)
• Maybe also: Conceptual logic programming? (Heymans et al.)
• BTW: Scoped negation could maybe also be a point here, but only briefly...

- No Hands-on Examples in this session

Unit 5a: Semantic Web Extensions part I

- Organization: (45 min) max 30 slides

- Responsible: Roman

- Key aspects:

• dl-programs (syntax, semantics, theory)
• how to import of RDF/OWL files

- Hands-on example: Now or at the end of unit 5?

Unit 5b: Semantic Web Extensions part I

- Organization: (45 min) max 30 slides

- Responsible: Thomas

- Key aspects:

• hex-programs (syntax, semantics, theory)
• how do these generalize dl programs and other features?
• more applications

- Hands-on example: Can we also have hands-on for hex programs or shall we focus on dl-programs only and introduce hex programs only theoretically?

Roman: actually - concerning the web-interface - I am much more in favour of hex-hands-on than dl-programs, because the dl-evaluation site is a slow PHP script, while I trust dlvhex much more. However, since dl-programs can be modeled by hex-programs, we could use dlvhex (and hence the dlvhex web-evaluation) invisibly for both formalisms (I will talk to my code-slave, uh, diploma student and suggest to implement the dl-to-hex rewriter)

Unit 6:

Hands-on: (45 min)

The question is how much hands-on we have already in the previous sessions. Actually, I think we should provide a booklet with exercises+solutions and how to solve them, along with the examples from the previous units here which people can solve in small groups tutored by the presenters.

If we proceed like this: showing examples in front of class only during the previous sessions, and guiding them through only in the end.

• I.e. we present all the examples from the previous sessions plus some small

extensions/questions for the participants to solve

• (solutions to be provided as well on the tutorial webpage)

exact organisation to be discussed!

What's missing?

Actually we should have some things on applications like planning etc as well? Maybe in Unit 3? Difficult to fit this?

Existing slidesets (I will check these in on CVS) and Units where these would fit:

• DL-workshop (Thomas)
  • (material could fit into Unit 1, Unit 4, Unit 5
• ASP and equivalences (Thomas), from presentation at DERI Innsbruck.
  • (I think this would be nice, but currently I don't know in which unit this whould fit, probably we could fit it into or after the Unit 5, however some of the stuff there can fit into Units 1)
• ICCL Summer School (Thomas)
  • (fits into Unit 1 (slidesets 1,3) Unit 2 (slideset 4)
• VO Declarative Wissensverarbeitung (Thomas)
  • German, but contains material for units 1,2
• ICLP 05 presentation (Thomas) basically I think thisd material is subsumed by the DL workshop material, yes?
• Talk Axel La Coruna (contains some motivation and discussion on rel works for Unit 4)
• rewerse slides: (Again good slides for units 4 and 5, probably more recent than the DL
  • workshop things?)
• Slides WLP06 from Roman: (Again good, recent slides for units 4 and 5)

II) Missing slidesets:

- Something on the DLV Java-API:

• TODO: GB ask Francesco?

Existing:

• ASP slides from thorsten Schaub from invited talk at WLP (I think these had some very nice approach to explain the ASP paradigm for non-experts). TODO: I can ask Thorsten for these slides!
• ASP Tutorial from Gerald, Nicola, Wolfgang at JELIA'02 (Old but maybe not bad... TODO: GB, could you check with Wolfgang?)
• ASP Tutorial at ICLP (Niemela):
  • TODO: Can we get these slides somehow?
• Infomix-slides for review: GB, Gianluigi have slides,
  • Query rewriting in dicj. logic programs Information Integration
  TODO: GB please add to CVS!
• ASP Showcases:
  • Large Databases, Security (Trento), Info Integration TODO: Thomas, where from can we gather slides+sources for these use cases?
    • Who to contact?
• Slides discussion related approaches for session 4.
  • TODO: Axel: I will work on this, Anybody else interested?

III) Examples:

• What running example shall we take? The reviewer selection example actually
  • seems to be a nice running example. We could extend it with some RDF stuff by e.g.
    • disallowing that the author know their reviewers (derived from their foaf-files)
    • or at least adding a respective weak constraint (by which example we could show
      • the weak constraints.
• I cannot really check Schema Web or any other before I come to Vienna.
  • Check: Schema Web: Bunch of good Ontologies, Problems with the Food/
  • Wine Ontologies of W3C: (we mentioned this in the proposal)
    • syntactic errors... inconsistent? (check this wirth Roman).
  TODO: Roman, Can you check suggest examples, ideally consistent for the different parts of the tutorial? (We can work them out in Viena, but simply starting up a whole would be nice.)

Roman: Finding good examples is not trivial - however, I think we should first define how many examples we need and what each of them should demonstrate. It could also be quite contrived to stick to one single example, maybe better to have two. Of course it would be very nice to have something from Bonatti's policy stuff - I could try to push him a bit to help us creating something meaningful, but not too complicated.

IV) Infrastructure: What we need for the Tutorial:

• Tutorial Website with examples, slides, questions and solutions,
  • link to DLV web interface, Maybe put some things as appendix in the Handouts, but having a website is probably easiest, the handouts can then simply be prints from this site and the slides with some space to make notes
• DLV server with Web interface. How many instances can run at once? Test this!!!
  • Fallback solution: What does a minimal binary for several pllatforms need?
    • WLAN!
    • DLV Server
    • failsafe solution for backup: i.e. one internet version, one local network.
• We should have a common layout for the slides
  • (TODO: Roman, can you provide a common beamer-template, maybe we should
    • add some ESWC-logo, but not to much graqhics apart...) Roman: Need to test this, I will report asap. For a local version, we would need a server running apache and php, nothing fancy.
• We should have a common layout for the examples: As said above,
  • best would be a nice homepage.
    • Roman: Can take care of this, will need some more days. As for the design: lately, I adopted a very clean, simple design for pages I

      created, e.g.: http://www.kr.tuwien.ac.at/staff/roman/aspruleml/