- From: Bob Morris <morris.bob@gmail.com>
- Date: Mon, 4 Feb 2013 12:49:29 -0500
- To: public-openannotation <public-openannotation@w3.org>
We have actionable Annotations that are sometimes processed by consuming applications without human intervention. I'm thinking of facilitating the consumer's business logic by modeling authorities with an oa:Motivation. Perhaps something like: <anno1> a oa:Annotation; oa:motivatedBy oa:editing; oa:motivatedBy fp:authorityConformance a oa:Motivation [fp:conformsTo <http://authority.org/fp/theRuleset#Rule1> ] ; .... The first motivation is meant to convey that a change to the Target is proposed in the Body. The second is meant to be an assertion that the annotator believes the edit will bring the the Target into compliance with an authority, and that is another reason the Annotation is offered. I image the Digital Library community has vocabularies that describe authority control that might be used instead of the invented ones here with "fp:", so really I am mainly raising two questions: 1. Is this a reasonable use of oa:motivatedBy and 2. (less important at this point) Is authorityConformance of sufficient interest to be added to the list of oa:Motivation instances? (I'm somewhat agnostic on this. Because it is probably a concept of wider applicability than just as a motivation. On the other hand so is "editing".) Bob p.s. "Anything can be a motivation." is not an entirely satisfactory answer to 1. :-) 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.
Received on Monday, 4 February 2013 17:49:58 UTC