Alvaro Graves Department of Cognitive Sciences Rensselaer Polytechnic Institute, Troy, NY 12180, USA gravea3@rpi.eduAbstractOne One aspect of the Semantic Web that has not been fully explored is the idea of ​​good interfaces for interacting with small pieces of semantic information, particularly with a few sets of triples. While more and more data has been published in RDF, it usually comes from existing databases. On the other hand, microblogging sites like Twitter have gained great popularity in the media and have become a major player in the so-called social networks. In this article we propose the reuse of several components of the Twitter syntax to help developers and designers develop user-friendly interfaces based on a syntax that people can easily recognize and from which semantics can be expressed.1 MotivationSemantic Web tools enable users to interact with data in multiple ways: you can store data in three stores, such as 4store, Virtuoso, AllegroGraph and others. You can also query this data using SPARQL and develop programs that manipulate this data by leveraging a plethora of frameworks and libraries for different programming languages ​​and platforms. It is also possible to design ontologies using editors such as Protege and Swoop, among others. However, as far as we know, there is no intuitive way to handle triples one by one. More generally, it is unclear whether there is a way to manipulate triples for (relatively) non-technical advanced users. It is in this scenario that microblogging sites appear as an interesting opportunity to express semantics on a human scale. There are several reasons why this is possible:1. The concept of microblogging short me... middle of paper... creating agents who will "listen" to these messages and act according to the semantics contained in them. Furthermore, it can help users express semantics by leveraging existing platforms for posting messages. Additionally, allowing users to publish just a few triples allows people to correct and maintain information on datasets without the need to own hosting. For future work, there is a clear need for user-friendly interfaces to simplify the Switter writing process. Although the proposed syntax is focused on readability, we believe that it is still difficult to remember the names of the predicates for the novice user. Interfaces that suggest predicates to use and show the different namespaces (and their meanings) available can greatly improve Switter adoption. Finally, a formal specification is needed to allow developers to create their own applications that support SWitter.