On Mon, Mar 13, 2006 at 03:50:13PM -0000, Andy Powell wrote:
> > 3. Use a broad property but restrict its definition, domain,
> > range, or use in an application profile.
>
> 3 is an area where we need to be careful. I don't think we should ever
> talk about restricting a property definition as part of an application
> profile. We can talk about annotating the wording of the definition to
> make its usage clearer in the context of an application - but we should
> not talk about changing the definition.
>
> Essentially, we should think of an application profile as adding an
> additional application-specific comment.
If the definitions are owned by DCMI, then arguably, nobody can
really "change the definition" (except DCMI). But "annotation"
is what I meant so I'm happy to refer to it only as annotation
if we think this will avoid confusion.
"Use a broad property but restrict the semantic scope of
its application in a particular context by annotating its
definition in an application profile." Is that better?
Tom
--
Dr. Thomas Baker [log in to unmask]
Director, Specifications and Documentation
Dublin Core Metadata Initiative
|