<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://labyrinth.rienkjonker.nl"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Informatiebeheer  - ImRec</title>
 <link>http://labyrinth.rienkjonker.nl/tags/imrec</link>
 <description></description>
 <language>nl</language>
<item>
 <title>A perfect match? Connecting partners in the labyrinth of information  (full text)</title>
 <link>http://labyrinth.rienkjonker.nl/content/perfect-match-connecting-partners-labyrinth-information-full-text</link>
 <description>&lt;div class=&quot;field field-name-body field-type-text-with-summary field-label-hidden&quot;&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot; property=&quot;content:encoded&quot;&gt;&lt;p&gt;Full text of my essay published in Frans Smit, Arnoud Glaudemans and Rienk Jonker (eds.), &lt;a href=&quot;/content/archives-liquid-times&quot;&gt;&lt;em&gt;Archives in liquid times&lt;/em&gt;&lt;/a&gt;, Stichting Archiefpublicaties, &#039;s Gravenhage, 2017.[&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;A perfect match? Connecting partners in the labyrinth of information &lt;/strong&gt;&lt;a class=&quot;see-footnote&quot; id=&quot;footnoteref1_l4xzqz6&quot; title=&quot;I would like to thank Eric Ketelaar for his remarks and suggestions on a prior version and Meike Geerlings for reviewing my English text. And especially I would like to thank Frans Smit and Arnoud Glaudemans for al the intervisionary discussions we had on several archivistic topics regarding the archival digital turn.&quot; href=&quot;#footnote1_l4xzqz6&quot;&gt;1&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Rienk Jonker&lt;/p&gt;
&lt;h1&gt;Introduction&lt;/h1&gt;
&lt;p&gt;In this essay I will give some insight into the results of my quest as an archivist&lt;a class=&quot;see-footnote&quot; id=&quot;footnoteref2_r98uyh2&quot; title=&quot;When I use the word archivist, both the archivist and records manager are included. The archivist as keeper of archives in archival holdings and the records manager as an official found in the frontline where the records are created, received and managed until their disposition.&quot; href=&quot;#footnote2_r98uyh2&quot;&gt;2&lt;/a&gt; to understand the fundamentals of information. It is not only about trying to understand the complexity, but mostly to grasp or grock this phenomenon. With the verb grock one indicates that he or she is to understand completely and thoroughly an object, subject or issue (Heinlein, 1961). At one point I was surprised to notice that the common perception of complexity of information and information management overshadows the relative simplicity of the outcome of the grocking.&lt;/p&gt;
&lt;p&gt;As an archivist in Leeuwarden I am on an almost regular basis confronted with born digital information. I have to answer questions related to (functional) requirements and tenders for digital systems, change management, information architecture, system management, process development and management, migrations, and conversions. The answers have to be simple, preferably fitting on one page (e.g. as a checklist), because those who are asking are not interested in long considerations, reports and notes. Often there is not much time and quick decisions have to be made. It makes my job interesting, because old and new theories clash sometimes.&lt;/p&gt;
&lt;p&gt;A couple of years ago I became aware that I had been using an implicit sort of internal reference model for a long time. It was based on what I learned working as an archivist and while working in ICT. In particular, the fundamentals of arranging and describing archives, the knowledge about describing archives that I acquired through the years and the rise of digital systems for this purpose were invaluable to me to understand today’s digital development. In fact, this model was at its core based on a kind of constant undercurrent. This awareness was prompted to me through remarks that my colleague Frans Smit made about the behaviour of people working in ICT, and their internal reference frameworks. As a result, I could explicate my implicit model and turn the concepts into checklists and forms that are now in use in my organisation. In addition, I understood that from certain perspectives and abstraction levels, age-old concepts such as filing structures and document types can be found in modern digital systems. In that sense, to paraphrase the writer of Ecclesiastes “there is nothing new under the sun”.&lt;/p&gt;
&lt;p&gt;Because of this journey I could develop a basic information model or framework that at its core only consists of three basic interconnected elements. Each element has its own characteristics. For me, an information model is a somewhat formal abstract description of objects, attributes, relationships, and rules in a particular domain. It was a feasible answer to questions about the possibility to come up with an information model, including a model for sharing and exchanging information – independent of social, organisational and technical changes – and at the same time a model compliant to the required information qualities and to the interests to preserve the information. This model I defiantly call the Leeuwarder Information Model (LIM) because Leeuwarden is the place where it came to existence. Although it is a kind of archival information model, I found it somewhat insolent to call it that. There are enough other archival information models around.&lt;/p&gt;
&lt;p&gt;Despite the organisational or cultural background of actors and despite what technical instruments are used for processing information, there is always a consistent undercurrent. An undercurrent from the viewpoint of information as a constant factor with basic interwoven notions or concepts as context, documents or more neutral information objects, activities with communication or exchange and particularly notions about their mutual dependencies.&lt;/p&gt;
&lt;p&gt;The sum of these three elements, context, information object and activity can be called meaningful information (MI). The three elements also determine if a set of meaningful information makes up an archival record. Information is considered a record when it can be used in a personal or organisational context as evidence of a transaction, for reasons of compliancy, conformance and governance. It is mostly about administrative, legal and fiscal values. As a rule, one can say a record is always meaningful information, but not all meaningful information is a record. Meaningful information is only a record because and whenever we want it to be a record. One could say a record is a construct that lies in the eyes of the beholder. But to avoid further distraction, this essay is not about the definition of records and recordness. That is a discussion that will have to take place elsewhere.&lt;/p&gt;
&lt;p&gt;A real surprise was to observe that essential parts of my notion of meaningful information could be annex to the concept of semantic information (SI) of Floridi (Floridi, 2010). This was a discovery I found worthwhile to look further into.&lt;/p&gt;
&lt;p&gt;I will begin with an abstract point by introducing the concept of “something” which is at the base of my information model (LIM). Then I will outline an example of daily life which portraits what happens when an activity is triggered by an event: an activity starts and information is processed. With that example, I can explain my information model and the concept of meaningful information. Then I will shortly point out the elements and characteristics that are part of the connection between the meaningful information of the LIM and the concept of semantic information of Floridi. This is preceded with some reflections about what influenced my quest.&lt;/p&gt;
&lt;h1&gt;The journey and the undercurrent&lt;/h1&gt;
&lt;p&gt;The world of information has all the characteristics of a chaotic complex system with lots of turbulence. It is in no way comparable to the familiar, almost static, paper environment. Nothing remains and everything changes, which is something we should accept as normal. We as archivists are in this fluid digital world looking for fixation points; we want to be able to fixate moments. But to be able to fix, it must be clear why something should be fixed, what content is to be fixed and eventually how this fixation is to be carried out technically. Our field, the archival science, has a broad variety of fundamental pillars at its disposal. To begin with – of course – the Manual for the Arrangement and Description of Archives (Muller, Feith, Fruin, 1898/1920). This work contains components and concepts that are still very useful in these modern times. This work has been supplemented by several useful standards from ICA, ISO, and even the European Union. Not to forget the results of the international research of InterPares (Duranti &amp;amp; Preston, 2008). The intention of these works is to provide the professional archivist guidance through the maze or the labyrinth of information concepts and information systems. But is this assumption of guidance right or are we missing something? If there is already enough guidance why is it that there are still so many questions asked, why is there so much unclear? In these turbulent times of digital change, archivists still need a sustainable fundamental layer on which they can build for a long time.&lt;/p&gt;
&lt;p&gt;Perhaps the current concepts and models with derived terms and definitions are still insufficient for the approach of the current changes. A lot of those approaches are often accrued from a very persistent &quot;paper mindset&quot;, a phenomenon and heritage which permeates our culture. It is a legacy that could be described as the paper paradigm. It is a phenomenon that actually leads to the ‘paperisation’ of the perception of the digital environment. This confusion must be resolved. Otherwise we will continue to drive forward at full speed, only relying on the rearview mirror while the windshield is still blinded. Therefore, a fundamental reinvention and redefinition of our professional paradigms is a prerequisite. On the other hand, the archivist as a practitioner has to travel on the moving high-speed train. And at the same time, he has to find his way into design departments, construction sites, maintenance sites and boardroom table. This is only possible when the archivist’s message is unambiguous and clear. To be able to do that he needs &#039;simple&#039; information models with instruments that meet the following requirements: it is generic, easy to handle and constant.&lt;/p&gt;
&lt;p&gt;It is becoming clearer and clearer that in the world of the infosphere, an archivist has to look far beyond the bubble of his own discipline. The infosphere is the whole informational environment constituted by all informational entities, their properties, interactions, processes, and mutual relations (Floridi, 2013). On the one hand, archivists need it to find extra support and partners in the complex new world, and on the other hand to make use of the recognised knowledge of those partners. But also, archivists have to bring those partners into contact with archival science. It is a science with methodologies that is in a way a secure scientific theory that cannot be proven wrong, because it has always been reinvented in totally different contexts, environments, places and times – only the re-inventors are not aware of this fact.&lt;/p&gt;
&lt;h1&gt;Starting point&lt;/h1&gt;
&lt;p&gt;The starting point – the basis for this model – is the concept of the “something”. With this concept it is possible, at a very high level of abstraction, to reveal the basic elements of an event or activity with its additional determining characteristics.&lt;/p&gt;
&lt;p&gt;Each event or activity has an element of time; there is always a starting point and an endpoint. Both beginning and end are fixed (as a rule). It is also possible that an event has started or ended unnoticed. In that case a begin or an end can be defined on the go. In addition, associated with it there are one or more actors in human or other form like computers or machines. The “something” delivers, whether or not there will be a result. Also within an event or activity information is received, processed and sent.&lt;/p&gt;
&lt;p&gt;&lt;img alt=&quot;&quot; src=&quot;/sites/default/files/images/perfectmatch/20170619TheSomething.jpg&quot; style=&quot;height:455px; margin:10px; width:564px&quot; /&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Figure 1: the “something”&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Because of the starting and endpoint and because of the steps taken in between (including the expected results), one could say this “something” behaves like a process. On a certain level of abstraction, one could even say that every activity behaves like a process, whether it is a real process, a project or another kind of action and can be approached like an object or an entity.&lt;/p&gt;
&lt;p&gt;In its essence the “something” is a representation of a constant undercurrent and can be described as an object. As undercurrent it is generic and, and it is also possible to show the minimal imperative components which make a “something” up, and in a generic way to describe its components like context, information objects and the activity. The process of adding metadata to those objects is implicitly executed by everyone in one way or another, but it is for sure recognisable for an archivist, because description is a very substantial part of his profession.&lt;/p&gt;
&lt;p&gt;This “something” is for me a starting point of view to answer questions about information- and records management in my organisation. Because everything behaves like a process, for me also organisations, organisational entities, board governors, management boards even individual members of staff fit in this generic concept. Although sometimes there is a great difference in nature they are all temporarily because the start or begin at some moment and will also at some given time stop or expire.&lt;/p&gt;
&lt;h1&gt;An everyday example&lt;/h1&gt;
&lt;p&gt;The concept of the “something” can be outlined by using an example outside the comfort zone of an archivist. The example is about what I call the activity of refuelling a car. Imagine you are driving your car and on a given moment the dashboard signals that the fuel tank is almost empty. It must be filled immediately, otherwise you will end up on the side of the road in the middle of nowhere. The signal is clear and it cannot be ignored either.&lt;/p&gt;
&lt;p&gt;&lt;img alt=&quot;&quot; src=&quot;/sites/default/files/images/perfectmatch/gauge.jpg&quot; style=&quot;height:309px; margin:10px; width:300px&quot; /&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Figure 2 - Information object (gauge)&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;img alt=&quot;(re) fueling&quot; src=&quot;/sites/default/files/images/perfectmatch/fuelling.jpg&quot; style=&quot;height:225px; margin:10px; width:300px&quot; /&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Figure &lt;/em&gt;&lt;em&gt;3&lt;/em&gt;&lt;em&gt; - Activity - (re)fuelling a car&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;To stay out of trouble, the wisest thing to do is to go to the closest petrol station. If time is available you could also choose to go to your favourite station, or the cheapest station, it is your personal choice. Before you can start refuelling, some things must be settled first. For example, you must park the car at a pump that has the right kind of fuel. You also want to find the tank opening on the right side of the pump. In this way, juggling the hose is not necessary.&lt;/p&gt;
&lt;p&gt;Once you have parked, you must execute the start of a financial transaction. The supplier wants to get paid. This transaction begins with your debit card. You’ll have to give the vendor permission (through the console) to debit the due amount from your account after fuelling. Via the same console, you can indicate what kind of fuel you need. The console tells you which pump you must use. After removing the debit card, you can refill the tank. The pump display informs you about the progress of the fuelling in terms of volume (litres) and the amount of money due at that moment. This comes in handy for motorists who only like to pay for ten Euros or ten litres at a time. With the information on the display you know when to stop refuelling. In most cases it is simple; people fill up the whole tank. Most people pay more attention to the hose and the tank opening than to the display.&lt;/p&gt;
&lt;p&gt;&lt;img alt=&quot;Display&quot; src=&quot;/sites/default/files/images/perfectmatch/display.jpg&quot; style=&quot;height:225px; margin:10px; width:300px&quot; /&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Figure 4 - Information object (display)&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;As soon as the tank is full, refuelling stops. At that point, in my view, the display gives no information about the fuelling process, but only delivers information about the final condition. You can see the total price you must pay and the amount of fuel that is delivered. Once you put the hose back in its place, the payment transaction is completed and committed. You then have the choice to receive a receipt on paper, partly with the same information supplemented with extras that may be useful for you for administration and declaration purposes. It may also be useful when there are problems with the delivery. As soon as a new customer arrives and starts refuelling his car, all the displays are set to zero. The case has been closed.&lt;/p&gt;
&lt;p&gt;&lt;img alt=&quot;Receipt&quot; src=&quot;/sites/default/files/images/perfectmatch/receipt.jpg&quot; style=&quot;height:416px; margin:10px; width:200px&quot; /&gt;&lt;/p&gt;
&lt;p&gt;Figure 5 - Information object (paper)&lt;/p&gt;
&lt;p&gt;This activity has two perspectives. The customer and the supplier who owns the pump. Both partly use the same information, only the usage context – the primary context – is different. You need the information for refuelling and, in the case you keep track of expenses, you can reuse the information for that purpose. The primary context of the supplier will also be the refuelling itself and the final payment transaction. In the back office of the supplier the information is needed for stock management and other forms of administration. When it is needed for business intelligence it can even become part of a data warehouse. The exchange of information between both parties takes place through the information on the display of the pump and the printed receipt. The information you receive on the receipt is also part of the information the supplier needs.&lt;/p&gt;
&lt;p&gt;A short conclusion: we have an activity, i.e. refuelling, with a primary context triggered by information (signal about the empty tank) and with the necessary information objects that are exchanged via visual (display) and physical (print) ways. These are the three basic components of the aforementioned “something”: a context, an activity and information objects, the main components of the information model that will be discussed in the next paragraph.&lt;/p&gt;
&lt;h1&gt;Leeuwarder Information model (LIM)&lt;/h1&gt;
&lt;h2&gt;Interwoven trinity&lt;/h2&gt;
&lt;p&gt;The model based on the concept of “something” represents meaningful information as the only constant factor in a continuum of time and space. Just three entities are the essence of this model. First of all, the information has to be provided with context. To process information, it should be contained in structured form in an information object. For information to come into existence an event or transaction must take place. Part of an event or transaction are the different ways of exchange and communication.&lt;/p&gt;
&lt;p&gt;&lt;img alt=&quot;&quot; src=&quot;/sites/default/files/images/perfectmatch/20171114_Konstanten v8 (Kaal)_EN_2.png&quot; style=&quot;height:790px; margin:10px; width:953px&quot; /&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Figure 6- The Leeuwarder Information Model&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;The Information is central and has several invariant constant elements which underpin certain qualities. Qualities like meaningful based on context, structured as in the form of an information object and trustworthy by the way the context is described, the information object is structured and fixated and the activity is executed. All qualities that are also essential composing parts of an archival record. In this model trustworthiness and veracity are derived qualities.&lt;/p&gt;
&lt;p&gt;The context defines the setting in which the information has come into existence and at the same time, the information is used.&lt;/p&gt;
&lt;p&gt;When speaking about use, I am talking about the primary use and therefore it is a primary context. Information can always be reused in other contexts. Within the context the characteristics of the information object and the activity are described and recorded.&lt;/p&gt;
&lt;p&gt;The information object is just a container with the required information in structured form. The activity or act is a dynamic element that at the functional level processes and exchanges information within its context by using information objects. This involves exchanging information via one or more inbound (receive) and outbound connectors (send) with other activities. These other activities are again part of their particular context and information objects.&lt;/p&gt;
&lt;p&gt;These three elements must be considered as an indivisible unit like a trinity. Together they make up meaningful information (MI). If one or two of the three elements are missing, there can be no meaningful information. If that occurs, the information is meaningless and therefore no more than useless data. These data may, of course, become meaningful by adding the missing elements artificially. Consequently, a new version is created. This new version constitutes a view of the original situation but is a reconstruction, and the information can therefore never be interpreted the same way as the original.&lt;/p&gt;
&lt;p&gt;By means of following up the connectors that are part of the activity it is possible to make up a chain of meaningful information. This chain is an independent set of meaningful information. It can be compared to chemical elements that are bound together and make a chain to become a new chemical element.&lt;/p&gt;
&lt;h2&gt;The context&lt;/h2&gt;
&lt;p&gt;Context is about coherence in which notions, elements or concepts are intertwined, interwoven or connected. From its Latin origin, the verb &lt;em&gt;cotexo&lt;/em&gt;, comes the meaning of interweaving and connecting. In the processing of information, context concerns the setting in which information is generated and used. Context is a concept that is at the essence of an archivist’s discipline and therefore an important part of his field of study. Context is the essential element in understanding information and in the existence of information. Parts of that context are the objects in which information is included and the activities in which the information and information objects are processed.&lt;/p&gt;
&lt;p&gt;There are many types of contexts to be considered. At first, a distinction can be made between primary and secondary context. Primary context is the context in which the information is originated or received. Context is secondary when already existing information is reused, so it is a use outside of the primary context of origin.&lt;/p&gt;
&lt;p&gt;Secondarily, context implies a point of view or perspective. A viewpoint determines in which way or with what purpose information is looked at. Also, it is the way the information is interpreted and appraised. There are infinite possibilities in this regard with for instance legal, spatial, economic, biological and theological and other professional views. All perspectives that can be intertwined with organisational and processual contexts.&lt;/p&gt;
&lt;p&gt;It should be taken into consideration that use and reuse of information is never neutral or impartial. Even though it is often denied, there is always a subjective element present, namely the personal context, the insights of the person using the information. These insights are the results of upbringing, education, social position, and someone’s own opinions and beliefs.&lt;/p&gt;
&lt;p&gt;Moreover, it should not be forgotten that all these types of contexts or perspectives can also be found in the way in which devices and algorithms process information. Because they are the products of thoughts, ideas and opinions that originate from the various contexts.&lt;/p&gt;
&lt;p&gt;In the model described above, the word context is used to describe or even define the connection between information objects and activities in a somewhat formal sense in order to understand the desired interrelationship. It is about the primary context.&lt;/p&gt;
&lt;p&gt;This primary context consists of nine basic mandatory elements. The relation between these elements can be described in a semantic way. An activity only starts with a warrant or trigger. This activity will be an assignment executed by one or more actors (both humans and machines). The actors work in the environment or domain of a process, project or other kind of activity. Each activity has a result or product. It is possible that there is no result, but then the result is the ‘non-result’. Information is processed by using functionalities, this information is recorded in information objects. Techniques deliver many functionalities to use, manage and preserve information objects. The context defines and describes both the activity and the information object.&lt;/p&gt;
&lt;table align=&quot;center&quot; cellpadding=&quot;9&quot; cellspacing=&quot;0&quot; style=&quot;height:762px; width:836px&quot;&gt;
&lt;caption&gt;Table 1 - Context - Elements&lt;/caption&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td colspan=&quot;2&quot;&gt;
&lt;p&gt;&lt;strong&gt;Element&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;&lt;strong&gt;Meaning&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style=&quot;background-color:#c0c0c0&quot;&gt;
&lt;p&gt; &lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;background-color:#c0c0c0&quot;&gt;
&lt;p&gt;1) Warrant&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;background-color:#c0c0c0&quot;&gt;
&lt;p&gt;The reason or assignment why information is processed.&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;p&gt; &lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;2) Assignment&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;The elaboration of the warrant in terms of an activity or transaction.&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;background-color:#c0c0c0&quot;&gt;
&lt;p&gt; &lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;background-color:#c0c0c0&quot;&gt;
&lt;p&gt;3) Actor&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;background-color:#c0c0c0&quot;&gt;
&lt;p&gt;Who are involved with the assignment and the information processing. This can be both humans and machines.&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;p&gt; &lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;4) Domain&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;The kind of work context in which the assignment is executed.&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;background-color:#c0c0c0&quot;&gt;
&lt;p&gt; &lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;background-color:#c0c0c0&quot;&gt;
&lt;p&gt;5) Result&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;background-color:#c0c0c0&quot;&gt;
&lt;p&gt;What kind of result, products or conclusions are to be expected or not.&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;p&gt; &lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;6) Functionality&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;What is allowed, what is possible for the different types of actors.&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;background-color:#c0c0c0&quot;&gt;
&lt;p&gt; &lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;background-color:#c0c0c0&quot;&gt;
&lt;p&gt;7) Data/Information&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;background-color:#c0c0c0&quot;&gt;
&lt;p&gt;What type of information is processed,&lt;/p&gt;
&lt;p&gt;Personal, subject, object, financial, geographic, juridical etc.&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;p&gt; &lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;8) Information object&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;How is the information captured, structured and shaped.&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;background-color:#c0c0c0&quot;&gt;
&lt;p&gt; &lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;background-color:#c0c0c0&quot;&gt;
&lt;p&gt;9)Technology&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;background-color:#c0c0c0&quot;&gt;
&lt;p&gt;What technical tools and instruments are available or needed to process and preserve the information and information objects.&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;&lt;strong&gt;`&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;In contrast with some archival standards, in this model an actor is not a separate entity with its own characteristics, but it is deliberately part of the context. The reason is simple. An actor, be it human or non-human, is just a passer-by in the in a continuum of time where information is at the centre. Only moment and place determine its role as participant or spectator.&lt;/p&gt;
&lt;p&gt;&lt;img alt=&quot;&quot; src=&quot;/sites/default/files/images/perfectmatch/20170930LIM-Proposities-EN_3.png&quot; style=&quot;height:687px; margin:10px; width:600px&quot; /&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Figure &lt;/em&gt;&lt;em&gt;7&lt;/em&gt;&lt;em&gt; - Context with propositions&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;The reason or warrant for the activity refuelling was the warning of the gauge. Refuelling the car became the assignment. As a driver I was one of the actors. Because of all the steps; parking, preparing the financial transaction, filling the tank and paying and getting a receipt, one could say this is a process. The other actors, the supplier, the oil company and the bank were not present in person but they communicated through the ticket machine, the pump, and the display of the pump. The system of the gas station included the functionality to perform a financial transaction, to supply the necessary process information and of course the fuel. Display and receipt are examples of information objects. The pump and the ticket machine where both part of technology. Not visible, but certainly present was the technology of sending and receiving messages between the pump, the ticket machine and the systems of the supplier and the bank. As a client, I believed the whole transaction was trustworthy.&lt;/p&gt;
&lt;h2&gt;The information objects&lt;/h2&gt;
&lt;h3&gt;Document&lt;/h3&gt;
&lt;p&gt;This part describes in what way information is recorded, structured and (sometimes) fixated. As a matter of fact, the word document can be used as a synonym for the concept information object. According to InterPares, a document is an indivisible unit of information constituted by a message affixed to a medium (recorded) in a stable syntactic manner. A document has a fixed form and stable content (Duranti &amp;amp; Preston, 2008). A document can be classified on the level of document types defined by its use or function e.g. evidential, informational, transactional.&lt;/p&gt;
&lt;p&gt;A user experiences a document in the manner that this document is presented. It is a simple and unobtrusive object for the user. He sees it on his screen, he takes it out of the printer and holds the paper in his hands. What the user will probably not realise is that each document, both paper and digital, exists as an object of different ways of materialisation, techniques and dimensions or layers. For the user, a text and/or image in a document and the data carrier seem to be an inseparable unit, but they are not. What he does not realise is that a display on a fuel pump (or other devices) is in a broad sense also an information object i.e. document. In a sense he must be aware that information and carrier are detached. Knowing this he can focus on what is really important: the information. The carriers are just the means to convey the messages.&lt;/p&gt;
&lt;table align=&quot;center&quot; cellpadding=&quot;9&quot; cellspacing=&quot;0&quot; style=&quot;height:530px; width:759px&quot;&gt;
&lt;caption&gt;Table 2 - Information object – Elements&lt;/caption&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;p&gt;&lt;strong&gt;Element&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;&lt;strong&gt;Meaning&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style=&quot;background-color:#c0c0c0&quot;&gt;
&lt;p&gt;&lt;strong&gt;1) Content&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;background-color:#c0c0c0&quot;&gt;
&lt;p&gt;The message/information to be conveyed by the object.&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;p&gt;&lt;strong&gt;2) Structure&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;The form of the message/information.&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;background-color:#c0c0c0&quot;&gt;
&lt;p&gt;&lt;strong&gt;3) Context&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;background-color:#c0c0c0&quot;&gt;
&lt;p&gt;The setting in which the object has a function and which is implicitly and / or explicitly present in the information object only.&lt;/p&gt;
&lt;p&gt;This context is therefore the result of the content and structure, and partly also the behaviour and technique.&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;p&gt;&lt;strong&gt;4) Behaviour&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Functionalities that must be executed to convey the message/information.&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;background-color:#c0c0c0&quot;&gt;
&lt;p&gt;&lt;strong&gt;5) Technology&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;background-color:#c0c0c0&quot;&gt;
&lt;p&gt;The tools needed to sustain the functionality and the information object and also to maintain and preserve the object.&lt;/p&gt;
&lt;p&gt;It consists of three main layers.&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt; &lt;/p&gt;
&lt;p&gt;A paper document can be copied to a digital image (scan), which still appears to be the same on the screen but is of a completely different order technically. For the user the text remains the same. The digitised text can be found via text recognition (OCR) and made digital as text and therefore usable for different operations. For example, by copying the recognised text to other documents.&lt;/p&gt;
&lt;p&gt;This is possible because in fact, each document is composed of five characteristic elements. These elements are, (1) content, (2) structure, (3) context, (4) behaviour and (5) technology.&lt;/p&gt;
&lt;p&gt;These five main elements are meant to hold information and convey a message. The intention of a message always depends on the context that is used within the object and the typology of the document. This typology itself is determined by the combination of structure (2), content (1) and context (3). For example, the labels (metadata) on the pump at the gas station clarify the meaning of the data on the display.&lt;/p&gt;
&lt;h3&gt;Technical layers&lt;/h3&gt;
&lt;p&gt;An Information object consists of at least three technical layers. These layers are for (1) presentation, (2) transport and processing, and (3) storing and fixation. They allow recording information in documents and for those documents to be created, saved, edited, viewed and consulted, copied, sent, received and erased. At the same time, these layers are the determining factor for the behaviour of a document. These layers directly affect the other features of a document.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;The presentation layer will display content, structure and context. This layer also ensures the way the content of a document must behave.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The transport layer provides for the processing of bit streams in such a way that the presentation is possible.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The storage layer ensures capture and maintenance of bit streams so that processing and presentation are possible.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt; &lt;/p&gt;
&lt;table align=&quot;center&quot; cellpadding=&quot;9&quot; cellspacing=&quot;0&quot; style=&quot;height:460px; width:948px&quot;&gt;
&lt;caption&gt;Table 3 - Information object - technological layers&lt;/caption&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;p&gt;&lt;strong&gt;&lt;u&gt;Layer&lt;/u&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;&lt;strong&gt;&lt;u&gt;Meaning&lt;/u&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style=&quot;background-color:#c0c0c0&quot;&gt;
&lt;p&gt;&lt;strong&gt;5.1) Presentation&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;background-color:#c0c0c0&quot;&gt;
&lt;p&gt;Presenting the object to either a machine and/or a human being including the performance of behaviour.&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;p&gt;&lt;strong&gt;5.2) Transport/processing&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Transforming the factual technical form (e.g. bit stream) to make the message (content) presentable and therefore usable.&lt;/p&gt;
&lt;p&gt;E.g. Print to paper, show on digital interfaces like display screens, digital messages in XML between machines.&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;background-color:#c0c0c0&quot;&gt;
&lt;p&gt;&lt;strong&gt;5.3) Store/Fixation&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;background-color:#c0c0c0&quot;&gt;
&lt;p&gt;With analogue media like paper: the ink/toner attached to (or in) the medium (paper).&lt;/p&gt;
&lt;p&gt;Digital data: the bit streams, the zeros and ones on a physical data carrier or on more than one datacarrier which together make up a document.&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt; &lt;/p&gt;
&lt;p&gt;As a practical example, this document is described below, using the above features and layers. This document is displayed on a screen of a PC or tablet or is available as a print on paper. This is possible because in the second layer, conversion of the digital source to the presentation layer (and vice versa) takes place. The digital source is visible as a file on the physical data carrier, but actually presents itself as a bit stream, a row of zeros and ones. Deep inside the technique of storage, the bit stream that makes up the document can be found, but unusable and unrecognisable without the support of software to operate the hardware and to make the document readable.&lt;/p&gt;
&lt;p&gt;Within a word processor such as MS Word, content, structure and behaviour can be edited, modified, and deleted. Saving this document from MS Word to a PDF/A file, the content and structure are maintained. Only a small portion of the behaviour will be available, such as using links and going to a paragraph or a note with one click. In the paper copy this behaviour is not available, the reader can only browse more easily using his hands and eyes and he can write down his annotations.&lt;/p&gt;
&lt;p&gt;The layers that make up the content cannot be seen separately from the technique. After all, the technique is instrumental in ensuring the use and survival of all components&lt;/p&gt;
&lt;h3&gt;Behaviour and compound documents&lt;/h3&gt;
&lt;p&gt;Behaviour, the fourth of the five characteristics of a document, exists by one or more embedded functionalities in a document. It is in a way part of the technology and is used to generate the presentation of the content and structure. Examples are animations or video and/or audio streams in presentations, generated charts, and execution of macros and formulas in spreadsheets. Another example is an embedded spreadsheet in a text document, which can be opened with just a click of the mouse. Also, hyperlinks – visible and embedded – to other documents or websites are part of the behaviour. The examples are uncountable. It is the element that makes a document dynamic.&lt;/p&gt;
&lt;p&gt;The situation becomes more complex when there are compound documents that present themselves as one, but are made up of separate components. These components are often different digital documents on their own. In many cases, these individual components are made up of different file formats. A lot of compound documents are already around us, although not everyone recognises them (Ford, 2015). Examples of compound documents are email messages with attachments, digital documents with digital attachments, web pages, digital documents with links to other documents, and games.&lt;/p&gt;
&lt;p&gt;Dynamic databases with queries and algorithms that are also documents – and that in a sense can be characterised as register – must be placed under the category of compound documents that contain a lot of complex behaviour.&lt;/p&gt;
&lt;p&gt;From a user&#039;s perspective there will not directly be a notion of a compound document. At the level of presentation, the user sees the document as a unit. This presentation depends on the three technical layers. Through the transport/processing route, the components are retrieved from the storage/fixation (the disks) by one or more applications and digitally forged to a temporally unit which is delivered to the presentation layer. These operations can be considered as behaviour (4).&lt;/p&gt;
&lt;p&gt;A document is also a compound when links refer to other documents that are stored on internal or external servers as if they were attachments. At an abstract level – although difficult to understand – the total of these files constitutes one document. Examples are web pages.&lt;/p&gt;
&lt;p&gt;These types of documents are a major preservation challenge for archivists because the management of these information objects is mostly beyond their reach. The complexity lays in the requirement that the presented unit, the total of the components of a compound document, must be preserved and maintained until the date of its disposition. An issue that may arise are broken links. Not all links are permanent: they can be modified, the external files are missing or have disappeared, or other versions of the external files are provided with the same link. Reference rot with content drift and link rot are looming and menacing perspectives.&lt;/p&gt;
&lt;h2&gt;The activity&lt;/h2&gt;
&lt;h3&gt;Time and steps&lt;/h3&gt;
&lt;p&gt;Within an activity, as described or defined in the context, the information objects are used and exchanged with other activities. Activities that are part of their own set of meaningful information (MI). Please note that when the word activity is mentioned, it is not about the (trans)action itself but about what happens with information and information objects during that activity.&lt;/p&gt;
&lt;p&gt; &lt;/p&gt;
&lt;table align=&quot;center&quot; cellpadding=&quot;9&quot; cellspacing=&quot;0&quot; style=&quot;height:538px; width:709px&quot;&gt;
&lt;caption&gt;Table 4 - Activity – Elements and aspects&lt;/caption&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;p&gt;&lt;strong&gt;Element&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;&lt;strong&gt;Aspect&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style=&quot;background-color:#c0c0c0&quot;&gt;
&lt;p&gt;&lt;strong&gt;Time&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;background-color:#c0c0c0&quot;&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Start&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Moment(s)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;End&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;p&gt;&lt;strong&gt;Exchange/Communicate &lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Send&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;(message, make available, transfer)&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Receive&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;(message, fetch, acquire)&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;background-color:#c0c0c0&quot;&gt;
&lt;p&gt;&lt;strong&gt;Steps&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;background-color:#c0c0c0&quot;&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Assess&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Capture&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Process&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Keep/Retain/Dispose&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt; &lt;/p&gt;
&lt;p&gt;From both the previously mentioned concept of “something” and the example of the activity of refuelling, the core elements in question are perhaps self-explanatory and visible. These are the time factor, the sequence of the steps within the information is processed and the moment the exchange of information takes place. The aspects of time are the beginning, the end and the moments in between.&lt;/p&gt;
&lt;p&gt;There are four aspects in the processing of information that are most likely default. Firstly, it is the step of assessing and appraising to get an answer to the question if the information in the information object has to be used and therefore ingested. When the answer is positive, the information object can be ingested and registered. Then the information can be interpreted and used within the context of the activity. Also, information can be changed, added or new information objects can be created. Within the fourth default step the used or created information is saved and kept for reasons of availability and accessibility or is perhaps disposed, transferred or destroyed.&lt;/p&gt;
&lt;p&gt;The steps when information is assessed, appraised, used and eventually saved or destroyed are usually not sequential. An often-enforced sequence can be found especially in formal situations where evidence, accountability, control and supervision play an important role. In other cases, it is therefore not strange when the steps mostly seem to run across. For example, during the time of use, the used information can directly be destroyed.&lt;/p&gt;
&lt;h3&gt;The exchange element&lt;/h3&gt;
&lt;p&gt;It is important to understand what happens when information is exchanged on a certain level of abstraction. Certainly, for archivists with that understanding and their deep rooted archival knowledge it is possible to determine which parts of digital information have to be archived. It is also possible to ascertain conditions and requirements the exchange should meet. For an archivist the message is always an information object, be it a document, a set of documents or datasets. Therefore, this information object has the same characteristics as every other information object; there is a content, a structure, a context, a behaviour and technology. Messages and additional metadata for sending and receiving are wrapped in a container, an envelope which is in again an information object.&lt;/p&gt;
&lt;p&gt;The exchange model is a straightforward broad concept; there is always a message, a sender, a receiver, and a channel. It is always a form of communication between one or more parties (actors and processes). It is necessary that information will get from place a to b unhindered and undamaged. In many cases, the received message after unwrapping and accepting becomes part of a new context. Although this is of concern for the sender, it is nevertheless beyond his reach. It is just a fact. As a result, the intention of the transmitter may not always occur to the recipient. Therefore, transmitted information must be provided with sufficient metadata to convey the intention.&lt;/p&gt;
&lt;p&gt;From the perspective of an archivist, the communication model may look as in the scheme below.&lt;/p&gt;
&lt;p&gt;&lt;img alt=&quot;&quot; src=&quot;/sites/default/files/images/perfectmatch/ModelInboundOutboundv2.jpg&quot; style=&quot;height:366px; margin:10px; width:927px&quot; /&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Figure 8 - Exchange model&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;This kind of exchange takes place at the moment when, for example&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Information is exchanged directly between or inside processes, projects or other activities, high standards of interoperability are necessary;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Information is exchanged via messaging, chat, correspondence via surface mail;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Information is published on websites; open data sets are made available;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Transferring information from one actor to another, an action that involves a move or migration, where the original is deleted (destroyed) after a successful transfer. High standards of interoperability are necessary.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Several communication models exist; they are models that indicate how information and data are transmitted. On the technical level, the best-known model is from Shannon (Shannon 1948). This model is about how information can be obtained from the sender by the receiver. The transmitter puts the message in a signal to be transmitted (encode), after transmission the receiver extracts the message (decode). The context of this model is the telecommunications.&lt;/p&gt;
&lt;p&gt;Another communication model comes from linguistics. This model can be found in the work of the linguist Roman Jacobson about his theory of communicative functions of language (Jacobson, 1960). In this model a channel encodes a message in a code. Then the message is intentionally send via a medium to a recipient who decodes the message. The message must have a context that can be referred to and that makes it understandable to the recipient. This linguistic model indicates what is needed to get the contents of a message from sender to recipient while maintaining interpretability.&lt;/p&gt;
&lt;p&gt;For all models, it is important that a message is transmitted without loss – be it in a technical, linguistic or archival sense. The nice thing is that for all three the core is the same, for example, there is always a transmitter and receiver, and in all three cases a message is converted (packed, encoded, encrypted, wrapped, unpacked, decoded, decrypted, and unwrapped). In the core all three use channels. The difference is the origin of the models, each with its own characteristics.&lt;/p&gt;
&lt;p&gt;The time difference between sending and receiving is invaluable. There is always a time difference between the time of sending and the moment of receiving information. In many cases, that time difference will be minimal and almost negligible because of the state of the art of the technique. But there may be cases where it is necessary to know if someone could have been aware of a specific situation at some point. In some transactions, like in stock markets, the quote ‘time is money’ has a literal meaning.&lt;/p&gt;
&lt;h1&gt;Semantic information&lt;/h1&gt;
&lt;p&gt;As said before, in these turbulent times of digital change an archivist needs a sustainable fundamental layer on which he can build instruments to do his work. Parts of that foundation may be found in the philosophy of information. For this it is necessary to find the conceptual relationship between archival science and information philosophy.&lt;/p&gt;
&lt;p&gt;According to Floridi, philosophy of information is the philosophical field concerned with the critical investigation of the conceptual nature and basic principles of information, including its dynamics, utilisation and sciences (Floridi, 2009).&lt;/p&gt;
&lt;p&gt;For a possible connection with the philosophy of information, the Leeuwarder information model (LIM) about meaningful information as described above will be used. From this starting point it is a small step to a model explained by Floridi (Floridi, 2010) where he introduces semantic content with elements as meaningful and well formed. According to Floridi is information semantic when it is also truthful and therefore true.&lt;/p&gt;
&lt;p&gt;Roughly speaking there are connections between two elements that make up semantic content from philosophical perspective and meaningful information from the archival perspective. These are from the viewpoint of the philosopher respectively “meaningful” and “well-formed” and from the viewpoint of the archivist “context” and “information object”. Because the context delivers meaning to information, both “meaningful” and “’ context” are on the same level. An information object contains information in such a structured form that it can be called well-formed.&lt;/p&gt;
&lt;p&gt;On the point of semantic information there is a more principle difference between the philosopher and the archivist. An archivist can only ensure and ascertain that an information object under his control has the same quality as when it was ingested, it is trustworthy with guarantees about the integrity. An archivist cannot and from an ethical viewpoint may not deliver a statement about truthfulness of the information&lt;a class=&quot;see-footnote&quot; id=&quot;footnoteref3_61otc4t&quot; title=&quot;This statement does not release an archivist from a moral obligation to help a user as much as possible with his research in the archive&quot; href=&quot;#footnote3_61otc4t&quot;&gt;3&lt;/a&gt;. The answer to the question if the information can be assumed truthful can only be given by the user of that information acting from his various contexts. Anyway knowing this difference, one could say that under certain conditions the archival trustworthiness is at the same level as the philosophical truthfulness. This means that a real connection between both fields of study is just as well possible.&lt;/p&gt;
&lt;p&gt;&lt;img alt=&quot;&quot; src=&quot;/sites/default/files/images/perfectmatch/SIvsRecord_v5_zw.png&quot; style=&quot;height:581px; margin:10px; width:863px&quot; /&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Figure 9 - Bridging the gap&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;This connection can be used as a bridge that spans the virtual gap between both sciences. This can be a route for archivists to enter the realm of the information philosopher. A world of very fundamental research on information and concepts of information with its own semantics which may be useful for the archivist who should be aware of the consequences of the infosphere on his discipline. At the same time for the philosopher the knowledge of the archivist as appraiser, broker and curator of meaningful or semantic information becomes available. As shown above there are certainly connections between the concepts of the philosopher and the archivist. These connections need further research.&lt;/p&gt;
&lt;h1&gt;Literature&lt;/h1&gt;
&lt;p&gt;Adriaans, Pieter (2013). &lt;em&gt;Information &lt;/em&gt;(lemma).&lt;em&gt; &lt;/em&gt;In The Stanford Encyclopedia of Philosophy. Retrieved from &lt;u&gt;&lt;a href=&quot;https://plato.stanford.edu/archives/fall2013/entries/information/&quot;&gt;https://plato.stanford.edu/archives/fall2013/entries/information/&lt;/a&gt;&lt;/u&gt;&lt;/p&gt;
&lt;p&gt;Acker, Amelia (2016). When is a record; A Research Framework for Locating Electronic Records in Infrastructure. In A. Gilliland, S. McKemmish, A.J. Lau (eds.) &lt;em&gt;Research in the Archival Multiverse &lt;/em&gt;(page 288-233). Clayton, VIC: Monash University Publishing. &lt;a href=&quot;http://dx.doi.org/10.26530/OAPEN_628143&quot;&gt;http://dx.doi.org/10.26530/OAPEN_628143&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Allo, Patrick, Bert Baumgaertner, &amp;amp; The Π Research Network (2013). &lt;em&gt;The Philosophy of Information; An Introduction. &lt;/em&gt;Retrieved from &lt;u&gt;&lt;a href=&quot;http://socphilinfo.org/news/teaching/412-philosophy-information-introduction-new-extended-version&quot;&gt;http://socphilinfo.org/news/teaching/412-philosophy-information-introduction-new-extended-version&lt;/a&gt;&lt;/u&gt;&lt;/p&gt;
&lt;p&gt;Beavers, Anthony F. (2012). &lt;em&gt;A Brief Introduction to the Philosophy of Information. &lt;/em&gt;Evansville, IND: University of Evansville, Philosophy / Cognitive Science. Retrieved from &lt;u&gt;&lt;a href=&quot;http://www.academia.edu/1230161/A_Brief_Introduction_to_the_Philosophy_of_Information&quot;&gt;http://www.academia.edu/1230161/A_Brief_Introduction_to_the_Philosophy_of_Information&lt;/a&gt;&lt;/u&gt;&lt;/p&gt;
&lt;p&gt;Duranti, Luciana (1998). &lt;em&gt;Diplomatics; New uses for an old science. &lt;/em&gt;Lanham / London: Society of American Archivists and Association of Canadian Archivists in Association with The Scarecrow Press Inc.&lt;/p&gt;
&lt;p&gt;Duranti, Luciana, &amp;amp; Randy Preston (2008). &lt;em&gt;International Research on Permanent Authentic Records in Electronic Systems (InterPARES) 2: Experiential, Interactive and Dynamic Records. &lt;/em&gt;Padova:&lt;em&gt; &lt;/em&gt;Associazione Nazionale Archivistica Italiana. Retrieved from &lt;u&gt;&lt;a href=&quot;http://www.interpares.org/ip2/book.cfm&quot;&gt;http://www.interpares.org/ip2/book.cfm&lt;/a&gt;&lt;/u&gt;&lt;/p&gt;
&lt;p&gt;Floridi, L. (2009). The Information Society and Its Philosophy: Introduction to the Special Issue on “The Philosophy of Information, Its Nature, and Future Developments”. &lt;em&gt;The Information Society,&lt;/em&gt; 25(3), 153–158. &lt;u&gt;&lt;a href=&quot;https://doi.org/10.1080/01972240902848583&quot;&gt;https://doi.org/10.1080/01972240902848583&lt;/a&gt;&lt;/u&gt;&lt;/p&gt;
&lt;p&gt;Floridi, L. (2010). &lt;em&gt;Information: A Very Short Introduction. &lt;/em&gt;Oxford: Oxford University Press.&lt;/p&gt;
&lt;p&gt;Floridi, L. (2013). &lt;em&gt;The Ethics of Information. &lt;/em&gt;Oxford: Oxford University Press.&lt;/p&gt;
&lt;p&gt;Floridi, L. (2014). &lt;em&gt;The Fourth Revolution; How the Infosphere is Reshaping Human Reality. &lt;/em&gt;Oxford: Oxford University Press.&lt;/p&gt;
&lt;p&gt;Floridi, L. (ed.) (2015). &lt;em&gt;The onlife&lt;/em&gt;&lt;u&gt;&lt;a href=&quot;http://link.springer.com/book/10.1007/978-3-319-04093-6&quot;&gt;&lt;em&gt; &lt;/em&gt;&lt;/a&gt;&lt;/u&gt;&lt;em&gt;manifesto&lt;/em&gt;&lt;u&gt;&lt;a href=&quot;http://link.springer.com/book/10.1007/978-3-319-04093-6&quot;&gt;&lt;em&gt;; &lt;/em&gt;&lt;/a&gt;&lt;/u&gt;&lt;em&gt;Being Human in a Hyperconnected Era. &lt;/em&gt;Heidelberg: Springer. Retrieved from &lt;u&gt;&lt;a href=&quot;https://link.springer.com/book/10.1007/978-3-319-04093-6&quot;&gt;https://link.springer.com/book/10.1007/978-3-319-04093-6&lt;/a&gt;&lt;/u&gt;&lt;/p&gt;
&lt;p&gt;Ford, Paul J.(2015). What is code? &lt;em&gt;Business week, &lt;/em&gt;11-jun-2015. Retrieved from &lt;u&gt;&lt;a href=&quot;https://www.bloomberg.com/graphics/2015-paul-ford-what-is-code&quot;&gt;https://www.bloomberg.com/graphics/2015-paul-ford-what-is-code&lt;/a&gt;&lt;/u&gt;&lt;/p&gt;
&lt;p&gt;Gilliland, A., S. McKemmish, &amp;amp; A.J. Lau (2016). &lt;em&gt;Research in the Archival Multiverse. &lt;/em&gt;Clayton, VIC: Monash University Publishing&lt;em&gt;. &lt;/em&gt;&lt;a href=&quot;http://dx.doi.org/10.26530/OAPEN_628143&quot;&gt;http://dx.doi.org/10.26530/OAPEN_628143&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Gleick, James (2011). &lt;em&gt;The Information; A History, a Theory, a Flood. &lt;/em&gt;New York: Knopf Doubleday Publishing Group.&lt;/p&gt;
&lt;p&gt;Glaudemans, Arnoud, Rienk Jonker, &amp;amp; Frans Smit (2015). The right people and the right forces need to get together,: Interview with Prof. Luciano Floridi. &lt;em&gt;Archievenblad&lt;/em&gt;, Januari 2015. Retrieved from &lt;u&gt;&lt;a href=&quot;http://www.youblisher.com/p/1048348-Archievenblad-uitgave-van-de-Koninklijke-Vereniging-van-Archivarissen-in-Nederland/&quot;&gt;http://www.youblisher.com/p/1048348-Archievenblad-uitgave-van-de-Koninklijke-Vereniging-van-Archivarissen-in-Nederland/&lt;/a&gt;&lt;/u&gt;&lt;/p&gt;
&lt;p&gt;Heinlein, Robert (1961). &lt;em&gt;Stranger in a strange land. &lt;/em&gt;New York: Puntnam’s Sons.&lt;/p&gt;
&lt;p&gt;Jacobson, Ramon (1960). &lt;em&gt;Closing Statements, Linguistics and Poetics&lt;/em&gt;. In Thomas A. Sebeok (ed.), &lt;em&gt;Style In Language &lt;/em&gt;(pp. 350–377). Cambridge MA: MIT Press.&lt;/p&gt;
&lt;p&gt;Maes, Rik (1999). &lt;em&gt;A generic framework for information management (PrimaVera Working Paper 99-03). &lt;/em&gt;Amsterdam: Department of Accountancy &amp;amp; Information Management. Retrieved from &lt;u&gt;&lt;a href=&quot;https://www.researchgate.net/publication/242321998_A_Generic_Framework_for_Information_Management&quot;&gt;&lt;em&gt;https://www.researchgate.net/publication/242321998_A_Generic_Framework_for_Information_Management&lt;/em&gt;&lt;/a&gt;&lt;/u&gt;&lt;/p&gt;
&lt;p&gt;McKemmish, S. (2005). &lt;em&gt;Archives: Recordkeeping in society&lt;/em&gt;. Wagga Wagga: Centre for Information Studies, Charles Sturt University.&lt;/p&gt;
&lt;p&gt;Muller, Samuel, Johan A. Feith, &amp;amp; Robert Fruin (2003). &lt;em&gt;Manual for the arrangement and description of archives (&lt;/em&gt;Transl. of the second ed. by Arthur H. Leavitt, with new introductions by Peter Horsman, Eric Ketelaar, Theo Thomassen, and Marjorie Rabe Barritt). Chicago: Society of American Archivists. Retrieved from &lt;u&gt;&lt;a href=&quot;https://hdl.handle.net/2027/mdp.39015057022447&quot;&gt;https://hdl.handle.net/2027/mdp.39015057022447&lt;/a&gt;&lt;/u&gt;&lt;/p&gt;
&lt;p&gt;Shannon, Claude (1948). A Mathematical Theory of Communication. &lt;em&gt;The Bell System Technical Journal&lt;/em&gt;, 27, 379-423 and 623-656.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Some standards:&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;ISO 23081-1:2006, Information and documentation -- Records management processes -- Metadata for records -- Part 1: Principles&lt;/li&gt;
&lt;li&gt;MoReq2010 - Modular Requirements for Records Systems, Volume 1 - Core Services &amp;amp; Plug-in Modules, DLM Forum Foundation, Brussel, 2011. Version 1.1 (updated text, but no new requirements)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt; &lt;/p&gt;
&lt;ul class=&quot;footnotes&quot;&gt;
&lt;li class=&quot;footnote&quot; id=&quot;footnote1_l4xzqz6&quot;&gt;&lt;a class=&quot;footnote-label&quot; href=&quot;#footnoteref1_l4xzqz6&quot;&gt;1.&lt;/a&gt; I would like to thank Eric Ketelaar for his remarks and suggestions on a prior version and Meike Geerlings for reviewing my English text. And especially I would like to thank Frans Smit and Arnoud Glaudemans for al the intervisionary discussions we had on several archivistic topics regarding the archival digital turn.&lt;/li&gt;
&lt;li class=&quot;footnote&quot; id=&quot;footnote2_r98uyh2&quot;&gt;&lt;a class=&quot;footnote-label&quot; href=&quot;#footnoteref2_r98uyh2&quot;&gt;2.&lt;/a&gt; When I use the word archivist, both the archivist and records manager are included. The archivist as keeper of archives in archival holdings and the records manager as an official found in the frontline where the records are created, received and managed until their disposition.&lt;/li&gt;
&lt;li class=&quot;footnote&quot; id=&quot;footnote3_61otc4t&quot;&gt;&lt;a class=&quot;footnote-label&quot; href=&quot;#footnoteref3_61otc4t&quot;&gt;3.&lt;/a&gt; This statement does not release an archivist from a moral obligation to help a user as much as possible with his research in the archive&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;field field-name-field-tags field-type-taxonomy-term-reference field-label-above clearfix&quot;&gt;&lt;h3 class=&quot;field-label&quot;&gt;Tags: &lt;/h3&gt;&lt;ul class=&quot;links&quot;&gt;&lt;li class=&quot;taxonomy-term-reference-0&quot; rel=&quot;dc:subject&quot;&gt;&lt;a href=&quot;/tags/imarch&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;ImArch&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-1&quot; rel=&quot;dc:subject&quot;&gt;&lt;a href=&quot;/tags/imrec&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;ImRec&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-2&quot; rel=&quot;dc:subject&quot;&gt;&lt;a href=&quot;/tags/informatiemodel&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;informatiemodel&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-3&quot; rel=&quot;dc:subject&quot;&gt;&lt;a href=&quot;/tags/leeuwarder-informatiemodel-lim&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;Leeuwarder Informatiemodel (LIM)&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-4&quot; rel=&quot;dc:subject&quot;&gt;&lt;a href=&quot;/tags/semantic-information&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;semantic information&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-5&quot; rel=&quot;dc:subject&quot;&gt;&lt;a href=&quot;/tags/philosophy-information&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;philosophy of information&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-6&quot; rel=&quot;dc:subject&quot;&gt;&lt;a href=&quot;/tags/informatie-object&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;informatie-object&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-7&quot; rel=&quot;dc:subject&quot;&gt;&lt;a href=&quot;/tags/communictie&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;communictie&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-8&quot; rel=&quot;dc:subject&quot;&gt;&lt;a href=&quot;/tags/zenden&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;zenden&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-9&quot; rel=&quot;dc:subject&quot;&gt;&lt;a href=&quot;/tags/ontvangen&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;ontvangen&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-10&quot; rel=&quot;dc:subject&quot;&gt;&lt;a href=&quot;/tags/context&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;context&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-11&quot; rel=&quot;dc:subject&quot;&gt;&lt;a href=&quot;/tags/common-ground&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;common ground&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-12&quot; rel=&quot;dc:subject&quot;&gt;&lt;a href=&quot;/tags/digitaal-paradigma&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;digitaal paradigma&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/div&gt;&lt;div class=&quot;field field-name-field-levenscyclus field-type-taxonomy-term-reference field-label-inline clearfix&quot;&gt;&lt;h3 class=&quot;field-label&quot;&gt;Levenscyclus: &lt;/h3&gt;&lt;ul class=&quot;links inline&quot;&gt;&lt;li class=&quot;taxonomy-term-reference-0&quot;&gt;&lt;a href=&quot;/levenscyclus/1-ontstaan&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;1 Ontstaan&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-1&quot;&gt;&lt;a href=&quot;/levenscyclus/2-waarderen&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;2 Waarderen&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-2&quot;&gt;&lt;a href=&quot;/levenscyclus/3-gebruiken-afstemmen-en-toezicht-houden&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;3 Gebruiken, afstemmen en toezicht houden&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-3&quot;&gt;&lt;a href=&quot;/levenscyclus/4-bewaren&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;4 Bewaren&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/div&gt;&lt;div class=&quot;field field-name-field-informatiemodel field-type-taxonomy-term-reference field-label-inline clearfix&quot;&gt;&lt;h3 class=&quot;field-label&quot;&gt;Informatiemodel: &lt;/h3&gt;&lt;ul class=&quot;links inline&quot;&gt;&lt;li class=&quot;taxonomy-term-reference-0&quot;&gt;&lt;a href=&quot;/contextmodel/context&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;Context&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-1&quot;&gt;&lt;a href=&quot;/contextmodel/handeling&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;Handeling&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-2&quot;&gt;&lt;a href=&quot;/contextmodel/informatieobject-0&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;Informatieobject&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/div&gt;&lt;div class=&quot;field field-name-field-adthis field-type-addthis field-label-above&quot;&gt;&lt;div class=&quot;field-label&quot;&gt;Sharte this / Add this:&amp;nbsp;&lt;/div&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot;&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;field field-name-field-datum-eerste-publicatie field-type-datetime field-label-inline clearfix&quot;&gt;&lt;div class=&quot;field-label&quot;&gt;Datum eerste publicatie:&amp;nbsp;&lt;/div&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot;&gt;&lt;span  property=&quot;dc:date&quot; datatype=&quot;xsd:dateTime&quot; content=&quot;2017-12-01T20:07:00+01:00&quot; class=&quot;date-display-single&quot;&gt;vrijdag, 1 december 2017 - 8:07pm&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
 <pubDate>Fri, 01 Dec 2017 19:15:15 +0000</pubDate>
 <dc:creator>webmaster</dc:creator>
 <guid isPermaLink="false">1371 at http://labyrinth.rienkjonker.nl</guid>
</item>
<item>
 <title>A perfect match? Connecting partners in the labyrinth of information</title>
 <link>http://labyrinth.rienkjonker.nl/content/perfect-match-connecting-partners-labyrinth-information</link>
 <description>&lt;div class=&quot;field field-name-field-levenscyclus field-type-taxonomy-term-reference field-label-inline clearfix&quot;&gt;&lt;h3 class=&quot;field-label&quot;&gt;Levenscyclus: &lt;/h3&gt;&lt;ul class=&quot;links inline&quot;&gt;&lt;li class=&quot;taxonomy-term-reference-0&quot;&gt;&lt;a href=&quot;/levenscyclus/1-ontstaan&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;1 Ontstaan&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-1&quot;&gt;&lt;a href=&quot;/levenscyclus/2-waarderen&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;2 Waarderen&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-2&quot;&gt;&lt;a href=&quot;/levenscyclus/3-gebruiken-afstemmen-en-toezicht-houden&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;3 Gebruiken, afstemmen en toezicht houden&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-3&quot;&gt;&lt;a href=&quot;/levenscyclus/4-bewaren&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;4 Bewaren&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/div&gt;&lt;div class=&quot;field field-name-field-informatiemodel field-type-taxonomy-term-reference field-label-inline clearfix&quot;&gt;&lt;h3 class=&quot;field-label&quot;&gt;Informatiemodel: &lt;/h3&gt;&lt;ul class=&quot;links inline&quot;&gt;&lt;li class=&quot;taxonomy-term-reference-0&quot;&gt;&lt;a href=&quot;/contextmodel/context&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;Context&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-1&quot;&gt;&lt;a href=&quot;/contextmodel/handeling&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;Handeling&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-2&quot;&gt;&lt;a href=&quot;/contextmodel/informatieobject-0&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;Informatieobject&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/div&gt;&lt;div class=&quot;field field-name-field-tags field-type-taxonomy-term-reference field-label-inline clearfix&quot;&gt;&lt;h3 class=&quot;field-label&quot;&gt;Trefwoord: &lt;/h3&gt;&lt;ul class=&quot;links inline&quot;&gt;&lt;li class=&quot;taxonomy-term-reference-0&quot;&gt;&lt;a href=&quot;/tags/digitaal-paradigma&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;digitaal paradigma&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-1&quot;&gt;&lt;a href=&quot;/tags/leeuwarder-informatiemodel-lim&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;Leeuwarder Informatiemodel (LIM)&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-2&quot;&gt;&lt;a href=&quot;/tags/informatiemodel&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;informatiemodel&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-3&quot;&gt;&lt;a href=&quot;/tags/context&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;context&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-4&quot;&gt;&lt;a href=&quot;/tags/handeling&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;handeling&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-5&quot;&gt;&lt;a href=&quot;/tags/semantische-informatie&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;semantische informatie&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-6&quot;&gt;&lt;a href=&quot;/tags/communicatie&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;communicatie&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/div&gt;&lt;div class=&quot;field field-name-field-datum-eerste-publicatie field-type-datetime field-label-inline clearfix&quot;&gt;&lt;div class=&quot;field-label&quot;&gt;Datum eerste publicatie:&amp;nbsp;&lt;/div&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot;&gt;&lt;span  property=&quot;dc:date&quot; datatype=&quot;xsd:dateTime&quot; content=&quot;2017-12-01T21:42:00+01:00&quot; class=&quot;date-display-single&quot;&gt;vrijdag, 1 december 2017 - 9:42pm&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;field field-name-node-gallery-media field-type-file field-label-above&quot;&gt;&lt;div class=&quot;field-label&quot;&gt;Bestanden:&amp;nbsp;&lt;/div&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot;&gt;&lt;table class=&quot;sticky-enabled&quot;&gt;
 &lt;thead&gt;&lt;tr&gt;&lt;th&gt;Bijlage&lt;/th&gt;&lt;th&gt;Grootte&lt;/th&gt; &lt;/tr&gt;&lt;/thead&gt;
&lt;tbody&gt;
 &lt;tr class=&quot;odd&quot;&gt;&lt;td&gt;&lt;span class=&quot;file&quot;&gt;&lt;img class=&quot;file-icon&quot; alt=&quot;PDF-pictogram&quot; title=&quot;application/pdf&quot; src=&quot;/modules/file/icons/application-pdf.png&quot; /&gt; &lt;a href=&quot;http://labyrinth.rienkjonker.nl/sites/default/files/Archives_in_Liquid_Times_Jonker.pdf&quot; type=&quot;application/pdf; length=5360291&quot;&gt;Archives_in_Liquid_Times_Jonker.pdf&lt;/a&gt;&lt;/span&gt;&lt;/td&gt;&lt;td&gt;5.11 MB&lt;/td&gt; &lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
 <pubDate>Wed, 13 Dec 2017 00:02:03 +0000</pubDate>
 <dc:creator>webmaster</dc:creator>
 <guid isPermaLink="false">1372 at http://labyrinth.rienkjonker.nl</guid>
</item>
<item>
 <title>Information model - Three elements - EN - version 2</title>
 <link>http://labyrinth.rienkjonker.nl/content/information-model-three-elements-en-version-2</link>
 <description>&lt;div class=&quot;field field-name-field-afbeelding field-type-image field-label-above&quot;&gt;&lt;div class=&quot;field-label&quot;&gt;Afbeelding:&amp;nbsp;&lt;/div&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot;&gt;&lt;a href=&quot;http://labyrinth.rienkjonker.nl/sites/default/files/Konstanten%20v8%20%28Kaal%29_EN.png&quot; title=&quot;Three constants and two connectors&quot; class=&quot;colorbox&quot; data-colorbox-gallery=&quot;gallery-node-1334-Gjsn38vt-74&quot; data-cbox-img-attrs=&quot;{&amp;quot;title&amp;quot;: &amp;quot;Three constants and two connectors&amp;quot;, &amp;quot;alt&amp;quot;: &amp;quot;&amp;quot;}&quot;&gt;&lt;img typeof=&quot;foaf:Image&quot; src=&quot;http://labyrinth.rienkjonker.nl/sites/default/files/styles/medium/public/Konstanten%20v8%20%28Kaal%29_EN.png?itok=cRGbEwb8&quot; width=&quot;220&quot; height=&quot;183&quot; alt=&quot;&quot; title=&quot;Three constants and two connectors&quot; /&gt;&lt;/a&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;field field-name-field-soort-image field-type-list-text field-label-inline clearfix&quot;&gt;&lt;div class=&quot;field-label&quot;&gt;Soort:&amp;nbsp;&lt;/div&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot;&gt;Schema&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;field field-name-body field-type-text-with-summary field-label-hidden&quot;&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot; property=&quot;content:encoded&quot;&gt;&lt;p&gt;A piece of Semantic Information (SI) consists of three constant elements&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;a context (C),&lt;/li&gt;
&lt;li&gt;an activity (A) and&lt;/li&gt;
&lt;li&gt;an information object (Io)&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;SI is not self contained communicates through inbound and outbound  connectors with other pieces of SI.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The contect (C) defines the activity (A) and the information object (Io).&lt;/li&gt;
&lt;li&gt;An information object (Io) is part of a activity (A) whithin a context (C)&lt;/li&gt;
&lt;li&gt;An activity (A) uses an information object (Io) whitin a context (C)&lt;/li&gt;
&lt;/ul&gt;
&lt;hr /&gt;
&lt;p&gt;Schema is onderdeel van / Scheme is part of&lt;/p&gt;
&lt;div&gt;Jonker, R, &lt;a href=&quot;https://labyrinth.rienkjonker.nl/content/perfect-match-connecting-partners-labyrinth-information-full-text&quot; style=&quot;font-size: 9pt; font-style: italic;&quot;&gt;A perfect match? Connecting partners in the labyrinth of information&lt;/a&gt;, &lt;/div&gt;
&lt;div&gt;In Frans Smit, Arnoud Glaudemans and Rienk Jonker (eds.), &lt;a href=&quot;https://labyrinth.rienkjonker.nl/content/archives-liquid-times&quot; style=&quot;font-size: 9pt; font-style: italic;&quot;&gt;Archives in liquid times&lt;/a&gt;, Stichting Archiefpublicaties, &#039;s Gravenhage, 2017. (p. 72-91)&lt;/div&gt;
&lt;p&gt;Zie ook de pagina&#039;s&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;a href=&quot;/content/informatiemodel-de-drie-elementen-nl-versie-1&quot;&gt;Informatiemodel - De drie elementen - NL versie 1&lt;/a&gt; (preceding first Dutch version without connectors)&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/content/informatie-een-conceptueel-labyrinth&quot;&gt;Informatie - een conceptueel labyrinth&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/content/semantic-information&quot;&gt;Semantic information&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/content/informatiemodel-context&quot;&gt;Informatiemodel - Context&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/content/record-vs-semantic-information&quot;&gt;Record vs semantic information&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/content/records-management-communicatiemodel&quot;&gt;Records Management Communicatiemodel&lt;/a&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;field field-name-field-album field-type-taxonomy-term-reference field-label-inline clearfix&quot;&gt;&lt;h3 class=&quot;field-label&quot;&gt;Album: &lt;/h3&gt;&lt;ul class=&quot;links inline&quot;&gt;&lt;li class=&quot;taxonomy-term-reference-0&quot;&gt;&lt;a href=&quot;/albums/lim&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;LIM&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-1&quot;&gt;&lt;a href=&quot;/albums/mijn-schemas&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;Mijn schema&amp;#039;s&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/div&gt;&lt;div class=&quot;field field-name-field-levenscyclus field-type-taxonomy-term-reference field-label-inline clearfix&quot;&gt;&lt;h3 class=&quot;field-label&quot;&gt;Levenscyclus: &lt;/h3&gt;&lt;ul class=&quot;links inline&quot;&gt;&lt;li class=&quot;taxonomy-term-reference-0&quot;&gt;&lt;a href=&quot;/levenscyclus/11-definitie&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;1.1 Definitie&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/div&gt;&lt;div class=&quot;field field-name-field-informatiemodel field-type-taxonomy-term-reference field-label-inline clearfix&quot;&gt;&lt;h3 class=&quot;field-label&quot;&gt;Informatiemodel: &lt;/h3&gt;&lt;ul class=&quot;links inline&quot;&gt;&lt;li class=&quot;taxonomy-term-reference-0&quot;&gt;&lt;a href=&quot;/contextmodel/context&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;Context&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-1&quot;&gt;&lt;a href=&quot;/contextmodel/handeling&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;Handeling&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-2&quot;&gt;&lt;a href=&quot;/contextmodel/informatieobject-0&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;Informatieobject&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/div&gt;&lt;div class=&quot;field field-name-field-tags field-type-taxonomy-term-reference field-label-inline clearfix&quot;&gt;&lt;h3 class=&quot;field-label&quot;&gt;Labels: &lt;/h3&gt;&lt;ul class=&quot;links inline&quot;&gt;&lt;li class=&quot;taxonomy-term-reference-0&quot;&gt;&lt;a href=&quot;/tags/imrec&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;ImRec&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-1&quot;&gt;&lt;a href=&quot;/tags/imarch&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;ImArch&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-2&quot;&gt;&lt;a href=&quot;/tags/semantische-informatie&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;semantische informatie&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-3&quot;&gt;&lt;a href=&quot;/tags/context&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;context&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-4&quot;&gt;&lt;a href=&quot;/tags/handeling&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;handeling&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-5&quot;&gt;&lt;a href=&quot;/tags/informatieobject&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;informatieobject&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-6&quot;&gt;&lt;a href=&quot;/tags/leeuwarder-informatiemodel-lim&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;Leeuwarder Informatiemodel (LIM)&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/div&gt;</description>
 <pubDate>Thu, 27 Apr 2017 19:28:25 +0000</pubDate>
 <dc:creator>webmaster</dc:creator>
 <guid isPermaLink="false">1334 at http://labyrinth.rienkjonker.nl</guid>
</item>
<item>
 <title>Overbrenging in digitale omgeving</title>
 <link>http://labyrinth.rienkjonker.nl/content/overbrenging-digitale-omgeving</link>
 <description>&lt;div class=&quot;field field-name-field-afbeelding field-type-image field-label-above&quot;&gt;&lt;div class=&quot;field-label&quot;&gt;Afbeelding:&amp;nbsp;&lt;/div&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot;&gt;&lt;a href=&quot;http://labyrinth.rienkjonker.nl/sites/default/files/modeloverbrengen.png&quot; title=&quot;Overbrenging in digitale omgeving&quot; class=&quot;colorbox&quot; data-colorbox-gallery=&quot;gallery-node-720-Gjsn38vt-74&quot; data-cbox-img-attrs=&quot;{&amp;quot;title&amp;quot;: &amp;quot;Overbrenging in digitale omgeving&amp;quot;, &amp;quot;alt&amp;quot;: &amp;quot;&amp;quot;}&quot;&gt;&lt;img typeof=&quot;foaf:Image&quot; src=&quot;http://labyrinth.rienkjonker.nl/sites/default/files/styles/medium/public/modeloverbrengen.png?itok=LO0d7QpS&quot; width=&quot;220&quot; height=&quot;149&quot; alt=&quot;&quot; title=&quot;Overbrenging in digitale omgeving&quot; /&gt;&lt;/a&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;field field-name-field-soort-image field-type-list-text field-label-inline clearfix&quot;&gt;&lt;div class=&quot;field-label&quot;&gt;Soort:&amp;nbsp;&lt;/div&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot;&gt;Schema&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;field field-name-body field-type-text-with-summary field-label-hidden&quot;&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot; property=&quot;content:encoded&quot;&gt;&lt;p&gt;Een eerste model voor overbrenging van digitale gegevens. Dit model is nog geënt op de &lt;a href=&quot;/content/layercake-prototype&quot;&gt;layercake van het semantisch web&lt;/a&gt; in samenhang met de modellen van OAIS en ED3. Dit schema is de voorganger van schema &lt;a href=&quot;/content/uitwisselbaarheid&quot;&gt;Uitwisselbaarheid &lt;/a&gt;dat uitgaat van negen lagen. &lt;/p&gt;
&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;field field-name-field-album field-type-taxonomy-term-reference field-label-inline clearfix&quot;&gt;&lt;h3 class=&quot;field-label&quot;&gt;Album: &lt;/h3&gt;&lt;ul class=&quot;links inline&quot;&gt;&lt;li class=&quot;taxonomy-term-reference-0&quot;&gt;&lt;a href=&quot;/albums/mijn-schemas&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;Mijn schema&amp;#039;s&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/div&gt;&lt;div class=&quot;field field-name-field-levenscyclus field-type-taxonomy-term-reference field-label-inline clearfix&quot;&gt;&lt;h3 class=&quot;field-label&quot;&gt;Levenscyclus: &lt;/h3&gt;&lt;ul class=&quot;links inline&quot;&gt;&lt;li class=&quot;taxonomy-term-reference-0&quot;&gt;&lt;a href=&quot;/levenscyclus/11-definitie&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;1.1 Definitie&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/div&gt;&lt;div class=&quot;field field-name-field-informatiemodel field-type-taxonomy-term-reference field-label-inline clearfix&quot;&gt;&lt;h3 class=&quot;field-label&quot;&gt;Informatiemodel: &lt;/h3&gt;&lt;ul class=&quot;links inline&quot;&gt;&lt;li class=&quot;taxonomy-term-reference-0&quot;&gt;&lt;a href=&quot;/contextmodel/context&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;Context&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/div&gt;&lt;div class=&quot;field field-name-field-tags field-type-taxonomy-term-reference field-label-inline clearfix&quot;&gt;&lt;h3 class=&quot;field-label&quot;&gt;Labels: &lt;/h3&gt;&lt;ul class=&quot;links inline&quot;&gt;&lt;li class=&quot;taxonomy-term-reference-0&quot;&gt;&lt;a href=&quot;/tags/overdragen&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;overdragen&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-1&quot;&gt;&lt;a href=&quot;/tags/imrec&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;ImRec&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-2&quot;&gt;&lt;a href=&quot;/tags/imarch&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;ImArch&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-3&quot;&gt;&lt;a href=&quot;/tags/informatiemodel&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;informatiemodel&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-4&quot;&gt;&lt;a href=&quot;/tags/oais&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;OAIS&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-5&quot;&gt;&lt;a href=&quot;/tags/semantisch-web&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;semantisch web&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-6&quot;&gt;&lt;a href=&quot;/tags/layercake&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;layercake&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-7&quot;&gt;&lt;a href=&quot;/tags/uitwisselbaarheid&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;uitwisselbaarheid&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/div&gt;</description>
 <pubDate>Sun, 07 Feb 2016 17:07:02 +0000</pubDate>
 <dc:creator>webmaster</dc:creator>
 <guid isPermaLink="false">720 at http://labyrinth.rienkjonker.nl</guid>
</item>
<item>
 <title>Een poging tot een archivistisch model - concept</title>
 <link>http://labyrinth.rienkjonker.nl/content/een-poging-tot-een-archivistisch-model-concept</link>
 <description>&lt;div class=&quot;field field-name-body field-type-text-with-summary field-label-hidden&quot;&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot; property=&quot;content:encoded&quot;&gt;&lt;h3&gt;Inleiding&lt;/h3&gt;
&lt;p&gt;Discussies tussen mensen willen vooral wel eens moeizaam verlopen wanneer er onduidelijkheid is over de exacte invulling van gebruikte termen en begrippen. Vooral de (spraak)verwarring die ontstaat omdat er verschillende beelden zijn van begrippen en activiteiten. Daardoor ontstaan er ook uit elkaar lopende verwachtingen die over en weer niet waar te maken zijn.&lt;br /&gt;
Zo ook de discussies binnen het vakgebied van de archivaris en de documentaire informatievoorziener. Op het eerste gezicht zou de indruk kunnen bestaan dat er tussen beide beroepsgroepen een bijna onoverbrugbare kloof bestaat. Immers wordt de archivaris beschouwd als de beheerder van het cultureel erfgoed (met veel hoofdletters) is de DIV-er (slechts) de beheerder van archief in de dynamische fase. Zo wordt er ook een verschil gemaakt tussen informatiebeheerders werkzaam in de publieke sector en binnen de private sector. Het steeds weer benadrukken van mogelijke verschillen komt de onderlinge verhoudingen niet ten goede.&lt;/p&gt;
&lt;!--break--&gt;&lt;p&gt;Willen beide groepen komen tot een serieuze professionalisering van het vak, een acceptatie als volwaardige professie door de verschillende gebruikers en een verbetering van het imago dan zal naar mijn mening een verandering moeten komen.&lt;/p&gt;
&lt;p&gt;Al een aantal jaren heb ik het gevoel dat er duidelijkheid moet komen over het informatiebeheer. Vanuit mijn werk als archiefinspecteur bij de gemeente Groningen, pendelend binnen de publieke sector tussen twee beroepsgroepen, zie ik zelf meer overeenkomsten dan verschillen. Juist de oprukkende digitalisering, de toenemende kwetsbaarheid van de informatie, de toenemende complexiteit van samenleving en organisaties maken een explicitering van impliciete archivistische kennis noodzakelijk. De volgende vragen zijn te beantwoorden:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;wat is de reikwijdte van het vak&lt;/li&gt;
&lt;li&gt;welke activiteiten horen bij het vak&lt;/li&gt;
&lt;li&gt;wat is het object van zorg&lt;/li&gt;
&lt;li&gt;wie zijn er bij betrokken&lt;/li&gt;
&lt;li&gt;is er sprake van een aspect van tijd&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;Terminologie&lt;/h3&gt;
&lt;p&gt;Belangrijk voor de afbakening van een vak of vakwetenschap is een begrippenapparaat waarmee duidelijk de grenzen worden afgebakend. In het begin van 2001 werd door de KVAN een concepttekst voor een nieuw archieflexicon gepresenteerd. Het is inhoudelijk gezien een gedegen vakwerk maar voor mijn gevoel ontbrak een basis.&lt;br /&gt;
Voor mijn gevoel was het concept meer een vernieuwde aangepaste versie van het Lexicon uit 1983. Een begrippenapparaat dat geënt was op het fundament van het Nederlandse archiefwezen, de 100 regels. De auteurs zijn te weinig in staat gebleken oude en nieuwe concepten zodanig op een lijn te brengen, omdat een fundament ontbrak. Terwijl toch duidelijk zou moeten zijn dat in de loop van de tijd door technologische veranderingen, veranderde inzichten en uitgangspunten het fundament aan aanpassing toe is.&lt;/p&gt;
&lt;p&gt;Zolang er geen nieuw fundament is gelegd heeft een nieuwe terminologie hoogstens zin als een tijdelijke verbetering van het bestaande Lexicon. De basis voor elke terminologie is een grondige beschrijving van het betrokken vakgebied.&lt;/p&gt;
&lt;h3&gt;Indeling&lt;/h3&gt;
&lt;p&gt;De meeste informatiebeheerders zijn dol op het maken van indelingen van de werkelijkheid die zij aantreffen. Dit doen zij in de vorm van classificaties of modellen. Vreemd genoeg is tot nu toe het eigen vak buiten schot gebleven. Gevolg is dat een concept of een model waar het hele vak aan gehangen kan worden ontbreekt.&lt;/p&gt;
&lt;p&gt;Mijn stelling is dat de manier waarop wij in dit tijdsgewricht met het vak omgaan door onze democratisch georiënteerde openbaarheidscultuur&lt;a class=&quot;see-footnote&quot; id=&quot;footnoteref1_69c9tca&quot; title=&quot;Clemens Rehm, Spielwiese oder Pflichtaufgabe; Archivistische Öffentlichkeitsarbeit als Fachaufgabe, Der Archivar, 1998. Jg. 51, 1998, H2.&quot; href=&quot;#footnote1_69c9tca&quot;&gt;1&lt;/a&gt;, wordt bepaald. Daar is niks mis mee, maar wij moeten wel in rekening houden met het feit dat hetzelfde vak ook wordt uitgevoerd in andere contexten, culturen en samenlevingen die een andere achtergrond hebben.&lt;br /&gt;
Doel van de archivistiek als vakwetenschap is primair een kader te bieden voor het archiveren van gegevens en secundair voor het beschikbaarstellen aan gebruikers &lt;a class=&quot;see-footnote&quot; id=&quot;footnoteref2_umnh6ht&quot; title=&quot;Arnoud Glaudemans, Over oude en nieuwe archiefwetenschap, Archievenblad, jaargang 106, nummer 8, (oktober 2002)&quot; href=&quot;#footnote2_umnh6ht&quot;&gt;2&lt;/a&gt;. Vooral het gebruikersdomein wordt door de geldende cultuur bepaald. Dat wij dat niet beseffen is volgens mij een van de belangrijkste oorzaken voor de vele verwarrende discussies.&lt;/p&gt;
&lt;h3&gt;Het model&lt;/h3&gt;
&lt;p&gt;&lt;img alt=&quot;Het model&quot; src=&quot;/sites/default/files/images/model.gif&quot; style=&quot;float:left; height:369px; margin:20px; width:425px&quot; /&gt;In dit verhaal wil ik een model schetsen waarin een 6-tal elementen gezamenlijk het hele terrein van de archivistiek beslaan.&lt;a class=&quot;see-footnote&quot; id=&quot;footnoteref3_4azag6t&quot; title=&quot;Een actuele versie van het model staat in Jonker, R, A perfect match? Connecting partners in the labyrinth of information, In Frans Smit, Arnoud Glaudemans and Rienk Jonker (eds.), Archives in liquid times, Stichting Archiefpublicaties, &#039;s Gravenhage, 2017. (p. 72-91)&quot; href=&quot;#footnote3_4azag6t&quot;&gt;3&lt;/a&gt; Het model bestaat uit een beschrijving van het aandachtsgebied, de grenzen, een afbakening en de raakvlakken met verwante vakgebieden. De grenzen en afbakening zijn van belang om buitenstaanders uit te kunnen leggen wat een vakgebied inhoud.&lt;br /&gt;
In de eerste plaats zullen we moeten aangeven waar de aandacht op gericht is. Vervolgens komt een beschrijving van de hoofdactiviteiten van de beroepsbeoefenaren. Dit bevat impliciet de afbakening. Een beschrijving van de spelers op het veld, beroepsbeoefenaren en anderen is ook aan te brengen. Het aspect van tijd is op te nemen om dat de tijd de volgorde van de activiteiten bepaald en de oorzaak kan zijn dat bepaalde activiteiten worden uitgevoerd.&lt;/p&gt;
&lt;h3&gt;Begrenzing&lt;/h3&gt;
&lt;p&gt;Voor mij staan niet dè archivaris en dè archivistiek centraal, maar de informatiebeheerder, het informatiebeheer en de archieffunctie, een prachtige term op de kaart gezet in het rapport &lt;em&gt;Het geheugen als actieve kracht; De archieffunctie binnen de digitale overheid&lt;/em&gt; uit 1999&lt;a class=&quot;see-footnote&quot; id=&quot;footnoteref4_apei7bu&quot; title=&quot;Paul Baak en Kees Koenen, Het geheugen als actieve kracht; De archieffunctie binnen de digitale overheid, Programma Digitale Duurzaamheid/Synergie Consultancy B.V, Den Haag, 1999.&quot; href=&quot;#footnote4_apei7bu&quot;&gt;4&lt;/a&gt;. Deze beide begrippen hebben een minder exclusieve en beladen betekenis, die eenvoudiger op elk moment binnen het records continuüm gehanteerd kunnen worden. Verder wil ik vooral voorkomen dat te veel de nadruk wordt gelegd op de archivaris in de zin van de beheerder van het cultureel erfgoed.&lt;br /&gt;
We willen wel over een consistent begrippenapparaat beschikken dat het werkterrein van het traditionele archiefbeheer en de moderne veelal digitale informatievoorziening omvat. De behoefte bestaat daarom aan termen en begrippen die de aspecten van vorm en inhoud en middelen (systemen, procedures, hardware, software, regels) en de materie (de informatie zelf) dekt.&lt;br /&gt;
Wat ik dus zal proberen is aan te geven wat een informatiebeheerder is en wat hij doet en wat zijn object van zorg is.&lt;/p&gt;
&lt;h3&gt;Informatiebeheer&lt;/h3&gt;
&lt;p&gt;Met deze term kan op globale wijze zonder al te specifiek te worden het aandachtsgebied van de functionarissen die hierin werkzaam ingekader worden.&lt;br /&gt;
Informatiebeheer is een containerbegrip dat het geheel van informatievoorziening en het feitelijk beheer van archiefbescheiden omvat.&lt;br /&gt;
Informatievoorziening is het geheel van handelingen, samenhangend met de inrichting en het beheer van informatiesystemen. Waarbij een informatiesysteem te beschouwen is als een samenhangend geheel van documentatie, procedures, apparatuur, programmatuur en ander materiaal, met behulp waarvan archiefbescheiden worden vervaardigd, geregistreerd, bewaard, bewerkt, verzonden, ontvangen, geraadpleegd en beschikbaar gesteld.&lt;br /&gt;
Op deze manier komt de term overeen met het veelgebruikte ‘record(s) management’.&lt;/p&gt;
&lt;h3&gt;Informatiebeheerder&lt;/h3&gt;
&lt;p&gt;De informatiebeheerder is een van de actoren die in allerlei hoedanigheden werkzaam is binnen de informatievoorziening van een organisatie en het beheer de archiefbescheiden uitvoert. Dit is een term die te beschouwen is als een goede equivalent van het begrip record(s)manager.&lt;br /&gt;
De term informatiebeheerder wordt gebruikt om aan te geven dat het kan gaan om een functionaris in de dynamische, semi-statische en statische fase.&lt;/p&gt;
&lt;h3&gt;Archieffunctie&lt;/h3&gt;
&lt;p&gt;De kernactiviteiten van een informatiebeheerder zijn samen te vatten met de term archieffunctie. De archieffunctie is het geheel van activiteiten en functionaliteiten die organisatie in staat stelt archiefbescheiden te gebruiken, zich op basis van deze archiefbescheiden te verantwoorden voor haar handelen en in overeenstemming met de wet om te gaan met materiaal met een cultureel-historische waarde. De archieffunctie is gericht op zowel digitale als niet-digitale bescheiden. De archieffunctie bestaat uit een 4-tal hoofdprocessen of activiteiten.&lt;/p&gt;
&lt;h4&gt;Registreren&lt;/h4&gt;
&lt;p&gt;Al die activiteiten die zijn gericht op het vastleggen van kenmerken van archiefbescheiden volgens een vooraf vastgestelde informatiebehoefte. Doel van het registreren is het leveren van bewijs van aanwezigheid van informatie, het snel kunnen vinden van informatie, het aanbrengen van logische verbanden tussen de archiefbescheiden en het leveren van managementinformatie.&lt;/p&gt;
&lt;h4&gt;Waarderen&lt;/h4&gt;
&lt;p&gt;Geheel van activiteiten gericht op het bepalen van de bewaartermijnen van archiefbescheiden, het uitvoeren van voorselectie en/of selectie, het uitvoeren van de feitelijke vernietiging en het overbrengen van permanent te bewaren archiefbescheiden naar een archiefbewaarplaats.&lt;/p&gt;
&lt;h4&gt;Bewaren&lt;/h4&gt;
&lt;p&gt;Activiteiten gericht op het beheren van archiefbescheiden op zodanige manier dat zij ongeschonden bewaard blijven gedurende de vooraf vastgestelde (wettelijke) bewaartermijn. De bewaring geschiedt met behoud van inhoud, structuur, context en registratiekenmerken.&lt;/p&gt;
&lt;h4&gt;Beschikbaarstellen&lt;/h4&gt;
&lt;p&gt;Activiteiten gericht op het op aanvraag ter inzage geven of uitlenen van archiefbescheiden of informatie daaruit aan afnemers.&lt;br /&gt;
Het beschikbaarstellen vindt plaats onder voorwaarden en restricties beschreven in privacyregelingen, regelingen ten aanzien van de openbaarheid en beveiligingsplannen.&lt;/p&gt;
&lt;h3&gt;Object van zorg&lt;a class=&quot;see-footnote&quot; id=&quot;footnoteref5_76tfrcz&quot; title=&quot;Het object van zorg is het Informatieobject inclusief de context. Zie NEN 2082.&quot; href=&quot;#footnote5_76tfrcz&quot;&gt;5&lt;/a&gt;&lt;/h3&gt;
&lt;div&gt;&lt;img alt=&quot;De lagen&quot; src=&quot;/sites/default/files/images/lagen.gif&quot; style=&quot;float:right; height:447px; line-height:20.8px; margin:20px; width:150px&quot; /&gt;
&lt;div&gt; &lt;/div&gt;
&lt;p&gt;De kern van het informatiebeheer richt zich op de gegevens die gebruikt worden binnen een bepaald (bedrijfs)proces. De gegevens bestaan uit een logische inhoudelijke en een fysieke technische component. Het logische gedeelte kan niet bestaan zonder het fysieke gedeelte. Het fysieke gedeelte, de toegepaste techniek kan in de loop van de tijd vervangen worden door nieuwe vormen van techniek om de levensduur van het logische gedeelte te verlengen.Het logische gedeelte bestaat uit drie elementen die onlosmakelijk bij elkaar horen. Dit zijn de context, de structuur en de inhoud. Ik ga hier niet te diep op in. Context is een ruime term, het betreft de omgeving of de situatie waarbinnen het gegeven bestaat. Structuur komt overeen met de term redactionele vorm. De redactionele vorm bepaald de status en de opmaak van de gegevens. De inhoud is het gegeven op zich. Deze zijn in de vorm van meta-gegevens te beschrijven. Het object van zorg bestaat uit een aantal lagen. Lijkt wel wat op het lagenmodel van ISAD(g). Per laag zijn kenmerken (meta-gegevens) vast te leggen. De grootste eenheid, een collectie, bestaat uit een verzameling blokken. De kenmerken van een collectie zijn van toepassing op de blokken. Blokken kunnen weer bestaan uit kleinere eenheden bestanddelen. Het laagste niveau is een enkel gegeven dat als item te beheren en te beschrijven is.&lt;/p&gt;&lt;/div&gt;
&lt;div&gt;
&lt;h3&gt;Kwaliteit&lt;/h3&gt;
&lt;p&gt;Beheershandelingen worden uitgevoerd om de informatie op een bepaald kwaliteitsniveau, een toestand, te brengen. Het niveau is afhankelijk van de cultuur, de belangen en de beschikbare middelen.&lt;br /&gt;
Er zijn verschillende soorten kwaliteiten. Om deze te groeperen zijn diverse gezichtspunten mogelijk. Mijn suggestie is ze op de volgende manier te groeperen.&lt;/p&gt;
&lt;h4&gt;1 Culturele kwaliteiten&lt;/h4&gt;
&lt;p&gt;Sommige kwaliteiten zijn cultureel bepaald en hebben betrekking op de normen en waarden die de samenleving aan de daarbinnen operende organisaties en personen (actoren) min of meer oplegt.&lt;br /&gt;
Voorbeelden: openbaarheid, vertrouwelijkheid, beschikbaarheid&lt;/p&gt;
&lt;h4&gt;2 Technische kwaliteiten&lt;/h4&gt;
&lt;p&gt;Dit betreft de normen en eisen die te stellen zijn aan de diverse vormen van techniek die binnen het vakgebied gebruikt worden.&lt;br /&gt;
Voorbeelden: duurzaamheid, goede staat, materiele staat, kwetsbaarheid&lt;/p&gt;
&lt;h4&gt;3 Juridische kwaliteiten&lt;/h4&gt;
&lt;p&gt;Er bestaan ook specifieke kwaliteiten die vanuit het vakgebied gesteld worden.&lt;br /&gt;
Voorbeelden: authenticiteit, betrouwbaarheid, toegankelijkheid, vindbaarheid, integriteit&lt;/p&gt;
&lt;h4&gt;4 Gebruikskwaliteiten&lt;/h4&gt;
&lt;p&gt;Dit betreft kwaliteiten die tijdens het beheer en het gebruik van het object van belang zijn.&lt;br /&gt;
Voorbeelden: leesbaarheid, interpreteerbaarheid, tijdigheid, onweerlegbaarheid&lt;/p&gt;
&lt;h3&gt;Schematische weergave&lt;/h3&gt;
&lt;p&gt;Dat de zes elementen niet los staan zal duidelijk zijn. Ze staan in een bepaalde onderlinge relatie die zichtbaar te maken is met een lopende zin waar zij als variabelen in opgenomen zijn. Met deze zin wordt in het kort het vakgebied van de informatiebeheerder weergegeven in welke omgeving dan ook.&lt;/p&gt;
&lt;p&gt;Op een bepaald &lt;em&gt;[moment]&lt;/em&gt; voert een &lt;em&gt;[actor]&lt;/em&gt; een &lt;em&gt;[beheershandeling]&lt;/em&gt; uit in het kader van de &lt;em&gt;[archieffunctie]&lt;/em&gt; op het &lt;em&gt;[object van zorg]&lt;/em&gt; om een bepaalde &lt;em&gt;[kwaliteit]&lt;/em&gt; te bereiken.&lt;/p&gt;
&lt;h3&gt;Tabel met waarden voor de variabelen&lt;/h3&gt;
&lt;table border=&quot;0&quot; style=&quot;height:278px; width:722px&quot;&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th scope=&quot;col&quot;&gt;&lt;strong&gt;Beheershandeling&lt;/strong&gt;&lt;/th&gt;
&lt;th scope=&quot;col&quot;&gt;&lt;strong&gt;Actor&lt;/strong&gt;&lt;/th&gt;
&lt;th scope=&quot;col&quot;&gt;
&lt;p&gt;&lt;strong&gt;Archieffunctie&lt;/strong&gt;&lt;/p&gt;
&lt;/th&gt;
&lt;th scope=&quot;col&quot;&gt;&lt;strong&gt;Kwaliteit&lt;/strong&gt;&lt;/th&gt;
&lt;th scope=&quot;col&quot;&gt;&lt;strong&gt;Moment&lt;/strong&gt;&lt;/th&gt;
&lt;th scope=&quot;col&quot;&gt;&lt;strong&gt;Object&lt;/strong&gt;&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;ul&gt;
&lt;li&gt;Acquireren&lt;/li&gt;
&lt;li&gt;beschikbaarstellen&lt;/li&gt;
&lt;li&gt;beveiligen&lt;/li&gt;
&lt;li&gt;conserveren&lt;/li&gt;
&lt;li&gt;creëren&lt;/li&gt;
&lt;li&gt;opmaken&lt;/li&gt;
&lt;li&gt;ordenen&lt;/li&gt;
&lt;li&gt;overbrengen&lt;/li&gt;
&lt;li&gt;raadplegen&lt;/li&gt;
&lt;li&gt;selecteren&lt;/li&gt;
&lt;li&gt;toegankelijk maken&lt;/li&gt;
&lt;li&gt;vernietigen&lt;/li&gt;
&lt;li&gt;verstoren&lt;/li&gt;
&lt;li&gt;vervangen&lt;/li&gt;
&lt;li&gt;vervreemden&lt;/li&gt;
&lt;li&gt;verzenden&lt;/li&gt;
&lt;li&gt;wijzigen&lt;/li&gt;
&lt;/ul&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;ul&gt;
&lt;li&gt;beheerder&lt;/li&gt;
&lt;li&gt;eigenaar&lt;/li&gt;
&lt;li&gt;gebruiker&lt;/li&gt;
&lt;li&gt;toezichthouder&lt;/li&gt;
&lt;li&gt;vormer&lt;/li&gt;
&lt;li&gt;zorgdrager&lt;/li&gt;
&lt;/ul&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;ul&gt;
&lt;li&gt;registreren&lt;/li&gt;
&lt;li&gt;waarderen&lt;/li&gt;
&lt;li&gt;bewaren&lt;/li&gt;
&lt;li&gt;beschikbaarstellen&lt;/li&gt;
&lt;/ul&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;ul&gt;
&lt;li&gt;authenticiteit&lt;/li&gt;
&lt;li&gt;benutbaarheid&lt;/li&gt;
&lt;li&gt;beschikbaarheid&lt;/li&gt;
&lt;li&gt;betrouwbaarheid&lt;/li&gt;
&lt;li&gt;controleerbaarheid&lt;/li&gt;
&lt;li&gt;duurzaamheid&lt;/li&gt;
&lt;li&gt;houdbaarheid&lt;/li&gt;
&lt;li&gt;integriteit&lt;/li&gt;
&lt;li&gt;interpreteerbaarheid&lt;/li&gt;
&lt;li&gt;juistheid&lt;/li&gt;
&lt;li&gt;leesbaarheid&lt;/li&gt;
&lt;li&gt;onweerlegbaarheid&lt;/li&gt;
&lt;li&gt;openbaarheid&lt;/li&gt;
&lt;li&gt;raadpleegbaarheid&lt;/li&gt;
&lt;li&gt;rechtmatigheid&lt;/li&gt;
&lt;li&gt;toegankelijkheid&lt;/li&gt;
&lt;li&gt;volledigheid&lt;/li&gt;
&lt;/ul&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;ol&gt;
&lt;li&gt;ontstaan&lt;/li&gt;
&lt;li&gt;waarderen&lt;/li&gt;
&lt;li&gt;gebruik&lt;/li&gt;
&lt;li&gt;afstoten&lt;/li&gt;
&lt;/ol&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;ul&gt;
&lt;li&gt;inhoud&lt;/li&gt;
&lt;li&gt;context&lt;/li&gt;
&lt;li&gt;gedrag&lt;a class=&quot;see-footnote&quot; id=&quot;footnoteref6_r0mgzdx&quot; title=&quot;In2016 bij de migratie van deze  site toegevoegd&quot; href=&quot;#footnote6_r0mgzdx&quot;&gt;6&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;structuur&lt;/li&gt;
&lt;li&gt;techniek&lt;/li&gt;
&lt;/ul&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;/div&gt;
&lt;ul class=&quot;footnotes&quot;&gt;
&lt;li class=&quot;footnote&quot; id=&quot;footnote1_69c9tca&quot;&gt;&lt;a class=&quot;footnote-label&quot; href=&quot;#footnoteref1_69c9tca&quot;&gt;1.&lt;/a&gt; Clemens Rehm, &lt;em&gt;Spielwiese oder Pflichtaufgabe; Archivistische Öffentlichkeitsarbeit als Fachaufgabe&lt;/em&gt;, Der Archivar, 1998. Jg. 51, 1998, H2.&lt;/li&gt;
&lt;li class=&quot;footnote&quot; id=&quot;footnote2_umnh6ht&quot;&gt;&lt;a class=&quot;footnote-label&quot; href=&quot;#footnoteref2_umnh6ht&quot;&gt;2.&lt;/a&gt; Arnoud Glaudemans, &lt;em&gt;Over oude en nieuwe archiefwetenschap&lt;/em&gt;, Archievenblad, jaargang 106, nummer 8, (oktober 2002)&lt;/li&gt;
&lt;li class=&quot;footnote&quot; id=&quot;footnote3_4azag6t&quot;&gt;&lt;a class=&quot;footnote-label&quot; href=&quot;#footnoteref3_4azag6t&quot;&gt;3.&lt;/a&gt; Een actuele versie van het model staat in Jonker, R, &lt;a href=&quot;https://labyrinth.rienkjonker.nl/content/perfect-match-connecting-partners-labyrinth-information-full-text&quot; style=&quot;font-size: 9pt; font-style: italic;&quot;&gt;A perfect match? Connecting partners in the labyrinth of information&lt;/a&gt;, In Frans Smit, Arnoud Glaudemans and Rienk Jonker (eds.), &lt;a href=&quot;https://labyrinth.rienkjonker.nl/content/archives-liquid-times&quot; style=&quot;font-style: italic; font-size: 9pt;&quot;&gt;Archives in liquid times&lt;/a&gt;, Stichting Archiefpublicaties, &#039;s Gravenhage, 2017. (p. 72-91)&lt;/li&gt;
&lt;li class=&quot;footnote&quot; id=&quot;footnote4_apei7bu&quot;&gt;&lt;a class=&quot;footnote-label&quot; href=&quot;#footnoteref4_apei7bu&quot;&gt;4.&lt;/a&gt; Paul Baak en Kees Koenen, &lt;em&gt;Het geheugen als actieve kracht; De archieffunctie binnen de digitale overheid&lt;/em&gt;, Programma Digitale Duurzaamheid/Synergie Consultancy B.V, Den Haag, 1999.&lt;/li&gt;
&lt;li class=&quot;footnote&quot; id=&quot;footnote5_76tfrcz&quot;&gt;&lt;a class=&quot;footnote-label&quot; href=&quot;#footnoteref5_76tfrcz&quot;&gt;5.&lt;/a&gt; Het object van zorg is het Informatieobject inclusief de context. Zie NEN 2082.&lt;/li&gt;
&lt;li class=&quot;footnote&quot; id=&quot;footnote6_r0mgzdx&quot;&gt;&lt;a class=&quot;footnote-label&quot; href=&quot;#footnoteref6_r0mgzdx&quot;&gt;6.&lt;/a&gt; In2016 bij de migratie van deze  site toegevoegd&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;field field-name-field-tags field-type-taxonomy-term-reference field-label-above clearfix&quot;&gt;&lt;h3 class=&quot;field-label&quot;&gt;Tags: &lt;/h3&gt;&lt;ul class=&quot;links&quot;&gt;&lt;li class=&quot;taxonomy-term-reference-0&quot; rel=&quot;dc:subject&quot;&gt;&lt;a href=&quot;/tags/actor&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;actor&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-1&quot; rel=&quot;dc:subject&quot;&gt;&lt;a href=&quot;/tags/archivistiek&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;archivistiek&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-2&quot; rel=&quot;dc:subject&quot;&gt;&lt;a href=&quot;/tags/definitie&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;definitie&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-3&quot; rel=&quot;dc:subject&quot;&gt;&lt;a href=&quot;/tags/informatieobject&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;informatieobject&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-4&quot; rel=&quot;dc:subject&quot;&gt;&lt;a href=&quot;/tags/kwaliteit&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;kwaliteit&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-5&quot; rel=&quot;dc:subject&quot;&gt;&lt;a href=&quot;/tags/model&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;model&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-6&quot; rel=&quot;dc:subject&quot;&gt;&lt;a href=&quot;/tags/terminologie&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;terminologie&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-7&quot; rel=&quot;dc:subject&quot;&gt;&lt;a href=&quot;/tags/informatiemodel&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;informatiemodel&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-8&quot; rel=&quot;dc:subject&quot;&gt;&lt;a href=&quot;/tags/imarch&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;ImArch&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-9&quot; rel=&quot;dc:subject&quot;&gt;&lt;a href=&quot;/tags/imrec&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;ImRec&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/div&gt;&lt;div class=&quot;field field-name-field-levenscyclus field-type-taxonomy-term-reference field-label-inline clearfix&quot;&gt;&lt;h3 class=&quot;field-label&quot;&gt;Levenscyclus: &lt;/h3&gt;&lt;ul class=&quot;links inline&quot;&gt;&lt;li class=&quot;taxonomy-term-reference-0&quot;&gt;&lt;a href=&quot;/levenscyclus/11-definitie&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;1.1 Definitie&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/div&gt;&lt;div class=&quot;field field-name-field-informatiemodel field-type-taxonomy-term-reference field-label-inline clearfix&quot;&gt;&lt;h3 class=&quot;field-label&quot;&gt;Informatiemodel: &lt;/h3&gt;&lt;ul class=&quot;links inline&quot;&gt;&lt;li class=&quot;taxonomy-term-reference-0&quot;&gt;&lt;a href=&quot;/contextmodel/context&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;Context&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-1&quot;&gt;&lt;a href=&quot;/contextmodel/handeling&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;Handeling&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-2&quot;&gt;&lt;a href=&quot;/contextmodel/informatieobject-0&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;Informatieobject&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/div&gt;&lt;div class=&quot;field field-name-field-adthis field-type-addthis field-label-above&quot;&gt;&lt;div class=&quot;field-label&quot;&gt;Sharte this / Add this:&amp;nbsp;&lt;/div&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot;&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;field field-name-field-datum-eerste-publicatie field-type-datetime field-label-inline clearfix&quot;&gt;&lt;div class=&quot;field-label&quot;&gt;Datum eerste publicatie:&amp;nbsp;&lt;/div&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot;&gt;&lt;span  property=&quot;dc:date&quot; datatype=&quot;xsd:dateTime&quot; content=&quot;2004-09-12T21:15:00+02:00&quot; class=&quot;date-display-single&quot;&gt;zondag, 12 september 2004 - 9:15pm&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
 <pubDate>Sat, 09 Jan 2016 15:45:21 +0000</pubDate>
 <dc:creator>webmaster</dc:creator>
 <guid isPermaLink="false">651 at http://labyrinth.rienkjonker.nl</guid>
</item>
<item>
 <title>Lagen versus Generiek Proces</title>
 <link>http://labyrinth.rienkjonker.nl/content/lagen-versus-generiek-proces</link>
 <description>&lt;div class=&quot;field field-name-field-afbeelding field-type-image field-label-above&quot;&gt;&lt;div class=&quot;field-label&quot;&gt;Afbeelding:&amp;nbsp;&lt;/div&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot;&gt;&lt;a href=&quot;http://labyrinth.rienkjonker.nl/sites/default/files/20211217_9394.png&quot; title=&quot;Lagen versus generiek proces (versie 17 december 2021)&quot; class=&quot;colorbox&quot; data-colorbox-gallery=&quot;gallery-node-488-Gjsn38vt-74&quot; data-cbox-img-attrs=&quot;{&amp;quot;title&amp;quot;: &amp;quot;Lagen versus generiek proces (versie 17 december 2021)&amp;quot;, &amp;quot;alt&amp;quot;: &amp;quot;&amp;quot;}&quot;&gt;&lt;img typeof=&quot;foaf:Image&quot; src=&quot;http://labyrinth.rienkjonker.nl/sites/default/files/styles/medium/public/20211217_9394.png?itok=p6Cx96iU&quot; width=&quot;220&quot; height=&quot;165&quot; alt=&quot;&quot; title=&quot;Lagen versus generiek proces (versie 17 december 2021)&quot; /&gt;&lt;/a&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;field field-name-field-soort-image field-type-list-text field-label-inline clearfix&quot;&gt;&lt;div class=&quot;field-label&quot;&gt;Soort:&amp;nbsp;&lt;/div&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot;&gt;Tabel&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;field field-name-body field-type-text-with-summary field-label-hidden&quot;&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot; property=&quot;content:encoded&quot;&gt;&lt;p&gt;Invulling (confrontatie) van de relatie tussen het generieke proces en de lagen van het contextmodel&lt;/p&gt;
&lt;p&gt;Vertikaal in de tabel de lagen van &lt;a href=&quot;/content/informatiemodel-context&quot; target=&quot;_blank&quot;&gt;het contextmodel&lt;/a&gt; en horizontaal de onderdelen van &lt;a href=&quot;/content/het-generiek-proces-21&quot; target=&quot;_blank&quot;&gt;het generieke proces&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Het idee is dat een informatieobject dankzij techniek bestaat uit gegevens (in eender welke vorm) afkomstig uit een of meer bestanden (dataobjecten).&lt;/p&gt;
&lt;p&gt;Versie 17 december 2021&lt;/p&gt;
&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;field field-name-field-album field-type-taxonomy-term-reference field-label-inline clearfix&quot;&gt;&lt;h3 class=&quot;field-label&quot;&gt;Album: &lt;/h3&gt;&lt;ul class=&quot;links inline&quot;&gt;&lt;li class=&quot;taxonomy-term-reference-0&quot;&gt;&lt;a href=&quot;/albums/lim&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;LIM&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-1&quot;&gt;&lt;a href=&quot;/albums/mijn-schemas&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;Mijn schema&amp;#039;s&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/div&gt;&lt;div class=&quot;field field-name-field-levenscyclus field-type-taxonomy-term-reference field-label-inline clearfix&quot;&gt;&lt;h3 class=&quot;field-label&quot;&gt;Levenscyclus: &lt;/h3&gt;&lt;ul class=&quot;links inline&quot;&gt;&lt;li class=&quot;taxonomy-term-reference-0&quot;&gt;&lt;a href=&quot;/levenscyclus/12-benoemen-informatiesysteem&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;1.2 Benoemen informatiesysteem&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/div&gt;&lt;div class=&quot;field field-name-field-informatiemodel field-type-taxonomy-term-reference field-label-inline clearfix&quot;&gt;&lt;h3 class=&quot;field-label&quot;&gt;Informatiemodel: &lt;/h3&gt;&lt;ul class=&quot;links inline&quot;&gt;&lt;li class=&quot;taxonomy-term-reference-0&quot;&gt;&lt;a href=&quot;/contextmodel/context&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;Context&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-1&quot;&gt;&lt;a href=&quot;/contextmodel/handeling&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;Handeling&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/div&gt;&lt;div class=&quot;field field-name-field-tags field-type-taxonomy-term-reference field-label-inline clearfix&quot;&gt;&lt;h3 class=&quot;field-label&quot;&gt;Labels: &lt;/h3&gt;&lt;ul class=&quot;links inline&quot;&gt;&lt;li class=&quot;taxonomy-term-reference-0&quot;&gt;&lt;a href=&quot;/tags/context&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;context&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-1&quot;&gt;&lt;a href=&quot;/tags/informatiemodel&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;informatiemodel&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-2&quot;&gt;&lt;a href=&quot;/tags/informatieobject&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;informatieobject&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-3&quot;&gt;&lt;a href=&quot;/tags/dataobject&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;dataobject&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-4&quot;&gt;&lt;a href=&quot;/tags/generiek-proces&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;generiek proces&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-5&quot;&gt;&lt;a href=&quot;/tags/proces&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;proces&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-6&quot;&gt;&lt;a href=&quot;/tags/communicatie&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;communicatie&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-7&quot;&gt;&lt;a href=&quot;/tags/zenden&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;zenden&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-8&quot;&gt;&lt;a href=&quot;/tags/ontvangen&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;ontvangen&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-9&quot;&gt;&lt;a href=&quot;/tags/imarch&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;ImArch&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-10&quot;&gt;&lt;a href=&quot;/tags/imrec&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;ImRec&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;taxonomy-term-reference-11&quot;&gt;&lt;a href=&quot;/tags/leeuwarder-informatiemodel-lim&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;Leeuwarder Informatiemodel (LIM)&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/div&gt;</description>
 <pubDate>Sat, 03 Oct 2015 20:27:52 +0000</pubDate>
 <dc:creator>webmaster</dc:creator>
 <guid isPermaLink="false">488 at http://labyrinth.rienkjonker.nl</guid>
</item>
</channel>
</rss>
