(r25) InterOpMay2006ResReg < IVOA

IVOA Web>IvoaEvents>InterOpMay2006>InterOpMay2006ResReg (revision 25) (raw view)~~EditAttach~~

The primary goal of this set of sessions will be to sign off on V1.0 of Registry schemas and Registry interface. We will also discuss whether to make these two and the current Registry Metadata document into a single standard.

Sessions and their agenda will be posted here nearer the meeting date.

%TOC%

---++ Agenda

%TABLE{sort="off" tableborder="1" cellpadding="4" cellspacing="2" valign="top" databg="none" headerbg="#FFFF99" headercolor="#000000" headeralign="center"}% 
| *Session* | *Date* | *Topic* | *Leader* | *Talks* | *Speaker* |
| *Open Plenary* | Mon <br>10:00&#8209;13:00 |  |  | Registry goals etc ([[%ATTACHURL%/Plenarystart-Registry.pdf][pdf]]) | Tony |
| *1* | Tue <br>09:00&#8209;10:30 | [[RegDMServices][Services DM]] | RayPlante | Basic VOResource changes ([[%ATTACHURL%/IVOAMay06VOResource.ppt][ppt]]) | Ray Plante |
|^|^| || VOServices (see previous) | Ray Plante |
|||||||
| *2* | Tue <br>11:00&#8209;12:30 | [[RegDMApplications][Applications DM]] | PaulHarrison | VOApplications (pdf) |  |
|||||||
| *3-4* | Thu <br>09:00&#8209;10:30 <br>11:00&#8209;12:30 | Registry Interface | KevinBenson | (pdf) |  |
|^|^| Registry Extensions | TonyLinde | <nop>VOResource schema: Security method | RayPlante |
|^|^| || Registry granularity <br>incl <nop>DataCollection | RayPlante & KevinBenson |
|^|^| || <del>Using CEA parameter structure</del> (done on Tues) | PaulHarrison |
|^|^| || _Publishing to VO_ document ([[http://us-vo.org/pubs/files/PublishHowTo.html][here]]) | RayPlante |
|||||||
| *5-6* | Thu <br>14:00&#8209;15:30 <br>16:00&#8209;17:30 | New Resource Types | TonyLinde | Outreach images ([[%ATTACHURL%/AOIMetadata_final.pdf][pdf]]) | BobHanisch |
|^|^| || VOEvent ([[%ATTACHURL%/IVOA-Reg5.ppt][ppt]]) | MatthewGraham |
|^|^| || Simulations ([[%ATTACHURL%/SD_simulations.pdf][pdf]]) | SebastienDerriere |
|^|^| Planning & Roadmap | TonyLinde |  |  |
| *Close Plenary* | Fri <br>13:30&#8209;15:30 |  |  | Registry roadmap etc (pdf) | Tony |
</div>

---++ Notes
*Links:*
   * http://ivoa.net/twiki/bin/view/IVOA/InterOpMay2006ResReg

   * http://ivoa.net/twiki/bin/view/IVOA/VOResourceV10
   * http://ivoa.net/internal/IVOA/VOResourceV10/WD-VOResource-v1.html

   * http://ivoa.net/twiki/bin/view/IVOA/RegDMServices

   * http://ivoa.net/twiki/bin/view/IVOA/RegDMApplications

---+++ Session 1
---++++ VOResource basic changes
   * Timestamp on created, updated
      * xs:dateTime instead of &lt;date>
      * Drop 'Z': assume UTC
      * *AGREED*
      * also *AGREED* that both elements should be ==mandatory==
   * Relationships
      * Define new relationships types in extension schema
         * Use xsi:type
         * *NOT AGREED*
      * Will add list of keywords for rel types in doc appendix and registry systems have to code that list validation
         * *AGREED*
   * Move webservice Interface sub-type to core schema
      * Allows desc of generic ws wo ext schema
      * accessURL is the service endpoint
      * *AGREED*
   * elementFormDefault="unqualified"
      * All terms look like from same namespace
      * Throws element name into noname ns
      * *DEFERRED*
   * Changes to resource class names
      * <nop>SkyService -> <nop>DataService
      * <nop>TabularSkyService -> <nop>CatalogService
      * *AGREED*
   * STC integration
      * Contents:
         * stc:STCResourceProfile, footprint, waveband
      * Issues
         * ns is "qualified"
         * Cannot index in same way e.g. for searching
            * Services under dev't
         * Help for authors
      * *AGREED*
         * But need to develop tools

The issue of the usability of registry interface applications was raised: how easy it was for users (primarily data centre persons) to enter and maintain resource information. It was *AGREED* that the Registry sessions for the September Interop meeting in Moscow should focus on ==registry systems usability==.

---++++ New Service Model
   * Goals
      * Indicate std version
      * Support multiple endpoints
      * Desc non-std i/fs
      * Clarify assoc between service cap metadata and i/f
   * Support for std via standardID
      * Registered as resource
         * Not mandated: use URI
      * Put into <nop>RofR
      * Req extension schema
      * *AGREED*
   * Service with capabilities
      * Structure
      * Finding services
      * Add validationLevel as child of Capability
      * Extra metadata validation reqd
      * *AGREED*
   * Interface: all content data optional except accessURL
      * Impl may list support for optional or non-std parameters
      * Interface info in std resource record

---+++ Session 2
---++++ Applications
   * Extension rather than 'core'
   * Goals: 
      * support app-specific metadata
      * Info on stds & formats
      * Concepts of desktop app, sw lib, apps called as services
   * voStandard
   * Execution environment
      * Platform: generic
      * Subtype
      * Version, …
   * Data formats
      * *AGREED* use MIMEtypes
   * *AGREED* for Paul to produce WD for VOApplications
      * *DEFERRED* decision on how to replicate such info across registries to final roadmap discussion

---++++ CEA Applications
   * CEA interface: how to define app asynchronously (not discussed here)
   * App model
   * Features
      * Multiple i/fs
      * Parameters
   * a number of people were interested in developing apps which would register and be able to be discovered using this extension
   * *AGREED* for Paul to produce WD for CEAApplication extension

---+++ Session 3
---++++ Registry Interface
   * Kev gave quick run through of existing document
      * http://ivoa.net/internal/IVOA/RegistryInterface/RegistryInterface-v0.8.1.pdf

*Issues:*
   * ADQL searching (with qualified resource schemas)
      * Unqualified ns allows no prefixes so spec needs to change
      * *AGREED* that Tues discussion re unqualified is ratified
   * ADQL core/extended
      * Core is simple sql with REGION
         * *AGREED* we will implement restricted set of v1.0 of ADQL core with xpath specification of the elements
      * Extended incl multiple tables, xmatch, etc
         * Not an issue
   * WSDL & <nop>RegInterface schema qualified & unqualified
      * WSDL qualified
      * But ==type section for messages will be unqualified==
   * <nop>KeywordSearch: boolean orWords
      * *AGREED* mandatory with default TRUE
   * Xquery
      * Root element: use /RootResource
         * *AGREED*
         * *AGREED* that it is Mandatory
      * Tag in schema which says whether registry supports XQuery 
         * done
   * Extensions for harvesting and storing
      * *AGREED* mandatory that all registries MUST return full record as harvested, whether or not it can search on the extension information
   * Xpath
      * Issue of e.g. selecting SIAP resources with maxRecords < 100
      * Where capability/@xsi:type="vr:SimpleImageAccess" AND capability/maxRecords<100
      * Might use keyword <nop>SimpleImageAccess or function (CAPABILITY)
      * ==Not an easy solution so v1.0 will not deal with this==
         * Need feedback from those providing relational registries
   * <nop>RofR
      * ==Need to create document==
   * Harvesting: sets
      * Allows selection of subset of collection
      * ivo_managed: only those defined in registry
         * Will mostly use this for harvesting
         * *AGREED* ==only this one in v1.0==
      * Following not in v1.0 spec: registries can try these out
         * ivo_standard: only standard schemas
         * ivo_name that matches resource type
   * Registering standards
      * Schema still under discussion

---+++ Session 4
---++++ Granularity
   * Prelim on securityMethod
      * *AGREED*
      * ==Interpreted as AND==

   * Ray introduced topic with presentation
      * http://ivoa.net/internal/IVOA/InterOpMay2006ResReg/IVOAMay06Graininess.ppt
   * Issues:
      * Metadata content: Fine-grained vs Coarse-grained
      * Types of resources in the registry
         * Larger aggregations vs images, people etc
   * Questions...

   * *AGREED* VOResource core must be searchable by all registries
   * *AGREED* every registry MUST return full record for any resource
   * *AGREED* flag against registry allowsExtendedSearch which indicates that registry is searchable on any extension schema element as well as core
   * *AGREED* that column metadata will include ==utype== string as an optional element which may be used in the future for data model pointers

   * Data collections
      * Esp important for <nop>VizieR
      * *AGREED* that concept should be developed into v1.0 spec
      * Need to know size of catalog: coverage.objectCount is in RM
         * But also need to know nr rows in tables for data collection ==so need element for that==

---+++ Session 5
---++++ Outreach Images
   * Very fine-grained metadata
      * Re image, video etc
   * Aimed at compatibility with existing registry info
   * ?relation to Semantics work
      * Different taxonomies?
   * Propose
      * Do not try to dissect document
      * Provide support from registry workgroup
   * *AGREED*
      * Will recommend they publish doc as IVOA Note
      * Recommend that Semantics group take account of controlled vocab
      * Will work with group to develop outreach collection schema and get their collections registered as VO resources

---++++ VOEvent
   * Work on registry extensions from VOEvent group
   * Matthew presented overview of VOEvent
   * Registry use cases
      * Tell me about author, publisher, ==repository== (each is ivorn)
      * Which publisher has this author
      * Which repository has this publisher
   * New types:
      * ==Publisher==
         * List of authors (cF managedAuthority)
         * Subscription interface
            * Transport protocol
            * Endpoint
            * User account/anonymous
      * ==Repository==
         * List of publishers (cF managedAuthority)
         * Query interface
            * Endpoint
            * SEAP (simple event ..)

---++++ Publishing to the VO
   * http://us-vo.org/pubs/files/PublishHowTo.html
   * =='Who are you'== approach
      * Which then points you to a set of instructions
   * *AGREED*
      * Will publish nvo doc as wiki page which others can contribute to making a generic guidelines

Attachments

Topic attachments
I	Attachment	History	Action	Size	Date	Who	Comment
pdf	AOIMetadata_final.pdf	r1	manage	401.9 K	2006-05-10 - 16:31	BobHanisch
ppt	IVOA-Reg5.ppt	r1	manage	1216.5 K	2006-05-18 - 21:56	MatthewGraham	VOEvent resource types
ppt	IVOAMay06Graininess.ppt	r2 r1	manage	219.5 K	2006-05-18 - 16:01	RayPlante
ppt	IVOAMay06SecMethod.ppt	r1	manage	333.0 K	2006-05-18 - 17:57	RayPlante
ppt	IVOAMay06VOResource.ppt	r1	manage	483.0 K	2006-05-16 - 15:10	RayPlante
ppt	ceaparamter.ppt	r1	manage	1435.5 K	2006-05-18 - 20:57	PaulHarrison	Cea application model
pdf	registryappdm.pdf	r1	manage	7232.0 K	2006-05-16 - 17:34	PaulHarrison	Registry Application Data Model
ppt	registryappdm.ppt	r1	manage	1103.5 K	2006-05-16 - 17:22	PaulHarrison	Registry Application Data Model

Topic revision: r25 - 2006-05-18 - TonyLinde

IVOA

Log in or Register

IVOA.net
Wiki Home
WebChanges
WebTopicList
WebStatistics

Twiki Meta & Help
IVOA
Know
Main
Sandbox
TWiki

TWiki intro
TWiki tutorial
User registration
Notify me

Working Groups

Interest Groups

Time Domain

Committees

Stds&Procs

www.ivoa.net
Documents
Events
Members
XML Schema