Healthline Networks is seeking an Informatics Sr. Java Software Engineer in San Francisco, California. This position offers the opportunity to “Work with dynamic Engineering and Medical Informatics Teams to enhance Healthline’s medical ontology. Healthline is a web health technology company, employing tools for the future.” The Responsibilities include: “Design and implement algorithms for integrating medical standard dictionaries into Healthline ontology; Develop data mining processes to create our Semantic Network; Work on an authoring tool that allows Medical Informatics Specialists to successfully and easily edit our ontology; Read more
Posts Tagged ‘OWL’
[Editor’s note: this guest post was co-written by Héctor Pérez-Urbina (Clark & Parsia) and Juan Sequeda (Capsenta)]
Important enterprise business logic is often buried deep within a complex ecosystem of applications. Domain constraints and assumptions, as well as the main actors and the relations with one another, exist only implicitly in thousands of lines of code distributed across the enterprise.
Sure, there might be some complex UML diagrams somewhere accompanied by hundreds of pages of use case descriptions; but there is no common global representation of the domain that can be effectively shared by enterprise applications. When the domain inevitably evolves, applications must be updated one by one, forcing developers to dive into long-forgotten code to try to make sense of what needs to be done. Maintenance in this kind of environment is time-consuming, error-prone, and expensive.
The suite of semantic technologies, including OWL, allows the creation of rich domain models (a.k.a., ontologies) where business logic can be captured and maintained. Crucially, unlike UML diagrams, OWL ontologies are machine-processable so they can be directly exploited by applications.
Reasoning is the task of deriving implicit facts from a set of given explicit facts. These facts can be expressed in OWL 2 ontologies and stored RDF triplestores. For example, the following fact: “a Student is a Person,” can be expressed in an ontology, while the fact: “Bob is a Student,” can be stored in a triplestore. A reasoner is a software application that is able to reason. For example, a reasoner is able to infer the following implicit fact: “Bob is a Person.”
Reasoning tasks considered in OWL 2 are: ontology consistency, class satisfiability, classification, instance checking, and conjunctive query answering.
The financial services industry is taking to semantic tech in an important way, and that’s in the form of the Financial Industry Business Ontology (FIBO), which aims to standardize the language used to precisely define the terms, conditions, and characteristics of financial instruments; the legal and relationship structure of business entities; the content and time dimensions of market data; and the legal obligations and process aspects of corporate actions. Attendees at SemTech Biz in San Francisco will get a deep dive on the how’s and why’s, at this session, while the FIBO Technology Summit invitation event will present an opportunity for working collaboratively to continue advancing the effort that has its roots in The Enterprise Data Management Council and communities of interests.
Leading that event will be Dennis E. Wisnosky, founder of Wizdom Systems, Inc. and former CTO and Chief Architect of the DoD Business Mission Area, who was recently named to provide technical strategy and operational guidance to help the Council finalize and implement FIBO standards, and David S. Newman, SVP & Strategic Planning Manager Enterprise Architecture at Wells Fargo, and Chair of the EDM Council’s Semantics Program. (Newman, with Enterprise Data Management Council Head of Semantics and Standards Mike Bennett, will also host the SemTech FIBO session.) Speaking of the upcoming event, Wisnosky explains that a goal is to cast a wide net to find the new tech ideas and developments that both can bring benefits to FIBO in the short term and influence the longer-term research agenda to help the financial industry.
As FIBO stands now, in June the second draft of the FIBO Foundations ontology and the conceptual FIBO Business Entities ontology will be presented at a meeting of the Object Management Group in Berlin. By year’s end it is expected that the OMG will have ratified these as formal standards. “We are on the path to turn the corner from thinking of what FIBO will be to delivering it,” says Wisnosky. Read more
IT leaders keeping an eye on Gartner’s top tech trends list know that early in March semantic technologies made the cut (see our original story here, and our follow-up with one of the authors of the Gartner report here). The big question for many enterprise IT pros, though, is what should they be doing with that knowledge – how can they start leveraging semantic technology to their own organizations’ benefit?
Help is on the way. Three experts in semantic web technologies and Linked Data weigh in with their advice on heading down that road:
Gartner Names Semantic Technologies To Its Top Technology Trends Impacting Information Infrastructure in 2013
Semantic technologies have made it to Gartner’s list of the top technology trends that will impact information infrastructure this year.
The research firm yesterday released the list of nine trends that it says will play key roles in modernizing information management and in making the role of information governance increasingly important. Semantic technologies come in at No.3 on the list – right behind closely-tied-to trends Big Data and modern information infrastructure.
OWL, the Web Ontology Language has been standardized by W3C as a powerful language to represent knowledge (i.e. ontologies) on the Web. OWL has two functionalities. The first functionality is to express knowledge in an unambiguous way. This is accomplished by representing knowledge as set of concepts within a particular domain and the relationship between these concepts. If we only take into account this functionality, then the goal is very similar to that of UML or Entity-Relationship diagrams. The second functionality is to be able to draw conclusions from the knowledge that has been expressed. In other words, be able to infer implicit knowledge from the explicit knowledge. We call this reasoning and this is what distinguishes OWL from UML or other modeling languages.
OWL evolved from several proposals and became a standard in 2004. This was subsequently extended in 2008 by a second standard version, OWL 2. With OWL, you have the possibility of expressing all kinds of knowledge. The basic building blocks of an ontology are concepts (a.k.a classes) and the relationships between the classes (a.k.a properties). For example, if we were to create an ontology about a university, the classes would include Student, Professor, Courses while the properties would be isEnrolled, because a Student is enrolled in a Course, and isTaughtBy, because a Professor teaches a Course.
Here are some final thoughts from our panel of semantic web experts on what to expect to see as the New Year rings in:
Broader deployment of the schema.org terms is likely. In the study by Muehlisen and Bizer in July this year, we saw Open Graph Protocol, DC, FOAF, RSS, SIOC and Creative Commons still topping the ranks of top semantic vocabularies being used. In 2013 and beyond, I expect to see schema.org jump to the top of that list.
Christine Connors, Chief Ontologist, Knowledgent:
I think we will see an uptick in the job market for semantic technologists in the enterprise; primarily in the Fortune 2000. I expect to see some M&A activity as well from systems providers and integrators who recognize the desire to have a semantic component in their product suite. (No, I have no direct knowledge; it is my hunch!)
We will see increased competition from data analytics vendors who try to add RDF, OWL or graphstores to their existing platforms. I anticipate saying, at the end of 2013, that many of these immature deployments will leave some project teams disappointed. The mature vendors will need to put resources into sales and business development, with the right partners for consulting and systems integration, to be ready to respond to calls for proposals and assistance.