(r3) InterOpOct2005ResReg < IVOA

IVOA Web>IvoaEvents>InterOpOct2005>InterOpOct2005ResReg (revision 3) (raw view)~~EditAttach~~

---+ IVOA Interoperability Meeting
---++ 6-7 Oct 2005: ESAC, Madrid, Spain
---++ Registry Session
---
---+++ Chaired by Bob Hanisch, standing in for Tony Linde

<br/>

Agenda

   * Applications software metadata
   * Resource Metadata V1.1
   * ESA VO registry
   * Curation
   * Other matters arising

Notes

(Thanks to Phil Warner, NOAO, for being note-taker!)

Capture about compilers.

How much build information should we provide.

What, at registry level do people need to know about search
capabilities, etc.?  What information to have displayed.

Compiler may not be useful.
  C#, .NET,
  astronomer wants to get information in as few clicks as possible.

Multiple uses of registry
  Users
  Developers

Too much - people won't read
Too little - not enough

Separate into categories?

Specify dependencies (libraries, compilers, version numbers)

Added "Dependencies" section.
  are deps registered?  deps may be IDL (link)

NetworkRequired y/n is not enough?
  Essential/Useful/Limited/Unnecessary

some criteria to whittle down
  - keywords by which to whittle down the list
    (e.g., for sorting)
  - sort of sourceforge {note-taker's addition: freshmeat or
                         packages.gentoo.org}
  - what can I use in my development of _____?
  or
  - what can I use in my research?

Bob went onto google to find places that categorize metadata
  name/text, no more
  why has no one else done this?

useful for workflows?  what workflow engine needs to invoke
if populated well, will allow to build workflows and find code

ongoing cost involved (human)

cost?
  description of pricing, if not freely available.
  optional?

Addition to "license" :
  ...including cost information

focus on Functionality
  - interactive/command-line/script/etc.

added VOStandards section
  - supported standards and protocols used or implemented

added ControlModes section
  - Interactive, command-line, scriptable, from browser, etc.

NVO project has had a registry of tools/software
  - nvo website->tools (list of 15 applications + five others)

machine consumption metadata
services registered by service type
this if focused on end-user applications

these metadata are placed into detailed schema

=================================

do we incorporate into resource metadata document?

get 1.1 out the door?  make this the next iteration?

What else in 1.2?
  this is it.

push through 1.1 first, let this follow with 1.2

==================================

ESAVO Registry & Curation Utility
   
http://esavo.esa.int/registry/

Is ESAVO registry freely available?  no, but could be.
  Could be packaged.

==================================

Registry of registries?
  Has been agreed to, but no action taken


<br/>
<!--
      * Set ALLOWTOPICRENAME = %MAINWEB%.TWikiAdminGroup
-->
   * [[%ATTACHURL%/ApplicationsSoftwareMetadata.pdf][ApplicationsSoftwareMetadata.pdf]]: Draft resource metadata for applications software

Attachments

Topic attachments
I	Attachment	History	Action	Size	Date	Who	Comment
pdf	ApplicationsSoftwareMetadata.pdf	r1	manage	69.4 K	2005-10-07 - 08:00	BobHanisch	Draft resource metadata for applications software

Topic revision: r3 - 2005-10-07 - BobHanisch

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

Committees

Stds&Procs

www.ivoa.net
Documents
Events
Members
XML Schema