DCMI Usage Board - telecon - report
Date: Fri, 2007-04-27 1300 UTC
1. The element Coverage is defined as "The spatial or temporal
topic of the resource...", then the comment says:
Spatial topic and spatial applicability may be a
named place or a location specified by its geographic
coordinates. Temporal period may be a named period, date,
or date range.
The second sentence is clearly meant to parallel the first.
This obvious mistake (once pointed out) has gone unnoticed
by UB reviewers and in Public Comment since 2005.
RESOLVED (on telecon): Change sentence
Temporal period may be a named period, date, or date range.
to read:
Temporal topic may be a named period, date, or date range.
ACTION 2007-04-27: Tom to communicate change to NISO and
make change in DCMI documentation.
2. ACTION 2007-04-27: All to comment on Makx's proposal for
DCMI process -- see April 15 dc-usage-bc posting [1].
3. ACTION 2007-04-27: All to comment on Future of Usage Board
issues [2]. In particular, please suggest criteria
("profiles" :-) for the membership mix of the Usage Board.
4. ACTION 2007-04-27: All to send Tom a) arrival and departure
dates in Singapore; b) airfare estimates.
5. Collections Application Profile - to be finalized on May 18
telecon. Ongoing action on Andrew to draft review result.
6. Domains and Ranges vocabulary - Plan to finalize in May for
Public Comment. Tom has action to draft Usage Board position
on ranges for date, description, title for Public Comment.
7. Next telecon: Friday, 18 May, same time (1300 UTC). Tom to
liaise beforehand with Diane, who will be on break. Tom will
send around summary of other outstanding Barcelona actions
in preparation.
[1] http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0704&L=dc-usage-bc&P=276
[2] http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0703&L=dc-usage-bc&P=1679
--
Dr. Thomas Baker <tbaker@tbaker.de>
Director, Specifications and Documentation
Dublin Core Metadata Initiative
From TBaker Sat Apr 28 10:38:49 2007
Received: from vsmtpgwdexc.exc.top.gwdg.de ([134.76.26.171]) by vs1.exc.top.gwdg.de with Microsoft SMTPSVC(6.0.3790.1830);
Sat, 28 Apr 2007 10:18:02 +0200
Received: from mx.gwdg.de ([134.76.10.20]) by vsmtpgwdexc.exc.top.gwdg.de with Microsoft SMTPSVC(6.0.3790.1830);
Sat, 28 Apr 2007 10:18:02 +0200
Received: from moutng.kundenserver.de ([212.227.126.187])
by mx.gwdg.de with esmtp (Exim 4.66)
(envelope-from <SRS0=AYg+=J7=JISCMAIL.AC.UK=owner-dc-usage@srs.kundenserver.de>)
id 1Hhi82-0007Z7-8O
for tbaker@gwdg.de; Sat, 28 Apr 2007 10:18:03 +0200
Received-SPF: pass (mxeu9: domain of JISCMAIL.AC.UK designates 130.246.192.56 as permitted sender) client-ip=130.246.192.56; envelope-from=owner-dc-usage@JISCMAIL.AC.UK; helo=ictmailer1.itd.rl.ac.uk;
Received: from [130.246.192.56] (helo=ictmailer1.itd.rl.ac.uk)
by mx.kundenserver.de (node=mxeu9) with ESMTP (Nemesis),
id 0MKt64-1Hhi8142HB-0001Qt for tbaker@TBAKER.DE; Sat, 28 Apr 2007 10:18:02 +0200
Received: from LISTSERV.JISCMAIL.AC.UK (jiscmail.ac.uk) by ictmailer1.itd.rl.ac.uk (LSMTP for Windows NT v1.1b) with SMTP id <5.00419167@ictmailer1.itd.rl.ac.uk>; Sat, 28 Apr 2007 9:18:01 +0100
Received: by JISCMAIL.AC.UK (LISTSERV-TCP/IP release 14.5) with spool id
96690901 for DC-USAGE@JISCMAIL.AC.UK; Sat, 28 Apr 2007 09:18:01 +0100
Received: from 130.246.193.104 by JISCMAIL.AC.UK (SMTPL release 1.0m) with TCP;
Sat, 28 Apr 2007 09:18:01 +0100
X-RAL-MFrom: <tbaker@tbaker.de>
X-RAL-Connect: <gwdexc-fe2.exc.top.gwdg.de [134.76.26.172]>
Received: from vsmtpgwdexc.exc.top.gwdg.de (gwdexc-fe2.exc.top.gwdg.de
[134.76.26.172]) by bifur.jiscmail.ac.uk (8.13.1/8.13.1) with ESMTP
id l3S8I0sh017366 for <DC-USAGE@JISCMAIL.AC.UK>; Sat, 28 Apr 2007
09:18:01 +0100
Received: from Octavius ([77.177.174.125]) by vsmtpgwdexc.exc.top.gwdg.de with
Microsoft SMTPSVC(6.0.3790.1830); Sat, 28 Apr 2007 10:17:58 +0200
Received: by Octavius (sSMTP sendmail emulation); Sat, 28 Apr 2007 10:19:50
+0200
References: <p06002056c256d24f817a@[192.168.1.100]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.2.1i
X-OriginalArrivalTime: 28 Apr 2007 08:17:58.0174 (UTC)
FILETIME=[BACC4BE0:01C7896D]
X-CCLRC-SPAM-report: 0 :
X-Scanned-By: MIMEDefang 2.57 on 130.246.193.104
Message-ID: <20070428081950.GA2328@Octavius>
Date: Sat, 28 Apr 2007 10:19:50 +0200
Reply-To: A mailing list for the Dublin Core Metadata Initiative's Usage Board <DC-USAGE@JISCMAIL.AC.UK>
Sender: A mailing list for the Dublin Core Metadata Initiative's Usage Board <DC-USAGE@JISCMAIL.AC.UK>
From: Thomas Baker <tbaker@TBAKER.DE>
Subject: Telecon on Friday 2007-04-27 - report
To: DC-USAGE@JISCMAIL.AC.UK
In-Reply-To: <p06002056c256d24f817a@[192.168.1.100]>
Precedence: list
List-Help: <http://jiscmail.ac.uk/cgi-bin/webadmin?LIST=DC-USAGE>;,
<mailto:LISTSERV@JISCMAIL.AC.UK?body=INFO DC-USAGE>
List-Unsubscribe: <mailto:DC-USAGE-unsubscribe-request@JISCMAIL.AC.UK>
List-Subscribe: <mailto:DC-USAGE-subscribe-request@JISCMAIL.AC.UK>
List-Owner: <mailto:DC-USAGE-request@JISCMAIL.AC.UK>
List-Archive: <http://jiscmail.ac.uk/cgi-bin/webadmin?LIST=DC-USAGE>;
X-Spam-Level: /
X-Spam-Report: Content analysis: 0.0 points, 6.0 required
0.0 UNPARSEABLE_RELAY Informational: message has unparseable relay lines
X-Virus-Scanned: (clean) by exiscan+sophie
Return-Path: SRS0=AYg+=J7=JISCMAIL.AC.UK=owner-dc-usage@srs.kundenserver.de
Status: RO
Content-Length: 2289
Lines: 60
> As you've probably heard, Tom (and most of Berlin) is without email
> access, so he asked me to send out a reminder for the call tomorrow
> and include his apologies for not sending out a revised agenda.
DCMI Usage Board - telecon - report
Date: Fri, 2007-04-27 1300 UTC
1. The element Coverage is defined as "The spatial or temporal
topic of the resource...", then the comment says:
Spatial topic and spatial applicability may be a
named place or a location specified by its geographic
coordinates. Temporal period may be a named period, date,
or date range.
The second sentence is clearly meant to parallel the first.
This obvious mistake (once pointed out) has gone unnoticed
by UB reviewers and in Public Comment since 2005.
RESOLVED (on telecon): Change sentence
Temporal period may be a named period, date, or date range.
to read:
Temporal topic may be a named period, date, or date range.
ACTION 2007-04-27: Tom to communicate change to NISO and
make change in DCMI documentation.
2. ACTION 2007-04-27: All to comment on Makx's proposal for
DCMI process -- see April 15 dc-usage-bc posting [1].
3. ACTION 2007-04-27: All to comment on Future of Usage Board
issues [2]. In particular, please suggest criteria
("profiles" :-) for the membership mix of the Usage Board.
4. ACTION 2007-04-27: All to send Tom a) arrival and departure
dates in Singapore; b) airfare estimates.
5. Collections Application Profile - to be finalized on May 18
telecon. Ongoing action on Andrew to draft review result.
6. Domains and Ranges vocabulary - Plan to finalize in May for
Public Comment. Tom has action to draft Usage Board position
on ranges for date, description, title for Public Comment.
7. Next telecon: Friday, 18 May, same time (1300 UTC). Tom to
liaise beforehand with Diane, who will be on break. Tom will
send around summary of other outstanding Barcelona actions
in preparation.
[1] http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0704&L=dc-usage-bc&P=276
[2] http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0703&L=dc-usage-bc&P=1679
--
Dr. Thomas Baker <tbaker@tbaker.de>
Director, Specifications and Documentation
Dublin Core Metadata Initiative