From 036ef47598f14b8ab35c4a18bc7ed868b59d1f47 Mon Sep 17 00:00:00 2001
From: Jeffrey Phillips Freeman <jeffrey.freeman@syncleus.com>
Date: Sun, 28 Jan 2018 13:13:20 -0500
Subject: [PATCH] New translations overview.md (Danish)

---
 da/overview.md | 5 +++++
 1 file changed, 5 insertions(+)
 create mode 100644 da/overview.md

diff --git a/da/overview.md b/da/overview.md
new file mode 100644
index 00000000..5a4bfd81
--- /dev/null
+++ b/da/overview.md
@@ -0,0 +1,5 @@
+The Ferma schema is defined by a collection of interfaces and classes written by the user. Each method will interact with the underlying graph to either modify the graph in some way, or to retrieve an element or property from the graph. There are two techniques for defining how these methods behave. Either you can explicitly implement the method, or you can leave the method as abstract and annotate the method in order to allow Ferma to implement the method for you. Here we will define the annotations available to you and how they work, along with a few examples.
+
+The behavior of an annotated method is dictated not only by the annotation applied to it but also the method's signature. Therefore an annotated method will behave differently if it's return type, arguments, or even if the method name were to change. It is important to note that when a method is explicitly defined (doesnt use an annotation) then the method signature can be anything.
+
+Method names that are annotated must have one of the following prefixes: add, get, remove, set, is. Exactly which prefixes are allowed varies from one annotation to the next so see the annotation's detailed documentation to make that determination. It is also possible to override this behavior by setting the `operation` argument available on most annotations which defaults to `AUTO`.
\ No newline at end of file
-- 
GitLab