POWL

[Ed Shaya]

I remembered seeing Collaborative Protege, so I thought I would give it 
a try.
  http://protege.stanford.edu/doc/collab-protege/
  http://www2007.org/workshops/paper_93.pdf

If you are interested in testing this out download Protege3.3.1 (or 
later) Full.  Install Everything.
Edit the run_protege.sh to have a line

PORTOPTS=" -Dprotege.rmi.server.port=5256"

When it fires up. Click on "Open Other"
Choose "Server" button
Host machine name: atlas.astro.umd.edu
The username and password should already be Guest and Guest.
Select Collaborative Project: Collaborative Astronomy
Wait at least 30 seconds.
You should get all of our ontologies to load in, but you can only change 
  Astronomy here (don't know if it can do multiple ontologies somehow). 
  Get the classes tab.
AstronomyEntities is all the way on the bottom.  You can open that up 
and make changes, comment the changes, make voting proposals, chat, etc.
It has the usual clunkiness of a large java application.

As we make changes, we should keep in the mind that the primary 
application of this ontology is the OWLViper tool which uses Jena and 
Pellet reasoners and generally hunts for data in archive/repositories, 
displays tables of this data, and allows transforms/Operations to be 
applied to the data. So, we require classification of objects, 
measurements and operations.  I did import the SKOS.owl, but this is not
meant to be the SV nor the SAV.

If you want me to, I can set up a separate Project with just skos.owl 
for the SV, but I take it that we are not mixing our modes of 
transportation, yet.

Ed




Tony Linde wrote:
> Not tried it but says it aims to 'deliver a PHP and web-based ontology
> editing and management solution'. Might be useful for any group wanting to
> collaboratively develop OWL-based ontology:
>   http://ontowiki.net/Projects/Powl
>  
> And maybe we could develop the SV using OntoWiki: would certainly provide a
> good interface for anyone wishing to view it:
>   http://ontowiki.net/Projects/OntoWiki 
> (Note: just tried to install this to my provider and could not even get db
> to build! Maybe next version.)
>  
> T.
>  
-------------- next part --------------
A non-text attachment was scrubbed...
Name: eshaya.vcf
Type: text/x-vcard
Size: 257 bytes
Desc: not available
URL: <http://www.ivoa.net/pipermail/semantics/attachments/20070926/e4dea071/attachment-0001.vcf>