2012-01-05. Frozen archive - links may not resolve - see directory of files at MoinMoin wiki archive

> AMPublicCommentApril2007

Report from public comment period on DCMI Abstract Model

Period: 2 April - 30 April 2007

This document summarises the principal comments received during the public comment period on the [WWW]DCMI Abstract Model (Version 2007-04-02) Proposed Recommendation, a revised version of the [WWW]previous Proposed Recommendation (Version 2007-02-05).

Proposals for moving forward are presented in the sections below.

OWL-DL, datatype properties & object properties

OWL-DL will require properties to be declared as either datatype properties & object properties. If both literal and non-literal values are required, then may need two parallel properties.

This is being taken into account by the Usage Board in their consideration of the ranges of DCMI properties

Proposals

References

Specification of which value string is intended for display

If statement has non-literal value surrogate with multiple value strings, how does application decide which string to display?

DCAM doesn't provide this, but can make use of description of value to differentiate "categories" of label e.g. using SKOS preferred/alternative label properties.

Proposals

References

Definition of literal

Provide fuller definition of literal rather than just referencing RDF Concepts.

Proposals

References

Requirement to use URI to reference VES & SES

The DCAM requires that properties, VES & SES are referred to in statements within DC metadata description sets using URIs.

Proposals

References

Distinction between Literal Value Surrogate ad Non-Literal Value Surrogate

Distinction is not based on number of value strings present in statement, but on type of value itself

Proposals

References

Language and Typed Value Strings/XML Literals

Typed literals can not carry language tags.

Proposals

References

dcam:memberOf equivalent in RDF

RDF has no "built-in" equivalent of VES, so no built-in equivalent of dcam:memberOf.

Proposals

References

Definition of "term"

Definition of "term" should be part of bullet list in section 2.3

Proposals

References

Set of resources (VES) v Set of literals (SES)

Not always clear when to use VES v when to use SES. A modelling choice. Depends on requirements of application. Usage Board choices for DCMI terms based on content of existing specifications.

Proposals

References

Description of "subproperty"

Bullet on subproperty in 2.3 should use the phrasing "...and the property is part of a property/value pair" (rather than "...and a described resource is related to a value by that property")

Proposals

References

Error in 2.4

Erroneous reference to "syntax encoding string"

Proposals

References

Abstract Syntax Required

Alistair Miles re-emphasised the points made in the previous comment period (the need to delineate an abstract syntax, to describe how to merge DC description sets, and to describe inference rules). He also suggested the need for use cases to specify the requirements that the DCAM is intended to meet.

Proposals

References

Definition of "vocabulary"

DCAM uses "vocabulary" to refer to set of "terms"; RDF Semantics uses "vocabulary" to refer to set of names (URIs/literals).

Proposals

References