DCMI Usage Board - 2007-06-29 telecon - agenda

Expected: Tom, Akira, Diane, Stuart, Joe, Andrew

Dialing instructions below.
Time: 0600 Seattle
      0900 New York
      1300 UTC
      1400 London
      1500 Berlin
      2200 Tokyo
      2300 Sydney

-- Changes to terms of the DCTERMS namespace

   "Revisions to DCMI Metadata Terms" will be published for Public 
   Comment on Monday, 2 July, so we need to finalize it on the telecon.
   The sources of the document are:

   -- Barcelona decisions [1] - see the proposal discussed meeting packet [3]
   -- My summary of changes made to the proposal discussed [4]
   -- Changes made between DCTERMS-2006 [6] and NISO Z39-85-2007 [5]

   [1] http://dublincore.org/usageboardwiki/DCTermsChangesActions
   [2] http://stage.dublincore.org/usage/public-comment/2007/07/dcterms-changes/index.shtml
   [3] http://dublincore.org/usage/meetings/2007/03/barcelona/2007-03-16.ub-agenda-barcelona.pdf
   [4] http://dublincore.org/usageboardwiki/DCTermsChangesActionsDone
   [5] http://www.niso.org/standards/resources/Z39-85-2007.pdf
   [6] http://dublincore.org/documents/dcmi-terms/

   ACTION 2007-06-08: Diane to shepherd discussion of this in Singapore.

   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
   -- DONE: see http://stage.dublincore.org/usage/public-comment/2007/07/dcterms-changes/#subjectscheme
                http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0706&L=dc-usage&P=1191

-- Domains and ranges

   The Domain Vocabulary [1] has been revised in light of
   Barcelona decisions [2].  In the telecon, we need to finalize
   it for Public Comment starting Monday, 2 July.

   Note: dcterms:identifier is being proposed with a range of
   rdfs:Literal.

   [1] http://stage.dublincore.org/documents/2007/07/02/domain-range/
   [2] http://dublincore.org/usageboardwiki/DomainsActions
   [3] http://stage.dublincore.org/documents/2007/07/02/domain-range/#dctermsidentifier

   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: 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.

-- Review of Collections profile (Andrew)

   Compare to:
   -- http://dublincore.org/usageboardwiki/CollectionsProfileReviewNotes

   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.

-- Future of Usage Board

   Tom recirculated the discussion materials on June 18 [1,2].

   [1] http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0706&L=dc-usage-bc&P=333
   [2] http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0706&L=dc-usage-bc&P=443

-- Application profile review criteria

   Revise http://dublincore.org/usageboardwiki/ProfileReviewCriteria ?
   In light of: http://dublincore.org/usageboardwiki/CollectionsProfileReviewNotes

   ACTION 2007-06-08: Joe to edit ProfileReviewCriteria.
   
   ACTION 2007-03-17: Stuart and Joe revise Term Decision Tree:
   http://dublincore.org/architecturewiki/TermDecisionTree.
   (Note: the difference is basically String vs. Thing.)

   ACTION 2007-03-17: Joe to draft a document discussing
   issues related to principles and purpose of UB decision-making.
   (The context was the decision to define ISO639-2 as a set of codes.)
   Joe will work with Stuart on this (2007-06-08).

-- 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

-- 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.
   -- DONE 2007-06-18: http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0706&L=dc-usage-bc&P=140

-- Singapore agenda
   -- DCTERMS changes - finalization after July public comment
   -- Domains and ranges - finalization after July public comment?
   -- VES and SES
   -- Application profile review?
      -- Simple Dublin Core profile
   -- Process?

   ACTION 2007-06-18: Diane to circulate a link to OLAC Application Profile.
   Diane and Stuart to investigate preliminary review of Education profile.

-- Legacy documentation dependent on model

   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.

-- Revisions to RDF schemas in light of DCAM

-- Structure of DCMI Metadata Terms document

   The document DCMI Metadata Terms 
   (http://dublincore.org/documents/dcmi-terms/) needs to
   be restructured in light of DCAM changes.  See proposed
   outline at
   http://dublincore.org/usageboardwiki/DcmiTermsOutline.

-- Next telecons

   Fri Jun 29
   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#