Difference between revisions of "F2F Meeting, 4/28/06, Seattle"

From Metadata-Registry
Jump to: navigation, search
Line 8: Line 8:
 
2. General open questions and issues:
 
2. General open questions and issues:
  
* How do we deal with the Super Properties?  For instance, do we allow people to add things labelled as "Notes" or do we require them to choose among the subproperties (definition, changeNote, etc.)
+
* How do we deal with the Super Properties?  For instance, do we allow people to add things labelled as "Notes" or do we require them to choose among the subproperties (definition, changeNote, etc.) This is also an issue with imported files.
 
* Is historyNote a good place to put term sources, such as we've defined in the NSDL Learning Resource Type vocabulary?  We're thinking that the use of skos:inScheme should wait until we do term mapping.
 
* Is historyNote a good place to put term sources, such as we've defined in the NSDL Learning Resource Type vocabulary?  We're thinking that the use of skos:inScheme should wait until we do term mapping.
 
* In the NSDL vocabularies, we've listed the sources of definitions but there's no place to put those in skos.  We're thinking it might be a something we should propose?
 
* In the NSDL vocabularies, we've listed the sources of definitions but there's no place to put those in skos.  We're thinking it might be a something we should propose?
Line 15: Line 15:
  
 
* Melanie's paper on Versioning
 
* Melanie's paper on Versioning
* Differences between "history" and "version" and how this translates into user services
+
* Differences between "history" and "version" and how this translates into user services. How much will versioning be automated? How much will we rely on snapshots? Will there need to be a distinction between automated snapshots and "intentional" versions? If so, how will we reflect those differences?
 
* Representing both history and version in the user interface
 
* Representing both history and version in the user interface
  
4. Joe's role with the project (should he choose to have one!)
+
4. Joe's role with the project (should he choose to have one!) Possible focus on identified gaps and issues with SKOS?
  
 
5. Technical Issues:
 
5. Technical Issues:
Line 24: Line 24:
 
* The URI issue: Should we use our own domain or purl.org?
 
* The URI issue: Should we use our own domain or purl.org?
 
* The hash/slash issue (Jon)
 
* The hash/slash issue (Jon)
 +
* Do we need to include all the SKOS properties in this release?  Not sure we understand how all of them would be used! This relates to some extent to the superproperties but there are also some subproperties we have questions about. (Diane will distribute a spreadsheet which specifies some areas of concern.)

Revision as of 06:42, 19 April 2006

Registry Project Meeting, Seattle, 4/28/06

1. Review of current work and progress

  • Infrastructure, interfaces, data, testing
  • Plans for demo to DC UB

2. General open questions and issues:

  • How do we deal with the Super Properties? For instance, do we allow people to add things labelled as "Notes" or do we require them to choose among the subproperties (definition, changeNote, etc.) This is also an issue with imported files.
  • Is historyNote a good place to put term sources, such as we've defined in the NSDL Learning Resource Type vocabulary? We're thinking that the use of skos:inScheme should wait until we do term mapping.
  • In the NSDL vocabularies, we've listed the sources of definitions but there's no place to put those in skos. We're thinking it might be a something we should propose?

3. Versioning issues:

  • Melanie's paper on Versioning
  • Differences between "history" and "version" and how this translates into user services. How much will versioning be automated? How much will we rely on snapshots? Will there need to be a distinction between automated snapshots and "intentional" versions? If so, how will we reflect those differences?
  • Representing both history and version in the user interface

4. Joe's role with the project (should he choose to have one!) Possible focus on identified gaps and issues with SKOS?

5. Technical Issues:

  • The URI issue: Should we use our own domain or purl.org?
  • The hash/slash issue (Jon)
  • Do we need to include all the SKOS properties in this release? Not sure we understand how all of them would be used! This relates to some extent to the superproperties but there are also some subproperties we have questions about. (Diane will distribute a spreadsheet which specifies some areas of concern.)