1. IVOA Interoperability Workshop Theory and the Applications Interest Group

2. General Issues How do ‘theory’ applications differ from ‘observation’ applications? Role of errors, positions, … Search criteria Data in analytic forms Data discovery How are they comparable? Simulation -> observation Data analysis Physical parameters can be comparable Data volumes Computational requirements What is the role of the VO in theory? Make it easier to combine compare theoretical calculations Like N-body libraries with standard starting condition, evolution formats Standardize bridge between theory and observation Comparison of theoretical model to observed data

3. Do current VO standards help? No: Cone Search, SIA, SSA all position based Yes: VOTable, UCD Can be used to structure theoretical results A little: RM, VOQL, SkyNode Anticipate positional info, but can be used without it Likely: Grids and control technologies Address resource requirements of theory applications

4. What are the Theory VO applications? What are types of theory? N-body, stellar atmospheres, evolution, atomic calculations How do we do data discovery on theory results? Can we package dynamic data generation as ‘discovery’? Are there standard search criteria? Do we need to repackage results or are current data formats comparable to observations? Do we need framework for transforming simulation into pseudo-observation? Can we standardize incorporation of theoretical results into applications? Atomic physics calculations (transition probabilities, etc.) Models (stellar atmospheres, hot plasmas)

5. How can the Applications Interest Group help? Announcements Documentation of extent models and algorithms Standard TBD protocols for announcement of new applications. Discussion Problems using standards/protocols Informal extensions to protocols/standards Experimental protocols Common interest in understanding gaps in standards