In Thursday's telecon I propose we focus on the
dc-architecture-related issues:
-- DCMI property domains and ranges
-- Vocabulary of Domain and Range Classes
-- Finalizing DCMI Type Vocabulary - this relates to a
vocabulary of domain and range classes because we would
want to be consistent between the two in the style of
definitions
-- Replicating ELEMENTS1.1 terms in the DCTERMS namespace
Andy, okay with you?
Tom
----
Version: Tue Mar 21 08:13:52 WEST 2006
HTML version: http://stage.dublincore.org/usageboard/log/.html/2006-03-23.ub-telecon-agenda.txt.html
Usage Board telecon - Draft agenda
2006-03-23 Thu 1400 UTC (1500 Berlin, 0600 Seattle, 2300 Tokyo)
See dialing instructions below
For IRC, type "/join #UB" on the chat line at:
-- irc://irc.ukoln.ac.uk/ or
-- http://dev.ukoln.ac.uk/irc
Regrets: Andrew
Recent telecons
2006-01-26 http://stage.dublincore.org/usageboard/log/.html/2006-01-26.ub-telecon-agenda.txt.html
2006-01-26 http://stage.dublincore.org/usageboard/log/.html/2006-01-26.ub-telecon-report.txt.html
2006-02-09 http://stage.dublincore.org/usageboard/log/.html/2006-02-09.ub-telecon-agenda.txt.html
2006-02-09 http://stage.dublincore.org/usageboard/log/.html/2006-02-09.ub-telecon-report.txt.html
2006-02-23 http://stage.dublincore.org/usageboard/log/.html/2006-02-23.ub-telecon-agenda.txt.html
2006-02-23 http://stage.dublincore.org/usageboard/log/.html/2006-02-23.ub-telecon-report.txt.html
2006-03-16 http://stage.dublincore.org/usageboard/log/.html/2006-03-16.ub-telecon-agenda.txt.html
2006-03-16 http://stage.dublincore.org/usageboard/log/.html/2006-03-16.ub-telecon-report.txt.html
HOT ISSUES
-- DCMI property domains and ranges (Andy)
http://dublincore.org/architecturewiki/DCPropertyDomainsRanges
2006-03-13. Andy has been working on this and proposes
that we put it on the agenda for Seattle.
-- Vocabulary of Domain and Range Classes (Andy)
http://dublincore.org/architecturewiki/DCPropertyDomainsRanges
2006-03-13. Andy's DCPropertyDomainsRanges draft (see above)
uses 30-40 "possible classes" as proposed domains and ranges
for all DCMI properties. For the domains and ranges to be
declared machine-readably, these classes would presumably
need to be defined, approved, given URIs, and maintained.
Giving them URIs would involve either expanding the DCMI
Type Vocabulary or creating a new Vocabulary. Creating a
new Vocabulary would involve revising the DCMI Namespace
Policy. Giving them definitions would presumably also
involve deciding on a style for definitions that is
consistent between the DCMI Type Vocabulary and this new
Domain-Range Vocabulary:
-- Current DCMI Type Style: "A service is a system that provides..."
-- DCMI Type Style, Renaud style: "A resource which is a system..." [2]
-- Domain-Range Vocabulary style: "The class of all services..." [1]
-- Finalizing DCMI Type Vocabulary after the comment period (Stuart)
2006-03-13. A public comment
period was held from 8 Dec to 31 Jan on
http://dublincore.org/usage/public-comment/2005/12/type-vocabulary-changes/.
The responses have been summarized in
http://stage.dublincore.org/usage/public-comment/2006/03/type-vocabulary-comments/.
-- Replicating ELEMENTS1.1 terms in the DCTERMS namespace (Tom, Andy)
On Tue, Jan 03, 2006 at 05:10:24PM -0000, Andy Powell wrote:
> http://dublincore.org/architecturewiki/NamespacePolicy
>
> During the Architecture WG f2f meeting in Madrid, we discussed the
> possibility of adding the 15 DCMES terms to the DCTERMS namespace (in
> addition to them being in the existing DCMES namespace). This would
> mean that many DC users would only need to use a single DCTERMS
> namespace. However, as far as I recall, there was no clear agreement
> about whether this should be done or not.
>
> Such a change, if we decided in favour of making it, would require
> further changes to the namespace policy.
-- 2006-03-21. Tom wonders if there are any documents
summarizing reasons pro and con. One possibility from a
process point of view would be for Architecture to ask
UB to take this on, and we could put it on the agenda for
Seattle.
SIMMERING ISSUES
-- Changes to terms in the ELEMENTS1.1 namespace (Andrew)
http://stage.dublincore.org/usageboard/2006/2006-01.definitions/term-changes/
2006-03-16. The background for this issue is that
documentation of any (and all) changes to the original
fifteen elements needs to be done on a priority basis
in order to prepare for a potential NISO review later
this year.
ACTION 2006-03-16 Andrew: Wordsmith justifications
for the proposed changes, also on a per-element basis
(sections marked "@@@TODO"), with particular attention to
"content of the resource".
ACTION 2006-03-16 Andrew: Suggest a comment for
dc:language along these lines ("Use an encoding
scheme...") and post to dc-usage for discussion.
-- Diane proposes to use some Seattle meeting time for a very
quick demo of the NSDL registry
ACTION 2006-03-16 Diane: Post to dc-usage proposing a demo
of NSDL registry for Seattle UB meeting - brief description,
rationale for using meeting time, time required.
-- Review of application profiles - documentation (Tom)
http://dublincore.org/usage/meetings/2005/09/profile-review/
ACTION 2006-01-26: Tom to propose draft "suite" for discussion - which
parts are "appendices", which are stand-alone, etc.
-- Review of application profiles - profiles
-- Simple Dublin Core
ACTION 2006-01-26: Tom to prepare for discussion in Seattle
-- Collection Description - will not be ready for Seattle - planned for Mexico, see:
http://dublincore.org/groups/collections/
http://homes.ukoln.ac.uk/~lispj/dc-cd/rep200602.html
-- Agents: will be ready by Mexico
http://dublincore.org/groups/agents/
-- Libraries
http://dublincore.org/groups/libraries/
-- DCMI Documentation Roadmap (Tom)
ACTION 2006-01-26: Tom to make available for discussion at mid-year meeting
ACTION 2006-02-09: DCMI Recommendations are taken to be "recommended by DCMI".
Is this the right message, and does it hamper progress? Time for a re-think?
Tom to consider in context of Roadmap - everyone to provide suggestions.
-- DCMI position paper for RDA review
http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0602&L=dc-usage&P=2056
http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0602&L=dc-general&P=769
-- Wikipedia article on Dublin Core (Diane)
http://en.wikipedia.org/wiki/Dublin_Core
ACTION 2006-02-23: Diane to work on Wikipedia article; put on agenda for Seattle.
UPDATE 2006-03-20: Diane asks us to take a look at what's there now.
-- Revised process document (Stuart and Diane)
http://dublincore.org/usage/documents/process/
2006-03-13. Stuart and Diane to lead discussion in Seattle
(30 minutes?). One issue: UB voting procedure.
-- Preparation for UB mid-year meeting, Seattle, Apr 29-30 (Stuart)
Stuart to report on local arrangements, http://www.watertownseattle.com/
2006-03-13. Everyone should be purchasing their tickets now
and confirming your dates of arrival/departure with Stuart.
-- Finalizing the revised DCSV specifications (Tom)
2006-03-16. After the end of the comment period
[1], everyone present on the call approves the
post-comment-period changes made by Tom -- specifically,
the three last paragraphs of the Introduction (starting
with "As of 2006") and the entire Section 3 ("DCSV syntax
encoding schemes") [2].
Unless Andy or Stuart have further comments, Tom
will prepare the revised documents for publication and
announcement with the April 10 Web build. This time, the
revised specs will replace both the 2006 comment-period
version and the 2000 legacy specs as documents with the
status DCMI Recommendation.
[1] http://dublincore.org/news/communications/public-comment.shtml
[2] http://stage.dublincore.org/usageboard/2006/2006-02.dcsv/2006-04-10.dcmi-dcsv.shtml
-- Changes to terms in the DCTERMS namespace (Diane)
http://dublincore.org/usageboardwiki/TermChanges
2006-03-13. As decided on 2006-02-23, Tom split off any
changes to terms in the DCTERMS namespace into a separate
document and placed it in the Wiki. Obviously, this
document needs to be re-formatted; Tom asks for suggestions
on how to do this efficiently.
ACTION 2006-02-23: Diane to consider changes to Date
refinements and other terms in the DCTERMS namespace.
2006-03-13. Note:
-- Added changed "See:" reference for dcterms:URI
-- Added changed label for dcterms:alternative
-- Someone should check for spelling consistency:
organisation/organization (prefer the latter).
-- dcterms:educationLevel needs a better definition, see
http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0503&L=DC-USAGE&P=5380
BACK BURNER
-- Issues related to dc:date
-- Accessibility application profile
-- dcam-text syntax-neutral notation
http://www.ukoln.ac.uk/metadata/dcmi/dc-text/
-- Wiki versus Subversion for UB document management
-- DCAM Text - http://www.ukoln.ac.uk/metadata/dcmi/dcam-text/2006-01-13/
----------------------------------------------------------------------
Scheduled UB Telecons (see also http://www.worldtimeserver.com/)
2006-03-23 Thu 1400 UTC = 1500 Berlin = 0600 Seattle = 2300 Tokyo
2006-03-30 Thu 1400 UTC = 1600 BERLIN = 0600 Seattle = 2300 Tokyo
----------------------------------------------------------------------
Dialing instructions
1) Dial: local country number (http://www.sprintbiz.com/intlaudio)
-- Germany 0800-181-2311
-- UK 0800-032-0634
-- Japan 00531-13-0842 "KDD Only"
-- US 888-448-7101
-- US 888-448-7101
2) Outside the US, you hear: "Welcome... Please enter your 10-digit..."
Type: 888-448-7101#
3) You hear: "Please enter..."
Type: 764-6081#
----------------------------------------------------------------------
IRC: Note that port 6667 needs to be open between your client and
the server. Your firewall may need to be opened slightly and/or
port-blocking settings in your virus/security tool may need to be
changed. You can always re-set your nickname with "/nick YourName".
--
Dr. Thomas Baker [log in to unmask]
Director, Specifications and Documentation
Dublin Core Metadata Initiative
|
