From a5ff715fc1c4b0920c8552278665a30c3e66bd13 Mon Sep 17 00:00:00 2001
From: Susa Giogoli <su.giogoli@icloud.com>
Date: Fri, 30 Jun 2023 16:53:20 +0200
Subject: [PATCH] testing changes in readme

---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index a9c62d5..8019eed 100644
--- a/README.md
+++ b/README.md
@@ -52,10 +52,10 @@ When you're ready to make this README your own, just edit this file and use the
 Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
 
 ## Name
-Choose a self-explaining name for your project.
+OPC UA-Generation from JSON-Files
 
 ## Description
-Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
+This project can iterate JSON-Models generated for SOIL-Interfaces and convert them into an opc-ua Server. At the moment events can't be generated but Functions, parameters and structures are working fine. Our code generates the functions as empty bodies but you get a descripton and a guide on how to integrate your algorithm.  
 
 ## Badges
 On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
-- 
GitLab