Key points: It was all about the best tool for the job, for example modeling tool that would generate great code, etc Rarely was integration a concern, if so done by export/import or very specialized Date isn’t the point, just some time ago
Other points: Integrations done past shipping the key features APIs were afterthoughts Caused lock-in to current installed versions and integration glue, to upgrade either end, required upgrading other end and glue.
Benefits: Applications can upgraded without impacting other apps Easy to add/remove tools into the ecosystem Easy to integrate completely different tools, different provider, technology platform, etc
Points: At the core is a set of Statements (aka facts), which are typically written down or learned Tell the story as if the present is a tester, they have knowledge of their test cases and of Joe. In the Web 1.0/2.0 way to learn these things is by publishing on a HTML page for a human consumer of it This follows TBL’s 4 rules for linked data First we give these statement URIs so computers can identify them and understand them. Grouping into subject-predicate-object builds the statement Next we can do a HTTP GET to learn more When we learn more, it is in the form of more statements with URIs Those URIs point to more things or relate things back to things we already know (Joe) Jira http://www.atlassian.com/software/jira/overview
Points: Same information as the previous slide but just as a direct graph Highlight this is just the way the web works Can point out that easy to extend to include things like: can learn when dependent software has been fixed, built and where it is available
I call this the 30,000 feet view and the previous example the 3 inch view. So taking a giant leap back, here’s what you get (in a way) at a global scale.
Highlights the different between Linked Data and how OSLC enhances and builds off it. When we have linked data (liked W3C Linked Data Platform), OSLC provides: Resource types and properties (vocabularies) based on scenarios An easy way to embed a fragment of HTML (link preview) into another application using standard HTTP content negotiation A way to take another web application’s (tool’s) web UI’s creation and selection dialog and embed them into your own
Key points Request URI == subject Resource has a type Simple defn Response representation is the full state of the resource (there is no other data the server knows about it, all other data is either inbound links or stored where it doesn’t know)
http://incubator.apache.org/clerezza/ Clerezza allows to easily develop semantic web applications by providing tools to manipulate RDF data, create RESTful Web Services http://stanbol.apache.org/index.html Apache Stanbol's intended use is to extend traditional content management systems with semantic services http://jena.apache.org/documentation/serving_data/index.html Apache Jena and Fuseki Fuseki is a SPARQL server. It provides REST-style SPARQL HTTP Update, SPARQL Query, and SPARQL Update using the SPARQL protocol over HTTP. http://incubator.apache.org/wink/ http://eclipse/lyo
OSLC is an open community of vendors, integrators, and users, that creates freely-available, scenario-driven, specifications for integrating software applications. Though OSLC’s initial focus for specification were ALM domains, the techniques used are universally applicable , and are already being applied in workgroups focused on PLM ( with leadership from Siemens ), and DevOps ( with leadership from IBM Tivoli ). (Optional for more technical presentations: All the specifications are based on the standard, and proven, architecture of the web: HTTP, REST, and Linked Data. This means integrations don’t have to copy and synchronize data, but can link to it where it “lives”. Wherever the data is, OSLC-based integrations let users work with data from their current context. ) Whether you want to work on the details of the specifications, get the community to focus on scenarios that are important to you, or use finalized OSLC specifications to integrate your own software, the OSLC community is open to you . (Links on this chart: open-services.net open-services.net/members open-services.net/participate )