Protege 3.4 Beta update (build 513)

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Protege 3.4 Beta update (build 513)

Jennifer Vendetti
Administrator
There is a new beta build available on our Web site:

http://protege.stanford.edu/download/prerelease/full/
http://protege.stanford.edu/download/prerelease/basic/

Changes in Standard Extensions
---------------------------------
- The EditorPaneWidget now supports text highlighting and insertion of
internal links to entities in the ontology (e.g., when clicking on an
internal link for class "Pizza", a window will appear showing class
details for Pizza).

Changes in Collaborative Protege & the Changes Tab
-------------------------------------------------------
- The Changes and Annotations Ontology (ChAO) used by the Changes Tab
[1] and Collaborative Protege [2] to store change tracking and
annotation information can now be stored in a database. We have
documented how to convert an existing ChAO from the RDF file-based
back-end to the database back-end on the wiki [3].
 
- The same ChAO project can now be shared by more than one project. For
example, the CollaborativePizza and CollaborativeNewspaper projects may
share the annotation_PizzaNewspaper.pprj project. There is also no
longer a requirement that the ChAO project name start with "annotation".

- When a user enables the Changes Tab for the first time, she will be
asked what type of ChAO project she wants to create. She can choose between:
a). RDF back-end (previous setup and default option)
b). Database back-end
c). Associate an existing ChAO project

- The Change menu has several new items:
a). Show Changes Ontology Details (e.g., location, back-end, number of
annotations and changes)
b). Browse Changes Ontology
c). View Change Statistics and Conflicts (e.g., the editing conflicts
between users)

- A new Changes and Annotations API provides full access to the changes
and annotation instances stored in a ChAO knowledge base. We have
documented this new API on the wiki [4].

- It is now possible to extend the set of existing annotation types
(Comment, Advice, Proposal, etc.) from ChAO with custom annotation
types, simply by creating a subclass of the Annotation class in the ChAO
project. You may add your own properties/slots to the new annotation
type and customize its user interface form. Collaborative Protege will
automatically pick up this new annotation type and show it in the
available annotation types combo box in the user interface.

- All annotations defined in ChAO now have a subject slot attached to
them. An automatic backwards compatibility fix is provided for previous
versions of the ChAO.

- The forms for annotations in ChAO have been updated to more closely
resemble a send email form. Users may now enter HTML styles in the body
of the annotations and internal links to entities in the ontology.

- The creation of annotations will show a dialog that will allow users
to post or cancel a message. In previous versions, when the user clicked
on the create annotation button, a new annotation was created
automatically. Now users have the chance to cancel submission of the new
annotation.

- All annotations are now rendered with a type specific icon so that
they can be more easily distinguished in the user interface. For
example, a comment will have a little "c" in its icon, a proposal will
have a "P", and so on.

As always, a web-based version of the release notes is available on our
site [5].

The Protege Team

[1] http://protegewiki.stanford.edu/index.php/Changes_Tab
[2] http://protegewiki.stanford.edu/index.php/Collaborative_Protege
[3]
http://protegewiki.stanford.edu/index.php/Changes_Tab#How_to_store_the_Changes_and_Annotations_ontology_in_a_database
[4] http://protegewiki.stanford.edu/index.php/ChAO_API
[5]
http://protege.stanford.edu/download/release_notes/release_notes_beta.html

_______________________________________________
protege-beta mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-beta

Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03