Title:       Summary of Public Comments on DCAM (5 February to 5 March)
Date:        2007-03-31
Creator:     Pete Johnston

See also DUBLINCORE:/architecturewiki/AMChanges
(changes to be made on the basis of 2007 Public Comment)

--  "Abstractness"

    Comment: Jon Mason, 2007-02-06 (1)
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=1318

    Reply: Mikael Nilsson, 2007-02-22
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=8054

    Proposal: Additional "primer"-style documentation may be needed.

    Resolution: No change required to DCAM.

--  Documentation of Changes

    Comment: Jon Mason, 2007-02-06 (2)
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=1318

    Reply: Pete Johnston
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=1420

    Proposal: Announcement of comment period provides details of changes.

    Resolution: No change required to DCAM.

--  "Reference Model"

    Comment: Jon Mason, 2007-02-06 (3, 4)
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=1318

    Reply: Mikael Nilsson, 2007-02-22
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=8403

    Proposal: Use "information model" (as defined by Wikipedia) instead
    of "reference model". DCAM-as-whole = information model, with three
    sub-models (each an information model).

    Resolution: Change DCAM to use "information model" instead of
    "reference model".

--  Described resource

    Comment: Jon Mason, 2007-02-06 (5, 10)
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=1318

    Reply: Pete Johnston, 2007-02-16
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=4935

    Proposal: Change either label "described resource" or definition to
    avoid repetition of "described". Also change "Each described resource
    may be described using one or more property-value pairs" to "Each
    described resource is described using one or more property-value
    pairs"

--  Definition of metadata

    Comment: Jon Mason, 2007-02-06 (6)
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=1318

    Reply: Mikael Nilsson, 2007-02-22
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=8678

    Resolution: No change required to DCAM.

--  Descriptions/Statements

    Comment: Jon Mason, 2007-02-06 (7)
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=1318

    Reply: Pete Johnston, 2007-02-07
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=2190

    Resolution: No change required to DCAM.

--  Values

    Comment: Jon Mason, 2007-02-06 (8, 11)
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=1318

    Reply: Pete Johnston, 2007-02-07
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=2364

    Pete Johnston, 2007-02-16
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=4455

    Resolution: No change required to DCAM.

--  Description model, description set and description

    Comment: Jon Mason, 2007-02-06 (9)
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=1318

    Reply: Pete Johnston, 2007-02-07
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=1989

    Proposal: either:

     * we replace the caption "The DCMI description model"
       with "The DCMI description set model" and we replace
       "The abstract model of DC metadata descriptions" with
       "The abstract model of DC metadata description sets"; or

     * we replace the caption "The DCMI description
       model" with "The DCMI information structure model"
       and we replace "The abstract model of DC metadata
       description sets" with "The abstract model of DC
       information structures" (or some other similar term
       for a generic construct)

--  Multiple URIs per Resource

    Comment: Douglas Campbell, 2007-02-07 (1, 2)
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=1543

    Reply: Pete Johnston, 2007-02-19
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=5108

    Resolution: No change required to DCAM.

--  Rich Representations v Value Strings

    Comment: Douglas Campbell, 2007-02-07 (3)
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=1543

    Reply: Pete Johnston, 2007-02-20
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=5241

    Proposal: Consider adding language tag (but not SES) for rich
    representations

    Resolution: Superceded by proposal to remove rich representation
    from description model?

--  Rich Representations and Value Strings as Resources

    Comment: Douglas Campbell, 2007-02-07 (4)
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=1543

    Reply: Mikael Nilsson, 2007-02-22
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=6422

    Proposal:
    Resolution: No change required to DCAM.

--  Vocabulary Encoding Schemes

    Comment: Douglas Campbell, 2007-02-07 (5)
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=1543

    Reply: Mikael Nilsson, 2007-02-22
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=6611

    Resolution: No change required to DCAM.

--  DCAM and RDF

    Comment: Douglas Campbell, 2007-02-07 (6)
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=1543

    Reply: Mikael Nilsson, 2007-02-22
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=6795

    Resolution: No change required to DCAM.

--  Definition of description set

    Comment: Douglas Campbell, 2007-02-07 (7)
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=1543

    Reply: Pete Johnston, 2007-02-07
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=2521

    Proposal: Change definition of Description Set in glossary to read
    "a set of one or more descriptions, each of which describes a single
    resource".

--  Definitions of has range and has domain

    Comment: Douglas Campbell, 2007-02-07 (8, 9)
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=1543

    Reply: Mikael Nilsson, 2007-02-22
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=6974

    Proposal: Extend definition of "has domain" to include "It may useful
    to think of it as the opposite to "class (of the described resource)
    has property"."

    Change definition of "has range" to "A relationship between a property
    and a class which indicates that when the property is part of a
    property/value pair, the corresponding value is always an instance
    of that class."

    Resolution: Change definitions for has range/has domain

--  Definitions of property/value pair

    Comment: Douglas Campbell, 2007-02-07 (10)
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=1543

    Reply: None

--  Definition of SES

    Comment: Douglas Campbell, 2007-02-07 (11)
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=1543

    Reply: Mikael Nilsson, 2007-02-22
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=6974

    Resolution: No change required to DCAM.

--  Resource URI

    Comment: Douglas Campbell, 2007-02-07 (12)
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=1543

    Reply: Pete Johnston, 2007-02-07
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=2701

    Proposal: Change
    "A description is made up of one or more statements (about one,
    and only one, described resource) and zero or one resource URI
    (a URI that identifies the described resource)."

    to

    "A description is made up of one or more statements (about one, and
    only one, described resource) and zero or one described resource URI
    (a URI that identifies the described resource)."

    Resolution: Change text as proposed.

--  Document Structure

    Comment: Douglas Campbell, 2007-02-07 (13)
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=1543

    Reply: Pete Johnston, 2007-02-07
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=2880

    Proposal: Add sub-headings/sub-sections to Section 2

    Resolution: Add sub-headings/sub-sections as proposed

--  Monotonicity, Sources of Statements etc

    Comment: Pete Johnston, 2007-02-09
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=3236

    Reply: Mikael Nilsson, 2007-02-22
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=8981

    Resolution: No change required to DCAM.

--  Rich Representation in RDF

    Comment: Ivan Herman, 2007-02-13
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=3957

    Reply: Pete Johnston, 2007-02-21
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=5524

    Resolution: No change required to DCAM. Superceded by proposal to
    remove rich representation from description model?

--  Value Representation and Value URI, DCAM and ranges

    Comment: Ivan Herman, 2007-02-13
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=4137

    Reply: Mikael Nilsson, 2007-02-22
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=7911

    (and subsequent messages)

    Resolution: No change required to DCAM. But see also range/OWL-DL
    compatability discussion.

--  Vocabulary Encoding Schemes (Set of resources v set of concepts)

    Comment: Joe Tennis, 2007-02-22
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=7142

    Reply: Multiple replies by Andy, Mikael, Pete

    Resolution: '''Unresolved'''.

--  Abstract Syntax Required

    Comment: Alistair Miles, 2007-02-26
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=10720

    Reply: Mikael Nilsson, 2007-02-26
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=11846

    Proposal: Description model = abstract syntax. Define rules for
    merging description sets, rules for inferencing separately from DCAM.

    Resolution: No change required to DCAM.

--  Indirection (Resources v URIs/References to Resources etc)

    Comment: Thomas Fischer, 2007-02-26
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=12269

    Reply: Mikael Nilsson, 2007-02-26
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=12486

    Resolution: No change required to DCAM.

--  Comparing URIs

    Comment: Thomas Fischer, 2007-02-27
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=12693

    Reply: Mikael Nilsson, 2007-02-27
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=12854

    Proposal: State that DCAM treats URIs in same way as RDF when
    comparing/merging?

    Resolution: Add reference to RDF treatment of URIs?

--  VES and Rich Representations/Lang Tag v language property?

    Comment: Thomas Fischer, 2007-02-27
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=14062

    Reply: Pete Johnston, 2007-02-28
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0702&L=dc-architecture&P=14630

    Resolution: No change required to DCAM.

--  Remove Rich Representations from Description Model

    Comment: Mikael Nilsson, 2007-03-05
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0703&L=dc-architecture&P=491

    Reply: Thomas Fischer, 2007-03-05
    http://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0703&L=dc-architecture&P=814

    Proposal: Remove rich representations from description model, allow
    XML Literals as value strings

    Resolution: Remove rich representations from description model,
    allow XML Literals as value strings.

    Justification: Representing rich representations usefully requires
    describing them as resources in their own rights, with MIME type,
    language, encoding, etc. From the one-to-one principle, it therefore
    follows that they are better treated as separate resources in
    the model, instead of making the part of a single statement. By
    consequence, the construct has been removed.

--  Literals as Values

    Comment: Mikael Nilsson, telecon 2007-03-01

    Proposal: If property has range rdfs:Literal or subclass, then
    description model should restrict statement components available

    Resolution: '''Unresolved'''