Re: ? best practice about extending motivations

I think the question is about best practices on publishing SKOS
ConceptSchemes? Antoine, and all, is there something we can point to in
this regard from the spec appendix?

Personally, I don't think there's a need to include all of the information
in every annotation, but it might be valuable to include the link to the
ConceptScheme so it can be dereferenced if that's desirable.

Rob


On Thu, Apr 11, 2013 at 12:02 PM, Bob Morris <morris.bob@gmail.com> wrote:

> I'm finding a need for what appear to be somewhat annotation specific
> motivations, typically more specific than one of the standard ones or
> a few application-specific motivations.  Typically these are
> text-based and not reusable, so the solution seems to add a local one,
> e.g.:
>
> =============================
> ex:anno a oa:Annotation;
>   oa:motivatedBy oa:editing;
>   oa:motivatedBy ex:myMotivation;
>   ....
>
> ex:myMotivation a oa:Motivation;
>   skos:inScheme ex:myScheme;
>   skos:prefLabel "Integrate data found on the lab spreadsheet into the
> database."
>
> ...
>
> ex:myScheme ....
> =============================
>
> Somehow having a skos concept and scheme local to the annotation seems
> very un-skos-like, but I don't see what else to do.
>
> Bob
>
>
>
>
>
> --
> Robert A. Morris
>
> Emeritus Professor  of Computer Science
> UMASS-Boston
> 100 Morrissey Blvd
> Boston, MA 02125-3390
>
> IT Staff
> Filtered Push Project
> Harvard University Herbaria
> Harvard University
>
> email: morris.bob@gmail.com
> web: http://efg.cs.umb.edu/
> web: http://wiki.filteredpush.org
> http://www.cs.umb.edu/~ram
> ===
> The content of this communication is made entirely on my
> own behalf and in no way should be deemed to express
> official positions of The University of Massachusetts at Boston or
> Harvard University.
>
>