DCMI Usage Board - 2007-06-18 telecon - report
Participants: Tom, Akira, Diane, Stuart, Joe
-- NEW ACTIONS
ACTION 2007-06-18: All to comment between June 18 and
June 29 on http://dublincore.org/usageboardwiki/CollectionsProfileReview
and http://dublincore.org/usageboardwiki/CollectionsProfileReviewTb --
goal is to add bullet points under "Comments" summarizing issues arising
during UB review.
ACTION 2007-06-18: Tom to re-circulate discussion materials on the
future of the Usage Board.
ACTION 2007-06-18: Diane to circulate a link to OLAC Application Profile.
Diane and Stuart to investigate preliminary review of Education profile.
-- Review of Collections profile (Andrew)
Compare to:
-- http://dublincore.org/usageboardwiki/CollectionsProfileReviewNotes
ACTION 2007-06-08: Andrew to lead discussion
of Collections Application Profile review draft
http://dublincore.org/usageboardwiki/CollectionsProfileReview
for discussion on the next telecon.
-- Application profile review generally
Revise http://dublincore.org/usageboardwiki/ProfileReviewCriteria ?
In light of: http://dublincore.org/usageboardwiki/CollectionsProfileReviewNotes
ACTION 2007-06-08: Joe to edit ProfileReviewCriteria.
-- Changes to terms of the DCTERMS namespace
-- decisions taken in Barcelona (= changes to be reflected in proposal)
http://dublincore.org/usageboardwiki/DCTermsChangesActions
-- proposal to be prepared for Public Comment, 2-30 July (Tom)
http://dublincore.org/usageboardwiki/DCTermsChanges
ACTION 2007-06-08: Diane to shepherd discussion of this in Singapore.
-- SES and VES clarification
http://dublincore.org/usage/meetings/2007/03/barcelona/Encoding-schemes.txt
AGREED: We need a deeper level of description and
differentiation between VES and SES, including definitions.
If you have a something already, how do you tell if it is
VES or SES. If an Encoding Scheme tells you what a value
string it it's a SES. If Encoding Scheme defines a class
of values, then it is a VES (e.g., concepts). For example,
if you develop a list of educational levels, and if you
define a list of strings, then you're defining an SES.
If you define a set of concepts and assign URIs to them (as
best practice), then you're defining a VES. Best practice
in this scenario is to define a set of concepts with URIs
rather than a set of strings. Agreed that DC-Education
is a great test-bed for these concepts. SES is a datatype
in RDF. VES is like conceptScheme in SKOS, only not limited
to concepts. For discussion: VES is a set of concepts that,
once in metadata, allows editors to handle assertion by
adding things to it. SES is a set of strings.
ACTION 2007-03-17: Stuart and Joe to write a one-page
explanation differentiating VES and SES, vet with Pete
Johnston, and consider revisions to the Term Decision Tree:
http://dublincore.org/architecturewiki/TermDecisionTree.
(Note: the difference is basically String vs. Thing.)
ACTION 2007-03-17: Joe will draft a document discussing
issues related to principles and purpose of UB decision-making.
Joe will work with Stuart on this (2007-06-08).
-- Domains and ranges
Proposal: http://dublincore.org/documents/2007/02/05/domain-range/
ACTION 2007-03-17: Domains and Ranges
vocabulary to be finalized for Public Comment.
Barcelona decisions are described in
http://dublincore.org/usageboardwiki/DomainsActions
ACTION 2007-03-17: (for lack of volunteers, by default
Tom): write a proposal capturing the issue of string,
unspecified, and thing for the problematic DCTERMS
properties (title and its subproperties, date and its
subproperties, and description and its subproperties).
Taking the following position:
1. Title and its subproperties as literals [check notes]
2. Date and its subproperties as literals
3. Description and its subproperties as range = rdfs:resource
Then send this proposal out for public comment. There
are two audiences for this comment: (1) multiple script
communities and (2) SW community asking: best practice for
unspecified ranges. Note that we will use the non-literal
resource in all cases where the domain of our properities
is listed as rdfs:resource (in the proposal).
ACTION 2007-03-18: Diane to define language - see
http://dublincore.org/usageboardwiki/DomainsActions
ACTION 2007-03-18: Andy to add a new class of non-literal
resource to the wiki, use as domain and range as
appropriate.
-- Process
http://dublincore.org/usage/documents/process/
http://dublincore.org/usage/meetings/2007/03/barcelona/Process_Doc_Revisions.txt
ACTION 2007-06-08: Tom to fold revisions into document and
forward to Makx.
-- Future of Usage Board
-- Singapore agenda
-- DCTERMS changes - finalization after July public comment
-- Domains and ranges - finalization after July public comment?
-- VES and SES
-- Application profile review?
-- Process?
-- Legacy documentation dependent on model
Revisions to RDF schemas in light of DCAM - a Usage Board issue?
ACTION 2006-10-01: Tom to replace the Principles
document at http://dublincore.org/usage/documents/principles/
with a page that copies the definitions of elements etc from
DCAM and includes a short text stating: that the document which
used to live here has been superseded by the DCAM. Update UB
page to say we do things in light of the DCAM.
ACTION 2006-10-01: Tom to look through DCMI site
and note those pages where a reference to the principles
document needs to be changed to a reference to the DCAM
as appropriate.
ACTION 2007-03-17: Tom to write a paragraph
about placing undeclared legacy DCTERMS classes
(SubjectScheme, etc, p.64) into historical context -
http://dublincore.org/usage/meetings/2007/03/barcelona/SubjectScheme.txt
-- Next telecons - how many do we need?
Mon Jun 18 - finalize Collections profile review
Fri Jun 29 - prepare public comment
Fri Jul 6
Time: 0600 Seattle
0900 New York
1300 UTC
1400 London
1500 Berlin
2200 Tokyo
2300 Sydney
Target: finalize meeting packet by August 17 (one
week before Singapore meeting).
---
Dialing instructions
(http://dublincore.org/usageboardwiki/DialingInstructions):
1) Dial: local country number
-- UK 0800-032-0634
-- Germany 0800-181-2311
-- Australia 1800-006-458
-- Sweden 020-792-635
-- Japan 00531-13-0842 "KDD Only"
-- US skip this step...
2) You hear: "Welcome... Please enter your 10-digit..."
Type: 888-448-7101#
3) You hear: "Please enter..."
Type: 764-6081#