Re: [Treebase-devel] [Nexml-discuss] CDAO term inclusion community process

[Hilmar L. <hl...@du...>]

Hi Arlin & Enrico - the OBO Foundry ontologies use the SourceForge- 
provided trackers to request and document new terms or relationships  
or changes to existing ones.

Do you anticipate CDAO to become accepted under the OBO Foundry too,  
and if so, do you think the SourcForge term tracker approach will not  
be suitable for CDAO?

	-hilmar

On Jun 4, 2009, at 11:20 AM, Arlin Stoltzfus wrote:

> We're listening.  Brandon has developed a term-request server to
> process requests for concepts and relations, but its still in an early
> stage.  In a few weeks we will be in a better position to have this
> discussion.
>
> Arlin
>
> On May 29, 2009, at 10:31 AM, Rutger Vos wrote:
>
>> Hi,
>>
>> I've done enough experimentation to establish the correct syntax for
>> attaching valid RDFa attachments to nexml so that standard RDFa
>> extractors can turn <meta/> elements - the new dictionaries - into  
>> RDF
>> triples. I've implemented this in the java and perl APIs (Jeet: I  
>> hope
>> that the examples I've mailed out give you enough of a template to do
>> this in python too, but please let me know of I can help - I know  
>> that
>> the wiki needs updating, for starters).
>>
>> The key issue now is the definition of predicates, i.e. the value of
>> the @property and @rel attributes. Over the course of many EvoInfo
>> discussions it's been decided that CDAO will be the principal  
>> artifact
>> for their mediation - so what's the community process for inclusion  
>> of
>> new predicates?
>>
>> Val and I have sketched out a couple of TreeBASE services whose  
>> search
>> keys should be part of a controlled vocabulary (things like tree.id,
>> tree.label, etc.), and this is just one use case of a project  
>> having a
>> potentially large number of predicates (other example: Mesquite).
>>
>> It would be great if team CDAO could tell us where to send our list  
>> of
>> proposed terms and where we can download an amended version of CDAO
>> that includes them :-)
>>
>> I note that there is a wiki page about this
>> (https://www.nescent.org/wg_evoinfo/CDAO_term_request), but ideally
>> there would be some sort of issue tracker with structured input  
>> fields
>> (e.g. subject/predicate/object name="XXX", suggested  
>> superclass="YYY",
>> suggested datatype(s)="ZZZ", description="..."). Behind this tracker
>> would be a team of curators that will promptly pick up a posted issue
>> and work towards a solution.
>>
>> I realize that this involves a support commitment from team CDAO, but
>> I think that's what we agreed to over free-form key/value pairs,
>> homegrown vocabularies or a BioMoby-like free-for-all.
>>
>> Any comments?
>>
>> Rutger
>>
>> -- 
>> Dr. Rutger A. Vos
>> Department of zoology
>> University of British Columbia
>> http://www.nexml.org
>> http://rutgervos.blogspot.com
>
>
> ------------------------------------------------------------------------------
> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
> looking to deploy the next generation of Solaris that includes the  
> latest
> innovations from Sun and the OpenSource community. Download a copy and
> enjoy capabilities such as Networking, Storage and Virtualization.
> Go to: http://p.sf.net/sfu/opensolaris-get
> _______________________________________________
> Nexml-discuss mailing list
> Nex...@li...
> https://lists.sourceforge.net/lists/listinfo/nexml-discuss

-- 
===========================================================
: Hilmar Lapp  -:-  Durham, NC  -:- hlapp at duke dot edu :
===========================================================