W3C home > Mailing lists > Public > public-openannotation@w3.org > February 2013

Re: confused about extending Motivations: oa:motivationScheme

From: Bob Morris <morris.bob@gmail.com>
Date: Fri, 22 Feb 2013 22:45:57 -0500
Message-ID: <CADUi7O7emHEP_macrDnDsipXo4VDN7S7tVRY8ooD_Zh2TW2GSg@mail.gmail.com>
To: Robert Sanderson <azaroth42@gmail.com>
Cc: public-openannotation <public-openannotation@w3.org>
Thanks, that's what I thought.  From your confirmation of my
understanding I also conclude

1. If I correctly read the thread initiated by Antoine as
http://lists.w3.org/Archives/Public/public-openannotation/2013Jan/0017.html
we would prefer that the example in
http://openannotation.org/spec/core/appendices.html#ExtendingMotivations
have capitalized oa:MotivationScheme  rather than oa:motivationScheme

2. We haven't actually declared oa:MotivationScheme anywhere except
implicitly by its need implied by
http://openannotation.org/spec/core/appendices.html#ExtendingMotivations
(Right?)

On Fri, Feb 22, 2013 at 11:40 AM, Robert Sanderson <azaroth42@gmail.com> wrote:
> You're perfectly correct, we don't want people to change our
> pre-defined Motivations, we want them to create their own in their own
> namespaces.
>
> The new:correcting and new2:fixing examples are the extensions, the
> oa: namespaced terms are in the RDF example only to give something to
> relate those hypothetical extensions to.
>
> Hope that helps!
>
> Rob
>
> On Thu, Feb 21, 2013 at 10:01 PM, Bob Morris <morris.bob@gmail.com> wrote:
>> Ummm, in the Feb 8
>> http://openannotation.org/spec/core/appendices.html#ExtendingMotivations
>> the example  avows
>>
>>  oa:motivationScheme a skos:ConceptScheme ;
>>
>> and then puts some skos data on it, presumably in order to support the
>> skos breadth comparisons to oa:editing.
>>
>> Rather than expect such triples
>>
>> oa:motivationScheme a skos:ConceptScheme ;
>>
>> oa:editing a oa:Motivation ;
>>     skos:inScheme oa:motivationScheme ;
>>     skos:prefLabel "Editing"@en.
>>
>> to be in extension code,  I would think such triples are actually
>> meant to be part of the spec in the case of every Section 2.3 declared
>> Motivation.
>>
>> In this case, I think I would also expect that for the most part, it
>> would be discouraged for extensions to change much of the skos in
>> these Section 2.3 Motivations except, perhaps  the skos:prefLabel.
>>
>> In other words, I imagine that Appendix is not really inviting the
>> world to put whatever skos semantics it wishes on the Section 2.3
>> instances.
>>
>> Am I confused?
>>
>> 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.
>>



-- 
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 Saturday, 23 February 2013 03:46:30 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:38:22 UTC