head	1.4;
access;
symbols;
locks; strict;
comment	@# @;


1.4
date	2011.07.06.18.33.40;	author PaulJMorris;	state Exp;
branches;
next	1.3;

1.3
date	2011.03.03.18.42.31;	author BobMorris;	state Exp;
branches;
next	1.2;

1.2
date	2011.01.15.03.15.30;	author BobMorris;	state Exp;
branches;
next	1.1;

1.1
date	2011.01.15.02.15.10;	author BobMorris;	state Exp;
branches;
next	;


desc
@none
@


1.4
log
@none
@
text
@%META:TOPICINFO{author="PaulJMorris" date="1309977220" format="1.1" version="1.4"}%
%META:TOPICPARENT{name="WebHome"}%
Subsequent to the day-long session in Woods Hole, where I presented a candidate data annotation ontology. The [[http://etaxonomy.org/FilteredPush FilteredPush (FP2)]] project met several times with Paulo Ciccerese and discussed whether  [[http://code.google.com/p/annotation-ontology/][AO Annotation Ontology]] would work for data annotation as well as document annotation and still meet therequirements met by the ontology I presented... Paolo thinks yes, with only the subclassing of what AO calls a Selector. From a lot of experience with XML, I have a natural skepticism that modeling documents and modeling data are the same thing, but part of my ontology work in the FP2 project is to try to use AO, and I have been working on Paolo's challenge to model our use cases with it. Curiously(?), one simple one needs no Selector at all and I can't tell yet whether the extensions I had to make to AO got simpler or more complex because of that. When I get a little farther, I'll report on it here.
-- Main.BobMorris - 15 Jan 2011

The [[http://etaxonomy.org/FilteredPush Filtered Push project]] had another meeting with Paulo Ciccerese to discuss two examples of Biodiversity data annotations I coded with a small extension of  [[http://code.google.com/p/annotation-ontology/][AO]]. We now believe that AO can be extended to the model I presented at Woods Hole and expect more collaboration with Paulo. Since the W3 Incubation Group that gave rise to  [[http://code.google.com/p/annotation-ontology/][AO]] for documents is at the end of its life as an Incubation Group, Paulo is setting up a proposal to W3C for a full working group to proceed toward a W3C Recommendation, including extensions for data annotation. 

Examples of annotations of biodiversity data expressed in the data extension of AO are illustrated at: [[http://etaxonomy.org/mw/AOD_Extension_of_AO_for_Data#Examples]].  -- Main.PaulJMorris - 06 Jul 2011@


1.3
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="BobMorris" date="1299177751" format="1.1" reprev="1.3" version="1.3"}%
d7 2
@


1.2
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="BobMorris" date="1295061330" format="1.1" version="1.2"}%
d3 1
a3 1
Subsequent to the day-long session in Woods Hole, where I presented a candidate data annotation ontology. The FilteredPush (FP2) project met several times with Paulo Ciccerese and discussed whether  [[http://code.google.com/p/annotation-ontology/][AO Annotation Ontology]] would work for data annotation as well as document annotation and still meet therequirements met by the ontology I presented... Paolo thinks yes, with only the subclassing of what AO calls a Selector. From a lot of experience with XML, I have a natural skepticism that modeling documents and modeling data are the same thing, but part of my ontology work in the FP2 project is to try to use AO, and I have been working on Paolo's challenge to model our use cases with it. Curiously(?), one simple one needs no Selector at all and I can't tell yet whether the extensions I had to make to AO got simpler or more complex because of that. When I get a little farther, I'll report on it here.
d6 1
a6 1
testing notification -- Main.BobMorris - 15 Jan 2011@


1.1
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="BobMorris" date="1295057710" format="1.1" reprev="1.1" version="1.1"}%
d5 2
@