Difference between revisions of "May 24, 2006"

From Metadata-Registry
Jump to: navigation, search
Line 10: Line 10:
 
** If we '''don't''' do this, what are our options for continuing to develop the Registry?  
 
** If we '''don't''' do this, what are our options for continuing to develop the Registry?  
 
*** Diane will distribute a spreadsheet suggesting some properties we might register
 
*** Diane will distribute a spreadsheet suggesting some properties we might register
 +
** Aren't we just creating an application profile of an application profile? (for which we'll need repeatability)
  
 
* Review of Issues we might want to bring up with SKOS
 
* Review of Issues we might want to bring up with SKOS
** Our versioning policy? (as discussed in Seattle, but not really written up very well yet)
+
** Our versioning policy? (as discussed in [http://metadataregistry.org/wiki/index.php/F2F_Meeting%2C_4/28/06%2C_Seattle Seattle], but not really written up very well yet)
 +
** Sources of definitions?
 
** Status
 
** Status
 
** What else?
 
** What else?

Revision as of 08:14, 24 May 2006

Agenda and Notes, May 24, 2006

  • Differences between Metadata Schemas and Application Profiles:
    • Metadata Schemas are sets of terms and definitions thereof (like a vocabulary)
    • Application Profiles use terms from schemas, and descriptions of usage, without being able to change definitions or create new terms
  • Review UB meeting progress. Questions:
    • Should we move ahead to specify vocabularies/properties for Metadata Schemas and Application Profiles (using our best guess of UB will come up with)?
    • Should we then register these properties as ours, and prepare to crosswalk to the UB set when that becomes possible? What's the downside of doing this?
    • If we don't do this, what are our options for continuing to develop the Registry?
      • Diane will distribute a spreadsheet suggesting some properties we might register
    • Aren't we just creating an application profile of an application profile? (for which we'll need repeatability)
  • Review of Issues we might want to bring up with SKOS
    • Our versioning policy? (as discussed in Seattle, but not really written up very well yet)
    • Sources of definitions?
    • Status
    • What else?
  • Review Timetables and deliverables for the remainder of the summer