Difference between revisions of "Other Meetings and Notes"

From Metadata-Registry
Jump to: navigation, search
Line 18: Line 18:
  
 
** Promises about Semantic Web applicability (RDF, etc.) needs to be addressed. Specifically management in RDF "space" counts towards success to NSF in its research mode. Decisions about how far to go will be made in the context of what is needed for the functionality.
 
** Promises about Semantic Web applicability (RDF, etc.) needs to be addressed. Specifically management in RDF "space" counts towards success to NSF in its research mode. Decisions about how far to go will be made in the context of what is needed for the functionality.
 +
 +
What's the registry for? Still for discovery and reuse, avoiding reinvention of wheels. Also promote use by machines, rather than reliance on humans (also support and management). At the basic level, provide discovery and identification of vocabularies at the description level, which do not have term-level information available.
  
 
* 10:00-11:00
 
* 10:00-11:00

Revision as of 07:31, 14 October 2005

F2F Meeting, Oct. 14, 2005, Ithaca, NY

Agenda

  • 9:00-10:00 Goals for the project: defining "success"
    • Is it usage? If so, how many (users, vocabularies, terms?)

Goal: 10 Organizations/50 vocabularies

    • Is it functionality? (can do all five below? and are all functions equally important?)
      • Creating/registering/maintaining a scheme (controlled vocabulary) and its member terms
      • Creating/registering/maintaining a schema (element/property set) and its member terms
      • Creating/registering/maintaining an application profile
      • Creating/registering/maintaining of a scheme-to-scheme mapping (value spaces)
      • Creating/registering/maintaining of a schema-to-schema mapping (element/properties)

First three are contractually mandated, last two "good if we can." Application profiles least baked.

    • Promises about Semantic Web applicability (RDF, etc.) needs to be addressed. Specifically management in RDF "space" counts towards success to NSF in its research mode. Decisions about how far to go will be made in the context of what is needed for the functionality.

What's the registry for? Still for discovery and reuse, avoiding reinvention of wheels. Also promote use by machines, rather than reliance on humans (also support and management). At the basic level, provide discovery and identification of vocabularies at the description level, which do not have term-level information available.

  • 10:00-11:00
    • Define coarse feature set, with basic tasks to accomplish for each

INPUTS:

  1. Externally managed vocabularies (SKOS, OWL)

ADMIN BITS:

  1. Search, browse, display terms, relationships, etc.

OUTPUTS:

  1. Lossless output of externally managed vocabularies (SKOS, OWL)
  • 11:00-noon
    • Attach priorities to each feature in terms of stakeholder and client satisfaction:
      • A (must have)
      • B (nice to have)
      • C (add it if we can)
      • D (future grants)
    • Determine complexity and assess risk for each feature
  • 12:30-1:30
    • Road map, includes timelines and milestones [a.k.a. "release dates"--may be internal]
      • Try to assign 'must have' features to milestones
  • 1:30-2:00
    • Review progress
    • Review task lists
  • 2:00-3:30
    • Add external review and testing tasks/timelines?
  • 4:00-5:00
    • Communication, documentation, meetings
      • Can we agree on "communication protocols" amongst the group?
      • How often do we need F2F meetings, telecons?
      • What are our expectations re: internal and external documentations?