# Linked Data Aware Agent Development Framework for Mobile Devices
## 3 Linked Data Support in LDAF-M  
The linked data concept, which has been originally introduced by [PERSON] in his technical note [30], refers to best practices for publishing, interlinking and consuming machine processable data on the web. In practice, Resource Description Framework (RDF) is the data model used for publishing structured and machine processable data on the web. A dataset represented using RDF can also include links to other datasets. These links can then be followed to aggregate data from different datasets [31; 32]. To perform queries on linked data, SPARQL query language [33] is used. RDF uses triples to represent resources and their relationships. Each triple consists of a subject, predicate and an object. The subject is the resource being defined and hence is represented by a Uniform Resource Identifier (URI). On the other hand, the object in a triple may also have a Uniform Resource Identifier (URI) value, since it is possible for an object to identify other resources. Otherwise, the object part of the triple contains a literal value. The predicate plays a key role in determining the relationship of the subject and the object in the triple. Using URIs to identify resources makes it possible to represent RDF statements as a graph where nodes represent subjects and objects, and arcs represent predicates. These relationships are illustrated in Figure 5. In the figure, the upper left node is a subject representing a resource. This subject is connected via predicates to the two objects labeled as object 1 and object 2. These two objects have literal values. Object 3 that the subject is connected to is also a resource. Thus, it is connected to another literal object labeled as object 4. For example, the subject that we are defining information about may be a URI representing a faculty in a university department. Object 1 and object 2 may be strings representing name and surname for that faculty. The faculty resource may be connected to an object representing a resource about a PhD student via the \"advisorOf\" predicate. Finally, the resource representing the PhD student may be connected to an object having a string value and representing \"UniversityId\" of the student. Linked data aims to transform a current web of documents into a global information space called \"web of data\". As a result of using RDF as the common standard for publishing and linking data, the \"web of data\" emerges as a big knowledge graph. Agents are the autonomous computing entities that will process the data in the linked data environment. We think that gathering data from the linked data environment and internalizing that data as an agent's beliefs is one of the most important requirements that should be fulfilled in order to establish a connection between agents and linked data. Since data is gathered from the linked data environment by parsing the RDF documents, we need a graph based data model that will be used for representing the RDF triples internally in an agent. Figure 5: Resource Description Framework (RDF) statements on a graph data structure. Within the BDI architecture of LDAF-M, everything that an agent believes about its environment, including knowledge about other agents, is represented by the belief component. Any LDAF-M agent firstly obtains data from its environment. Subsequently, it associates a significant part of the obtained data with the belief component it contains. On the other hand, a LDAF-M agent can also obtain data from resources which have been developed in accordance with the principles of the linked data. Initially, a LDAF-M agent has been designed and implemented so that it can take its beliefs from Freebase [34]. Freebase provides documents and their relations expressed following the linked data principles. However, the belief component and architecture of LDAF-M has been designed and developed in such a flexible structure that data from other linked data sources such as DBpedia can also be obtained by easily integrating the necessary implementation to the system.