Difference between revisions of "Dec. 7, 2005"

From Metadata-Registry
Jump to: navigation, search
Line 3: Line 3:
 
== Agenda==
 
== Agenda==
  
#Data model for agents
+
1. Data model for agents
 
#*See Jon and Diane's first whack at elements
 
#*See Jon and Diane's first whack at elements
 
#*Note 'agent' attributes here http://info-uri.info/registry/register.html
 
#*Note 'agent' attributes here http://info-uri.info/registry/register.html
Line 11: Line 11:
 
'''Action item:''' Diane will add descriptive information for each element and URIs.
 
'''Action item:''' Diane will add descriptive information for each element and URIs.
  
#Elements for top-level vocabulary (vocabulary description) registration
+
2. Elements for top-level vocabulary (vocabulary description) registration
  
We will need a namespace for the top-level vocabulary terms. Need to determine whether and how we version the top level vocabulary description itself.  We may need use cases around this: change in URI or change in maintenance agency.
+
We will need a namespace for the top-level vocabulary terms. Need to determine whether and how we version the top level vocabulary description itself.  We may need use cases around this: change in URI or change in maintenance agency at the vocabulary description level.
  
#Review functional requirements on search (External User Interactions) to clarify distinctions between "search" and "browse"
+
3. Review functional requirements on search (External User Interactions) to clarify distinctions between "search" and "browse"
#Establish a short-term process for reviewing/modifying current functional specification
+
 
 +
4. Establish a short-term process for reviewing/modifying current functional specification
  
 
Stuart would like to develop a process for reviewing the requirements on successive calls.  He will begin by annotating some of the pieces.
 
Stuart would like to develop a process for reviewing the requirements on successive calls.  He will begin by annotating some of the pieces.
  
#Discuss use of CMFMember
+
5. Discuss use of CMFMember
#Discuss December milestone #3
+
6. Discuss December milestone #3
  
 
== NOTES:==
 
== NOTES:==
  
 
Ryan and Stuart have been adding some Plone Product information on the page with functional requirements.
 
Ryan and Stuart have been adding some Plone Product information on the page with functional requirements.

Revision as of 13:13, 8 December 2005

Telecon Dec. 7, 2005

Agenda

1. Data model for agents

Action item: Diane & Jon will look again at foaf--apparently some stuff was missed. foaf doesn't do regular addresses, should use vCard or info-uri organisation-address.

Action item: Diane will add descriptive information for each element and URIs.

2. Elements for top-level vocabulary (vocabulary description) registration

We will need a namespace for the top-level vocabulary terms. Need to determine whether and how we version the top level vocabulary description itself. We may need use cases around this: change in URI or change in maintenance agency at the vocabulary description level.

3. Review functional requirements on search (External User Interactions) to clarify distinctions between "search" and "browse"

4. Establish a short-term process for reviewing/modifying current functional specification

Stuart would like to develop a process for reviewing the requirements on successive calls. He will begin by annotating some of the pieces.

5. Discuss use of CMFMember 6. Discuss December milestone #3

NOTES:

Ryan and Stuart have been adding some Plone Product information on the page with functional requirements.