Wednesday, January 04, 2006

Fw: Global Integration Summit 2006 

> Global Integration Summit 2006 (GIS'06)
> "Integration For Everyone"
> Annual Meeting of the Integration Consortium
> Fairmont Copley Plaza
> Boston, May 22-24, 2006
> ----------------------------------------------------------------------
> --- OVERVIEW ---
> The Global Integration Summit (GIS) is the annual meeting of the
Integration Consortium (IC), the non-profit, user-driven association of IT
professionals focused on application, information, process,service, and
system integration technologies.
> The GIS differs from other industry events as it is truly user-driven and
vendor-neutral. With an attendance hovering above 200 every year, and
involving senior integration executives from leading Global 2000
corporations, the event offers a personal atmosphere for networking.
> The Integration Consortium is calling on integration thought
leaders,practice leaders, business leaders, and product leaders to present
papers at the 2006 Global Integration Summit that can help the industry
achieve a higher degree of maturity and application interoperability. If you
are such a leader, you are invited to submit a paper, by January 31, 2006,
> the GIS Program Committee for consideration at the 2006 Summit. A
peer-review process will select the best papers which will be published in
the Summit Proceedings. Of the accepted papers, the best ones (the best of
the best) will be invited to present their papers at the Summit in Boston
and to defend their perspective at a plenary of their peers. The top three
presentations, as voted on by attendees at the Summit, will also receive a
cash award ($1,000, $2,000, or $3,000) at the annual awards banquet.
> --- THEME ---
> For our 3rd edition, the theme "Integration For Everyone" seeks to build a
unified view of the Integration Discipline. One outcome of the Summit will
be to develop a new Integration Body of Knowledge (I-BOK) As such, we
welcome IT thought leaders from industry, vendors, analysts, and academia to
expose the "State of the Art" in integration solutions.
> --- TOPICS ---
> Topics can range from business drivers for integration such as Governance
and Regulatory Compliance, to integration approaches and platforms such as
the Service Oriented Architecture (SOA) and Business Process Management
(BPM), to technical infrastructure issues such as Enterprise Service Bus
(ESB) and Open Source Middleware.
> Papers can take the form of conceptual frameworks, research in
progress,best practice reports, case studies, and executive viewpoints.
> We welcome papers that contribute to enriching the I-BOK. Please see below
for an outline, with a detailed list of 50 topics available at:
> Part A - Business Perspective
> 1. Business Trends and Integration Drivers
> 2. Industry-Specific Integration Drivers
> Part B - Application Requirements
> 3. Application-Specific Integration Solutions
> 4. User-Centric Integration Solutions
> Part C - Development Capabilities
> 5. Strategic Management of the Integration Function
> 6. Integration Development Methods and Standards
> 7. Integration Development Tools and Best Practices
> Part D - Technologies and Standards
> 8. Integration Platforms and System Architecture
> 9. Core Integration Technologies and Standards
> 10. Integration Runtime Infrastructure
> * Papers Submission Deadline >>> January 31, 2006
> * Notification of Paper Selection >>> February 20, 2006
> * Confirmation by Author to present at GIS 2006 >>> February 28, 2006
> * Early Bird Registration Deadline >>> April 1, 2006
> * Upload Final Paper and Presentation >>> May 1, 2006
> * Global Integration Summit >>> May 22-24, 2006
> --- SUBMISSION ---
> * Instructions:
> * Paper Template:
> * Submission System:
> --- CO-CHAIRS ---
> John Schmidt
> President, Integration Consortium
> Senior Vice President, Integration, Bank of America
> Peter Anadranistakis
> Board of Directors Member, Integration Consortium
> Chief Partnership Officer, Online Business Systems
> Dr. Stephane Gagnon
> VP Research and Standards, Integration Consortium
> Assistant Professor, New Jersey Institute of Technology
> --- CONTACT ---
> Please send all enquiries by email to:
> --------------------------------------------------------------------------

Tuesday, January 03, 2006

Dave Beckett - Journalblog » Blog Archive » Raptor RDF Parser Toolkit 1.4.8 

Dave Beckett - Journalblog » Blog Archive » Raptor RDF Parser Toolkit 1.4.8: "Raptor RDF Parser Toolkit 1.4.8

I am happy to announce a new version of my Raptor library for dealing with syntaxes for RDF. I still call it a parser toolkit, otherwise the PT in raptor wouldn’t be so correct but it’s really more of an RDF syntax, URI and web library. It deals with low-level web detail you don’t want to care about when you are writing RDF applications. Raptor is primarily different from Redland in that Raptor provides the web and syntax functionality but only knows about how to read and write single RDF triples. Redland has RDF graphs, stores for them, proper developer APIs and higher level features like querying.

This is a major release for Raptor as it covers all the pending stuff that was ready to release before I rushed off to my new job at Yahoo! plus new things since then."

Monday, January 02, 2006

Simple javascript RDF Parser and query thingy. 

Simple javascript RDF Parser and query thingy.: "This RDF parser is designed to run in a web-browser or SVG browser, allowing you to process RDF on the client. The parser isn't complete, there's no support for various bits of the spec, and isn't all that fast, especially with large XML/RDF files. I've found it quite useful though for simple querying.

The parser is generally tested and expected to work in Adobe SVG Viewer, Batik's Squiggle, Internet Explorer 5.5+ and Mozilla Family, Opera 8+ and Safari browsers, Ice Softs Ice Browser is probably the only other browser with a large enough API for it to work, but it's never been tested there - don't expect it to work elsewhere..

rdfs:subProperty is supported, if you include triples which detail subProperties then triples with that property will be duplicated in the output list allowing queries to work on either property.

owl:sameAs is also supported, if you include triples which contain owl:sameAs information, then triples are again duplicated to enable querying, if you don't want this, or the subProperty in your code, it's probably wise to remove the two calls to the functions doSubProperties(); and doOwlSameAs();.

RDF datatypes and languages are supported in the parser, but the query engine provides no way of querying against it currently, should be quite simple for anyone who wants to look at the querying parts, they really"

A Vision of Consumer Applications of Software Agent Technology 

Agtivity | A Vision of Consumer Applications of Software Agent Technology: "Introduction

Software agent technology has been an active field of research for more than a decade. Although there have been limited applications of the technology for consumer use, deeper success has been achieved in industrial applications. There have been numerous false starts to commercialize agent technology on a wide spread basis, including for consumers, but alas the hype has greatly exceeded both the capabilities of off-the-shelf technology and our own abilities. With every passing year we remain on the cusp of finally breaking out and fielding the kind of technological breakthroughs which will finally make the consumer application of software agent technology a reality.

Please note that the intention of this vision of software agent technology is not to turn the computer into a human-like robot, but simply to enable the computer as a competent assistant in the lives of consumers. The goal is not to pursue artificial intelligence per se, but to incorporate those aspects of AI which relate to agency, where the consumer decides what responsibilities to delegate and is the controlling authority for goals to be pursued by software agents.

The focus of this vision is not to preview the totality of consumer applications that could be constructed, but to establish a base vision upon which consumer applications can then be envisioned. Alternatively, this vision can be considered as the model for a platform upon which consumer applications can be built.

Central to a new wave of consumer-oriented computing is support for interactions that are based on higher-level knowledge rather than simply moving information from one location to another. The goal of using software agent technology is to enable knowledge-based computing."

Links on the Semantic Web 

Links on the Semantic Web | Decentralized Information Group (DIG) Breadcrumbs: "On the Semantic Web, links are also critical. Here, the local name, and the URI formed using the hash, refer to arbitrary things. When a semantic web document gives information about something, and uses a URI formed from the name of a different document, like foo.rdf#bar, then that's an invitation to look up the document, if you want more information about. I'd like people to use them more, and I think we need to develop algorithms which for deciding when to follow Semantic Web links as a function of what we are looking for.

To play with semantic web links, I made a toy semantic web browser, Tabulator. Toy, because it is hacked up in Javascript (a change from my usual Python) to experiment with these ideas. It is AJAR - Asynchronous Javascript and RDF. I started off with Jim Ley's RDF Parser and added a little data store. The store understands the mimimal OWL ([inverse] functional properties, sameAs) to smush nodes representing the same thing together, so it doesn't matter if people use many different URIs for the same thing, which of course they can. It has a simple index and supports simple query. The API is more or less the one which cwm and had been tending toward in python."

Combining OWL Ontologies Using E-Connections 

Combining OWL Ontologies Using E-Connections (PDF)
authors: Bernardo Cuenca Grau, Bijan Parsia, Evren Sirin

The standardization of the Web Ontology Language, OWL, leaves (at least) two crucial issues for Web-based ontologies unsatisfactorily resolved, namely how to represent and reason with multiple distinct, but linked ontologies, and how to enable effective knowledge reuse and sharing on the Semantic Web.

In this paper, we present a solution for these fundamental problems based on EConnections. We aim to use E-Connections to provide modelers with suitable means for developing Web ontologies in a modular way and to provide an alternative to the owl:imports construct. With such motivation, we present in this paper a syntactic and semantic extension of the Web Ontology language that covers E-Connections of OWL-DL ontologies. We show how to use such an extension as an alternative to the owl:imports construct in many modeling situations. We investigate different combinations of the logics SHIN(D), SHON(D) and SHIO(D) for which it is possible to design and implement reasoning algorithms, well-suited for optimization.

Finally, we provide support for E-Connections in both an ontology editor, SWOOP, and an OWL reasoner, Pellet."

This page is powered by Blogger. Isn't yours?