LOG.DISIT.ORG is a unified solution for problems and cases such as:
1) Linked Open Data, linked data are complex structures to be understood if you just access to them for their exploitation and reuse.
A tool for browsing LD/LOD selecting relationships among URI elements and their attributes can be a solution for developer for data and knowledge engineers. Therefore, services that allow you to insert URI of LOD to navigate on their structure are very important. And the graph may bring you to other connected RDF stores via their definitions in terms of LD.
2) portals and services need to cope with relationships among Users, Contents and external sources (see for example Social Graph). Thus the users need to have a clear view about the relations among these entities to better understand context at a glance, such as:
Who has provided a given content: group, user, etc.; How a given content has been used by other users: promoted, played, uploaded, updated, etc.; Which are the geographical locations mentioned by a content, and where is located, may be connected with external geoname, and GPS coordinates; Which are the person names cited into a content: vip names related to dbPedia, users of the portals, other person names cited in many other content; Who has been contact with how, what they have done, etc. The users need to discover and navigate among these relations by selecting those of interest for each specific case.
3) Multiple SPARQL entry points. The access and browse to a RDF store via the SPARQL entry point is a way to understand the knowledge base and the relationships among the included entities. In some cases, the entities/URIs (URI(a), URI(b) ) of different RDF stores (accessible via different SPARQL entry points: URL(a) and URL(b)) may be connected each other. Typically the connection can be via URI representing classes of common ontologies and definitions. The visualization of graphs associated with URL(a),URI(a) and URL(b),URI(b) on the same screen may allow to put in evidence the relationships among these two graphs. They may be the basis for (i) integrating the two ontologies, for federating RDF storage, (ii) understand differences and relationships, and/or (iii) for creating additional connections. For example, by creating an owl:sameAsrelationship among two entities that represent the same concept in the two models. In some cases, they have not been intentionally defined by using the same vocabulary since they are different for somehow, while in other context they should be the same, otherwise deductions in the knowledge base would not take into account all needed facts.
For these cases the Linked Open Graph provides algorithms and tools to solve the problem dynamically showing the relationships and resolving connections. The Users can play with graph elements moving and zooming, turning on/off connections, filtering and expanding, exploring and playing to see more information, exploiting connection with LOD, etc. Social Graph is a simplified Linked Open Graph for social networks
Regarding the user interactions the User is able to: Expand an entity node with its relations adding them to the graph; Focus on an entity, in this case the graph is cleared and only the focused node is shown with its relations; Open, that is the play of the page or content associated with the node; use the Back button to go back to previous states of the graph (e.g. after a focus); Zoom/Pan the view; Hide/show types of relations to reduce the complexity of the graph. Search, this allow you to search your preferred entities and URI into a set of SPARQL databases. A special node is the 'More' node that is presented when in a relation are present many nodes (e.g., the content associated with a group). Save and share graphs and share with other colleagues, avoid cuplicated links, explore inbound and outbound relatiojnships, navigating on OD and LOD in a transparent manner. Work on relatioshhips you prefer. |
Try Linked Open Graph http://log.disit.org/
it works on Europeana, dbPedia, British Museum, Sii-Mobility smart city, OSIM knowledge and competence, ICARO cloud, Getty, Senato and Camera linked open data, IEEE video stanford, linked go data, all sparql 1.1
LOG can be embedded into your WEB pages. On this regard you can customize the buttons and the actions you allow at your users on the ebedded version of the LOG.disit.org tool instance and on which segement of graph starting.
Access and Query |
Access and rendering of LD |
Access and rendering URI from SPARQL entry point |
Managing Entry Points with different URL in URI. |
Multiple SPARQL entry points |
Making keyword based query |
Inspecting entry point for searching classes |
Relationships vs entities |
Showing relationships, turning on/off, singularly or globally |
Representing relationships (managing complexity) |
Discovering inbound/outbound relationships, URI and queries |
Expand all relationships |
Close all relationships |
Counting number of elements |
“sameAs” management |
Blank nodes rendering |
General Manipulation |
Undo actions performed, “back” |
Save and Load LOD graphs |
Share and collaborative LOD graphs |
Re-layouting the graph |
Focusing on an URI |
Zooming the graph |
Centering the graph |
Panning the graph with mouse/finger |
URI Details |
URI attributes (showing info or an URI) |
Map allocation of URI |
URL to resources |
Open play resources |
Representing entities |
Non Functional |
Web based tool |
Embed in web pages of third party service: ECLAP |
Graph Invoked by URL |
Paolo Nesi, paolo.nesi@unifi.it The LOG.disit.org tools is provided under dual lincense. Free of charge and open source for no profit organizations and under a license agreement for profit companies. You can embedd in your tools and web pages, you can customize according to your needs. In any case, we can improve and customize the LOG for you, according to your needs. The formal definition of the license is reported in the LOG and below
Linked Open Graph