> Andy's posting to dc-accessibility about "where to draw the
> line between using properties and vocabularies" addresses a
> design issue we have acknowledged and discussed several times
> before, but I also do not recall that we ever wrote down or
> even ever articulated the problem more clearly than here.
>
> Maybe it would help to give this issue a handle, like
> "Semantic specificity options". For completeness, those
> options would need to distinguish between term declarations
> and application profiles. The options might look something
> like the following:
>
> 1. Instead of using one broader property, use multiple,
> semantically more specific properties (i.e., declared
> in term declarations).
>
> 2. Use a broad property and specify its values with
> vocabulary encoding schemes (i.e., declared in term
> declarations).
>
> 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.
Andy
--
Head of Development, Eduserv Foundation
http://www.eduserv.org.uk/foundation/
[log in to unmask]
+44 (0)1225 474319
|