├── 201801020916 Using tags in The Archive.md ├── 201801020929 Finding notes in The Archive.md ├── 201705120848 An omnibar to rule them all.md ├── 201705110829 Saved Searches.md ├── 201705120916 Our reasons for Software Agnosticism.md ├── 201705110850 The nv-Core.md ├── 201705110828 The Archive App.md ├── 201705091531 Connections of notes.md ├── 201801231551 Links to remote control The Archive.md ├── 201705091535 Direct Links as Wiki-Links.md ├── README.md ├── 201801020926 Creating notes in The Archive.md ├── 201705120913 The plain text approach.md ├── 201801232029 Note identifiers and The Archive.md ├── 201705221802 Integrated Image Capturing Tool.md ├── 201705180836 Structure notes.md ├── 201705120948 Tags in The Archive.md ├── 201705110956 History of the Method.md ├── 201801231614 Markdown.md ├── 201705111034 Luhmanns Zettelkasten.md ├── 201705180756 How to tag properly.md ├── 201705120915 Software-agnostic Programming.md └── LICENSE /201801020916 Using tags in The Archive.md: -------------------------------------------------------------------------------- 1 | # 201801020916 Using tags in The Archive 2 | #tags #archiveapp-demo 3 | 4 | Tags are nothing but a saved search. If you click on #archive you will search for all notes that contain `#archive`. 5 | -------------------------------------------------------------------------------- /201801020929 Finding notes in The Archive.md: -------------------------------------------------------------------------------- 1 | # 201801020929 Finding notes in The Archive 2 | #archiveapp-demo #finding 3 | 4 | You can find your notes in different ways: 5 | 6 | 1. You can make a full text search in the Omnibar. 7 | 2. You can search for a tag in the Omnibar. 8 | 3. You can search for an ID in the Omnibar. 9 | 10 | Everything is in the Omnibar. Simple and fast. 11 | -------------------------------------------------------------------------------- /201705120848 An omnibar to rule them all.md: -------------------------------------------------------------------------------- 1 | # 201705120848 An Omnibar to rule them all 2 | #archiveapp-demo #search 3 | 4 | The Omnibar is the place to interact with your archive. It's the search-and-create box at the top of the app, similar to a web browser. 5 | 6 | Imagine *The Archive* as a remote control for your directory of plain text files. Familiarize yourself with the shortcut to access the Omnibar quickly from anywhere: ⌘L. You'll need this a lot to navigate in your archive. 7 | 8 | When the Omnibar is focused, you can use the arrow keys to navigate around in the list of found notes. No need to click inside the search result list with the mouse. Hit Tab to get back to the note editor quickly. 9 | -------------------------------------------------------------------------------- /201705110829 Saved Searches.md: -------------------------------------------------------------------------------- 1 | # 201705110829 Saved Searches 2 | #search #archiveapp-demo 3 | 4 | Saved searches are one of the advancements from the nv-Core.[[201705110850]] 5 | 6 | While working with nvALT, we recognized that we performed the same searches over and over again. A good example is a search for tags [[201705120948]] that concern your current writing project. You will want to get back to the same collection of notes again and again, repeating the search all the time. 7 | 8 | Remember the importance of speed we mentioned in the note about the nv-Core? Speed is one of the central paradigms we used to make decisions about this app's features, and saved searches are a great help. 9 | 10 | For every step you do repeatedly, there ought to be a fast solution or you will cease to use this solution. This is one reason, by the way, why some apps don't *feel* right. They repeatedly force us into clunky work flows. 11 | -------------------------------------------------------------------------------- /201705120916 Our reasons for Software Agnosticism.md: -------------------------------------------------------------------------------- 1 | # 201705120916 Our reasons for Software Agnosticism 2 | #archiveapp-demo #software 3 | 4 | We believe that there is one simple reason to adhere to software agnostic programming as the very best approach to software development: the developer is not primarily motivated by fulfillment of his own desires. It forces developers to give up vendor lock-in and favor open standards and open formats. It means that you are willing to lose users and therefore money and reputation. 5 | 6 | In other words: it puts the end user's interests first, and the business and the developer second. 7 | 8 | Sure, computer users say they want dead simple apps where they don't have to learn anything to complete a task. But this does not serve them well. Removing all resistance will not make them smarter, better, or at the very least keep their data usable. (See why we think the plain text approach is superior. [[201705120913]]) 9 | -------------------------------------------------------------------------------- /201705110850 The nv-Core.md: -------------------------------------------------------------------------------- 1 | # 201705110850 The nv-Core 2 | #nvALT #archiveapp-demo 3 | 4 | The core of our app is derived from [Notational Velocity][nv] and its popular fork, [nvALT][]. Why? It is the fastest app for note taking. We used the nvALT branch during recent years. The "nv" core delivers the speed and ease of use to the archive. 5 | 6 | We stand on the shoulders of giants and make it a point to honor the ancestors of the archive. 7 | 8 | [nv]: http://notational.net/ 9 | [nvalt]: http://brettterpstra.com/projects/nvalt/ 10 | 11 | Why is speed so important? The reason is found in basic psychology. The more you do something the more important small aspects become. I don't mind losing a second or two when I wait for the bus. I don't do it very often. But a second or two can be **a lot** when it comes to repeating steps in the archive. 12 | 13 | Speed is important because it is one of the main determinants on how smooth the app can bend around your actions. 14 | 15 | -------------------------------------------------------------------------------- /201705110828 The Archive App.md: -------------------------------------------------------------------------------- 1 | # 201705110828 The Archive App 2 | #archiveapp-demo 3 | 4 | ## Origins of The Archive App 5 | 6 | History of the Method.................................[[201705110956]] 7 | Luhmann's Zettelkasten................................[[201705111034]] 8 | 9 | ## Understanding The Archive App 10 | 11 | Creating Notes........................................[[201801020926]] 12 | Finding Notes.........................................[[201801020929]] 13 | An Omnibar to Rule Them All...........................[[201705120848]] 14 | Note IDs..............................................[[201801232029]] 15 | Tags..................................................[[201801020916]] 16 | Saved Searches........................................[[201705110829]] 17 | Integrated Image Capture Tool.........................[[201705221802]] 18 | Connecting Notes......................................[[201705091531]] 19 | 20 | ## Software Agnosticism 21 | 22 | The Concept of Software Agnostic Programming..........[[201705120915]] 23 | The Plain Text Approach...............................[[201705120913]] 24 | -------------------------------------------------------------------------------- /201705091531 Connections of notes.md: -------------------------------------------------------------------------------- 1 | # 201705091531 Connections of notes 2 | #archiveapp-demo #connection #note #ZettelkastenMethod 3 | 4 | One if not *the* main principle of a Zettelkasten is the principle of connection. 5 | 6 | There are typically three entities mentioned: 7 | 8 | 1. Data 9 | 2. Information 10 | 3. Knowledge 11 | 12 | There are in a hierarchy with data being the simplest and knowledge the most sophisticated. One of the big questions out there is: How can you get from data to information to knowledge? 13 | 14 | Every attempt to answer this questions has one thing in common: Connection. 15 | 16 | 1. What to connect Data, Information, Knowledge? 17 | 2. How to connect Data, Information, Knowledge? 18 | 19 | While we don't have a theoretical answer to this theoretical question we can give the practical solution to knowledge work with quite robust confidence: Make connection possibel. 20 | 21 | There are different types of connection: 22 | 23 | 1. Direct links..................... [[201705091535]] 24 | 2. tags (ref. tagcloud)............. [[201705120948]] 25 | 3. structure notes.................. [[201705180836]] -------------------------------------------------------------------------------- /201801231551 Links to remote control The Archive.md: -------------------------------------------------------------------------------- 1 | # 201801231551 Links to remote control The Archive 2 | #automation 3 | 4 | First, remember that we suggest to stick to the plain text approach and use IDs to reference your Zettel notes from external sources, like digital Mind-Maps or spreadsheets. Sticking to IDs instead of application-specific features prevents you from suffering from app lock-in effects. See [[201705120915 Software-agnostic programming]]. 5 | 6 | That being said, if you want to write scripts that remote control *The Archive*, or if you want to insert clickable links in other applications to open a note in this app, you can use the built-in URL scheme for these purposes: 7 | 8 | - `thearchive://search/SEARCH_TERM` will filter your list of notes just like a manual search for "SEARCH_TERM" would; it behaves like clicking on `#hashtags`. 9 | - `thearchive://match/TERM` will filter your list of notes *and* open a note that starts with "TERM", if any; it behaves like clicking on `[[WikiLinks]]`. 10 | - `thearchive://matchOrCreate/TERM` will behave like `match` but creates a note called "TERM" if no match was found; it behaves like searching for "TERM" and then hitting return to create a new note. 11 | -------------------------------------------------------------------------------- /201705091535 Direct Links as Wiki-Links.md: -------------------------------------------------------------------------------- 1 | # 201705091535 Direct Links as Wiki-Links 2 | #connection #link #ZettelkastenMethod #archiveapp-demo 3 | 4 | In *The Archive*, if you put an ID in double brackets you create a direct link to the note that starts with the ID.[[201801232029]] All double brackets with IDs in them you have encountered so far are basically a clickable search in *The Archive*, selecting the best literal match of the search term to display by default. 5 | 6 | The search results include all the notes that refer to this particular target. For example: If you search for `201705091535` by clicking on [[201705091535]], the search results include two notes: 7 | 8 | 1. This note. You searched for it. 9 | 2. "Connection of notes". That note refers to this note. It contains the ID in double brackets, as `[[201705091535]]`. 10 | 11 | This means that a direct link refers to a particular note via its ID and shows you all the backlinks to that note. This gives you a bit of an overview for the context of the searched note. This context will become handy when your archive grows and navigating in it becomes harder. 12 | 13 | Since double bracketed links are performing a search under the hood, you can put the whole title in double brackets, too, like this: [[201705091531 Connections of notes]] 14 | 15 | You can also create links into The Archive from other applications using the built-in URL scheme.[[201801231551]] 16 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # The Archive: A Demo Zettelkasten 2 | 3 | A small Zettelkasten of interconnected notes about the Zettelkasten Method and [The Archive](https://zettelkasten.de/the-archive/) 4 | 5 | 6 | 7 | ## License 8 | 9 | Creative Commons License
The Archive Demo Zettelkasten by Sascha Fast and Christian Tietze is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.
Based on a work at https://github.com/Zettelkasten-Method/The-Archive-Demo-Notes/. 10 | 11 | This work is licensed under the Creative Commons Attribution-ShareAlike 4.0 International License. To view a copy of this license, see [the LICENSE file](LICENSE) or visit http://creativecommons.org/licenses/by-sa/4.0/ or send a letter to Creative Commons, PO Box 1866, Mountain View, CA 94042, USA. -------------------------------------------------------------------------------- /201801020926 Creating notes in The Archive.md: -------------------------------------------------------------------------------- 1 | # 201801020926 Creating notes in The Archive 2 | #archive #creation 3 | 4 | There are a different ways to create a note, each with pros and cons depending on your workflow. 5 | 6 | 1. Type the note title you want into the Omnibar and hit the return key. If you type a term in the Omnibar that is not used as the name of a note already, *The Archive* will create a matching note for you; if a note exists, it will be opened instead. 7 | 2. Use a Wiki-Link: create a link that leads nowhere, click on it to follow the link, then create a note from the Omnibar as in (2).[[201705091535]] The Wiki-link feature is built on top of the search. Similar rules apply to entering a term in the Omnibar: if a note with the linked text exists, it will be displayed for you. If there is no matching note, you can hit the return key from within the Omnibar to create a note with the title set to the search term. 8 | 3. Create an empty note in *The Archive* without changing your search. Just hit ⌘N (or pick 'Note > New' from the menu). The Archive will create a note for you that will be named "Untitled" and take you right into the editor. After you complete the note you can rename it by hitting ⌘R (or via 'Note > Rename' from the main menu). 9 | 4. Use the "Quick Entry" popup window from anywhere on your system to capture a thought. You have to configure the shortcut in the application preferences (⌘,) to make it globally accessible. 10 | -------------------------------------------------------------------------------- /201705120913 The plain text approach.md: -------------------------------------------------------------------------------- 1 | # 201705120913 The plain text approach 2 | #archiveapp-demo #plaintext #ZettelkastenMethod 3 | 4 | This is one of biggest differences from other note taking applications. `.txt` files are not just the way *The Archive* stores your stuff. There simply is nothing else to this app than the text files. 5 | 6 | Did you ever wonder why we don't use Finder file metadata for tagging but decided to use hashtags in the file? 7 | 8 | 1. Text is the most robust way to store data. It is ultimately transferable to all operating systems. 9 | 2. There are many ways to manipulate text files. Text editors for manual manipulation is just one of them. You can also easily automate workflows and write scripts with simple programming languages like Ruby or Python. 10 | 3. Text files gives *you* total control. We highly recommend to keep it that way. Don't use any app that stores things differently. That would imprison you and make a change of apps or operating systems quite complicated, also known as "vendor lock-in". A bunch of text files is easiest to transfer. Just copy & paste. 11 | 12 | The plain text approach offers you the best of speed, flexibility, and control over your knowledge. It forces you to learn how to manipulate text *as text*. Text is the most important and most widely used container of knowledge out there. That means: Whatever you want to do with your knowledge on a computer, ask yourself: "How can I do this with mere text files?" Once you get the hang of it, you'll be surprised! 13 | -------------------------------------------------------------------------------- /201801232029 Note identifiers and The Archive.md: -------------------------------------------------------------------------------- 1 | # 201801232029 Note identifiers and The Archive 2 | #id #archiveapp-demo 3 | 4 | To create links between notes, you need to define how to *target* a note first. On the web, it is simple: each website has its own unique address that you can copy from the address bar of your web browser. 5 | 6 | When you work with plain text files [[201705120913]], it might sound obvious to use the file names. And if you want to have clickable links, you might use the full path to a note, like `file:///Users/JaneDoe/Archive/some-note.txt`. But that's fragile, since the links break when you rename the note or move your archive to a different path. 7 | 8 | This is how we do it: every Zettel note gets its own unique ID. We choose the timestamp-like IDs like `201402260939` which would be based on the date and time "2014-02-26 9:39a.m." Moments in time a unique and offer a guaranteed uniqueness. The ID is fixed, the title may change over time. 9 | 10 | When you reference a note from someplace else, you paste the ID there. You will soon learn to recognize such sequences of digits as IDs because of the way they look. Then you know, "there's a Zettel with this ID, I should check it out!" 11 | 12 | *The Archive* tries to be helpful and offers these nifty [[201705091535 Direct Links as Wiki-Links]]. Adhering to the double-square-bracket convention of wikis, you get clickable links using Zettel IDs without buying into any proprietary file format or fragile file paths. 13 | 14 | Further reading on our blog: https://zettelkasten.de/posts/add-identity/ 15 | -------------------------------------------------------------------------------- /201705221802 Integrated Image Capturing Tool.md: -------------------------------------------------------------------------------- 1 | # 201705221802 Integrated Image Capturing Tool 2 | #images #archiveapp-demo 3 | 4 | The image capturing tool (⌥⌘M) is for integration of images into your workflow. Especially, if you draw a diagram or something similar. 5 | 6 | You should draw. Drawing is good for your brain and it improves your productivity.[^1][^2] Images are *the* way to capture flows, systems, and wholeness in general. But drawing with the mouse or the trackpad is pesky and very few people have a pen tablet. So you're better off drawing with pen and paper. Also, in general, drawing by hand is faster, more precise, more engaging and more fun. 7 | 8 | The image capturing tool is a shortcut from your real-world desk into your digital archive. 9 | 10 | Before *The Archive*, users would have had to take pictures with their phones, pair them with their Mac, move the image file into the right directory, and finally add a the Markdown [[201801231614]] syntax. Now, you can just take the damn picture and have it where you need it. 11 | 12 | Remember the importance of speed? [[201705110850]] The image capturing tool, in all it's beautiful simplicity, is another factor to reduce friction and increase speed. Image capturing allows you to integrate your pencil and your keyboard. 13 | 14 | Try it yourself: Select "Edit > Capture Image..." and insert a photo from a drawing in this note! 15 | 16 | 17 | 18 | [^1]: Manfred Spitzer (2012): Digitale Demenz. Wie wir uns und unsere Kinder um den Verstand bringen, München: Kroemer. 19 | 20 | [^2]: Pam A. Mueller and Daniel M. Oppenheimer (2014): The Pen Is Mightier Than the Keyboard, Psychological Science 6, 2014, Vol. 25, S. 1159-1168. -------------------------------------------------------------------------------- /201705180836 Structure notes.md: -------------------------------------------------------------------------------- 1 | # 201705180836 Structure notes 2 | #StructureNotes #archiveapp-demo 3 | 4 | Structure notes are a big cornerstone of the Zettelkasten Method. The bigger the archive gets, the more important they become. A good example for a structure note is the overview for this app: [[201705110828]] 5 | 6 | Structure notes do not contain any new content on their own. They also do not simply list all the notes that are important for some purpose. A structure note's intent is to provide a good overview over a topic -- structure it. 7 | 8 | Sometimes, structure notes grow naturally. For example, you have a regular note, edit it a lot and add more links to related details to it. Meanwhile, you extract the original contents of this note into new notes, thinning it out and leaving mostly links behind. This regular note one day appears to have become a hub to direct you to detail notes more than a piece of content. 9 | 10 | **Example:** Sascha had an idea about the definition of modernity. Modernity marks the end of a delayed coupling of work and gratification. He did research on this topic and ended up using much of it as evidence for the validity of this claim. The tiny note that at first contained the definition of modernity grew a lot over time and became difficult to use. Sascha cleaned it up and made it a structure note about the note cluster on modernity. 11 | 12 | Sometimes, you can predict without doubt that you will be working on a topic a lot. Then do not wait until a structure note emerges naturally. Begin with a structure note right from the start as the hub for your upcoming topic notes. This is how this whole introduction into *The Archive* got started, too: as an overview of topics that were then fleshed out. 13 | -------------------------------------------------------------------------------- /201705120948 Tags in The Archive.md: -------------------------------------------------------------------------------- 1 | # 201705120948 Tags in The Archive 2 | #tags #archiveapp-demo 3 | 4 | Tags are another way to make connections between notes. They are not the main way to organize knowledge. They give you an unsorted list of notes for a particular subject. *The Archive* supports the `#hashtag` convention to make tags clickable, but you can use anything to denote a tag. Remember that at the core, it's all just text.[[201705120913]] 5 | 6 | We have to mention their limitations first because of the wide-spread misconception that tags are the way to go. Connection is a big thing in knowledge work: Every attempt to go from raw data to information to knowledge depends on connecting parts to form a new whole. 7 | 8 | **Example 1:** If you craft an argument, you put together statements in a specific manner so that at least one is the premise and another is the conclusion. The new wholeness and its structure are now capable of serving as an argument. There statements are not independent anymore. 9 | 10 | **Example 2:** If you have collected a lots of data you look for patterns that connect the data points. If the patterns turn out to be meaningful, you will have created information. 11 | 12 | The more rigor you apply to the connections the better this process works. Imagine you ask someone for directions. He roughly waves his arm to the north as a response. This is not very useful information although it is something to work with. But if he points exactly to your destination and gives you a brief overview of the path ahead with his smartphone -- now we are talking. 13 | 14 | Tags are similar to waving an arm in a broad direction. Direct links are precise pointers to specific locations. 15 | 16 | But don't disregard tags completely. They are super useful *when* you don't want specific directions. [[201705180756 How to tag properly]] 17 | -------------------------------------------------------------------------------- /201705110956 History of the Method.md: -------------------------------------------------------------------------------- 1 | # 201705110956 History of the Method 2 | #archiveapp-demo #Luhmann #ZettelkastenMethod #written-by-sascha 3 | 4 | Luhmann is not the first person who used a note archive called *Zettelkasten*. But he surely is the godfather of our method to knowledge work. 5 | 6 | ## Beginnings of Christian's and my eternal friendship (no homo but with occasional ambush) 7 | 8 | Christian and I met for the first time in university. Our connection: The search for a method to handle the knowledge we gather during our studies. While Christian leaned more to the technical side I researched more from a historical science perspective. He searched for software and other technical solutions. I researched on how others solved this problem. 9 | 10 | But we both had on thing in common. Luhmanns approach seemed to be genious and we took it as the prototype for our own solutions. See the note on Luhmanns Zettelkasten: [[201705111034]] 11 | 12 | ## The development of a unified method 13 | 14 | In the beginning, we used quite different approaches. The biggest difference was that Christian used the plain text approach but I didn't. I was still caught up in the idea that an app will solve this problem. But nevertheless I did work on a theory of knowledge work and applied what I learned studying philosophy of knowledge. 15 | 16 | Together this layed out the groundwork for a **method**. The Zettelkasten Method goes way beyond this app. It is the realization of general knowledge work principles. It is designed to work with most texteditors. Of course, this is the best one. After all, we designed it for knowledge work. 17 | 18 | The numbers you see in double-brackets everywhere are the IDs. Don't worry, I will introduce you to the core of the method in some later notes. I started with the system Luhmann used; Christian already used time-stamps but with very much clutter. 19 | 20 | Me: 1a23f,1 21 | Christian: 2008-09-07_0445_T1-2 22 | 23 | You immediatly see how clunkiness our first approaches. We boiled it down and down and down. Until we were both to the point we couldn't simplify the ID any further without loosing important functions. -------------------------------------------------------------------------------- /201801231614 Markdown.md: -------------------------------------------------------------------------------- 1 | # 201801231614 Markdown 2 | #markdown #plaintext #archiveapp-demo 3 | 4 | *The Archive* is a plain text note editor, but it highlights Markdown-Syntax. This means you can use the Markdown convention of marking up text. This can guide your eye when you scan notes, and it can ease exporting your notes into various formats for publishing on the web or in print. 5 | 6 | For a full documentation see this website from the creator of markdown: https://daringfireball.net/projects/markdown/basics 7 | 8 | ## Basic textual markup 9 | 10 | The line above demonstrates a level 2 heading. The more hashes you add, the deeper level of the heading is. This is useful to structure longer text but not used that often in notes. 11 | 12 | - Lists are useful. 13 | - They are especially useful when list items get longer, as *The Archive* wraps the lines around and adds indentation to guide your eye along the list when you read. 14 | 1. Nested lists work, too. 15 | 2. And, as you see, you can number items to make the list an ordered list instead of an unordered list. 16 | - And so you may start an overview. 17 | 18 | You separate paragraphs of text with empty lines, not just with single line breaks. Inside paragraphs, you can **embolden parts of text** like this to really stress something, or *italicize text* for a much milder emphasis. Or you ***Italicize emboldened text*** for maximum emphasis. Shouting in all caps is optional and not recommended during office hours. Be smart and *emphasize* with style. 19 | 20 | If you want to add code or put something that would be recognized as Markdown in verbatim, `you can use backticks, disabling *emphasis*, too`. 21 | 22 | Quoted from the Markdown guide: 23 | 24 | > Blockquotes are indicated using email-style ‘>’ angle brackets. 25 | 26 | ## Code blocks 27 | 28 | Then there's verbatim or "code" blocks, 29 | 30 | either by block-indenting text with 4 spaces 31 | or a tabulator, 32 | 33 | or you can use 34 | 35 | ``` 36 | GitHub-style code fences to ease copy & pasting. 37 | ``` 38 | 39 | Themes for *The Archive* are recommended to use monospace fonts. Monospace fonts are very predictable which is useful for lists, tables and more. 40 | -------------------------------------------------------------------------------- /201705111034 Luhmanns Zettelkasten.md: -------------------------------------------------------------------------------- 1 | # 201705111034 Luhmanns Zettelkasten 2 | #Luhmann #Zettelkasten #archiveapp-demo 3 | 4 | Luhmann is the unquestioned godfather of the Zettelkasten Method. Yes, there are others who used Zettelkasten archives. But Luhmann is the first one who used a hypertext approach and let go of irrational urges of control. And he did all of this on paper. 5 | 6 | He made the big change that every note had a fixed position. Other Zettelkasten users had a system of categories that allowed to shuffle the notes within the categories freely. Luhmann assinged a unique ID to every note that never changed and that expressed its placement between other notes: The first note had the ID `1`, the second note hat the ID `2`. If he now wrote a note that should branch off from `1` he gave it the ID `1a` and put it right after `1`. If he'd continue this new note on the same level, he would add with `1b` and could branch off again with `1a1`. 7 | 8 | This led to the first of Luhmann's principles: A **flexible branching capability**. The archive grows along the train of thoughts organically and is not pre-determined by a system of fixed categories. Categories are problematic because you have to choose them before you start, but at that point you do not have a clue where the journey will be taking you. (If you knew in advance, it would not be creative knowledge work.) 9 | 10 | The second principle is **connectivity**. With IDs and fixed positions, you can link from one note to another. If the position in the archive would be able to change, the link would break because you couldn't find the note again. Remember: We are talking about paper. :) Luhmann had 66.000 notes in his second archive, by the way. No chance of even finding something that got filed at the wrong position. 11 | 12 | The third principle is to be having a **register**. This was the first entrance for Luhmann when he wanted to get started communicating with his archive. For our purposes, this is not important. We have full text search and also can search for tags directly in our archive. 13 | 14 | If you want to read a translation of Luhmann's article "Kommunikation mit Zettelkästen", where he talks about his method, written by [Manfred Kuehn][mk], follow this link: 15 | 16 | [mk]: http://takingnotenow.blogspot.com/ "Blog of Prof. Manfred Kuehn" 17 | -------------------------------------------------------------------------------- /201705180756 How to tag properly.md: -------------------------------------------------------------------------------- 1 | # 201705180756 How to tag properly 2 | #tags #archiveapp-demo 3 | 4 | There are three types of tags: 5 | 6 | 1. **Topic tags.** They connect a note to a specific topic. A note about health issues of eating grains can be tagged with "nutrition". The note is not specifically about nutrition itself but falls under the broader topic. 7 | 2. **Ontology tags.** They connect a note to a specific concept. If you write a note about the importance of healthy eating habits and tag it with "nutrition" you connected the note to the concept of nutrition itself. The note about health issues of eating grains has an ontology tag of "grains". 8 | 3. **Project tags.** They connect notes under the umbrella of a specific project. If you write an essay on the first World War I you could tag notes with "ww1" if they are relevant to this essay. If you write a book on healthy diets, you can tag the above mentioned notes with "mybestdietadvice". The tag #archiveapp-demo would count as a project tag. 9 | 10 | There are several issues to consider: 11 | 12 | ## Mainly Be Using Ontology Tags 13 | 14 | If you use topic tags a lot, you will run into problems once your archive grows. 15 | 16 | Unless it is a very specific topic, you soon will get too many results. If you search for a tag, you are interested what you have written about the concept and not everything that could be related to it. 17 | 18 | The proper way to capture topics in your archive is via structure notes. See: [[201705180836]] 19 | 20 | ## Use Project Tags Only As a First Approach -- But Nothing More 21 | 22 | The best way to write with any note archive is via the outline method. This is true for every software you use. Solely depending on project tags is a lazy approach that will punish you later. Use the Outline Method instead. Learn about the outline method on our blog: 23 | 24 | Project tags are useful when you start a new project and want to collect a bunch of relevant notes. But in the long run, too many unsorted notes will accumulate. Use a structure note [[2017051808]] to organize your project instead. Then put links to your notes into an outline. See: [[201705110828]] 25 | 26 | Another great use of project tags is to mark the top structure notes of a very complex project, like the structure notes for a book. Use your project tag for every structure note of the project's chapters. Then you can jump to these chapter notes quickly using the search instead of clicking your way through the archive from the main project note. 27 | -------------------------------------------------------------------------------- /201705120915 Software-agnostic Programming.md: -------------------------------------------------------------------------------- 1 | # 201705120915 Software-agnostic Programming 2 | #software #archiveapp-demo 3 | 4 | While the theoretical framework of this paradigm is quite complicated, its application and goal are very easy to grasp. 5 | 6 | ## The Goal 7 | 8 | 9 | 10 | As a developer, you want to create a solution to a real problem as software. It is not about creating software in itself. It is not that you create software that merely enables new actions, like tech demos, without any end in mind. 11 | 12 | That means that the software in itself does not contain the solution. Take this app for example. It is a sophisticated plain text editor. It allows for fast actions. But the solution to knowledge work is the Zettelkasten Method. We think that *The Archive* is the best solution because we optimize it to fit this problem. 13 | 14 | It is our job to understand knowledge work to its core and work on the method behind the software. It is more about the method than about the software. 15 | 16 | Think about *Getting Things Done*. If you had to pick, would you rather have developed this method of self management or programmed an app? GTD spawned a plethora of apps but no app solves the underlying problem on its own. 17 | 18 | ## Some Consequences and Practical Application 19 | 20 | 1. As a developer, you let the user pick the best software to solve a problem, not necessarily your own. 21 | 2. Open formats enable collaboration between user inventions and developers. 22 | 3. Domain knowledge and skin in the game are key to good decision-making. 23 | 24 | ### 1. Let the User Pick 25 | 26 | Every problem already has a ton of software attempts at a solution. If you are honestly interested in the solution to a problem, you allow your users to choose their means, to pick which software they want to use and to switch with minimum effort. 27 | 28 | **Example:** We believe that the plain text approach is the mightiest to store text. It enables maximal mobility of the user's data between different apps. With plain text, you can use the widest variety of apps and even operating systems. 29 | 30 | This produces very basic rules: 31 | 32 | 1. Save text as plain text. 33 | 2. Save images as images. 34 | 3. Do not use any storage system that differ from the files you want to store. 35 | 36 | If software violates these rules it imprisons the user. That is not about solving a problem but locking-in users. 37 | 38 | ### 2. Open Formats 39 | 40 | A good user is a good problem solver. The software should take this into account and allow user from different levels of expertise to contribute to the pool of problem solutions. 41 | 42 | **Example:** Because we use a plain text data storage, you can easily manipulate your data with various script languages. That's why we plan to integrate a scripting interface into *The Archive* to speed this up. User who cannot code are still able to use and combine scripts by other people for a variety of use cases. 43 | 44 | The fun thing is that both the user and the developer can learn from each other and work together on a solution. Usually, though, the situation ends with a powerless user sending in complaints to developers, and developers lacking the empathy to understand less experienced end users' demands. 45 | 46 | ### 3. Skin in the Game 47 | 48 | Objectively, there are better solutions and there are worse. You can argue about some individual differences but that doesn't brush away the fact that some solutions are just plain better than others. 49 | 50 | Good software contains not just features that users wish for. Sometimes, users are wrong. As a software developer, you have to be an expert not only in software development but also in the domain in which you try to solve a problem. That means: You have to have skin in the game to make good software. 51 | 52 | **Example:** We are using a Zettelkasten over half a decade now. Sascha did extensive research on the subject of knowledge work and writes all day, every day. Christian is using the method for an even longer period of time, albeit less intense than Sascha. He has to code stuff like this app, after all. We eat our own dog food. This experience and skin in the game gives us some authority to reject proposed solutions with a reason. It is rare that we are confronted with a proposal of a feature that we didn't already test to oblivion. 53 | 54 | Of course you will make mistakes. But with skin in the game and the habit of learning about the topic, developers can more easily take ownership of the product and its coming-about. This results in the required self-esteem to say "No" to user requests *and* to admit when one has misjudged something. 55 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Attribution-ShareAlike 4.0 International 2 | 3 | ======================================================================= 4 | 5 | Creative Commons Corporation ("Creative Commons") is not a law firm and 6 | does not provide legal services or legal advice. Distribution of 7 | Creative Commons public licenses does not create a lawyer-client or 8 | other relationship. Creative Commons makes its licenses and related 9 | information available on an "as-is" basis. Creative Commons gives no 10 | warranties regarding its licenses, any material licensed under their 11 | terms and conditions, or any related information. Creative Commons 12 | disclaims all liability for damages resulting from their use to the 13 | fullest extent possible. 14 | 15 | Using Creative Commons Public Licenses 16 | 17 | Creative Commons public licenses provide a standard set of terms and 18 | conditions that creators and other rights holders may use to share 19 | original works of authorship and other material subject to copyright 20 | and certain other rights specified in the public license below. The 21 | following considerations are for informational purposes only, are not 22 | exhaustive, and do not form part of our licenses. 23 | 24 | Considerations for licensors: Our public licenses are 25 | intended for use by those authorized to give the public 26 | permission to use material in ways otherwise restricted by 27 | copyright and certain other rights. Our licenses are 28 | irrevocable. Licensors should read and understand the terms 29 | and conditions of the license they choose before applying it. 30 | Licensors should also secure all rights necessary before 31 | applying our licenses so that the public can reuse the 32 | material as expected. Licensors should clearly mark any 33 | material not subject to the license. This includes other CC- 34 | licensed material, or material used under an exception or 35 | limitation to copyright. More considerations for licensors: 36 | wiki.creativecommons.org/Considerations_for_licensors 37 | 38 | Considerations for the public: By using one of our public 39 | licenses, a licensor grants the public permission to use the 40 | licensed material under specified terms and conditions. If 41 | the licensor's permission is not necessary for any reason--for 42 | example, because of any applicable exception or limitation to 43 | copyright--then that use is not regulated by the license. Our 44 | licenses grant only permissions under copyright and certain 45 | other rights that a licensor has authority to grant. Use of 46 | the licensed material may still be restricted for other 47 | reasons, including because others have copyright or other 48 | rights in the material. A licensor may make special requests, 49 | such as asking that all changes be marked or described. 50 | Although not required by our licenses, you are encouraged to 51 | respect those requests where reasonable. More_considerations 52 | for the public: 53 | wiki.creativecommons.org/Considerations_for_licensees 54 | 55 | ======================================================================= 56 | 57 | Creative Commons Attribution-ShareAlike 4.0 International Public 58 | License 59 | 60 | By exercising the Licensed Rights (defined below), You accept and agree 61 | to be bound by the terms and conditions of this Creative Commons 62 | Attribution-ShareAlike 4.0 International Public License ("Public 63 | License"). To the extent this Public License may be interpreted as a 64 | contract, You are granted the Licensed Rights in consideration of Your 65 | acceptance of these terms and conditions, and the Licensor grants You 66 | such rights in consideration of benefits the Licensor receives from 67 | making the Licensed Material available under these terms and 68 | conditions. 69 | 70 | 71 | Section 1 -- Definitions. 72 | 73 | a. Adapted Material means material subject to Copyright and Similar 74 | Rights that is derived from or based upon the Licensed Material 75 | and in which the Licensed Material is translated, altered, 76 | arranged, transformed, or otherwise modified in a manner requiring 77 | permission under the Copyright and Similar Rights held by the 78 | Licensor. For purposes of this Public License, where the Licensed 79 | Material is a musical work, performance, or sound recording, 80 | Adapted Material is always produced where the Licensed Material is 81 | synched in timed relation with a moving image. 82 | 83 | b. Adapter's License means the license You apply to Your Copyright 84 | and Similar Rights in Your contributions to Adapted Material in 85 | accordance with the terms and conditions of this Public License. 86 | 87 | c. BY-SA Compatible License means a license listed at 88 | creativecommons.org/compatiblelicenses, approved by Creative 89 | Commons as essentially the equivalent of this Public License. 90 | 91 | d. Copyright and Similar Rights means copyright and/or similar rights 92 | closely related to copyright including, without limitation, 93 | performance, broadcast, sound recording, and Sui Generis Database 94 | Rights, without regard to how the rights are labeled or 95 | categorized. For purposes of this Public License, the rights 96 | specified in Section 2(b)(1)-(2) are not Copyright and Similar 97 | Rights. 98 | 99 | e. Effective Technological Measures means those measures that, in the 100 | absence of proper authority, may not be circumvented under laws 101 | fulfilling obligations under Article 11 of the WIPO Copyright 102 | Treaty adopted on December 20, 1996, and/or similar international 103 | agreements. 104 | 105 | f. Exceptions and Limitations means fair use, fair dealing, and/or 106 | any other exception or limitation to Copyright and Similar Rights 107 | that applies to Your use of the Licensed Material. 108 | 109 | g. License Elements means the license attributes listed in the name 110 | of a Creative Commons Public License. The License Elements of this 111 | Public License are Attribution and ShareAlike. 112 | 113 | h. Licensed Material means the artistic or literary work, database, 114 | or other material to which the Licensor applied this Public 115 | License. 116 | 117 | i. Licensed Rights means the rights granted to You subject to the 118 | terms and conditions of this Public License, which are limited to 119 | all Copyright and Similar Rights that apply to Your use of the 120 | Licensed Material and that the Licensor has authority to license. 121 | 122 | j. Licensor means the individual(s) or entity(ies) granting rights 123 | under this Public License. 124 | 125 | k. Share means to provide material to the public by any means or 126 | process that requires permission under the Licensed Rights, such 127 | as reproduction, public display, public performance, distribution, 128 | dissemination, communication, or importation, and to make material 129 | available to the public including in ways that members of the 130 | public may access the material from a place and at a time 131 | individually chosen by them. 132 | 133 | l. Sui Generis Database Rights means rights other than copyright 134 | resulting from Directive 96/9/EC of the European Parliament and of 135 | the Council of 11 March 1996 on the legal protection of databases, 136 | as amended and/or succeeded, as well as other essentially 137 | equivalent rights anywhere in the world. 138 | 139 | m. You means the individual or entity exercising the Licensed Rights 140 | under this Public License. Your has a corresponding meaning. 141 | 142 | 143 | Section 2 -- Scope. 144 | 145 | a. License grant. 146 | 147 | 1. Subject to the terms and conditions of this Public License, 148 | the Licensor hereby grants You a worldwide, royalty-free, 149 | non-sublicensable, non-exclusive, irrevocable license to 150 | exercise the Licensed Rights in the Licensed Material to: 151 | 152 | a. reproduce and Share the Licensed Material, in whole or 153 | in part; and 154 | 155 | b. produce, reproduce, and Share Adapted Material. 156 | 157 | 2. Exceptions and Limitations. For the avoidance of doubt, where 158 | Exceptions and Limitations apply to Your use, this Public 159 | License does not apply, and You do not need to comply with 160 | its terms and conditions. 161 | 162 | 3. Term. The term of this Public License is specified in Section 163 | 6(a). 164 | 165 | 4. Media and formats; technical modifications allowed. The 166 | Licensor authorizes You to exercise the Licensed Rights in 167 | all media and formats whether now known or hereafter created, 168 | and to make technical modifications necessary to do so. The 169 | Licensor waives and/or agrees not to assert any right or 170 | authority to forbid You from making technical modifications 171 | necessary to exercise the Licensed Rights, including 172 | technical modifications necessary to circumvent Effective 173 | Technological Measures. For purposes of this Public License, 174 | simply making modifications authorized by this Section 2(a) 175 | (4) never produces Adapted Material. 176 | 177 | 5. Downstream recipients. 178 | 179 | a. Offer from the Licensor -- Licensed Material. Every 180 | recipient of the Licensed Material automatically 181 | receives an offer from the Licensor to exercise the 182 | Licensed Rights under the terms and conditions of this 183 | Public License. 184 | 185 | b. Additional offer from the Licensor -- Adapted Material. 186 | Every recipient of Adapted Material from You 187 | automatically receives an offer from the Licensor to 188 | exercise the Licensed Rights in the Adapted Material 189 | under the conditions of the Adapter's License You apply. 190 | 191 | c. No downstream restrictions. You may not offer or impose 192 | any additional or different terms or conditions on, or 193 | apply any Effective Technological Measures to, the 194 | Licensed Material if doing so restricts exercise of the 195 | Licensed Rights by any recipient of the Licensed 196 | Material. 197 | 198 | 6. No endorsement. Nothing in this Public License constitutes or 199 | may be construed as permission to assert or imply that You 200 | are, or that Your use of the Licensed Material is, connected 201 | with, or sponsored, endorsed, or granted official status by, 202 | the Licensor or others designated to receive attribution as 203 | provided in Section 3(a)(1)(A)(i). 204 | 205 | b. Other rights. 206 | 207 | 1. Moral rights, such as the right of integrity, are not 208 | licensed under this Public License, nor are publicity, 209 | privacy, and/or other similar personality rights; however, to 210 | the extent possible, the Licensor waives and/or agrees not to 211 | assert any such rights held by the Licensor to the limited 212 | extent necessary to allow You to exercise the Licensed 213 | Rights, but not otherwise. 214 | 215 | 2. Patent and trademark rights are not licensed under this 216 | Public License. 217 | 218 | 3. To the extent possible, the Licensor waives any right to 219 | collect royalties from You for the exercise of the Licensed 220 | Rights, whether directly or through a collecting society 221 | under any voluntary or waivable statutory or compulsory 222 | licensing scheme. In all other cases the Licensor expressly 223 | reserves any right to collect such royalties. 224 | 225 | 226 | Section 3 -- License Conditions. 227 | 228 | Your exercise of the Licensed Rights is expressly made subject to the 229 | following conditions. 230 | 231 | a. Attribution. 232 | 233 | 1. If You Share the Licensed Material (including in modified 234 | form), You must: 235 | 236 | a. retain the following if it is supplied by the Licensor 237 | with the Licensed Material: 238 | 239 | i. identification of the creator(s) of the Licensed 240 | Material and any others designated to receive 241 | attribution, in any reasonable manner requested by 242 | the Licensor (including by pseudonym if 243 | designated); 244 | 245 | ii. a copyright notice; 246 | 247 | iii. a notice that refers to this Public License; 248 | 249 | iv. a notice that refers to the disclaimer of 250 | warranties; 251 | 252 | v. a URI or hyperlink to the Licensed Material to the 253 | extent reasonably practicable; 254 | 255 | b. indicate if You modified the Licensed Material and 256 | retain an indication of any previous modifications; and 257 | 258 | c. indicate the Licensed Material is licensed under this 259 | Public License, and include the text of, or the URI or 260 | hyperlink to, this Public License. 261 | 262 | 2. You may satisfy the conditions in Section 3(a)(1) in any 263 | reasonable manner based on the medium, means, and context in 264 | which You Share the Licensed Material. For example, it may be 265 | reasonable to satisfy the conditions by providing a URI or 266 | hyperlink to a resource that includes the required 267 | information. 268 | 269 | 3. If requested by the Licensor, You must remove any of the 270 | information required by Section 3(a)(1)(A) to the extent 271 | reasonably practicable. 272 | 273 | b. ShareAlike. 274 | 275 | In addition to the conditions in Section 3(a), if You Share 276 | Adapted Material You produce, the following conditions also apply. 277 | 278 | 1. The Adapter's License You apply must be a Creative Commons 279 | license with the same License Elements, this version or 280 | later, or a BY-SA Compatible License. 281 | 282 | 2. You must include the text of, or the URI or hyperlink to, the 283 | Adapter's License You apply. You may satisfy this condition 284 | in any reasonable manner based on the medium, means, and 285 | context in which You Share Adapted Material. 286 | 287 | 3. You may not offer or impose any additional or different terms 288 | or conditions on, or apply any Effective Technological 289 | Measures to, Adapted Material that restrict exercise of the 290 | rights granted under the Adapter's License You apply. 291 | 292 | 293 | Section 4 -- Sui Generis Database Rights. 294 | 295 | Where the Licensed Rights include Sui Generis Database Rights that 296 | apply to Your use of the Licensed Material: 297 | 298 | a. for the avoidance of doubt, Section 2(a)(1) grants You the right 299 | to extract, reuse, reproduce, and Share all or a substantial 300 | portion of the contents of the database; 301 | 302 | b. if You include all or a substantial portion of the database 303 | contents in a database in which You have Sui Generis Database 304 | Rights, then the database in which You have Sui Generis Database 305 | Rights (but not its individual contents) is Adapted Material, 306 | 307 | including for purposes of Section 3(b); and 308 | c. You must comply with the conditions in Section 3(a) if You Share 309 | all or a substantial portion of the contents of the database. 310 | 311 | For the avoidance of doubt, this Section 4 supplements and does not 312 | replace Your obligations under this Public License where the Licensed 313 | Rights include other Copyright and Similar Rights. 314 | 315 | 316 | Section 5 -- Disclaimer of Warranties and Limitation of Liability. 317 | 318 | a. UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE 319 | EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS 320 | AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF 321 | ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, 322 | IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, 323 | WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR 324 | PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS, 325 | ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT 326 | KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT 327 | ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU. 328 | 329 | b. TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE 330 | TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, 331 | NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, 332 | INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES, 333 | COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR 334 | USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN 335 | ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR 336 | DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR 337 | IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. 338 | 339 | c. The disclaimer of warranties and limitation of liability provided 340 | above shall be interpreted in a manner that, to the extent 341 | possible, most closely approximates an absolute disclaimer and 342 | waiver of all liability. 343 | 344 | 345 | Section 6 -- Term and Termination. 346 | 347 | a. This Public License applies for the term of the Copyright and 348 | Similar Rights licensed here. However, if You fail to comply with 349 | this Public License, then Your rights under this Public License 350 | terminate automatically. 351 | 352 | b. Where Your right to use the Licensed Material has terminated under 353 | Section 6(a), it reinstates: 354 | 355 | 1. automatically as of the date the violation is cured, provided 356 | it is cured within 30 days of Your discovery of the 357 | violation; or 358 | 359 | 2. upon express reinstatement by the Licensor. 360 | 361 | For the avoidance of doubt, this Section 6(b) does not affect any 362 | right the Licensor may have to seek remedies for Your violations 363 | of this Public License. 364 | 365 | c. For the avoidance of doubt, the Licensor may also offer the 366 | Licensed Material under separate terms or conditions or stop 367 | distributing the Licensed Material at any time; however, doing so 368 | will not terminate this Public License. 369 | 370 | d. Sections 1, 5, 6, 7, and 8 survive termination of this Public 371 | License. 372 | 373 | 374 | Section 7 -- Other Terms and Conditions. 375 | 376 | a. The Licensor shall not be bound by any additional or different 377 | terms or conditions communicated by You unless expressly agreed. 378 | 379 | b. Any arrangements, understandings, or agreements regarding the 380 | Licensed Material not stated herein are separate from and 381 | independent of the terms and conditions of this Public License. 382 | 383 | 384 | Section 8 -- Interpretation. 385 | 386 | a. For the avoidance of doubt, this Public License does not, and 387 | shall not be interpreted to, reduce, limit, restrict, or impose 388 | conditions on any use of the Licensed Material that could lawfully 389 | be made without permission under this Public License. 390 | 391 | b. To the extent possible, if any provision of this Public License is 392 | deemed unenforceable, it shall be automatically reformed to the 393 | minimum extent necessary to make it enforceable. If the provision 394 | cannot be reformed, it shall be severed from this Public License 395 | without affecting the enforceability of the remaining terms and 396 | conditions. 397 | 398 | c. No term or condition of this Public License will be waived and no 399 | failure to comply consented to unless expressly agreed to by the 400 | Licensor. 401 | 402 | d. Nothing in this Public License constitutes or may be interpreted 403 | as a limitation upon, or waiver of, any privileges and immunities 404 | that apply to the Licensor or You, including from the legal 405 | processes of any jurisdiction or authority. 406 | 407 | 408 | ======================================================================= 409 | 410 | Creative Commons is not a party to its public 411 | licenses. Notwithstanding, Creative Commons may elect to apply one of 412 | its public licenses to material it publishes and in those instances 413 | will be considered the “Licensor.” The text of the Creative Commons 414 | public licenses is dedicated to the public domain under the CC0 Public 415 | Domain Dedication. Except for the limited purpose of indicating that 416 | material is shared under a Creative Commons public license or as 417 | otherwise permitted by the Creative Commons policies published at 418 | creativecommons.org/policies, Creative Commons does not authorize the 419 | use of the trademark "Creative Commons" or any other trademark or logo 420 | of Creative Commons without its prior written consent including, 421 | without limitation, in connection with any unauthorized modifications 422 | to any of its public licenses or any other arrangements, 423 | understandings, or agreements concerning use of licensed material. For 424 | the avoidance of doubt, this paragraph does not form part of the 425 | public licenses. 426 | 427 | Creative Commons may be contacted at creativecommons.org. 428 | 429 | --------------------------------------------------------------------------------