 |
Page History
| Scrollbar | ||
|---|---|---|
|
| Page info | ||||
|---|---|---|---|---|
|
| Include Page | ||||
|---|---|---|---|---|
|
...
Tools Recommended for Semantic Infrastructure Work
| Info | ||
|---|---|---|
| ||
Supported CBIIT application structures, such as the Java platform, Tomcat, JBOSS, Ant, and Maven, are discussed in the architecture sections of this roadmap and the caGrid 2.0 Roadmap, 6 - caGrid 2.0 Architecture and 6 - Semantic Infrastructure 2.0 Architecture. Additional standards are discussed in section 10.4 - CBIIT Project Recommendations of the caGrid 2.0 Roadmap and on the VCDE WS Standards Efforts page. |
...
ARQ (openjena.org) - Supports the W3C standard for RDF queries. This is packaged with Jena and can be used against Jena models.
| Info | ||
|---|---|---|
| ||
These systems can be used in combinations. For example, OWL files created with OwlAPI can be read by Jena. However, Jena TDB is specific to Jena, and you must use Jena to access it. See below for persistence methods. |
...
db2rq (wiwiss.fu-berline.de) - Not technically a general purpose store, db2rq provides a semantic reference layer to an existing RDBMS environment, allowing for SPARQL and other interactions within a given environment.
| Info | ||
|---|---|---|
| ||
These systems can also interact. Specifically Jena can access Sesame through a model factory component and Sesame can access Jena through a SAIL. This does not indicate compatibility, but rather an abstraction. This means that the database tables created by Jena SDB do not match the RDBMS tables generated by Sesame. However, as an example, code written using Jena as an interface, if written correctly, can be independent of the persistence method. |
...
| Anchor | ||||
|---|---|---|---|---|
|
| Scrollbar | ||
|---|---|---|
|
