What are key benefits of ontologies in Systematic Literature Review? - semantic-web

I am working on a Systematic Literature Review (SLR) and about to done with data synthesis. After SLR, I want to create an Ontology and include different details of the SLR in Ontology. I have almost completed the practical steps, but unable to write the motivation behind using Ontology in SLR.
I want you all to please briefly guide me about some key benefits of Ontologies over data which are described in tables and graphs. Please comment also if my question does not fulfill the stackoverflow criteria.
Thank you

Related

Where can I find various existing ontologies regarding certain aspects?

I need to create – possibly, by reusing various (parts of) existing ontologies – an ontological model regarding certain aspects – data communication, data processing, data storage, etc. – regarding a distributed system (platform, framework,...) used in the context of big data. Significant concepts, relations, restrictions, individuals should be considered as examples for a real software product like Hadoop or Git Large File Storage might be taking into account. Do someone know if there are ontologies that describes the system for one of the above or any other distributed system?
I don't know a specific vocabulary for that, but there are sites out there that can help you find what you need, e.g. http://lov.okfn.org/dataset/lov/

Where to store assessment name/type in Clinical Impression Resource?

I’m currently working on an implementation that facilitates the flow of data, from clinical record(s) into a personal health record.
We are planning to use the FHIR ClinicalImpression resource for routine planned heath reviews and it seems to be a good match.
These reviews are part of a standard care plan, have specific names/types to differentiate them and have a form with a set questions, tests, findings and follow up for the health professional to fill out with the patient.
Looking at the ClinicalImpression resource I see no property for (a) location where the assessment took place and (b) the name/type of the assessment.
This seems an oversight. Should these be implemented using extensions?
We see investigations[0]/code as inappropriate, because the name / type of the assessment relates to all of the information in the clinical impression
Any comments, suggestions or feedback would be most welcome.
Thanks in advance,
Bob.
ClinicalImpression is still draft, so it may be missing important pieces of information. Feel free to submit a change request proposing the addition of these elements. In the meantime, extensions would have to be your solution. (Location could also be captured via Provenance.)

difference between requirements documents specification document and requirement specification document

A google search gave me the following definitions
Requirements document what is needed - they shouldn't specify the how, but the what.
Specifications document how to achieve the requirements - they should specify the how.
then what is requirement specification document...
can you please clarify me with examples I didnt have any experiennce with this, I started to gain knowledge in testing,
And also what documents are needed to start writing testcases....
Thank you
The sound-bite answer is that requirements are what your program should do, the specifications are how you plan to do it.
Another way to look at it is that the requirements represent the application from the perspective of the user, or the business as a whole. The specification represents the application from the perspective of the technical team. Specifications and requirements roughly communicate the same information, but to two completely different audiences.

How to design a web ERP software for school using ASP.net and mysql

I have to design a school web ERP for a client of mine.
The following modules need to be present as of now:
Student
Inventory
Cafeteria
Admissions
Please help me with the required links or book which can guide me with the steps that need to be followed to create the design. Difference between different designs that can be used for e.g. in one of the links i read that Component based design should be used.
Also, Please note that the modules need to be licensed. i.e. The user must be able to choose one or more modules of his interest and only those modules should be installed.
I am new to this area and this exercise is primarily for learning process so I WANT TO DO THIS FROM SCRATCH AND NOT USE THE EXISTING OPEN SOURCE AT THIS POINT OF TIME.
Please help me with the required links / books / papers etc...
This question is way too broad to be completely answered with a single post. But if you're looking for a book to explore architectural approaches I can highly recommend the following, which in my opinion is a must-read for every developer anyway:
Patterns of Enterprise Architecture by Martin Fowler

Ontology in “semantic web”

I have been attempting to keep up to date with up to date topics in computer science, and I keep reading about the "semantic web".
From my understanding, the semantic web means the following:
1)Information on the web is given explicit meaning
2)It would be possible for web services to automatically process and integrate information available on the web.
Simple enough, Im sure there are specifics that are not covered in these points, but I am not focusing on them right now.
I also am aware of the concept of "Ontology" as a method of implementing the semantic web.
This is what Im failing to conceptualize as practical.
Is there a real world, or a practical example of what this would be like? Is there any examples of this currently being used?
One very practical "semantic" example is the Rich Snippets supported by google. See the website at: http://www.google.com/support/webmasters/bin/answer.py?answer=99170 . By embedding specific markup you can describe things like "hours of operation" for your business to the search engine. I believe that Bing and Yahoo also support this same standard.
In this case the ontology is defined by a schema.
The "Semantic Web" is really a idealisation and conceptualisation; it is a state where all data and information are represented in a way that is understandable and interpretable by machines, so that information can be retrieved precisely according to to one's intent.
The idea of a Semantic Web was proposed (and probably coined) by Tim Berners-Lee in one of his numerous seminal articles: The Semantic Web, Scientific American, May 2001, along with James Hendler and Ora Lassila. Tim founded the Semantic Web Activity in W3C, which endeavours to pursue this idealisation. Its homepage provides a brief introduction as well as several important references, shall you want to research into this topic in more depth.
Miller and Swick also wrote an introductory article on "An Overview of W3C Semantic Web Activity" in 2003. I found this article a good entry point to understanding what "Semantic Web" means.
It's a web of data. All machine readable. Here's an example, but not a real implementation. http://www.youtube.com/watch?v=RNJl9EEcsoE
Semantic web is a web that is connected in such a way that one point leads to another relevant point.In semantic web every image or data will have a meaning and will not be based on key words.
http://www.business-science-articles.com/science/articles/computer/601-semantic-web
Very brief overview can be found here.
Real world examples are out there, and there are plenty of them.
While Semantic Web was originally meant for the web, it is more useful than that. For example, it can be used to discover and build knowledge bases (expressed as ontologies). In my work context we are looking into using it for dealing with changing aspects of domain analysis, and since our perception about the domain changes (or is not yet clear at the moment), it is easier to express knowledge and some dependencies with ontologies.
The alternative could be using standard software engineering techniques, relational databases, diagrams, etc., but again, in our context (scientific and shared knowledge) it makes sense to use semantic web concepts.
The easiest way to think Semantic web is to see how it can be applied to real world scenarios.
Let's take example sentences:
1. John Smith is a professor at MIT.
2. Prof. Smith is also dean of CS.
We, humans, can easily try to relate the above two sentences. For machines, it's not possible. why? because they don't know whether John is a car,person or a street name. And whether Smith is a last name or the job title.
But what if we have following additional information somewhere in the web:
'John Smith' is a person.
a. John is first name
b. Smith is last name
c. unique address on web is http://www.example.com//person/uid/9087809812
'MIT' is university
'professor' is position at university
'Prof.' is same as 'Professor'
'Dean' is position
'CS' is acronym for 'computer science'
Now, if we have additional information (often called metadata) for each entity like above and if they can be dereferenced (i.e. if we can look up using corresponding unique address), machines can relate entities on their own. This is the vision of semantic web- to have meta information about every possible entities and create meta information following certain controlled vocabularies and logics referred to as 'ontology'.
One way to look at ontologies (very simplistic view mind you) is to just focus on the subject-predicate-triples found in ontologies themselves and then refer to some of the already published ontologies out there (many of them from the natural sciences.)
YMMV, but at least for me, the idea of the semantic web and ontologies didn't click on me until I went back to my school years and found an analogy in Prolog's rules and facts.
Using trivial examples, say you want to express information as relations in subject-predicate-object triples (disease "X" caused-by agent "Y", legal precedent "A" related-to some law "B" and so on.) This is not possible by just using keywords. So you build relations to express information, and then those relations are implemented in some machine-readable format.
Then, at least so the idea goes, these relations can be enumerable. They can be processed and people can ask questions such as: is X related to Y by relation Z? What is related to X? What is related via relation Z? You can infer new knowledge this way, specially if one uses a well-established ontology (as in the link I previously provided)...
... or so does the theory goes. It is a good concept, one that people are already putting to good use, and I think we are moving in the right direction. Time will tell if the idea is universally applicable in a practical manner.

Resources