<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://www.infra-repository.org/oiar/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Jan+Schoonderbeek</id>
	<title>OIAr - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://www.infra-repository.org/oiar/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Jan+Schoonderbeek"/>
	<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php/Special:Contributions/Jan_Schoonderbeek"/>
	<updated>2026-05-04T12:01:32Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.40.0</generator>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=User:Neil_Kemp&amp;diff=1659</id>
		<title>User:Neil Kemp</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=User:Neil_Kemp&amp;diff=1659"/>
		<updated>2024-01-07T16:33:44Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: Started user page&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Contact Data&lt;br /&gt;
|displayname=Neil Kemp&lt;br /&gt;
|title=Enterprise Architect&lt;br /&gt;
|company=&lt;br /&gt;
|department=&lt;br /&gt;
|telephone=&lt;br /&gt;
|extension=&lt;br /&gt;
|mobile=&lt;br /&gt;
|email=&lt;br /&gt;
|pic=&lt;br /&gt;
|sex=M&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Table Owner Of|Neil Kemp}}&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=User:Jan_Schoonderbeek&amp;diff=1658</id>
		<title>User:Jan Schoonderbeek</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=User:Jan_Schoonderbeek&amp;diff=1658"/>
		<updated>2024-01-07T16:25:30Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Contact Data&lt;br /&gt;
|displayname=J.A.H. Schoonderbeek&lt;br /&gt;
|title=Enterprise Architect&lt;br /&gt;
|company=Architecting.nl&lt;br /&gt;
|department=&lt;br /&gt;
|telephone=&lt;br /&gt;
|extension=&lt;br /&gt;
|mobile=+31-(0)6-45 26 23 16&lt;br /&gt;
|email=j.schoonderbeek@architecting.nl&lt;br /&gt;
|pic=Jan Schoonderbeek.jpg&lt;br /&gt;
|sex=M&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Table Owner Of|Jan Schoonderbeek}}&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=File:GP.Data_Zone_Protection.png&amp;diff=1656</id>
		<title>File:GP.Data Zone Protection.png</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=File:GP.Data_Zone_Protection.png&amp;diff=1656"/>
		<updated>2020-10-20T15:13:39Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: Jan Schoonderbeek uploaded a new version of File:GP.Data Zone Protection.png&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Summary ==&lt;br /&gt;
Generic Pattern for Data Transport&lt;br /&gt;
[[Category:Generic Pattern graphic]]&lt;br /&gt;
== Licensing ==&lt;br /&gt;
{{self|cc-by-3.0}}&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=Main_Page&amp;diff=1177</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=Main_Page&amp;diff=1177"/>
		<updated>2018-08-26T19:06:26Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: deprecated keyword __NOTITLE__&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div id=&amp;quot;mainpage_topbox&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;div id=&amp;quot;mainpage_pagetitle&amp;quot;&amp;gt;&#039;&#039;&#039;Welcome to the OIAr&#039;&#039;&#039;&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;div class=&amp;quot;mainpage_boxcontents&amp;quot;&amp;gt;[[File:OIAmLogo.png|150px|OIAm|right|alt=Open Infrastructure Architecture method]]This site is the home for everyone that is concerned with IT architecture according to OIAm. OIAm stands for &#039;&#039;&#039;Open Infrastructure Architecture method&#039;&#039;&#039; (OIAm). OIAm provides a structured, repeatable, efficient and powerful way to create meaningful overarching designs for IT infrastructure. The method is tried and proven with organizations up to multinationals, and has community content at the front and centre. &#039;&#039;&#039;This site is in the process of being updated&#039;&#039;&#039;, to reflect the latest insights that are being described in a new book, &#039;[https://www.kleineuil.nl/businessboeken/levende-it-architectuur-details Levende IT-Architectuur]&#039; (Dutch). An English translation of this book is underway.{{clear}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;div id=&amp;quot;mainpage_sitelinks&amp;quot;&amp;gt;&lt;br /&gt;
&#039;&#039;&#039;[[Project:About|About this site]]&#039;&#039;&#039; &amp;amp;nbsp; | &amp;amp;nbsp; &lt;br /&gt;
&#039;&#039;&#039;[[The Open Infrastructure Architecture method|About OIAm]]&#039;&#039;&#039; &amp;amp;nbsp; | &amp;amp;nbsp;&lt;br /&gt;
&#039;&#039;&#039;[[The OIAm community|About the community]]&#039;&#039;&#039; &amp;amp;nbsp; | &amp;amp;nbsp;&lt;br /&gt;
&#039;&#039;&#039;[[How to contribute|Contribute]]&#039;&#039;&#039;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
{| style=&amp;quot;border:0; margin: 0;&amp;quot; width=&amp;quot;100%&amp;quot; cellspacing=&amp;quot;10&amp;quot;&lt;br /&gt;
|style=&amp;quot;width: 35%&amp;quot; &amp;quot;align:top&amp;quot;| {{Mainpage/RepositoryTable}}&lt;br /&gt;
|style=&amp;quot;width: 65%&amp;quot; &amp;quot;align:top&amp;quot; | {{Mainpage/TheoryTable}}&lt;br /&gt;
|}&lt;br /&gt;
{| role=&amp;quot;presentation&amp;quot; style=&amp;quot;border:0; margin: 0;&amp;quot; width=&amp;quot;100%&amp;quot; cellspacing=&amp;quot;10&amp;quot;&lt;br /&gt;
|style=&amp;quot;width: 100%&amp;quot;| {{Mainpage/NewsTable}}&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=GP.Facilities_Deployment&amp;diff=1176</id>
		<title>GP.Facilities Deployment</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=GP.Facilities_Deployment&amp;diff=1176"/>
		<updated>2018-08-06T06:23:00Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: two missing functions added&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Maturity|3}}&lt;br /&gt;
{{Pageheaderbox4GP&lt;br /&gt;
|name=Facilities Deployment&lt;br /&gt;
|sector=Operations&lt;br /&gt;
|version=0.4&lt;br /&gt;
|owner=J.A.H. Schoonderbeek&lt;br /&gt;
|summary=This Function can deploy the software part of an IT (sub)system, and/or configurations thereof.&lt;br /&gt;
}}&lt;br /&gt;
This Function can deploy the software part of an IT (sub)system, and/or configurations thereof. This entails the digital transformation from a packaged form to an operational working state, either of the IT (sub)system in its entirity, or of specific datasets for that system.&lt;br /&gt;
To this end, this Function makes use of a Deploying function, that is controlled by a Rules Engine. The Rules Engine (optionally supported by Scheduling) controls the actual deployment, a.o. by checking a Configuration Register for the configuration to be deployed. Optionally, Configuration Retrieval can be used to compare the actual configuration with the required configuration.&lt;br /&gt;
Optionally a Reporting function is used to report to the operators of the Facilities Deployment Function on the state of various deployments.&lt;br /&gt;
{{Pattern Realizes&lt;br /&gt;
|service=GS.Facilities Deployment&lt;br /&gt;
}}&lt;br /&gt;
{{Pattern Graphic&lt;br /&gt;
|graphic=GP.Facilities Deployment.png&lt;br /&gt;
|source=GP.&lt;br /&gt;
|size=600px&lt;br /&gt;
|title=Facilities Deployment&lt;br /&gt;
|kind=Generic&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Deploying&lt;br /&gt;
|choice=Must&lt;br /&gt;
|reason=This function carries out the act of rolling out software and/or configurations to (remote) facilities that are set up and/or configured centrally.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Rules Engine&lt;br /&gt;
|choice=Must&lt;br /&gt;
|reason=The Process Engine function is the heart of automated deployment solutions. It is programmed by operators to carry out deployment jobs. Depending on it&#039;s implementation, deployment activities are carried out based on rules, pre-defined jobs, configuration data, et cetera.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Configuration Register&lt;br /&gt;
|choice=Must&lt;br /&gt;
|reason=This Function is used to consult the deployment configuration data. Stored configuration data can be used by the Rules Engine to guide the deployment of software and/or configurations. Of course, the availability of configuration data in a structured way is also useful to operators.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Configuration Retrieval&lt;br /&gt;
|choice=May&lt;br /&gt;
|reason=This Function is used to collect configuration data from the facilities to which deployment must/may take place. This configuration data can be stored using the configuration register function and/or directly used by the Rules Engine to guide the deployment of software and/or configurations. Of course, the availability of current configuration data is also useful to operators.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Controlling&lt;br /&gt;
|choice=Must&lt;br /&gt;
|reason=The Controlling Function provides the management interface to deployment solutions. Depending on the implementation, this may be a programming interface to operators, or a self-service interface to (authenticated and authorized) end-users, who can trigger the installation of (user workspace) applications or configurations.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Scheduling&lt;br /&gt;
|choice=May&lt;br /&gt;
|reason=The Scheduling Function allows for automation of the deployment process. It can initiate a deployment on predetermined points in time, intervals, or events.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Reporting&lt;br /&gt;
|choice=May&lt;br /&gt;
|reason=The Reporting Function makes it possible for consumers of the Facilities Deployment pattern to obtain reports on aspects of the deployment, e.g. the status of previous deployments, or the eligibility of facilities for deployments.&lt;br /&gt;
}}&lt;br /&gt;
{{Table Ending}}&lt;br /&gt;
{{Pattern Adjacent Services}}&lt;br /&gt;
{{Generic Pattern Adjacent Service Row&lt;br /&gt;
|service=GS.Authentication+Authorization&lt;br /&gt;
|choice=May&lt;br /&gt;
|reason=Authentication &amp;amp; Authorization services may be used&lt;br /&gt;
* to control who operates the Facilities Deployment solution, and/or&lt;br /&gt;
* to ensure that a deployment takes place only on a properly authenticated target system.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Adjacent Service Row&lt;br /&gt;
|service=GS.Data Management&lt;br /&gt;
|choice=May&lt;br /&gt;
|reason=This service may be used to store deployment rules, reports, configurations, and/or the actual deployable information&lt;br /&gt;
}}&lt;br /&gt;
{{Table Ending}}&lt;br /&gt;
{{Text Footer GP}}&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=Property:Owl:differentFrom&amp;diff=1175</id>
		<title>Property:Owl:differentFrom</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=Property:Owl:differentFrom&amp;diff=1175"/>
		<updated>2018-08-05T17:44:43Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: Semantic MediaWiki default vocabulary import&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* [[Imported from::owl:differentFrom]] &lt;br /&gt;
* [[Has property description::The property that determines that two given individuals are different.@en]] &lt;br /&gt;
&lt;br /&gt;
[[Category:Imported vocabulary]] {{DISPLAYTITLE:owl:differentFrom}}&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=Property:Foaf:homepage&amp;diff=1174</id>
		<title>Property:Foaf:homepage</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=Property:Foaf:homepage&amp;diff=1174"/>
		<updated>2018-08-05T17:44:43Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: Semantic MediaWiki default vocabulary import&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* [[Imported from::foaf:homepage]] &lt;br /&gt;
* [[Has property description::URL of the homepage of something, which is a general web resource.@en]] &lt;br /&gt;
&lt;br /&gt;
[[Category:Imported vocabulary]] {{DISPLAYTITLE:foaf:homepage}}&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=Property:Foaf:name&amp;diff=1173</id>
		<title>Property:Foaf:name</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=Property:Foaf:name&amp;diff=1173"/>
		<updated>2018-08-05T17:44:43Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: Semantic MediaWiki default vocabulary import&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* [[Imported from::foaf:name]] &lt;br /&gt;
* [[Has property description::A name for some thing or agent.@en]] &lt;br /&gt;
&lt;br /&gt;
[[Category:Imported vocabulary]]{{DISPLAYTITLE:foaf:name}}&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=Property:Foaf:knows&amp;diff=1172</id>
		<title>Property:Foaf:knows</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=Property:Foaf:knows&amp;diff=1172"/>
		<updated>2018-08-05T17:44:43Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: Semantic MediaWiki default vocabulary import&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* [[Imported from::foaf:knows]] &lt;br /&gt;
* [[Has property description::A person known by this person (indicating some level of reciprocated interaction between the parties).@en]] &lt;br /&gt;
&lt;br /&gt;
[[Category:Imported vocabulary]] {{DISPLAYTITLE:foaf:knows}}&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=MediaWiki:Smw_import_owl&amp;diff=1171</id>
		<title>MediaWiki:Smw import owl</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=MediaWiki:Smw_import_owl&amp;diff=1171"/>
		<updated>2018-08-05T17:44:43Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: Semantic MediaWiki default vocabulary import&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;http://www.w3.org/2002/07/owl#|[http://www.w3.org/2002/07/owl Web Ontology Language (OWL)]&lt;br /&gt;
 AllDifferent|Category&lt;br /&gt;
 allValuesFrom|Type:Page&lt;br /&gt;
 AnnotationProperty|Category&lt;br /&gt;
 backwardCompatibleWith|Type:Page&lt;br /&gt;
 cardinality|Type:Number&lt;br /&gt;
 Class|Category&lt;br /&gt;
 comment|Type:Page&lt;br /&gt;
 complementOf|Type:Page&lt;br /&gt;
 DataRange|Category&lt;br /&gt;
 DatatypeProperty|Category&lt;br /&gt;
 DeprecatedClass|Category&lt;br /&gt;
 DeprecatedProperty|Category&lt;br /&gt;
 differentFrom|Type:Page&lt;br /&gt;
 disjointWith|Type:Page&lt;br /&gt;
 distinctMembers|Type:Page&lt;br /&gt;
 equivalentClass|Type:Page&lt;br /&gt;
 equivalentProperty|Type:Page&lt;br /&gt;
 FunctionalProperty|Category&lt;br /&gt;
 hasValue|Type:Page&lt;br /&gt;
 imports|Type:Page&lt;br /&gt;
 incompatibleWith|Type:Page&lt;br /&gt;
 intersectionOf|Type:Page&lt;br /&gt;
 InverseFunctionalProperty|Category&lt;br /&gt;
 inverseOf|Type:Page&lt;br /&gt;
 isDefinedBy|Type:Page&lt;br /&gt;
 label|Type:Page&lt;br /&gt;
 maxCardinality|Type:Number&lt;br /&gt;
 minCardinality|Type:Number&lt;br /&gt;
 Nothing|Category&lt;br /&gt;
 ObjectProperty|Category&lt;br /&gt;
 oneOf|Type:Page&lt;br /&gt;
 onProperty|Type:Page&lt;br /&gt;
 Ontology|Category&lt;br /&gt;
 OntologyProperty|Category&lt;br /&gt;
 owl|Type:Page&lt;br /&gt;
 priorVersion|Type:Page&lt;br /&gt;
 Restriction|Category&lt;br /&gt;
 sameAs|Type:Page&lt;br /&gt;
 seeAlso|Type:Page&lt;br /&gt;
 someValuesFrom|Type:Page&lt;br /&gt;
 SymmetricProperty|Category&lt;br /&gt;
 Thing|Category&lt;br /&gt;
 TransitiveProperty|Category&lt;br /&gt;
 unionOf|Type:Page&lt;br /&gt;
 versionInfo|Type:Page&lt;br /&gt;
&lt;br /&gt;
[[Category:Imported vocabulary]]&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=MediaWiki:Smw_import_foaf&amp;diff=1170</id>
		<title>MediaWiki:Smw import foaf</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=MediaWiki:Smw_import_foaf&amp;diff=1170"/>
		<updated>2018-08-05T17:44:43Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: Semantic MediaWiki default vocabulary import&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;http://xmlns.com/foaf/0.1/|[http://www.foaf-project.org/ Friend Of A Friend]&lt;br /&gt;
 name|Type:Text&lt;br /&gt;
 homepage|Type:URL&lt;br /&gt;
 mbox|Type:Email&lt;br /&gt;
 mbox_sha1sum|Type:Text&lt;br /&gt;
 depiction|Type:URL&lt;br /&gt;
 phone|Type:Text&lt;br /&gt;
 Person|Category&lt;br /&gt;
 Organization|Category&lt;br /&gt;
 knows|Type:Page&lt;br /&gt;
 member|Type:Page&lt;br /&gt;
&lt;br /&gt;
[[Category:Imported vocabulary]]&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=MediaWiki:Smw_import_skos&amp;diff=1169</id>
		<title>MediaWiki:Smw import skos</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=MediaWiki:Smw_import_skos&amp;diff=1169"/>
		<updated>2018-08-05T17:44:43Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: Semantic MediaWiki default vocabulary import&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;http://www.w3.org/2004/02/skos/core#|[http://www.w3.org/TR/skos-reference/skos.rdf Simple Knowledge Organization System (SKOS)]&lt;br /&gt;
 altLabel|Type:Monolingual text&lt;br /&gt;
 broader|Type:Annotation URI&lt;br /&gt;
 broaderTransitive|Type:Annotation URI&lt;br /&gt;
 broadMatch|Type:Annotation URI&lt;br /&gt;
 changeNote|Type:Text&lt;br /&gt;
 closeMatch|Type:Annotation URI&lt;br /&gt;
 Collection|Class&lt;br /&gt;
 Concept|Class&lt;br /&gt;
 ConceptScheme|Class&lt;br /&gt;
 definition|Type:Text&lt;br /&gt;
 editorialNote|Type:Text&lt;br /&gt;
 exactMatch|Type:Annotation URI&lt;br /&gt;
 example|Type:Text&lt;br /&gt;
 hasTopConcept|Type:Page&lt;br /&gt;
 hiddenLabel|Type:String&lt;br /&gt;
 historyNote|Type:Text&lt;br /&gt;
 inScheme|Type:Page&lt;br /&gt;
 mappingRelation|Type:Page&lt;br /&gt;
 member|Type:Page&lt;br /&gt;
 memberList|Type:Page&lt;br /&gt;
 narrower|Type:Annotation URI&lt;br /&gt;
 narrowerTransitive|Type:Annotation URI&lt;br /&gt;
 narrowMatch|Type:Annotation URI&lt;br /&gt;
 notation|Type:Text&lt;br /&gt;
 note|Type:Text&lt;br /&gt;
 OrderedCollection|Class&lt;br /&gt;
 prefLabel|Type:String&lt;br /&gt;
 related|Type:Annotation URI&lt;br /&gt;
 relatedMatch|Type:Annotation URI&lt;br /&gt;
 scopeNote|Type:Text&lt;br /&gt;
 semanticRelation|Type:Page&lt;br /&gt;
 topConceptOf|Type:Page&lt;br /&gt;
&lt;br /&gt;
[[Category:Imported vocabulary]]&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=Form:News_item&amp;diff=1095</id>
		<title>Form:News item</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=Form:News_item&amp;diff=1095"/>
		<updated>2017-04-06T11:59:39Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: explained date order&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;noinclude&amp;gt;&lt;br /&gt;
{{ombox&lt;br /&gt;
| type       = notice&lt;br /&gt;
| image      = none&lt;br /&gt;
| imageright = [[File:Tv.png|64px]]&lt;br /&gt;
| style      = width: 800px; &lt;br /&gt;
| text       = This is the &amp;quot;News item&amp;quot; form.&lt;br /&gt;
To add a page with this form, enter the page name below; News pages MUST reside in the News: namespace, so they should be called something like &amp;quot;News:title&amp;quot;.&lt;br /&gt;
If a page with that name already exists, you will be sent to a form to edit that page, i.e. that news item.&lt;br /&gt;
Note that the form will attempt to autocomplete what you type based on existing pages.}}&lt;br /&gt;
&lt;br /&gt;
{{#forminput:News item}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/noinclude&amp;gt;&amp;lt;includeonly&amp;gt;&lt;br /&gt;
&amp;lt;div id=&amp;quot;wikiPreview&amp;quot; style=&amp;quot;display: none; padding-bottom: 25px; margin-bottom: 25px; border-bottom: 1px solid #AAAAAA;&amp;quot;&amp;gt;&amp;lt;/div&amp;gt;&lt;br /&gt;
{{{for template|News item}}}&lt;br /&gt;
{| class=&amp;quot;formtable&amp;quot;&lt;br /&gt;
! Headline:&lt;br /&gt;
| {{{field|headline|mandatory|size=80}}}&lt;br /&gt;
|-&lt;br /&gt;
! News date:&lt;br /&gt;
| {{{field|newsdate|mandatory}}} (preferably use YYYY-MM-DD)&lt;br /&gt;
|-&lt;br /&gt;
! Author:&lt;br /&gt;
| {{{field|author|mandatory|default=current user|autocomplete on namespace=user}}}&lt;br /&gt;
|-&lt;br /&gt;
! Expiry date:&lt;br /&gt;
| {{{field|expirydate}}}  (preferably use YYYY-MM-DD)&lt;br /&gt;
|-&lt;br /&gt;
! News summary:&lt;br /&gt;
| {{{field|blurb|mandatory|input type=textarea|cols=40|rows=4}}}&lt;br /&gt;
|}&lt;br /&gt;
{{{end template}}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;News item main text:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
{{{standard input|free text|rows=10}}}&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
{{{standard input|summary}}}&lt;br /&gt;
&lt;br /&gt;
{{{standard input|minor edit}}} {{{standard input|watch}}}&lt;br /&gt;
&lt;br /&gt;
{{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}}&lt;br /&gt;
&amp;lt;/includeonly&amp;gt;&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=News:2017-03-31_New_Architecture_book_launch&amp;diff=1094</id>
		<title>News:2017-03-31 New Architecture book launch</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=News:2017-03-31_New_Architecture_book_launch&amp;diff=1094"/>
		<updated>2017-04-06T11:46:01Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{News item&lt;br /&gt;
|headline=Launch of new OIAm based architecture book&lt;br /&gt;
|newsdate=2017-04-05&lt;br /&gt;
|author=Daniel Jumelet&lt;br /&gt;
|expirydate=2019-12-31&lt;br /&gt;
|blurb=A big thank you to the OIAm community for enabling the emergence of a new IT architecture guide&lt;br /&gt;
}}&lt;br /&gt;
Friday, March 31st, a new IT architecture guide is launched, strongly based on OIAm. Therefore, a big thank you to all the community members that made the wish for a new book come true. From those that were involved in the review process up to the members that came with little suggestions for improvements or important questions.  Some impressions of the book presentation event:&lt;br /&gt;
[[File:Launch_Impression.png|900px|centre|Book Launch Event]]&lt;br /&gt;
This release of the new book (&#039;[https://www.kleineuil.nl/businessboeken/levende-it-architectuur-details Levende IT-Architectuur, praktische toepassing van een functiegerichte methode]’, ISBN 9789492190413) is in Dutch, but an English translation is underway in cooperation with NXP Semiconductors. During the coming weeks and months, the OIAr will be updated to reflect the new insights that are presented by the book.&lt;br /&gt;
__SHOWFACTBOX__&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=News:2017-03-31_New_Architecture_book_launch&amp;diff=1093</id>
		<title>News:2017-03-31 New Architecture book launch</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=News:2017-03-31_New_Architecture_book_launch&amp;diff=1093"/>
		<updated>2017-04-06T11:35:02Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: Reverted edits by Jan Schoonderbeek (talk) to last revision by Daniel Jumelet&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{News item&lt;br /&gt;
|headline=Launch of new OIAm based architecture book&lt;br /&gt;
|newsdate=05-04-2017&lt;br /&gt;
|author=Daniel Jumelet&lt;br /&gt;
|expirydate=31-12-2019&lt;br /&gt;
|blurb=A big thank you to the OIAm community for enabling the emergence of a new IT architecture guide&lt;br /&gt;
}}&lt;br /&gt;
Friday, March 31st, a new IT architecture guide is launched, strongly based on OIAm. Therefore, a big thank you to all the community members that made the wish for a new book come true. From those that were involved in the review process up to the members that came with little suggestions for improvements or important questions.  Some impressions of the book presentation event:&lt;br /&gt;
[[File:Launch_Impression.png|900px|centre|Book Launch Event]]&lt;br /&gt;
This release of the new book (&#039;[https://www.kleineuil.nl/businessboeken/levende-it-architectuur-details Levende IT-Architectuur, praktische toepassing van een functiegerichte methode]’, ISBN 9789492190413) is in Dutch, but an English translation is underway in cooperation with NXP Semiconductors. During the coming weeks and months, the OIAr will be updated to reflect the new insights that are presented by the book.&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=News:2017-03-31_New_Architecture_book_launch&amp;diff=1092</id>
		<title>News:2017-03-31 New Architecture book launch</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=News:2017-03-31_New_Architecture_book_launch&amp;diff=1092"/>
		<updated>2017-04-06T11:27:13Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: corrected news date&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{News item&lt;br /&gt;
|headline=Launch of new OIAm based architecture book&lt;br /&gt;
|newsdate=04-05-2017&lt;br /&gt;
|author=Daniel Jumelet&lt;br /&gt;
|expirydate=31-12-2019&lt;br /&gt;
|blurb=A big thank you to the OIAm community for enabling the emergence of a new IT architecture guide&lt;br /&gt;
}}&lt;br /&gt;
Friday, March 31st, a new IT architecture guide is launched, strongly based on OIAm. Therefore, a big thank you to all the community members that made the wish for a new book come true. From those that were involved in the review process up to the members that came with little suggestions for improvements or important questions.  Some impressions of the book presentation event:&lt;br /&gt;
[[File:Launch_Impression.png|900px|centre|Book Launch Event]]&lt;br /&gt;
This release of the new book (&#039;[https://www.kleineuil.nl/businessboeken/levende-it-architectuur-details Levende IT-Architectuur, praktische toepassing van een functiegerichte methode]’, ISBN 9789492190413) is in Dutch, but an English translation is underway in cooperation with NXP Semiconductors. During the coming weeks and months, the OIAr will be updated to reflect the new insights that are presented by the book.&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=GP.Identity%2BPermission_Management&amp;diff=1080</id>
		<title>GP.Identity+Permission Management</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=GP.Identity%2BPermission_Management&amp;diff=1080"/>
		<updated>2016-11-10T09:01:17Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: spelling&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Maturity|3}}&lt;br /&gt;
{{Pageheaderbox4GP&lt;br /&gt;
|name=Identity &amp;amp; Permission Management&lt;br /&gt;
|sector=Operations&lt;br /&gt;
|version=0.5&lt;br /&gt;
|owner=J.A.H. Schoonderbeek&lt;br /&gt;
|summary=Instances of this Generic Pattern are able to maintains the propagation and consistency of digital identities and digital permissions that are recognized within the organization.&lt;br /&gt;
}}&lt;br /&gt;
Instances of this Generic Pattern are able to maintains the propagation and consistency of digital identities and digital permissions that are recognized within the organization. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Identity management&#039;&#039;&#039;&lt;br /&gt;
This Generic Pattern can perform the following tasks related to digital identities:&lt;br /&gt;
* It can provide new digital identities to instances of A&amp;amp;A services when the circumstances call for it (either an eligible new identity presents itself in another connected A&amp;amp;A system that&#039;s deemed authoritative, or an existing identity becomes eligible), including all accompanying identity attributes that are used in that particular A&amp;amp;A service instance;&lt;br /&gt;
* It can provide new digital groups to instances of A&amp;amp;A services that are going to be involved with Role Based Access Control under that A&amp;amp;A service&#039;s authority;&lt;br /&gt;
* It can direct A&amp;amp;A services to change group membership of a digital identity to reflect a change in roles;&lt;br /&gt;
* It can convey the effects of a change in business rules on the relevant aspects of the digital identities under an affected A&amp;amp;A service;&lt;br /&gt;
* When an update occurs in a digital identity&#039;s attribute under an A&amp;amp;A service that&#039;s deemed authoritative for that attribute, then the Pattern can detect this update, and have it applied to all A&amp;amp;A services that contain that same identity and attribute;&lt;br /&gt;
* It can direct A&amp;amp;A services to disable or remove identities, as soon as that identity&#039;s eligibility for an account in that particular A&amp;amp;A service ends, or the digital identity is disabled or removed from an authoritative A&amp;amp;A service;&lt;br /&gt;
* It can automatically resolve certain conflicts in account information between different A&amp;amp;A services. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Permission management&#039;&#039;&#039;&lt;br /&gt;
This Generic Pattern can perform the following tasks related to permission management:&lt;br /&gt;
* It can direct an A&amp;amp;A service to create or update the necessary permissions associated with a digital resource, when a digital identity becomes eligible for use of this resource;&lt;br /&gt;
* It directs an A&amp;amp;A service to update or remove the relevant permi rsions associated with a digital resource, when a digital identity loses eligibility for use of this resource;&lt;br /&gt;
* It can detect and resolve certain conflicts between specific permissions assigned (or not) to a digital identity by a specific A&amp;amp;A service, and the permissions that should (or should not) actually be granted to it&lt;br /&gt;
{{Pattern Realizes&lt;br /&gt;
|service=GS.Identity+Permission Management&lt;br /&gt;
}}&lt;br /&gt;
{{Pattern Graphic&lt;br /&gt;
|graphic=GP.Identity+Permission Management.png&lt;br /&gt;
|source=GP.&lt;br /&gt;
|size=650px&lt;br /&gt;
|title=Generic Pattern Identity &amp;amp; Permission Management&lt;br /&gt;
|kind=Generic&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Rules Engine&lt;br /&gt;
|choice=Must&lt;br /&gt;
|reason=This function processes new or changed digital identities and/or permissions. It can source authoritative identity attributes and permissions from multiple connected A&amp;amp;A services. Furthermore, it hands off new or changed identity (attributes) and/or permissions to the Deploying function for replication over the relevant A&amp;amp;A services.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Structured Data Store&lt;br /&gt;
|choice=May&lt;br /&gt;
|reason=Unless the Pattern is implemented as a Virtual Metadirectory, the Pattern needs a means remember the state of the identities/permissions it has distributed over the organization; this function provides this means. Ideally the function contains a metadirectory combining the authoritative data of all appointed identity stores and permission registers (although it&#039;s most likely unwanted to have any facility call upon this metadirectory directly). If not a metadirectory, then still some sort of record needs to be kept to prevent the Pattern from unnecessarily provisioning accounts, or missing out on updated accounts.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Configuration Retrieval&lt;br /&gt;
|choice=Must&lt;br /&gt;
|reason=The Pattern needs a means to interrogate connected A&amp;amp;A services that receive data and/or supply (authoritative) data. Hence this function serves to model this means. Interrogation can occur on external triggers (a change in a monitored Store/Register), on schedule, or on another internal trigger.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Scheduling&lt;br /&gt;
|choice=May&lt;br /&gt;
|reason=This function serves to model the timed triggers that cause the Pattern to perform tasks such as collection or deployment of A&amp;amp;A information.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Deploying&lt;br /&gt;
|choice=Must&lt;br /&gt;
|reason=This function enables the Pattern to push the new or changed identity (attributes) and/or permissions to connected A&amp;amp;A services.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Controlling&lt;br /&gt;
|choice=Must&lt;br /&gt;
|reason=If implemented, this function can be used by administrators, and possibly by authorized clients, to change the way the Pattern works. Among the changes that can be made via this function are:&lt;br /&gt;
* The rules used to determine how identities and permissions are provisioned;&lt;br /&gt;
* Connecting or disconnecting A&amp;amp;A services;&lt;br /&gt;
* The schedule by which the Pattern performs its actions;&lt;br /&gt;
* Triggering maintenance actions directly.&lt;br /&gt;
Care must be taken to limit access to this function to authorized systems and users.&lt;br /&gt;
}}&lt;br /&gt;
{{Table Ending}}&lt;br /&gt;
{{Pattern Adjacent Services}}&lt;br /&gt;
{{Generic Pattern Adjacent Service Row&lt;br /&gt;
|service=GS.Authentication+Authorization&lt;br /&gt;
|choice=Must&lt;br /&gt;
|reason=As this Pattern serves to consolidate multiple A&amp;amp;A services, they are required to be connected.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Adjacent Service Row&lt;br /&gt;
|service=GS.Facilities Monitoring&lt;br /&gt;
|choice=May&lt;br /&gt;
|reason=Correct management of digital identities and permissions is vital to client&#039;s access to IT services, as well as to the security of the organization&#039;s IT resources. This calls for monitoring of this Pattern by both IT Operations staff and security officers.&lt;br /&gt;
}}&lt;br /&gt;
{{Table Ending}}&lt;br /&gt;
{{Text Footer GP}}&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=GP.Raw_Storage&amp;diff=1079</id>
		<title>GP.Raw Storage</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=GP.Raw_Storage&amp;diff=1079"/>
		<updated>2016-10-12T20:42:10Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: updated adjacent service&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Maturity|4}}&lt;br /&gt;
{{Pageheaderbox4GP&lt;br /&gt;
|name=Raw Storage&lt;br /&gt;
|sector=Core&lt;br /&gt;
|version=0.95&lt;br /&gt;
|owner=J.A.H. Schoonderbeek&lt;br /&gt;
|summary=This Pattern offers functionality for the storage and retrieval of unstructured data at a single, logical location; it may also provide &amp;quot;intelligence&amp;quot; to administrators and/or consumers.&lt;br /&gt;
}}&lt;br /&gt;
This Pattern offers functionality for the storage and retrieval of &amp;quot;unstructured data&amp;quot; at a single, logical location; optionally it provides advanced functionality (&amp;quot;intelligence&amp;quot;) to administrators and/or consumers. It has the following characteristics:&lt;br /&gt;
* operates on data at the lowest abstraction level, i.e. [[OIAm_data_view|&amp;quot;unstructured data&amp;quot;]] (e.g. bits and bytes),&lt;br /&gt;
* located at a single logical location,&lt;br /&gt;
* access by general or dedicated storage network facilities (indicated by [[GP.Data Transport|Data Transport]]),&lt;br /&gt;
* the ability to perform storage related &amp;quot;intelligent&amp;quot; tasks, such as replication, migration, encryption and data reduction. This intelligence is characterized as &amp;quot;back-end facing&amp;quot; intelligence; generally speaking the facility&#039;s consumers don&#039;t get (direct) access to it, only the administrators and back-end systems. &lt;br /&gt;
As examples: realizations of Raw Storage can include:&lt;br /&gt;
* SAN storage cabinets,&lt;br /&gt;
* (the back-end of) NAS appliances,&lt;br /&gt;
* hard disk solutions such as RAID arrays.&lt;br /&gt;
{{Pattern Realizes&lt;br /&gt;
|service=GS.Raw Storage&lt;br /&gt;
}}&lt;br /&gt;
{{Pattern Graphic&lt;br /&gt;
|graphic=GP.Raw Storage.png&lt;br /&gt;
|source=GP.&lt;br /&gt;
|size=500px&lt;br /&gt;
|kind=Generic&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Retention Engine&lt;br /&gt;
|choice=Must&lt;br /&gt;
|reason=This function provides &amp;quot;intelligence&amp;quot; to the storage solution with respect to its handling of the stored data, with the aim of meeting the quality requirements, improving infrastructure management, and/or providing sufficient performance. It may handle migration/replication to other instances of itself, encryption, reduction, and other &amp;quot;standard&amp;quot; storage-related processing. Note that for some types of functionality an implementation/realization of Retention Engine may need to invoke another implementation/realization (e.g. for replication/migration over longer distances, there likely is a separate realization in each physical location).&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Raw Retention&lt;br /&gt;
|choice=Must&lt;br /&gt;
|reason=This function handles the actual retention of data at the &amp;quot;unstructured data&amp;quot; level. It supports the actions creation, reading, updating and/or deletion of the data.&lt;br /&gt;
Physically this function can be realized with devices containing (re)writeable media, such as Solid State Disks, hard disks, tape, optical media et cetera.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Caching&lt;br /&gt;
|choice=May&lt;br /&gt;
|reason=An intelligent storage facility may use Caching functionality to increase its capacity to receive and/or return data on request.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Controlling&lt;br /&gt;
|choice=May&lt;br /&gt;
|reason=If implemented, this function can be used by administrators, and possibly by authorized clients, to change the way the Pattern works. Among the changes that can be made via this function are:&lt;br /&gt;
* Creating or changing back-up schedules;&lt;br /&gt;
* Restoring back-ups;&lt;br /&gt;
* Capacity &amp;amp; Performance Management;&lt;br /&gt;
* Provisioning;&lt;br /&gt;
* Rules Management, in order to guide data migration between Tiers.&lt;br /&gt;
Care must be taken to limit access to this function to authorized systems and users.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Encryption&lt;br /&gt;
|choice=May&lt;br /&gt;
|reason=This function ensures that all data gets written in an encrypted form; after this, any reading, updating, and possibly deleting, can only take place if a client can offer this Pattern the right encryption key. If an implementation of this Pattern is to help maintain the Confidentiality of the data contained, then this function is required.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Reduction&lt;br /&gt;
|choice=May&lt;br /&gt;
|reason=To increase the data capacity of the Pattern, the Reduction function may be used to reduce the size to the data actually stored by Raw Retention, compared to the size of the data offered to the Pattern by its clients. Usually this Reduction function works lossless, meaning that upon access, the data can be reproduced exactly as it had been offered. Reduction of unstructured data can take place by different means, mainly data compression algorithms and/or sparse volumes/thin provisioning.&lt;br /&gt;
}}&lt;br /&gt;
{{Table Ending}}&lt;br /&gt;
{{Pattern Adjacent Services}}&lt;br /&gt;
{{Generic Pattern Adjacent Service Row&lt;br /&gt;
|service=GS.Authentication+Authorization&lt;br /&gt;
|choice=May&lt;br /&gt;
|reason=This service may be needed to limit access to the Controlling function and/or the Pattern as a whole to authorized clients.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Adjacent Service Row&lt;br /&gt;
|service=GS.Data Protection Management&lt;br /&gt;
|choice=May&lt;br /&gt;
|reason=If the data stored in this Pattern requires one or more secondary copies (backups), then this service can create and manage these.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Adjacent Service Row&lt;br /&gt;
|service=GS.Data Transport&lt;br /&gt;
|choice=May&lt;br /&gt;
|reason=This service is needed to transport the data from the clients to the Pattern and back. Raw Storage facilities often use specialized Data Transport services, instead of the generic &amp;quot;network&amp;quot; services.&lt;br /&gt;
}}&lt;br /&gt;
{{Table Ending}}&lt;br /&gt;
{{Text Footer GP}}&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=Community_event_2015-07-01_minutes&amp;diff=1078</id>
		<title>Community event 2015-07-01 minutes</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=Community_event_2015-07-01_minutes&amp;diff=1078"/>
		<updated>2015-07-15T10:46:01Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: Event minutes&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;big&amp;gt;&#039;&#039;&#039;Report of the 2015 OIAm community event (summer edition)&#039;&#039;&#039;&amp;lt;/big&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[File:Logo-windesheim-1024x261.jpg|350px|right]]On a smouldering hot July 1st, the 7th edition of the OIAm community event was held at [http://www.windesheiminternational.nl/ Windesheim University of Applied Sciences], Zwolle. The event itself was preceded by a workshop, in which community members involved with teaching and training focussed on discussing and sharing their experiences with the teaching of infrastructure architecture and OIAm. The following is a report compiled from the minutes taken by several community members, mainly those of Mischa Frenk.&lt;br /&gt;
&amp;lt;br clear=all&amp;gt;&lt;br /&gt;
=OIAm didactics workshop (morning)=&lt;br /&gt;
The aim of the workshop was to gain insight into the educational issues surrounding functional thinking and infrastructure architecture. Jan Schoonderbeek ([http://architecting.nl/ Architecting.nl]) introduces this part of the workshop. Learning functional thinking and modeling proves a tricky issue for both young students and experienced consultants/professionals in the field - but for different reasons. The examples that are given indicate that in some cases people have difficulties with abstract thinking, an important skill for functional design. There also seems to be a general opinion that people that perform the architect role are not always best equipped. Some professionals have grown up in IT construction (software or infrastructure) and slowly rise to the role of architect of sorts, but not always fully develop the necessary skills, others get the role of Architect in some other way that doesn’t train, or test for, the necessary skills and competences.&lt;br /&gt;
&lt;br /&gt;
At Windesheim, the topic of Architecture is part of the Infrastructure Design and Security bachelor course. The importance of Architecture, requirements elicitation and functional modelling (for which OIAm is used) is part of this course&#039;s curriculum that mainly focusses on infrastructure construction, as Bram Abbekerk ([http://www.windesheiminternational.nl/ Windesheim University]) explained. He mentioned that his students are generally very hands on at infrastructure construction and solving related security issues. Both Bram and a student of his course (Stephan Vorstenberg) related on the relative shortcomings and successes when teaching architecture, functional thinking and the OIAm method to (relatively inexperienced) infrastructure students. OIAm’s toughest challenges, next to functional thinking itself, were listed as a lack of written materials and examples, and the on-line repository OIAr not being complete and still somewhat in flux. Where OIAm offers it’s strongest benefits are in the area of requirements elicitation, and as a modelling method that allows for comprehensive models even when detailed technical knowledge of infrastructure products is not (yet) present in the student.&lt;br /&gt;
&lt;br /&gt;
Hans van Drunen ([http://atos.net/ Atos]) then recounted on the Infrastructure architecture master class he developed and teaches at Atos, which contains an OIAm module taught by Jan Schoonderbeek. After explaining the build-up of the master class program, he shares insights he gained. A lot of architects are very knowledgeable about the current techniques and services that deliver state of the art IT. On the other hand he also sees architects having difficulties with functional thinking. Changing this sometimes proves to be challenging due to a lack of willingness to leave their comfort zone on the constructional side of IT that people have build up over the years. In discussion, there seem to be a host of underlying issues: level of knowledge may be inadequate (insufficient knowledge of infrastructure, insufficient knowledge of modeling), not enough (functional) architecture examples available, quality of training and training materials and outdated and incomplete sources. Issues to be solved are about the (possibility of and) ability to learn the role of an architect, how to properly separate the differences between architects and designers/engineers and adjust the didactic curriculum and materials accordingly.&lt;br /&gt;
&lt;br /&gt;
During the workshop, the discussion often veered from education towards the perception of architecture by the stakeholders involved, as well as (to a lesser extent) the actual meaning and content of the field of Architecture. By and large, the participants agreed that architecture is about conveying context, envisioning and visualizing the essence of the functional needs and translating these into solutions. But on the topic of &amp;quot;selling&amp;quot; architecture to &amp;quot;the business&amp;quot;, the opinions and ideas were more widespread.&lt;br /&gt;
&lt;br /&gt;
The following suggestion were made to improve on these observations: Elaborate on the architecture body of knowledge; why the need for architecture, what defines the process, what skills ([http://www.ecompetences.eu/ eCF]) and soft skills are required. How to go from analysis to a functional design and then transforming it to a solution design (essence vs solution), generalisation versus specialization, function-construction thinking, taxonomy and hierarchy, more on abstract thinking, educational profiles to support career paths. And, of course it also comes down to &amp;quot;learning by doing&amp;quot;. Learning how to ride a bike works best when under supervision. Examples include University of Amsterdam and the municipality Bergen op Zoom.&lt;br /&gt;
&lt;br /&gt;
In the wrap-up of the workshop, Jan Schoonderbeek called for cooperation between those that develop educational programs, the sharing of materials (such as use cases and examples), and an investigation into the didactic requirements and prerequisites for OIAm training. The representatives of Hogeschool Windesheim/Utrecht/Amsterdam are going to take up this latter investigation.&lt;br /&gt;
&lt;br /&gt;
=Community event (afternoon)=&lt;br /&gt;
During the afternoon workshop Daniël Jumelet ([https://www.it2fit.nl/ it2fit]) together with Robert Kuijvenhoven ([http://www.centric.eu/NL/Default Centric]) presented a small video tutorial they developed to help others better understand OIAm modeling. The initiative, and the video itself, was well received, but Robert and Daniël indicated there is a need to develop more and better scripts, so more tutorials can be created. Please contact [[User:Daniel_Jumelet|Daniël Jumelet]] if you would like to contribute. Daniël also updated the status of his new book on OIAm, slated for November 2015 (in Dutch; English version will follow shortly after). Although he is still in the process of writing it, people are welcomed to review. Those present at the event were given an early opportunity to do so, by means of a handout of chapter 3.&lt;br /&gt;
&lt;br /&gt;
Next, Bram Abbekerk introduced the Windesheim bachelor course Infrastructure Design and Security, supported by Stephan Vorstenberg and David Maas, both students of the IDS course. The students presented their project and explained their approach, as well as the strengths and weaknesses of using OIAm as they perceived them. Bram also reminded the audience that Windesheim has student teams available to tackle infrastructure projects in their own organizations.&lt;br /&gt;
&lt;br /&gt;
Then Jan Schoonderbeek gave a presentation that summarized the experiences of Hans van Drunen and himself when teaching OIAm to experienced professionals, be they for upskilling or retraining. This was in part a recap of the talk that Hans van Drunen had at the workshop. During discussion Daniël Jumelet showed and explained about the practice of NXP, briefly presenting their service landscape and underlying definitions and descriptions of [http://pubs.opengroup.org/architecture/togaf9-doc/arch/chap37.html ABB&#039;s and SBB&#039;s]. Lively discussion ensued, confirming and somewhat expounding on the conclusions of the morning.&lt;br /&gt;
&lt;br /&gt;
The final presentation of the afternoon was also by Jan Schoonderbeek, who presented the current status of OIAm and the library content of the new online repository (OIAr). This consisted of a brief recap of the history of OIAr, techniques used, and current state of affairs. There is still some work left to put the finishing touches on the library contents of the OIAr. Furthermore, it needs vetting. For this there is a need for a (renewal of the OIAr) review board. To start, there is a call for volunteers that will establish the process for this. The following attendants volunteered to assist Jan Schoonderbeek and Daniël Jumelet with this: Antoon Wuijster (Ordina), Bert Kroek (ArchiCoach), Roelof Boersma (ABN AMRO), Bram Abbekerk (Windesheim) and Mischa Frenk (Defensie).&lt;br /&gt;
&lt;br /&gt;
Jan also presented a new idea: a cookbook approach to OIAm. This approach should offer users of OIAm an easy start to gain experience using the OIAm method. To this end, the cookbook should offer generic problems and contexts, and corresponding OIAm solutions. The solutions would offer a modicum of detail, considerations and motivations, as well as multiple solutions if warranted by differing contexts. The solutions presented then can serve as an outline for actual solutions by users of the OIAr.&lt;br /&gt;
&lt;br /&gt;
After a short closing address by Bram Abbekerk of Windesheim University, the day was concluded with drinks and networking opportunities, sponsored by it2fit and Architecting.nl. A sizeable part of the attendants chose to join, and many discussions were had, and acquaintances made or renewed. The last attendees left the premises only around 18:00.&lt;br /&gt;
&lt;br /&gt;
=In conclusion=&lt;br /&gt;
&lt;br /&gt;
As always, we&#039;re open to compliments, critique or recommendations, either here on LinkedIn or at the [mailto:community@infra-repository.org community mail address]. The presentations can be downloaded from this site:&lt;br /&gt;
* [https://www.infra-repository.org/share/event2015-07-01/01%20OIAm%202015-07-01%20Development%20status.pptx OIAm development status] (PowerPoint, Dutch);&lt;br /&gt;
* [https://www.infra-repository.org/share/event2015-07-01/02%20OIAm%202015-07-01%20Windesheim.pptx OIAm and Windesheim] (PowerPoint, Dutch);&lt;br /&gt;
* [https://www.infra-repository.org/share/event2015-07-01/03%20OIAm%202015-07-01%20Consultants%20trainen%20in%20OIAm.pptx Training consultants in OIAm] (PowerPoint, Dutch);&lt;br /&gt;
* [https://www.infra-repository.org/share/event2015-07-01/04%20OIAm%202015-07-01%20The%20new%20OIAr%20+%20Cookbook.pptx The new OIAr &amp;amp; a cookbook approach] (PowerPoint, English);&lt;br /&gt;
We wish to thank Windesheim University for hosting the event, the presenters and moderators for their contributions, but most of all the attendants of the workshop and the community event for their participation.&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=File:Logo-windesheim-1024x261.jpg&amp;diff=1077</id>
		<title>File:Logo-windesheim-1024x261.jpg</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=File:Logo-windesheim-1024x261.jpg&amp;diff=1077"/>
		<updated>2015-07-15T10:42:17Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: Logo for [http://www.windesheiminternational.nl/ Windesheim university of applied sciences]&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Summary ==&lt;br /&gt;
Logo for [http://www.windesheiminternational.nl/ Windesheim university of applied sciences]&lt;br /&gt;
== Licensing ==&lt;br /&gt;
{{subst:No license from license selector|Somewebsite}}&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=GP.Message_Handling&amp;diff=1069</id>
		<title>GP.Message Handling</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=GP.Message_Handling&amp;diff=1069"/>
		<updated>2015-05-08T19:51:16Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: New GP&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Maturity|4}}&lt;br /&gt;
{{Pageheaderbox4GP&lt;br /&gt;
|name=Message Handling&lt;br /&gt;
|sector=Commons&lt;br /&gt;
|version=0.4&lt;br /&gt;
|owner=J.A.H. Schoonderbeek&lt;br /&gt;
|summary=This Pattern accepts messages from senders, and then handles transport, storage, and delivery to recipients.&lt;br /&gt;
}}&lt;br /&gt;
This infrastructure function accepts chunks of digital data, or &amp;quot;messages&amp;quot;, from parties called senders, and then handles transport, storage, and delivery of these messages to parties called recipients. The parties involved may be human users, digital systems, or even the digital equivalent of a mailboxes of which it is not known in advance who or what will send or collect the message. Any consumer of (the service delivered by) this Pattern may be a sender, a recipient, or both.&lt;br /&gt;
&lt;br /&gt;
A message may be directed at a single recipient or multiple recipients, and the message may be delivered (near-) realtime or asynchronously. A message can most always be thought of to consist of two different sets of information:&lt;br /&gt;
* Message header: this contains the information necessary to route and deliver the message. A message header is analogous to the information printed on the outside of a letter (to, from, priority of message etc.) The message header may be invisible/inaccessible to the consumers of the Message Handling service.&lt;br /&gt;
* Message body: this contains the data transmitted to the intended recipient(s). The semantics of the message body data must be known to the intended recipient(s).&lt;br /&gt;
Important aspects of a Message Handling Pattern are:&lt;br /&gt;
* this Pattern makes it unnecessary for the sender to be in direct contact with the recipient(s);&lt;br /&gt;
* if any routing of the message is required, it is handled mainly or fully by this Pattern;&lt;br /&gt;
* the Pattern may provide a sender with acknowledgment of the message&#039;s reception, or not (&amp;quot;fire and forget&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
The Generic Pattern already has a sizeable amount of optional Generic Functions and Generic Services. However, please note that in the interest of brevity, the following aspects have not been included (as either recommended or optional). These may require consideration nevertheless:&lt;br /&gt;
* The [[GS.Data_Transport|Data Transport]] service(s) that will actually carry the messages from sender to (an instance of) the Pattern, between (instances of) the Pattern, and from (an instance of) the Pattern to the recipients;&lt;br /&gt;
* [[GF.Encryption|Encryption]] and compression ([[GF.Reduction|Reduction]]), which may operate on individual messages and/or on the communication channels that the Pattern uses;&lt;br /&gt;
* [[GF.Load Balancing|Load Balancing]] and [[GF.Queuing|Queuing]], which may be handled outside of (an implementation of) this Pattern, or may need to be included explicitly.&lt;br /&gt;
{{Pattern Realizes&lt;br /&gt;
|service=GS.Message Handling&lt;br /&gt;
}}&lt;br /&gt;
{{Pattern Graphic&lt;br /&gt;
|graphic=GP.Message Handling.png&lt;br /&gt;
|size=600px&lt;br /&gt;
|title=Message Handling pattern&lt;br /&gt;
|kind=Generic&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Message Engine&lt;br /&gt;
|choice=Must&lt;br /&gt;
|reason=The Message Engine is the core functionality of the Message Handling Pattern. It is responsible for receiving and sending messages, and comprises the intelligence for message processing (or delivering these messages to other facilities that process them). Among its tasks is making sure the messages are stored if they cannot continue on their way to the final recipient. &lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Presentation Engine&lt;br /&gt;
|choice=Must&lt;br /&gt;
|reason=Whether an instance of this Pattern is being used by humans or automated systems, it&#039;s often required that a Message Handling system can present and accept messages to and from the outside world in common, often open, standards. To this end, possible proprietary internal message formats need to be converted into the formats used outside of the facility, and vice versa.&lt;br /&gt;
In this way, this function can be used to change message headers and/or content to enable communication between senders and receivers that use different message formats. Types of transformation encompass &#039;message splitting&#039;, &#039;message aggregation&#039;, &#039;message resequencing&#039;, &#039;message enrichment&#039; and &#039;message content translation&#039;. &lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Controlling&lt;br /&gt;
|choice=Must&lt;br /&gt;
|reason=This function models the manner in which the Pattern&#039;s administrators, and possibly authorized consumers, can administer message transmission. Since the messages handled by the Pattern may be business critical and/or have a certain level of confidentiality, care must be taken to limit access to this function to authorized users. &lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Message Store&lt;br /&gt;
|choice=May&lt;br /&gt;
|reason=Since this pattern may need to accommodate indirect communication between sender and receiver, messages may need to be stored in the process of their transfer. The Message Store function might have a temporary or a more long-term use, depending on it&#039;s location in the path of the message: intermediate stores along the way act as buffers only, but at the destination, a message may reside in the Message Store even after the recipient has read the message.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Message Distribution&lt;br /&gt;
|choice=May&lt;br /&gt;
|reason=This function is used to move messages to their intended destination, based on message addresses and/or message content. It enables a flexible usage of virtual paths (sometimes called Message Channels) between sender and receiver(s), without the necessity that senders have &#039;knowledge&#039; of intermediate paths. On behalf of senders and receivers, this type of function does need routing information, either automatically or configured. &lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Address Lookup&lt;br /&gt;
|choice=May&lt;br /&gt;
|reason=This function may be used to resolve high-level addresses of message senders and receivers to corresponding lower-level addresses, e.g. from human readable email addresses to IP addresses. As such this function may be needed for advanced forms of message distribution&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Filtering&lt;br /&gt;
|choice=May&lt;br /&gt;
|reason=In the process of sending and receiving messages, it is possible to filter messages, based on a set of predefined rules or mechanisms. Basic filtering is done by checking message metadata, more advanced filtering may comprise payload or content filtering. If rule-based filtering is used, then the rules may be stored in some sort of Permission Register. &lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Data Scanning&lt;br /&gt;
|choice=May&lt;br /&gt;
|reason=In the process of filtering messages, this function might be used to scan message metadata and/or content, in order to support filtering decisions.&lt;br /&gt;
}}&lt;br /&gt;
{{Table Ending}}&lt;br /&gt;
{{Pattern Adjacent Services}}&lt;br /&gt;
{{Generic Pattern Adjacent Service Row&lt;br /&gt;
|service=GS.Authentication+Authorization&lt;br /&gt;
|choice=May&lt;br /&gt;
|reason=This adjacent facility can server a number of purposes:&lt;br /&gt;
* to validate permissions of senders, before accepting messages from these senders;&lt;br /&gt;
* to authenticate and authorize consumers/recipients that want to access messages contained in the facility;&lt;br /&gt;
* to provide Message Filtering with appropriate filtering rules. &lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Adjacent Service Row&lt;br /&gt;
|service=GS.Data Management&lt;br /&gt;
|choice=May&lt;br /&gt;
|reason=The Pattern may be connected with a Data Management service to store some or all of the data processed by the Pattern: it may host the Message Store, sets of contact or address data, or configuration data.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Adjacent Service Row&lt;br /&gt;
|service=GS.File Storage&lt;br /&gt;
|choice=May&lt;br /&gt;
|reason=The Pattern may be connected with a File Storage service to store some or all of the data processed by the Pattern: it may host the Message Store, sets of contact or address data, or configuration data.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Adjacent Service Row&lt;br /&gt;
|service=GS.Archive Management&lt;br /&gt;
|choice=May&lt;br /&gt;
|reason=Messages contained in this facility may be archived outside of the facility, using this Archive Management service. Reasons for using an archive can be &lt;br /&gt;
* to reduce the storage requirements of a Message Store function;&lt;br /&gt;
* to conserve a copy of messages for future reference. &lt;br /&gt;
}}&lt;br /&gt;
{{Table Ending}}&lt;br /&gt;
{{Text Footer GP}}&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=File:GP.Message_Handling.png&amp;diff=1068</id>
		<title>File:GP.Message Handling.png</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=File:GP.Message_Handling.png&amp;diff=1068"/>
		<updated>2015-05-08T19:30:53Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: Generic Pattern for Message Handling.
Category:Generic Pattern graphic&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Summary ==&lt;br /&gt;
Generic Pattern for Message Handling.&lt;br /&gt;
[[Category:Generic Pattern graphic]]&lt;br /&gt;
== Licensing ==&lt;br /&gt;
{{self|cc-by-3.0}}&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=GF.Message_Engine&amp;diff=1067</id>
		<title>GF.Message Engine</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=GF.Message_Engine&amp;diff=1067"/>
		<updated>2015-05-08T19:28:16Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: new GF&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Maturity|3}}&lt;br /&gt;
{{Pageheaderbox4GF&lt;br /&gt;
|name=Message Engine&lt;br /&gt;
|WorkingArea=Middleware&lt;br /&gt;
|version=0.2&lt;br /&gt;
|owner=J.A.H. Schoonderbeek&lt;br /&gt;
|summary=This function can receive, process and/or send messages.&lt;br /&gt;
}}&lt;br /&gt;
This function can receive, process and/or send chunks of digital data, or &amp;quot;messages&amp;quot;. A message can most always be thought of to consist of two different sets of information:&lt;br /&gt;
* Message header: this contains the information necessary to route and deliver the message. A message header is analogous to the information printed on the outside of a letter (to, from, priority of message etc.);&lt;br /&gt;
* Message body: this contains the data transmitted in the message. The semantics of the message body data must be known to the intended recipient(s).&lt;br /&gt;
The message engine can send and receives messages using one of the following two messaging styles:&lt;br /&gt;
&lt;br /&gt;
===Asynchronous messaging===&lt;br /&gt;
Asynchronous messaging is a way of data exchange that makes use of a specific data format in order to make this data routable at application level. It transmits data without making use of an internal coordination mechanism between sender and recipient. Common messaging styles:&lt;br /&gt;
* Request-reply (note that this can be both synchronous and asynchronous);&lt;br /&gt;
* Fire and forget;&lt;br /&gt;
* Publish-subscribe.&lt;br /&gt;
Asynchronous messaging has some advantages over synchronous messaging:&lt;br /&gt;
* The recipient of the message doesn&#039;t have to be available or reachable at the moment the message is sent;&lt;br /&gt;
* The communication path that the message must travel need not be fixed and available; when a part of the communication path becomes unavailable while the message is in transit, a relay station may store the message until the path becomes available again (if a &#039;&#039;message store&#039;&#039; is available at that station) or reroute the message over another, available path;&lt;br /&gt;
* A recipient that was unavailable/unreachable at the moment of sending a message will still receive it, if a &#039;&#039;message store&#039;&#039; is used (often referred to as queue). The message can always be retrieved by the recipient at a later time from the store that retains the message;&lt;br /&gt;
* One sender can reach many recipients, by broadcasting (or multicasting) a message to a specific &#039;&#039;group recipient address&#039;&#039;.&lt;br /&gt;
Asynchronous messaging also has some disadvantages over synchronous messaging:&lt;br /&gt;
* Information required to detect and or/recover data from lost communication is not provided by the messaging facility itself. If detection of/recovery from message loss is needed, it should be provided by sender and receiver(s) separately, for example by making use of a separate set of (synchronous) messages or another way of data exchange.&lt;br /&gt;
* The very nature of asynchronous messaging precludes the sender to know when the recipient actually receives the message.&lt;br /&gt;
Some of the disadvantages can be overcome by the appliance of Message Store functionality.&lt;br /&gt;
&lt;br /&gt;
===Synchronous messaging===&lt;br /&gt;
Synchronous messaging transmits data in an established, synchronized relationship between sender and recipient. Messages are sent when the sender has assessed that the recipient is ready to receive the data, and using appropriate means (think parameters like speed, error correction etc). A synchronization mechanism ensures sequentiality, e.g. by timing the communication to a fixed time signal, or by using sequence numbers. An internal coordination mechanism may be used to enable automated error detection and recovery (reliable message exchange).&lt;br /&gt;
&lt;br /&gt;
Synchronous messaging offers some distinct advantages over asynchronous messaging:&lt;br /&gt;
* The synchronization mechanism usually lends itself to promotion of &#039;&#039;reliable messaging&#039;&#039; where the sender has a certain level of certainty that the message that was sent is actually received;&lt;br /&gt;
* Synchronous messaging makes it possible for the sender to predict in advance &#039;&#039;when&#039;&#039; the recipient will actually receive the message, and confirm after the fact that the message was actually received.&lt;br /&gt;
Synchronous messaging also has some disadvantages over asynchronous messaging:&lt;br /&gt;
* The recipient of the message must be available (reachable) at the moment the message is sent;&lt;br /&gt;
* Also, all parts of the communication path that the message must travel need to be available. When a part of the communication path becomes unavailable while the message is in transit and no rerouting is possible, the sequentiality of the communication may be lost;&lt;br /&gt;
&lt;br /&gt;
===Message processing===&lt;br /&gt;
Besides sending and receiving messages, a message engine can also perform other message-related tasks. While some of these tasks have been described in their own separate infrastructure functions (e.g. message filtering), all other tasks may be considered part of the message engine, a.o.:&lt;br /&gt;
* Validating a message upon receiving it, or prior to sending it;&lt;br /&gt;
* Allowing for authentication of service consumers (senders and/or recipients);&lt;br /&gt;
* Allowing for authorization of message related activity;&lt;br /&gt;
* Responding to events (such as delivery notification) by sending out a message on its own behalf.&lt;br /&gt;
{{FunctionIcon&lt;br /&gt;
|image=Icon GF Message Engine.png&lt;br /&gt;
}}&lt;br /&gt;
{{Text Footer GF}}&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=GF.Message_Engine&amp;diff=1066</id>
		<title>GF.Message Engine</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=GF.Message_Engine&amp;diff=1066"/>
		<updated>2015-05-08T19:25:28Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: Created page with &amp;quot;{{Maturity|3}} {{Pageheaderbox4GF |name=Message Engine |WorkingArea=Middleware |version=0.2 |owner=J.A.H. Schoonderbeek |summary=unspecified }}  {{FunctionIcon |image=Icon GF....&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Maturity|3}}&lt;br /&gt;
{{Pageheaderbox4GF&lt;br /&gt;
|name=Message Engine&lt;br /&gt;
|WorkingArea=Middleware&lt;br /&gt;
|version=0.2&lt;br /&gt;
|owner=J.A.H. Schoonderbeek&lt;br /&gt;
|summary=unspecified&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{FunctionIcon&lt;br /&gt;
|image=Icon GF.&lt;br /&gt;
}}&lt;br /&gt;
{{Text Footer GF}}&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=GF.Presentation_Engine&amp;diff=1065</id>
		<title>GF.Presentation Engine</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=GF.Presentation_Engine&amp;diff=1065"/>
		<updated>2015-05-08T16:39:31Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: updated description&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Maturity|4}}&lt;br /&gt;
{{Pageheaderbox4GF&lt;br /&gt;
|name=Presentation Engine&lt;br /&gt;
|WorkingArea=Server&lt;br /&gt;
|version=0.4&lt;br /&gt;
|owner=S.A.D. Jumelet&lt;br /&gt;
|summary=This function processes input to and output from an infrastructure facility.&lt;br /&gt;
}}&lt;br /&gt;
A Presentation Engine function processes the input to and/or output from a facility, modelling the (technical) intelligence involved. This function can be used to model&lt;br /&gt;
* a client interface;&lt;br /&gt;
* an application programming interface (API);&lt;br /&gt;
* translating data that is exchanged with/from that facility.&lt;br /&gt;
&lt;br /&gt;
Presentation Engine functionality can also be deployed model how input/output capability is delivered to the consumer of a facility. For instance, a specialized Presentation Engine can decouple the physical location where the infrastructure facility is located from the physical location where the results are to be consumed. This comes in handy in situations where data is processed in bulk while data transport capabilities to/from the consumer are limited, e.g. when consulting a large database, or when using a remote workspace from a location with little bandwidth.&lt;br /&gt;
{{FunctionIcon&lt;br /&gt;
|image=Icon GF Presentation Engine.png&lt;br /&gt;
}}&lt;br /&gt;
{{Text Footer GF}}&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=GF.Message_Formatting&amp;diff=1064</id>
		<title>GF.Message Formatting</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=GF.Message_Formatting&amp;diff=1064"/>
		<updated>2015-05-08T16:20:33Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: move to middleware&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Maturity|2}}&lt;br /&gt;
{{Pageheaderbox4GF&lt;br /&gt;
|name=Message Formatting&lt;br /&gt;
|WorkingArea=Middleware&lt;br /&gt;
|version=0.21&lt;br /&gt;
|owner=J.A.H. Schoonderbeek&lt;br /&gt;
|summary=This function is used to format messages for exchange between a facility and a message handling service.&lt;br /&gt;
}}&lt;br /&gt;
The Message Formatting function can be used by an infrastructure facility to properly format and address messages that the infrastructure facility needs to send out, and hand them over to a message handling service. This includes authentication, signaling and exception handling. Conversely, the function can accept incoming messages from a Message Handling facility, and make them available for processing.&lt;br /&gt;
{{FunctionIcon&lt;br /&gt;
|image=Icon GF Message Formatting.png&lt;br /&gt;
}}&lt;br /&gt;
{{Text Footer GF}}&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=File:Icon_GF_Message_Engine.png&amp;diff=1063</id>
		<title>File:Icon GF Message Engine.png</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=File:Icon_GF_Message_Engine.png&amp;diff=1063"/>
		<updated>2015-05-08T15:56:44Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: OIAm icon for Message Engine function
Category:Generic Function Icon&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Summary ==&lt;br /&gt;
OIAm icon for Message Engine function&lt;br /&gt;
[[Category:Generic Function Icon]]&lt;br /&gt;
== Licensing ==&lt;br /&gt;
{{self|cc-by-3.0}}&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=GF.Message_Distribution&amp;diff=1062</id>
		<title>GF.Message Distribution</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=GF.Message_Distribution&amp;diff=1062"/>
		<updated>2015-05-08T15:54:51Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: new GF&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Maturity|4}}&lt;br /&gt;
{{Pageheaderbox4GF&lt;br /&gt;
|name=Message Distribution&lt;br /&gt;
|WorkingArea=Middleware&lt;br /&gt;
|version=0.2&lt;br /&gt;
|owner=J.A.H. Schoonderbeek&lt;br /&gt;
|summary=This function offers to direct messages between and/or within instances of the Message Handling facility.&lt;br /&gt;
}}&lt;br /&gt;
This function offers to direct messages from one instance of a Message Handling facility to the appropriate next one, and/or within the current instance. As such, it can be seen as a specialized form of [[GF.Distribution|Distribution]]. The message direction is accomplished by performing one or more of the following actions on messages:&lt;br /&gt;
* Interpreting destination addresses included in the message;&lt;br /&gt;
* Routing and forwarding;&lt;br /&gt;
* Multiplying a message (e.g. when intended for multiple recipients).&lt;br /&gt;
Optionally, forwarding decisions can be based not only on address information, but also on filtering criteria. However, for practical reasons this functionality is described in, and assigned to, the Generic Function Filtering.&lt;br /&gt;
{{FunctionIcon&lt;br /&gt;
|image=Icon GF Message Distribution.png&lt;br /&gt;
}}&lt;br /&gt;
{{Text Footer GF}}&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=File:Icon_GF_Message_Distribution.png&amp;diff=1061</id>
		<title>File:Icon GF Message Distribution.png</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=File:Icon_GF_Message_Distribution.png&amp;diff=1061"/>
		<updated>2015-05-08T15:45:58Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: OIAm icon for Message Distribution function
Category:Generic Function Icon&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Summary ==&lt;br /&gt;
OIAm icon for Message Distribution function&lt;br /&gt;
[[Category:Generic Function Icon]]&lt;br /&gt;
== Licensing ==&lt;br /&gt;
{{self|cc-by-3.0}}&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=GF.Message_Store&amp;diff=1060</id>
		<title>GF.Message Store</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=GF.Message_Store&amp;diff=1060"/>
		<updated>2015-05-08T15:37:30Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: new GF&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Maturity|4}}&lt;br /&gt;
{{Pageheaderbox4GF&lt;br /&gt;
|name=Message Store&lt;br /&gt;
|WorkingArea=Middleware&lt;br /&gt;
|version=0.2&lt;br /&gt;
|owner=J.A.H. Schoonderbeek&lt;br /&gt;
|summary=This function preserves and organizes digital messages.&lt;br /&gt;
}}&lt;br /&gt;
Message Store functionality is used to preserve and organize digital messages, and can be used by other parts of a Message Handling facilities for intermediate storage of messages, e.g. as a message queue. Thus it can be seen as a specialized version of [[GF.Queuing|Queuing]]. However, it can also store messages for as long as a recipient needs to have access to any individual message - such as with user e-mail.&lt;br /&gt;
&lt;br /&gt;
This Generic Function can be used as the front end for a (more generic) Data Management or File Storage service, allowing for message related metadata, indexing of messages, et cetera. However, if details about the underlying storage mechanisms aren&#039;t needed, the Message Store function may also be used to represent the whole of the message store functionality.&lt;br /&gt;
{{FunctionIcon&lt;br /&gt;
|image=Icon GF Message Store.png&lt;br /&gt;
}}&lt;br /&gt;
{{Text Footer GF}}&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=File:Icon_GF_Message_Store.png&amp;diff=1059</id>
		<title>File:Icon GF Message Store.png</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=File:Icon_GF_Message_Store.png&amp;diff=1059"/>
		<updated>2015-05-08T15:34:50Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: OIAm icon for Message Store function
Category:Generic Function Icon&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Summary ==&lt;br /&gt;
OIAm icon for Message Store function&lt;br /&gt;
[[Category:Generic Function Icon]]&lt;br /&gt;
== Licensing ==&lt;br /&gt;
{{self|cc-by-3.0}}&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=GP.Message_Handling&amp;diff=1058</id>
		<title>GP.Message Handling</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=GP.Message_Handling&amp;diff=1058"/>
		<updated>2015-05-08T12:38:00Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: stub&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Maturity|4}}&lt;br /&gt;
{{Pageheaderbox4GP&lt;br /&gt;
|name=Message Handling&lt;br /&gt;
|sector=Commons&lt;br /&gt;
|version=0.4&lt;br /&gt;
|owner=J.A.H. Schoonderbeek&lt;br /&gt;
|summary=This Pattern accepts messages from senders, and then handles transport, storage, and delivery to recipients. &lt;br /&gt;
}}&lt;br /&gt;
This infrastructure function accepts chunks of digital data, or &amp;quot;messages&amp;quot;, from parties called senders, and then handles transport, storage, and delivery of these messages to parties called recipients. The parties involved may be human users, digital systems, or even the digital equivalent of a mailboxes of which it is not known in advance who or what will send or collect the message. Any consumer of (the service delivered by) this Pattern may be a sender, a recipient, or both.&lt;br /&gt;
&lt;br /&gt;
A message may be directed at a single recipient or multiple recipients, and the message may be delivered (near-) realtime or asynchronously. A message can most always be thought of to consist of two different sets of information:&lt;br /&gt;
* Message header: this contains the information necessary to route and deliver the message. A message header is analogous to the information printed on the outside of a letter (to, from, priority of message etc.) The message header may be invisible/inaccessible to the consumers of the Message Handling service.&lt;br /&gt;
* Message body: this contains the data transmitted to the intended recipient(s). The semantics of the message body data must be known to the intended recipient(s).&lt;br /&gt;
Important aspects of a Message Handling Pattern are:&lt;br /&gt;
* this Pattern makes it unnecessary for the sender to be in direct contact with the recipient(s);&lt;br /&gt;
* if any routing of the message is required, it is handled mainly or fully by this Pattern;&lt;br /&gt;
* the Pattern may provide a sender with acknowledgment of the message&#039;s reception, or not (&amp;quot;fire and forget&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
The Generic Pattern already has a sizeable amount of optional Generic Functions and Generic Services. However, please note that in the interest of brevity, the following aspects have not been included (as either recommended or optional). These may require consideration nevertheless:&lt;br /&gt;
* The [[GS.Data_Transport|Data Transport]] service(s) that will actually carry the messages from sender to (an instance of) the Pattern, between (instances of) the Pattern, and from (an instance of) the Pattern to the recipients;&lt;br /&gt;
* [[GF.Encryption|Encryption]] and compression ([[GF.Reduction|Reduction]]), which may operate on individual messages and/or on the communication channels that the Pattern uses;&lt;br /&gt;
* [[GF.Load Balancing|Load Balancing]] and [[GF.Queuing|Queuing]], which may be handled outside of (an implementation of) this Pattern, or may need to be included explicitly.&lt;br /&gt;
{{Pattern Realizes&lt;br /&gt;
|service=GS.Message Handling&lt;br /&gt;
}}&lt;br /&gt;
{{Pattern Graphic&lt;br /&gt;
|graphic=No graphic yet.png&lt;br /&gt;
|size=600px&lt;br /&gt;
|kind=Generic&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition}}&lt;br /&gt;
{{Table Ending}}&lt;br /&gt;
{{Pattern Adjacent Services}}&lt;br /&gt;
{{Table Ending}}&lt;br /&gt;
{{Text Footer GP}}&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=Template:PatternRealizingThisService&amp;diff=1057</id>
		<title>Template:PatternRealizingThisService</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=Template:PatternRealizingThisService&amp;diff=1057"/>
		<updated>2015-05-08T11:47:16Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: cut down the diagnostic message&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{#vardefine:pagename|{{PAGENAME}}}}{{#if:{{{page|}}}|{{#vardefine:pagename|{{{page}}}}}}}{{#vardefine:typetest|{{#ask:[[{{#var:pagename}}]] [[Category:Generic Service]]|format=list|link=none}}}}{{#vardefine:kind|{{#ifexist:{{#var:typetest}} | Generic | Applied }}}}{{#switch:{{#ask: [[Category:{{#var:kind}} Pattern]][[Realizes::{{#var:pagename}}]]|format=count}}&lt;br /&gt;
|0=(no {{#var:kind}} pattern found)&lt;br /&gt;
|1={{#vardefine:pattern|{{#ask: [[Category:{{#var:kind}} Pattern]][[Realizes::{{#var:pagename}}]]|link=none}}}}{{FriendlyPageLink|{{#var:pattern}}}} ({{#show: {{#var:pattern}} |?Brief description}})&lt;br /&gt;
|{{#ask: [[Category:{{#var:kind}} Pattern]][[Realizes::{{#var:pagename}}]]|link=none|format=template|template=PrintPatterns}}&lt;br /&gt;
}}&amp;lt;noinclude&amp;gt;&lt;br /&gt;
{{Documentation}}&lt;br /&gt;
&amp;lt;!-- Add categories and interwikis to the /doc subpage, not here! --&amp;gt;&lt;br /&gt;
&amp;lt;/noinclude&amp;gt;&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=GS.Message_Handling&amp;diff=1056</id>
		<title>GS.Message Handling</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=GS.Message_Handling&amp;diff=1056"/>
		<updated>2015-05-08T11:45:58Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: updated functionality&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Maturity|4}}&lt;br /&gt;
{{Pageheaderbox4GS&lt;br /&gt;
|name=Message Handling&lt;br /&gt;
|version=0.6&lt;br /&gt;
|owner=J.A.H. Schoonderbeek&lt;br /&gt;
|summary=This service handles transport, storage and delivery of messages between senders and recipients.&lt;br /&gt;
}}&lt;br /&gt;
This service handles transport, storage and delivery of chunks of digital data, or &amp;quot;messages&amp;quot;, between parties, called senders and recipients. The parties involved may be human users, digital systems, or even the digital equivalent of a mailboxes of which it is not known in advance who or what will receive the message. Any consumer of the Message Handling service may be a sender, a recipient, or both. A message may be directed at a single recipient or multiple recipients, and the message may be delivered (near-) realtime or asynchronously. A message can most always be thought of to consist of two different sets of information:&lt;br /&gt;
* Message header: this contains the information necessary to route and deliver the message. A message header is analogous to the information printed on the outside of a letter (to, from, priority of message etc.) The message header may be invisible/inaccessible to the consumers of the Message Handling service.&lt;br /&gt;
* Message body: this contains the data transmitted to the intended recipient(s). The semantics of the message body data must be known to the intended recipient(s).&lt;br /&gt;
Important aspects of a Message Handling service are:&lt;br /&gt;
* the sender does not need to be in direct contact with the recipient(s); instead direct contact with the Message Handling service is the only requirement;&lt;br /&gt;
* if any routing of the message is required, it is handled mainly or fully by the service;&lt;br /&gt;
the service may provide acknowledging of the message&#039;s reception, or not (&amp;quot;fire and forget&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
Three common forms of Message Handling services are:&lt;br /&gt;
* e-mail (since MIT&#039;s [http://en.wikipedia.org/wiki/Email#Host-based_mail_systems CTSS MAIL], 1965);&lt;br /&gt;
* direct messaging or instant messaging ([http://en.wikipedia.org/wiki/Instant_messaging#Statistics such as] SMS, WhatsApp, IRC);&lt;br /&gt;
* Enterprise Service Bus ([http://en.wikipedia.org/wiki/Enterprise_service_bus ESB]).&lt;br /&gt;
&lt;br /&gt;
{{Text Footer GS}}&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=GP.Managed_File_Transfer&amp;diff=1055</id>
		<title>GP.Managed File Transfer</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=GP.Managed_File_Transfer&amp;diff=1055"/>
		<updated>2015-04-23T12:41:27Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: added dataprot mgmt as adjacent service &amp;amp; updated maturity&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Maturity|3}}&lt;br /&gt;
{{Pageheaderbox4GP&lt;br /&gt;
|name=Managed File Transfer&lt;br /&gt;
|sector=Business Support&lt;br /&gt;
|version=0.2&lt;br /&gt;
|owner=J.A.H. Schoonderbeek&lt;br /&gt;
|summary=This Pattern provides a means to transport loosely structured data from a source to one or more targets, either ad hoc or structurally..&lt;br /&gt;
}}&lt;br /&gt;
Managed File Transfer (abbreviated MFT) indicates the automated transfer of data in a loosely structured form (&amp;quot;files&amp;quot;) between IT facilities. These facilities can be owned by the organization, but an MFT instance may also be used to transfer files into or out of the organization, from or to external IT systems. Furthermore, human users may also make use of the MFT pattern to exchange data with other users and/or IT systems.&lt;br /&gt;
A realization of this MFT Pattern handles the reception and/or collection of files from a source, and their delivery to and/or collection by one or more targets. It may also additionally modify the files by transcoding, encrypting/decrypting, (de)compressing, and/or it may provide means to modify the files in transit in other respects. Incoming and outgoing traffic may be regulated using predescribed rules and/or by schedules that act on times, periods or order. The Pattern requires use of an instance of Data Transport (and optionally Message Handling), since the data to be transported comes in and goes out over these services. Most data transfers will require the Managed File Transfer Pattern to authenticate itself to the source and/or target. Furthermore functionality can be present to provide logging of each file transfer for operational and security purposes.&lt;br /&gt;
{{Pattern Realizes&lt;br /&gt;
|service=GS.Managed File Transfer&lt;br /&gt;
}}&lt;br /&gt;
{{Pattern Graphic&lt;br /&gt;
|graphic=GP.Managed_File_Transfer.png&lt;br /&gt;
|source=GP.&lt;br /&gt;
|size=710px&lt;br /&gt;
|title=Generic Pattern Managed File Transfer&lt;br /&gt;
|kind=Generic&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.File Engine&lt;br /&gt;
|choice=Must&lt;br /&gt;
|reason=This function represents the core intelligence of the Managed File Transfer service. This function performs the collection or accepting of files from the source, and the transmission or offering of files to one or more targets.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Presentation Engine&lt;br /&gt;
|choice=Must&lt;br /&gt;
|reason=This function represents the transcoding that is required when a source offers a file in a different format and/or using a different transfer protocol from the format/protocol used by the file transfer&#039;s target(s). Furthermore, if the Pattern offers ad hoc file transfers to human users, then this function shapes the users&#039; experience when using the Managed File Transfer service (e.g. a web environment for uploading and downloading the files).&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Caching&lt;br /&gt;
|choice=Must&lt;br /&gt;
|reason=Any file in transit will be buffered in the Managed File Transfer facility while it is processing file transfer tasks such as transcoding. This transient storage of files inside the MFT facility needs attention because of three aspects:&lt;br /&gt;
* Security: the storing of files needs to be secured to the level that&#039;s appropriate for the confidentiality required by the business and security department;&lt;br /&gt;
* Storage space: enough space needs to be present to store the maximum volume of files that may reside in transient storage at the facility at any given time; an overflow to the adjacent service File Storage may be in order;&lt;br /&gt;
* Business continuity: when a technical problem or disaster impedes the MFT facility, measures must be taken to account for files that were residing only in transient storage at the time of the problem.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Rules Engine&lt;br /&gt;
|choice=May&lt;br /&gt;
|reason=This function represents the additional intelligence that can drive extra manipulation of files in transit, advanced exception handling, logging and/or routing  by the Pattern. Active collection of information on the files in transit, source and/or target(s) may lead to execution of (implicit or explicit) rules.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Logging&lt;br /&gt;
|choice=May&lt;br /&gt;
|reason=This function is often included, as logs of file transfers are required not only by Operations, but also Security/Compliance. Furthermore, a business entity responsible for sending files, or one that expects incoming files, may require access to the logged information to verify data transfers.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Scheduling&lt;br /&gt;
|choice=May&lt;br /&gt;
|reason=Scheduling can serve to initiate file tranfers and/or internal maintenance tasks, on regular or predetermined times.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Controlling&lt;br /&gt;
|choice=Must&lt;br /&gt;
|reason=This function models the manner in which the Pattern&#039;s administrators, and possibly authorized clients, can administer file transfers. Among the administrative tasks can be the following:&lt;br /&gt;
* Administering file transfer end points;&lt;br /&gt;
* Administeringfile transfer tasks (which in turn make use of transfer end points);&lt;br /&gt;
* Administering schedules for automated file transfers.&lt;br /&gt;
Since the files transferred by the Pattern may be business critical and/or have a certain level of confidentiality, care must be taken to limit access to this function to authorized users.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Encryption&lt;br /&gt;
|choice=May&lt;br /&gt;
|reason=This function can be used to model the encryption/decryption that is associated with secure file transfer protocols, as well as the manipulation of files in transit, when the MFT is required to encrypt/decrypt files or file archives.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Reduction&lt;br /&gt;
|choice=May&lt;br /&gt;
|reason=This function can be used to model the compression that is often associated with file transfer protocols, as well as the manipulation of files in transit, when the MFT is required to compress/decompress files or file archives, or manipulate files that sit inside a file archive.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Distribution&lt;br /&gt;
|choice=May&lt;br /&gt;
|reason=When the MFT facility is required to deliver files to multiple targets, then this function models the handling of addressing and routing.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Message Formatting&lt;br /&gt;
|choice=May&lt;br /&gt;
|reason=When the MFT facility makes use of a Message Handling services, then the Message Formatting functionality provides the interface to such a service.&lt;br /&gt;
}}&lt;br /&gt;
{{Table Ending}}&lt;br /&gt;
{{Pattern Adjacent Services}}&lt;br /&gt;
{{Generic Pattern Adjacent Service Row&lt;br /&gt;
|service=GS.Data Transport&lt;br /&gt;
|choice=Must&lt;br /&gt;
|reason=All files that an MFT facility handles come in and go out over a Data Transport service. Especially the transfer of files over one or more security delineations require attention, so the explicit modelling of Data Transport is recommended.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Adjacent Service Row&lt;br /&gt;
|service=GS.Authentication+Authorization&lt;br /&gt;
|choice=May&lt;br /&gt;
|reason=The Pattern will likely be required to authenticate itself when collecting and/or delivering a file. Furthermore, the Pattern probably will require systems and users to authenticate themselves when they wish to transfer or collect files. Finally, access to the services provided by the Managed File Transfer Pattern must likely be limited to authorized personnel.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Adjacent Service Row&lt;br /&gt;
|service=GS.Facilities Monitoring&lt;br /&gt;
|choice=May&lt;br /&gt;
|reason=The logs of file transfers are of interest to security and operational personnel, as well as the business units that make use of Managed File Transfer. Connections with Facilities Monitoring services provide these monitoring services with the data with which they can provide their respective users the required insights and overview.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Adjacent Service Row&lt;br /&gt;
|service=GS.File Storage&lt;br /&gt;
|choice=Must&lt;br /&gt;
|reason=A file in transit will be stored in the Managed File Transfer facility when the target is required to actively fetch the file (&amp;quot;pull-out&amp;quot;) instead of having the file delivered as soon as it enters the MFT from the source. This storage of files inside the MFT facility needs attention because of three aspects:&lt;br /&gt;
* Security: the storing of files needs to be secured to the level that&#039;s appropriate for the confidentiality required by the business and security department;&lt;br /&gt;
* Storage space: enough space needs to be present to store the maximum volume of files that may reside at the facility at any given time (including exceptional times such as when one or more sources cannot accept files for any given reason, e.g. connectivity issues);&lt;br /&gt;
* Business continuity: when a technical problem or disaster impedes the MFT facility, files already accepted from the source but not yet delivered to (all) targets may be at risk of loss or corruption. The connection between the MFT facility and the File Storage service should correctly handle such events.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Adjacent Service Row&lt;br /&gt;
|service=GS.Data Protection Management&lt;br /&gt;
|choice=May&lt;br /&gt;
|reason=When data en route between sender and recipient(s) is residing in a Managed File Transfer facility, it needs to be protected from corruption and data loss, possibly even in the event of a total loss of the MFT facility itself. Adequate protection may be obtained by calling upon an external Data Protection Management service.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Adjacent Service Row&lt;br /&gt;
|service=GS.Message Handling&lt;br /&gt;
|choice=May&lt;br /&gt;
|reason=This service may be adjacent because of either of the following reasons:&lt;br /&gt;
* files are transported in and/or out of the MFT facility via a messaging protocol;&lt;br /&gt;
* the MFT facility uses Message Handling services to notify security, operational and business users about events in the facility, such as failure/success of file transfers.&lt;br /&gt;
}}&lt;br /&gt;
{{Table Ending}}&lt;br /&gt;
{{Text Footer GP}}&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=File:GP.Managed_File_Transfer.png&amp;diff=1054</id>
		<title>File:GP.Managed File Transfer.png</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=File:GP.Managed_File_Transfer.png&amp;diff=1054"/>
		<updated>2015-04-23T12:37:40Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: Jan Schoonderbeek uploaded a new version of &amp;amp;quot;File:GP.Managed File Transfer.png&amp;amp;quot;: added data protection mgmt&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Summary ==&lt;br /&gt;
Generic Pattern for managed file transfers.&lt;br /&gt;
== Licensing ==&lt;br /&gt;
{{self|cc-by-3.0}}&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=GP.Workspace&amp;diff=1053</id>
		<title>GP.Workspace</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=GP.Workspace&amp;diff=1053"/>
		<updated>2015-04-19T21:10:47Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: smaller pic&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Maturity|4}}&lt;br /&gt;
{{Pageheaderbox4GP&lt;br /&gt;
|name=Workspace&lt;br /&gt;
|sector=Commons&lt;br /&gt;
|version=0.5&lt;br /&gt;
|owner=J.A.H. Schoonderbeek&lt;br /&gt;
|summary=This Pattern models a gateway between the physical and digital world, such as a user workspace.&lt;br /&gt;
}}&lt;br /&gt;
This Pattern models the generic (user) digital workspace, which acts as a gateway between the digital and physical world. The goal of this pattern is to provide a digital consumer (applications and/or other ICT systems) a means to interact with the physical world, including the human users of ICT.&lt;br /&gt;
&lt;br /&gt;
While the Pattern can be used to model many systems varying from smart watches to multifunctional workgroup printers, its main application is in the modelling of a user workspace.&lt;br /&gt;
By and large there are three types of user workspace:&lt;br /&gt;
# A &amp;quot;fat client&amp;quot;: a workspace that delivers its consumers (most or all) computational resources from the location of the human user, resulting in less dependence on the organization&#039;s central IT. However, the consumers running on the workspace may well make use of centralized resources such as shared file storage, and the workspace itself may be serviced from a centralized facility, e.g. applications may be deployed from a remote deployment service. The applications running locally, and the human user working the applications, can have all necessary rights and abilities to manage the workspace, or these rights and abilities can be partially or wholly restricted, e.g. by centrally managed policies&lt;br /&gt;
# A &amp;quot;virtual desktop&amp;quot; providing consumers with a centralized personal workspace: the workspace has all the properties of a fat client, except that the computational resources are delivered from one or more centralized locations. At the physical location of the human user, an extra workspace is required for handling the actual physical input and output, using connectivity to the centralized location to transmit the digital input/output. This may involve only a minimal device (&amp;quot;thin client&amp;quot;).&lt;br /&gt;
# A &amp;quot;shared applications environment&amp;quot; providing access to a centralized shared workspace: the workspace has the properties of the centralized personal workspace, except that groups of human users share the same workspace, with limited or no personalization, and little or no flexibility in installing applications for the user itself. Every update or new application is handled at the centralized location, resulting in uniform workspaces between users in the same group, and predictable maintenance load for the centralized facility.&lt;br /&gt;
Note that while the fat client and thin client characterizations point toward &amp;quot;traditional&amp;quot; computers, this Pattern is equally suitable to model different form factors, purposes and information delivery, ranging from tablets and mobile devices through gaming consoles and wearable IT. The different form factors and other properties of these clients are then represented in the Input and Output functionality, and in Workspace Accommodation if need be.&lt;br /&gt;
&lt;br /&gt;
While Workspace implementations often use the desktop computer metaphor, OIAm&#039;s use of the term is not limited to facilities that can deliver a user the desktop experience. Other devices and systems may also be modelled, as long as either user input and/or output are present. Examples are multifunctional workgroup printers (a single printer directly attached to a single user workspace is better represented as an Output function instance), surveillance camera systems, telemetry platforms, CNC ([http://en.wikipedia.org/wiki/Numerical_control Computer Numerical Control]) systems and most any other system that interacts with the physical world.&lt;br /&gt;
&lt;br /&gt;
The Pattern often depends on many adjacent services, only some of which have been included in this Pattern Type description.&lt;br /&gt;
{{Pattern Realizes&lt;br /&gt;
|service=GS.Workspace&lt;br /&gt;
}}&lt;br /&gt;
{{Pattern Graphic&lt;br /&gt;
|graphic=GP.Workspace.png&lt;br /&gt;
|source=GP.&lt;br /&gt;
|size=600px&lt;br /&gt;
|kind=Generic&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Workspace Engine&lt;br /&gt;
|choice=Must&lt;br /&gt;
|reason=This function provides the main functionality of the pattern: the support of applications.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Presentation Engine&lt;br /&gt;
|choice=Must&lt;br /&gt;
|reason=Output to, and input from the physical world will surely require appropriate formatting and/or processing. For example, camera images presented by [[GF.Input|Input]] may require a form of compression (not separately included in the Pattern), while force feedback output will require adaptation to the format in use at the targeted [[GF.Output|Output]] device.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Output&lt;br /&gt;
|choice=Must&lt;br /&gt;
|reason=This function provides the actual output to the physical world.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Input&lt;br /&gt;
|choice=Must&lt;br /&gt;
|reason=This function provides the actual input from the physical world.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Controlling&lt;br /&gt;
|choice=Must&lt;br /&gt;
|reason=This function models the manner in which the Pattern&#039;s administrators, and possibly authorized clients, can administer the Workspace. Among the administrative tasks can be the following:&lt;br /&gt;
* Administering look &amp;amp; feel of the Workspace as it presents itself to a (human or ICT) consumer;&lt;br /&gt;
* Configuring input &amp;amp; output parameters;&lt;br /&gt;
* Administering updates, policies, logging, and other operational and security related parameters.&lt;br /&gt;
Care must be taken to limit access to this function to users that are sufficiently knowledgeable and authorized, as misconfiguration likely impacts both operational efficiency and IT security.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Workspace Accommodation&lt;br /&gt;
|choice=May&lt;br /&gt;
|reason=Accommodation covers mainly physical traits of the workspace, including how the workspace is projected from the place of generation (e.g. server farm) to the location of use (e.g. a user&#039;s office). Accommodation is regularly used to describe the functionality of a &amp;quot;thin client&amp;quot;, negating the need to separately model this client as a physical Workspace that supports a centralized virtual Workspace.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Logging&lt;br /&gt;
|choice=May&lt;br /&gt;
|reason=As the interaction with the physical world and with human users gives greater rise to incidents, good logging is recommended for both operational and security purposes.&lt;br /&gt;
}}&lt;br /&gt;
{{Table Ending}}&lt;br /&gt;
{{Pattern Adjacent Services}}&lt;br /&gt;
{{Generic Pattern Adjacent Service Row&lt;br /&gt;
|service=GS.File Storage&lt;br /&gt;
|choice=Must&lt;br /&gt;
|reason=The way in which the Workspace stores data and other files may be either local to the physical device (in which case it can be included in an applied version of this Generic Pattern), or relegated to a centralized service.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Adjacent Service Row&lt;br /&gt;
|service=GS.Authentication+Authorization&lt;br /&gt;
|choice=May&lt;br /&gt;
|reason=Often the normal interaction with human users will require Authentication, as in the case of a regular user workspace (but not in the case of, for instance, a kiosk system). But even if this is not the case, then still Authentication &amp;amp; Authorization is recommended for the [[GF.Controlling|Controlling]] functionality.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Adjacent Service Row&lt;br /&gt;
|service=GS.Facilities Monitoring&lt;br /&gt;
|choice=May&lt;br /&gt;
|reason=Workspaces often form a significant load on operational support, and are also regularly a concern for security personnel. Monitoring (often subdivided into operational and security monitoring) helps inform these groups of incidents, status and general use of Workspace instances.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Adjacent Service Row&lt;br /&gt;
|service=GS.Facilities Deployment&lt;br /&gt;
|choice=May&lt;br /&gt;
|reason=Workspace facilities may be instantiated many times, as can be seen with user workspaces. In that case, use of a Facilities Deployment service may reduce operational effort and response times, while increasing quality and uniformity.&lt;br /&gt;
}}&lt;br /&gt;
{{Table Ending}}&lt;br /&gt;
{{Text Footer GP}}&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=GP.Workspace&amp;diff=1052</id>
		<title>GP.Workspace</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=GP.Workspace&amp;diff=1052"/>
		<updated>2015-04-19T21:10:17Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: fixed image link&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Maturity|4}}&lt;br /&gt;
{{Pageheaderbox4GP&lt;br /&gt;
|name=Workspace&lt;br /&gt;
|sector=Commons&lt;br /&gt;
|version=0.5&lt;br /&gt;
|owner=J.A.H. Schoonderbeek&lt;br /&gt;
|summary=This Pattern models a gateway between the physical and digital world, such as a user workspace.&lt;br /&gt;
}}&lt;br /&gt;
This Pattern models the generic (user) digital workspace, which acts as a gateway between the digital and physical world. The goal of this pattern is to provide a digital consumer (applications and/or other ICT systems) a means to interact with the physical world, including the human users of ICT.&lt;br /&gt;
&lt;br /&gt;
While the Pattern can be used to model many systems varying from smart watches to multifunctional workgroup printers, its main application is in the modelling of a user workspace.&lt;br /&gt;
By and large there are three types of user workspace:&lt;br /&gt;
# A &amp;quot;fat client&amp;quot;: a workspace that delivers its consumers (most or all) computational resources from the location of the human user, resulting in less dependence on the organization&#039;s central IT. However, the consumers running on the workspace may well make use of centralized resources such as shared file storage, and the workspace itself may be serviced from a centralized facility, e.g. applications may be deployed from a remote deployment service. The applications running locally, and the human user working the applications, can have all necessary rights and abilities to manage the workspace, or these rights and abilities can be partially or wholly restricted, e.g. by centrally managed policies&lt;br /&gt;
# A &amp;quot;virtual desktop&amp;quot; providing consumers with a centralized personal workspace: the workspace has all the properties of a fat client, except that the computational resources are delivered from one or more centralized locations. At the physical location of the human user, an extra workspace is required for handling the actual physical input and output, using connectivity to the centralized location to transmit the digital input/output. This may involve only a minimal device (&amp;quot;thin client&amp;quot;).&lt;br /&gt;
# A &amp;quot;shared applications environment&amp;quot; providing access to a centralized shared workspace: the workspace has the properties of the centralized personal workspace, except that groups of human users share the same workspace, with limited or no personalization, and little or no flexibility in installing applications for the user itself. Every update or new application is handled at the centralized location, resulting in uniform workspaces between users in the same group, and predictable maintenance load for the centralized facility.&lt;br /&gt;
Note that while the fat client and thin client characterizations point toward &amp;quot;traditional&amp;quot; computers, this Pattern is equally suitable to model different form factors, purposes and information delivery, ranging from tablets and mobile devices through gaming consoles and wearable IT. The different form factors and other properties of these clients are then represented in the Input and Output functionality, and in Workspace Accommodation if need be.&lt;br /&gt;
&lt;br /&gt;
While Workspace implementations often use the desktop computer metaphor, OIAm&#039;s use of the term is not limited to facilities that can deliver a user the desktop experience. Other devices and systems may also be modelled, as long as either user input and/or output are present. Examples are multifunctional workgroup printers (a single printer directly attached to a single user workspace is better represented as an Output function instance), surveillance camera systems, telemetry platforms, CNC ([http://en.wikipedia.org/wiki/Numerical_control Computer Numerical Control]) systems and most any other system that interacts with the physical world.&lt;br /&gt;
&lt;br /&gt;
The Pattern often depends on many adjacent services, only some of which have been included in this Pattern Type description.&lt;br /&gt;
{{Pattern Realizes&lt;br /&gt;
|service=GS.Workspace&lt;br /&gt;
}}&lt;br /&gt;
{{Pattern Graphic&lt;br /&gt;
|graphic=GP.Workspace.png&lt;br /&gt;
|size=800px&lt;br /&gt;
|kind=Generic&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Workspace Engine&lt;br /&gt;
|choice=Must&lt;br /&gt;
|reason=This function provides the main functionality of the pattern: the support of applications.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Presentation Engine&lt;br /&gt;
|choice=Must&lt;br /&gt;
|reason=Output to, and input from the physical world will surely require appropriate formatting and/or processing. For example, camera images presented by [[GF.Input|Input]] may require a form of compression (not separately included in the Pattern), while force feedback output will require adaptation to the format in use at the targeted [[GF.Output|Output]] device.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Output&lt;br /&gt;
|choice=Must&lt;br /&gt;
|reason=This function provides the actual output to the physical world.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Input&lt;br /&gt;
|choice=Must&lt;br /&gt;
|reason=This function provides the actual input from the physical world.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Controlling&lt;br /&gt;
|choice=Must&lt;br /&gt;
|reason=This function models the manner in which the Pattern&#039;s administrators, and possibly authorized clients, can administer the Workspace. Among the administrative tasks can be the following:&lt;br /&gt;
* Administering look &amp;amp; feel of the Workspace as it presents itself to a (human or ICT) consumer;&lt;br /&gt;
* Configuring input &amp;amp; output parameters;&lt;br /&gt;
* Administering updates, policies, logging, and other operational and security related parameters.&lt;br /&gt;
Care must be taken to limit access to this function to users that are sufficiently knowledgeable and authorized, as misconfiguration likely impacts both operational efficiency and IT security.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Workspace Accommodation&lt;br /&gt;
|choice=May&lt;br /&gt;
|reason=Accommodation covers mainly physical traits of the workspace, including how the workspace is projected from the place of generation (e.g. server farm) to the location of use (e.g. a user&#039;s office). Accommodation is regularly used to describe the functionality of a &amp;quot;thin client&amp;quot;, negating the need to separately model this client as a physical Workspace that supports a centralized virtual Workspace.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Composition Row&lt;br /&gt;
|function=GF.Logging&lt;br /&gt;
|choice=May&lt;br /&gt;
|reason=As the interaction with the physical world and with human users gives greater rise to incidents, good logging is recommended for both operational and security purposes.&lt;br /&gt;
}}&lt;br /&gt;
{{Table Ending}}&lt;br /&gt;
{{Pattern Adjacent Services}}&lt;br /&gt;
{{Generic Pattern Adjacent Service Row&lt;br /&gt;
|service=GS.File Storage&lt;br /&gt;
|choice=Must&lt;br /&gt;
|reason=The way in which the Workspace stores data and other files may be either local to the physical device (in which case it can be included in an applied version of this Generic Pattern), or relegated to a centralized service.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Adjacent Service Row&lt;br /&gt;
|service=GS.Authentication+Authorization&lt;br /&gt;
|choice=May&lt;br /&gt;
|reason=Often the normal interaction with human users will require Authentication, as in the case of a regular user workspace (but not in the case of, for instance, a kiosk system). But even if this is not the case, then still Authentication &amp;amp; Authorization is recommended for the [[GF.Controlling|Controlling]] functionality.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Adjacent Service Row&lt;br /&gt;
|service=GS.Facilities Monitoring&lt;br /&gt;
|choice=May&lt;br /&gt;
|reason=Workspaces often form a significant load on operational support, and are also regularly a concern for security personnel. Monitoring (often subdivided into operational and security monitoring) helps inform these groups of incidents, status and general use of Workspace instances.&lt;br /&gt;
}}&lt;br /&gt;
{{Generic Pattern Adjacent Service Row&lt;br /&gt;
|service=GS.Facilities Deployment&lt;br /&gt;
|choice=May&lt;br /&gt;
|reason=Workspace facilities may be instantiated many times, as can be seen with user workspaces. In that case, use of a Facilities Deployment service may reduce operational effort and response times, while increasing quality and uniformity.&lt;br /&gt;
}}&lt;br /&gt;
{{Table Ending}}&lt;br /&gt;
{{Text Footer GP}}&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=The_infrastructure_landscape&amp;diff=1051</id>
		<title>The infrastructure landscape</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=The_infrastructure_landscape&amp;diff=1051"/>
		<updated>2015-04-19T21:08:27Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: direct links to infra sector pages&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The set of [[Generic Pattern overview|Generic Patterns]] defined by OIAm cover most, if not all, of any organization&#039;s infrastructure functionality. As such, it can serve as an index, useful for classifying the functionality of a realized set of infrastructure facilities, or as an abstract sort of infrastructure landscape map.&lt;br /&gt;
&lt;br /&gt;
A clickable map of the Generic Patterns that together form the archetype of the Infrastructure Landscape is depicted below. The overarching [[OIAm_data_view|Data View]] is added for reference. The Generic Patterns themselves are grouped by the [[Property:Belongs_to_infrastructure_sector|infrastructure sector]] to which they belong:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;imagemap&amp;gt;&lt;br /&gt;
Image:Infrastructure Landscape.png|800px|&lt;br /&gt;
rect  22 110  191 175  [[GP.Workspace|Workspace]]&lt;br /&gt;
rect  22 224  191 291  [[GP.Digital_Output_Management|Digital Output Management]]&lt;br /&gt;
rect  22 337  191 402  [[GP.Streams_Management|Streams Management]]&lt;br /&gt;
rect 239 110  409 175  [[GP.Portal|Portal]]&lt;br /&gt;
rect 239 224  409 291  [[GP.Message_Handling|Message Handling]]&lt;br /&gt;
rect 239 337  409 402  [[GP.Orchestration|Orchestration]]&lt;br /&gt;
&lt;br /&gt;
rect 456 110  625 175  [[GP.Access_Security|Access Security]]&lt;br /&gt;
rect 456 224  625 291  [[GP.Access_Distribution|Access Distribution]]&lt;br /&gt;
rect 456 337  625 402  [[GP.Application Hosting|Application Hosting]]&lt;br /&gt;
rect 674 224  845 291  [[GP.Managed_File_Transfer|Managed File Transfer]]&lt;br /&gt;
rect 674 337  845 402  [[GP.Content_Hosting|Content Hosting]]&lt;br /&gt;
&lt;br /&gt;
rect 892 224 1062 291  [[GP.Facilities Deployment|Facilities Deployment]]&lt;br /&gt;
rect 892 337 1062 402  [[GP.Facilities Monitoring|Facilities Monitoring]]&lt;br /&gt;
rect 892 452 1062 518  [[GP.Identity+Permission Management|Identity &amp;amp; Permission Management]]&lt;br /&gt;
rect 892 564 1062 631  [[GP.Backup+Archive Management|Backup &amp;amp; Archive Management]]&lt;br /&gt;
&lt;br /&gt;
rect  22 452  191 518  [[GP.Data Transport|Data Transport]]&lt;br /&gt;
rect  22 564  191 631  [[GP.Data Zone Protection|Data Zone Protection]]&lt;br /&gt;
rect 239 452  409 518  [[GP.File Storage|File Storage]]&lt;br /&gt;
rect 239 497  409 566  [[GP.Raw Storage|Raw Storage]]&lt;br /&gt;
rect 456 452  625 518  [[GP.Data Management|Data Management]]&lt;br /&gt;
rect 674 452  845 518  [[GP.Authentication+Authorization|Authentication &amp;amp; Authorization]]&lt;br /&gt;
&lt;br /&gt;
rect   3   6 1080  63  [[OIAm_data_view|Data View]]&lt;br /&gt;
rect   3  81  428 412  [[Commons|Sector &amp;quot;Commons&amp;quot;]]&lt;br /&gt;
rect 437  81  863 412  [[Business Support|Sector &amp;quot;Business Support&amp;quot;]]&lt;br /&gt;
rect   3 423  863 640  [[Core|Sector &amp;quot;Core&amp;quot;]]&lt;br /&gt;
rect 872  81 1080 640  [[Operations|Sector &amp;quot;Operations&amp;quot;]]&lt;br /&gt;
&lt;br /&gt;
desc bottom-left&lt;br /&gt;
&amp;lt;/imagemap&amp;gt;&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=Infrastructure_Sector_Commons&amp;diff=1050</id>
		<title>Infrastructure Sector Commons</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=Infrastructure_Sector_Commons&amp;diff=1050"/>
		<updated>2015-04-19T21:07:31Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: handy redirect&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;#REDIRECT [[Commons]]&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=Infrastructure_Sector_Business_Support&amp;diff=1049</id>
		<title>Infrastructure Sector Business Support</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=Infrastructure_Sector_Business_Support&amp;diff=1049"/>
		<updated>2015-04-19T21:07:10Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: handy redirect&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;#REDIRECT [[Business Support]]&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=Infrastructure_Sector_Operations&amp;diff=1048</id>
		<title>Infrastructure Sector Operations</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=Infrastructure_Sector_Operations&amp;diff=1048"/>
		<updated>2015-04-19T21:06:43Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: handy redirect&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;#REDIRECT [[Operations]]&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=Operations&amp;diff=1047</id>
		<title>Operations</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=Operations&amp;diff=1047"/>
		<updated>2015-04-19T21:05:52Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: new sector&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Infrastructure Sector]]&lt;br /&gt;
Patterns that are part of this Infrastructure Sector provide functionality that is used mainly by IT support staff.&lt;br /&gt;
&lt;br /&gt;
{{Infrasector footer}}&lt;br /&gt;
&lt;br /&gt;
{{#set:Infrastructure Sector Color=E42419}}&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=Commons&amp;diff=1046</id>
		<title>Commons</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=Commons&amp;diff=1046"/>
		<updated>2015-04-19T21:05:11Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: Created page with &amp;quot;Category:Infrastructure Sector Patterns that are part of this Infrastructure Sector provide functionality that serve most all business users in the company.  {{Infrasector...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Infrastructure Sector]]&lt;br /&gt;
Patterns that are part of this Infrastructure Sector provide functionality that serve most all business users in the company.&lt;br /&gt;
&lt;br /&gt;
{{Infrasector footer}}&lt;br /&gt;
&lt;br /&gt;
{{#set:Infrastructure Sector Color=D88C02}}&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=Business_Support&amp;diff=1045</id>
		<title>Business Support</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=Business_Support&amp;diff=1045"/>
		<updated>2015-04-19T21:03:47Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: new sector&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Infrastructure Sector]]&lt;br /&gt;
Patterns that are part of this Infrastructure Sector provide functionality that is used mainly to support the Business in performing its core operations.&lt;br /&gt;
&lt;br /&gt;
{{Infrasector footer}}&lt;br /&gt;
&lt;br /&gt;
{{#set:Infrastructure Sector Colour=F2D13D}}&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=Infrastructure_Sector_Core&amp;diff=1044</id>
		<title>Infrastructure Sector Core</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=Infrastructure_Sector_Core&amp;diff=1044"/>
		<updated>2015-04-19T20:58:56Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: Jan Schoonderbeek moved page Infrastructure Sector Core to Core: Easier to rename page than adapt queries&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;#REDIRECT [[Core]]&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=Core&amp;diff=1043</id>
		<title>Core</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=Core&amp;diff=1043"/>
		<updated>2015-04-19T20:58:56Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: Jan Schoonderbeek moved page Infrastructure Sector Core to Core: Easier to rename page than adapt queries&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Infrastructure Sector]]&lt;br /&gt;
Patterns that are part of this Infrastructure Sector provide essential functionality. Many of the Patterns in this Sector can be found as adjacent Patterns for most other patterns.&lt;br /&gt;
&lt;br /&gt;
{{Infrasector footer}}&lt;br /&gt;
&lt;br /&gt;
{{#set:Infrastructure Sector Colour=6B5E4F}}&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=Template:Infrasector_footer/doc&amp;diff=1042</id>
		<title>Template:Infrasector footer/doc</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=Template:Infrasector_footer/doc&amp;diff=1042"/>
		<updated>2015-04-19T20:55:48Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: template documentation added&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Documentation subpage}}&lt;br /&gt;
&amp;lt;!-- PLEASE ADD CATEGORIES AND INTERWIKIS AT THE BOTTOM OF THIS PAGE --&amp;gt;&lt;br /&gt;
This template creates the footer for an Infrasector definition page.&lt;br /&gt;
&lt;br /&gt;
=== Usage ===&lt;br /&gt;
To use the template, cut and paste the following code at the end of an infrastructure sector page:&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;lt;nowiki&amp;gt;{{Infrasector footer}}&amp;lt;/nowiki&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;includeonly&amp;gt;&lt;br /&gt;
&amp;lt;!-- CATEGORIES AND INTERWIKIS HERE, THANKS --&amp;gt;&lt;br /&gt;
[[Category:Templates]]&lt;br /&gt;
&amp;lt;/includeonly&amp;gt;&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=Template:Infrasector_footer&amp;diff=1041</id>
		<title>Template:Infrasector footer</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=Template:Infrasector_footer&amp;diff=1041"/>
		<updated>2015-04-19T20:53:40Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: template for infrasector pages&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;includeonly&amp;gt;This Infrastructure Sector groups the following Generic Pattern:&lt;br /&gt;
{{#ask: [[Category:Generic Pattern]][[Belongs to infrastructure sector::{{PAGENAME}}]][[Page maturity::&amp;lt;9]]&lt;br /&gt;
|?Brief description|?Owner|?Page maturity}}&lt;br /&gt;
&lt;br /&gt;
This Infrastructure Sector groups the following Applied Pattern:&lt;br /&gt;
{{#ask: [[Category:Applied Pattern]][[Belongs to infrastructure sector::{{PAGENAME}}]][[Page maturity::&amp;lt;9]]&lt;br /&gt;
|?Brief description|?Owner|?Page maturity}}&amp;lt;/includeonly&amp;gt;&amp;lt;noinclude&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{documentation}}&lt;br /&gt;
&amp;lt;/noinclude&amp;gt;&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
	<entry>
		<id>https://www.infra-repository.org/oiar/index.php?title=Category:Infrastructure_Sector&amp;diff=1040</id>
		<title>Category:Infrastructure Sector</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar/index.php?title=Category:Infrastructure_Sector&amp;diff=1040"/>
		<updated>2015-04-19T20:48:27Z</updated>

		<summary type="html">&lt;p&gt;Jan Schoonderbeek: Category defined&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;An &amp;quot;Infrastructure sector&amp;quot; within OIAm indicates a grouping of patterns with similar meaning or roles in the infrastructure landscape. Note that we recognize that any form of grouping is debatable; nevertheless the grouping used by OIAm has proved useful for didactic purposes, as well as for taking inventory of existing landscapes.&lt;br /&gt;
&lt;br /&gt;
Currently we recognize the infrastructure sectors as indicated below.&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
</feed>