Andy:
I think you're right on this. I've noted that some people setting up
APs have a tendency to change the wording in definitions from
"resource" to "something-else-that-they're-interested-in" which has
the effect of restricting the definition. I've tried to convince the
ones I've worked with to leave the defs as is and add a comment that
accomplishes essentially the same thing.
Diane
> >
>> 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
|