Difference between revisions of "Mar. 12, 2007"
From Metadata-Registry
| (3 intermediate revisions by 2 users not shown) | |||
| Line 2: | Line 2: | ||
1. Jon's mockup of the AP Registration process: | 1. Jon's mockup of the AP Registration process: | ||
| − | * URLs: | + | * URLs:<br />Note: whenever you see a dropdown selection, it contains the correct proposed values |
http://beta.metadataregistry.org/schema.html | http://beta.metadataregistry.org/schema.html | ||
http://beta.metadataregistry.org/schema_namespace.html | http://beta.metadataregistry.org/schema_namespace.html | ||
| Line 10: | Line 10: | ||
* Issues: | * Issues: | ||
** In the [http://dublincore.org/groups/collections/collection-ap-summary/2006-08-24/ DC CD-AP], obligations under values are separately recorded, indicating whether URIs or strings are mandatory, fixed, optional or not allowed. Diane thinks this might lead to odd combinations and bad outcomes. For instance, if both URIs and strings are marked mandatory, would people interpret that as requiring repeated statements, one with a string, one with a URI? If that combination ''were'' valid, how would people encode that? The ultimate question is, should the Registry enforce common sense, or allow all combinations? | ** In the [http://dublincore.org/groups/collections/collection-ap-summary/2006-08-24/ DC CD-AP], obligations under values are separately recorded, indicating whether URIs or strings are mandatory, fixed, optional or not allowed. Diane thinks this might lead to odd combinations and bad outcomes. For instance, if both URIs and strings are marked mandatory, would people interpret that as requiring repeated statements, one with a string, one with a URI? If that combination ''were'' valid, how would people encode that? The ultimate question is, should the Registry enforce common sense, or allow all combinations? | ||
| + | https://netfiles.uiuc.edu/sshreeve/www/dcmi/Collection-application-profile/2007-03-09/#coldctype1 | ||
** Order of input screens in the mock-ups is similar to "standard" order that has been used before, but we may want to fiddle. For instance, should "obligation" for the property be higher, to avoid confusion with obligations for values lower down? | ** Order of input screens in the mock-ups is similar to "standard" order that has been used before, but we may want to fiddle. For instance, should "obligation" for the property be higher, to avoid confusion with obligations for values lower down? | ||
| Line 16: | Line 17: | ||
* What else still needs to be done? | * What else still needs to be done? | ||
** Diane has internal paperwork to do, but can't proceed on that until the overhead decision is made and we can finalize budgets | ** Diane has internal paperwork to do, but can't proceed on that until the overhead decision is made and we can finalize budgets | ||
| − | ** We still need figures on how much the CUL evaluation will cost. Elaine | + | ** We still need figures on how much the CUL evaluation will cost. Elaine has promised to have them to me by Wed., which means we should be able to add those to the budget and see where we stand. |
| + | 3. Reply to the query from the Australian Broadcasting System. | ||
| + | * Do we need a licensing decision? | ||
| + | * What should we suggest to them? (and who will do it?) | ||
Latest revision as of 08:16, 12 March 2007
Telecon Agenda and Notes, Mar. 12, 2007
1. Jon's mockup of the AP Registration process:
- URLs:
Note: whenever you see a dropdown selection, it contains the correct proposed values
http://beta.metadataregistry.org/schema.html http://beta.metadataregistry.org/schema_namespace.html http://beta.metadataregistry.org/schema_property.html http://beta.metadataregistry.org/profile.html http://beta.metadataregistry.org/profile_property.html
- Issues:
- In the DC CD-AP, obligations under values are separately recorded, indicating whether URIs or strings are mandatory, fixed, optional or not allowed. Diane thinks this might lead to odd combinations and bad outcomes. For instance, if both URIs and strings are marked mandatory, would people interpret that as requiring repeated statements, one with a string, one with a URI? If that combination were valid, how would people encode that? The ultimate question is, should the Registry enforce common sense, or allow all combinations?
https://netfiles.uiuc.edu/sshreeve/www/dcmi/Collection-application-profile/2007-03-09/#coldctype1
- Order of input screens in the mock-ups is similar to "standard" order that has been used before, but we may want to fiddle. For instance, should "obligation" for the property be higher, to avoid confusion with obligations for values lower down?
2. The proposals:
- Diane reports that there is still no decision from Cornell about overheads, but she was solicited on Friday to write up how the proposals related to the library, which she did. This signifies movement, I hope a decision (the right decision) comes soon. The library management is supporting us fully on this.
- What else still needs to be done?
- Diane has internal paperwork to do, but can't proceed on that until the overhead decision is made and we can finalize budgets
- We still need figures on how much the CUL evaluation will cost. Elaine has promised to have them to me by Wed., which means we should be able to add those to the budget and see where we stand.
3. Reply to the query from the Australian Broadcasting System.
- Do we need a licensing decision?
- What should we suggest to them? (and who will do it?)
