innovation in metadata design, implementation & best practices

Title: Other business
Created: 2006-09-22

Term - the See: reference

-- Is
   Should be:

-- Decided in Seattle but fell through the cracks.

-- Documentation question - Change note ? ?

Obsolete Principles document
   Note: this document is used in
   as the base URI for "Type of Term", e.g.:

-- Tom proposes to replace this document with a shorter document

   -- One paragraph of context about DCAM
   -- Definitions for Element, etc, copied from DCAM

-- Longer-term solution to URIs for Type of Term?

MARC Relator terms
-- Endorsement of LoC assertions - in RDF?
-- Resolvability of

Issues related to dc:date


Changes to terms in the DCTERMS namespace

    As decided on 2006-02-23, Tom split off changes to terms of
    the DCTERMS namespace into a separate document and placed it
    in the Wiki [1]. Additional errata and unfinished business
    with regard to DCTERMS terms have since been added by Tom
    (DDC, alternative) and Diane (date refinements).

    ACTION 2006-04-30: Tom to go through DCTERMS to
    normalize their style -- e.g. spelling consistency --
    organisation/organization (to prefer the latter).

    PROPOSAL 2006-09-21: Tom thinks that need for these changes
    has been known for a long time but is not urgent enough
    to justify an extra build of the terms documentation.
    The proposal is to finalize any remaining changes out for
    Public Comment along with the assignments of domains and
    ranges in 2007 and finalize them at the same time.

        -- snapshot of:

    Term: ALTERNATIVE TITLE (decided in Seattle, added to Wiki document)

        Potential problem with the comment to alternative title --
        it seems odd, but not necessarily wrong. It seems like
        it is addressing a question and is not as consistent
        with other comments.

        There are: (a) parallel titles, and (b) translated
        titles. Is Alternative Title used for primary-ness or
        secondary-ness? The intention was to allow a distinction
        between primary and secondary titles (the secondary title
        is there for access purposes).


            Proposed definition:
            An alternative name for the resource

            Proposed comment:
            The distinction between titles and alternative titles
            is application-specific.

Alternative paths to semantic specificity (discussed in Seattle, 2006-04-30)

    Is it better to use one broader property and specify its
    values with vocabulary encoding schemes? Or to use multiple,
    semantically more specific properties? Is it good practice to
    use a broad property but restrict the scope of its application
    by annotating the definition accordingly in an Application