Dear users,
Today we are pleased to announce the first public beta of TopBraid Suite 3.6. A list of key changes in 3.6 is provided below.
To download and try:
Beta download of TopBraid Composer (TBC) is accessible from the main download page http://www.topquadrant.com/products/TB_download.html
An evaluation copy of Enterprise Vocabulary
Net (EVN) for the “stand-alone” use can be obtained by downloading
the Maestro Edition of TopBraid Composer (TBC-ME) from the aforementioned link
and opening a browser to: http://localhost:8083/evn.
An evaluation copy of TopBraid Live (TBL) for the “stand-alone” use
can be obtained by downloading the Maestro Edition of TopBraid Composer
(TBC-ME) from the aforementioned link and opening a browser to: http://localhost:8083/tbl.
Licensed TBL and EVN customers will
be able to access the beta versions of the enterprise server distributions at http://www.topquadrant.com/topbraid/live/
starting with this Monday.
As always, we appreciate your participation in our beta test program and look forward to your feedback. Please submit your input by March 9th.
If you have questions, please do not hesitate to contact us:
TopBraid Suite Users forum: http://groups.google.com/group/topbraid-users
Composer support: compose...@topquadrant.com
TopBraid Suite support (valid TBL and EVN licenses): TBSsu...@topquadrant.com
(+1-650-265-1700)
Sales: sa...@topquadrant.com
TopQuadrant Team
KEY CHANGES IN 3.6
TopBraid Platform
· Large updates for all databases are now significantly faster
TopBraid Enterprise Vocabulary Net (EVN)
· SPARQL Query form included in the EVN edit and browse applications
· Also see general improvements for TBE
SPARQL Rules (SPIN)
· Improvements and bug fixes to SPIN OWL 2 RL rule base
SPARQL Web Pages (SWP)
· Several incremental enhancements for SWP 1.1, see http://uispin.org/ui-1.1.0.html#new-1.1 for details
· Experimental SWP Applications Library with components for trees, grids, forms, etc.
TopBraid Composer (TBC)
· Class diagrams are now editable
Dropped features:
· BIRT plugin in TBC – this feature was rarely used because it had little value in TBC only without server support
· SPARQL JSP tags - duplicate functionality, use SPARQL Web Pages instead
· Pellet plugin – version of Pellet shipped with TopBraid got very outdated. With the change in Pellet licensing we are not able to ship newer versions with our product without increasing its price. User survey showed that it was rarely used and demonstrated lack of interest in paying premium for its bundling. OWL reasoning continues to be supported through OWLIM plugin and SPIN (OWL 2 RL rule base).
· Java development environment in TBC –inclusion of Java development environment cluttered TBC user interface with options not appropriate for RDF/OWL data modeling. Furthermore, it encouraged the use of internal TopBraid Java APIs that are not sufficiently stable and, thus, not supported for external use. Supported Java extension points include user-defined SPARQL functions, SPARQLMotion modules and SPIN API.
TopBraid Ensemble (TBE)
· Ability to specify sort order when generating a query from the Search Form
· Switch from Yahoo! Maps API to MapQuest API
· Improved multi-lingual support
Known bugs (will be fixed for the general release):
· Tab delimited files importer does not work in TBC, SM module is also affected (need a better description from Gokhan)
· Spreadsheet import in EVN does not work for the working copies
· The Deploy project to TBL Server in export wizards cannot deploy a project, with default options selected in the wizard. Recipe:
- Create a new project and export using Deploy project to TBL Server
- A similar error occurs: Project upload: <project-name> failed. An existing project blocked the upload.
- Work-around: Enable Overwrite and run the wizard.
Missing features planned to be included in the general release:
· Web user interface for deletion of EVN vocabularies
· Additional cleanup of TopBraid SPARQL endpoint to support all the official parameters and result types
· Additional usability improvements for the wizard connecting to relational databases
The .owl file ending has been taken over by OWL 2 XML, so .rdf is now the only recommended file ending for RDF/XML.
.n3 was identical to .ttl anyway and since we never supported native N3 features this was misleading. Use .ttl instead.
Holger
--
You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary Network (EVN), TopBraid Composer,
TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN.
To post to this group, send email to
topbrai...@googlegroups.com
To unsubscribe from this group, send email to
topbraid-user...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/topbraid-users?hl=en