"Parsed text" is een vooraf gedefinieerde eigenschap. Deze eigenschap is van te voren gedefinieerd (ook bekend als een speciale eigenschap) en komt met extra beheersprivileges, maar kan worden gebruikt net als elk andere door de gebruiker gedefinieerde eigenschap.
T
TH WG SRP 40 +
TH WG SRP 41 +
TH WG SRP 43 +
De TOMP-API wordt ontwikkeld door een open source werkgroep genaamd Transport Operator, MaaS Provider - Working Group (TOMP-WG) bestaande uit publieke en private stakeholders, gericht op het faciliteren van de implementatie van MaaS en de bijbehorende gegevensuitwisseling. De TOMP-API beschrijft een volledige MaaS-journey, inclusief informatie over de operator, planning, boeking, ondersteuning, betalingen en reisuitvoering.
De TOMP-WG is een samenwerkingsinitiatief om een standaard API te creëren voor de technische communicatie tussen Transport Operators en MaaS Providers binnen het MaaS ecosysteem door middel van een API (Applicable Programming Interface). De API beschrijft hoe de verschillende stakeholders met elkaar moeten communiceren. +
Displays the tags, assuming that you on a page that has the CSP base properties. +
Taxonomieën bieden machine-geordende representaties in een formele structuur. Ze worden vaak gebruikt om de ontwikkeling van modellen voor machine learning te sturen, bijvoorbeeld door een reeks labels te verstrekken waarvoor geclassificeerd moet worden.
Een taxonomie vertegenwoordigt de formele structuur van klassen of soorten objecten binnen een domein. Taxonomieën:
volgen een hiërarchische indeling en geven namen voor elk object in relatie tot andere objecten.
kunnen ook de lidmaatschapseigenschappen van elk object in relatie tot andere objecten vastleggen.
hebben specifieke regels die gebruikt worden om elk object in een domein te classificeren of te categoriseren. Deze regels moeten volledig, consistent en ondubbelzinnig zijn.
moeten streng zijn in de specificatie, zodat elk nieuw ontdekt object in één en slechts één categorie of object past
erven alle eigenschappen van de klasse erboven, maar kunnen ook extra eigenschappen hebben.
Meer informatie over de term taxonomie kan hier gevonden worden. +
Template:Managed
{{Technologie properties
|Abstract= <text>
|Tags= <text>
}} +
Template:Managed
This is the Technologie sidebar template. It should be called in the following format:
{{Technologie sidebar }}
$base array is defined in MediaWiki:Ws-sub-header
$page array is defined in MediaWiki:Ws-sub-header +
<style>
/* #vloca_all { opacity: 0.7 } */
.vloca-frame:hover #vloca_all { filter: grayscale(100%); }
.vloca-layer > img { width: 700px; }
.vloca-layer { position: absolute; }
</style>
<script src=" https://code.jquery.com/jquery-3.6.0.min.js "
integrity="sha256-/xUj+3OJU5yExlq6GSYGSHk7tPXikynS7ogEvDej/m4="
crossorigin="anonymous"></script>
<img src="/imec_files/tech_donut/all.png" id="vloca_all" >
<img class="vloca-image" src="/imec_files/tech_donut/applications.png" id="vloca_applications">
<img class="vloca-image" src="/imec_files/tech_donut/network.png" id="vloca_network">
<img class="vloca-image" src="/imec_files/tech_donut/infrastructure.png" id="vloca_infrastructure">
<img class="vloca-image" src="/imec_files/tech_donut/monitoring.png" id="vloca_monitoring">
<img class="vloca-image" src="/imec_files/tech_donut/security.png" id="vloca_security">
<img class="vloca-image" src="/imec_files/tech_donut/devices.png" id="vloca_devices">
<img class="vloca-image" src="/imec_files/tech_donut/personal_data.png" id="vloca_personal">
<img class="vloca-image" src="/imec_files/tech_donut/iam.png" id="vloca_iam">
<img class="vloca-image" src="/imec_files/tech_donut/compute.png" id="vloca_compute">
<img class="vloca-image" src="/imec_files/tech_donut/process.png" id="vloca_process">
<img class="vloca-image" src="/imec_files/tech_donut/broker.png" id="vloca_broker">
<img class="vloca-image" src="/imec_files/tech_donut/service.png" id="vloca_service">
<img class="vloca-image" src="/imec_files/tech_donut/capture.png" id="vloca_capture">
<img class="vloca-image" src="/imec_files/tech_donut/storage.png" id="vloca_storage">
<img src="/imec_files/tech_donut/empty.png" usemap="#image-map">
<map name="image-map" id="image-map">
<area
href="Devices"
class="vloca_area"
id="devices"
coords="58,498,66,583,89,654,116,713,154,771,218,836,273,876,249,914,185,868,121,804,75,735,41,662,20,591,13,499"
shape="poly">
<area
href="Security"
class="vloca_area"
id="security"
coords="330,953,404,974,494,984,596,973,668,954,736,921,711,881,648,911,583,929,495,937,415,928,349,910,277,879,255,917"
shape="poly">
<area
href="Monitoring"
class="vloca_area"
id="monitoring"
coords="717,877,745,918,822,859,883,796,927,725,961,643,978,569,982,501,938,500,932,563,914,633,884,704,846,770,789,826"
shape="poly">
<area
href="Infrastructure"
class="vloca_area"
id="infrastructure"
coords="743,80,796,114,861,177,922,262,953,330,974,409,981,494,937,494,931,412,907,339,876,277,829,210,767,151,718,119"
shape="poly">
<area
href="Network & connectivity"
class="vloca_area"
id="network"
coords="258,77,280,116,340,86,414,67,490,58,565,64,638,83,712,115,738,75,653,37,571,17,486,13,401,22,325,44"
shape="poly">
<area
href="Applications"
class="vloca_area"
id="applications"
coords="252,79,273,117,219,156,164,210,116,283,86,347,66,409,57,491,13,490,23,404,42,332,75,259,128,180,189,124"
shape="poly">
<area
href="?curid=956"
class="vloca_area"
id="personal"
coords="313,647,339,674,372,699,274,863,235,838,194,801,162,770"
shape="poly">
<area
href="?curid=955"
class="vloca_area"
id="iam"
coords="380,703,408,716,441,727,401,917,357,902,311,884,278,869"
shape="poly">
<area
href="?curid=958"
class="vloca_area"
id="compute"
coords="449,730,525,736,599,715,647,686,688,644,716,595,732,550,919,586,905,639,883,693,843,756,784,820,716,868,641,902,569,922,485,928,405,916"
shape="poly">
<area
href="?curid=957"
class="vloca_area"
id="process"
coords="731,542,917,576,929,493,919,407,900,342,868,275,804,192,668,330,698,364,720,413,735,474"
shape="poly">
<area
href="?curid=960"
class="vloca_area"
id="broker"
coords="379,82,434,268,497,258,556,266,617,289,664,325,801,189,736,138,661,96,565,70,473,65"
shape="poly">
<area
href="?curid=959"
class="vloca_area"
id="service"
coords="370,87,427,271,382,289,349,313,316,341,294,375,124,280,177,207,262,136,312,108"
shape="poly">
<area
href="?curid=963"
class="vloca_area"
id="capture"
coords="124,285,286,380,263,441,256,497,264,554,279,599,309,642,159,763,116,697,82,615,68,518,68,436,89,357"
shape="poly">
<area
href="?curid=954"
class="vloca_area"
id="storage"
coords="499,496,225"
shape="circle">
</map>
<script type="text/javascript">
class ResponsiveImageMap {
constructor(map, oldWidth, newWidth) {
this.originalWidth = oldWidth;
this.newWidth = newWidth
this.areas = [];
for (const area of map.getElementsByTagName('area')) {
this.areas.push({
element: area,
originalCoords: area.coords.split(',')
});
}
window.addEventListener('resize', e => this.resize(e));
this.resize();
}
resize() {
const ratio = this.newWidth / this.originalWidth;
for (const area of this.areas) {
const newCoords = [];
for (const originalCoord of area.originalCoords) {
newCoords.push(Math.round(originalCoord * ratio));
}
area.element.coords = newCoords.join(',');
}
return true;
};
}
$(document).ready(function(){
$('.vloca-image').hide();
var map = document.getElementById('image-map');
new ResponsiveImageMap(map, 1000, 700);
$('.vloca_area').mouseover(function() {
$('#vloca_' + $(this)[0].id).fadeIn(200);
}).mouseout(function(){
$('#vloca_' + $(this)[0].id).fadeOut(100);
});
});
</script>
This is the "Add version history item" template. It should be called in the following format:
{{Add version history item
|Type= (value options: minor, major)
|Description= (text) note description might have comma's wrapped around it which should be filterd, e.g. ",Example description,"
}}
or
{{subst:Add version history item
|Type=major
|Description=Example description
}} +
This is the "Alert" template.
It should be called in the following format:
{{Alert
|yourmessagehere
|Text=orlikethis
|Type=danger/warning/info/success (default 'danger')
|Fa icon=default 'exclamation-triangle'
}} +
This is the Application page subheader template. It should be called in the following format:
{{Application page subheader
|$pageData= (Arrayfunctions export) slotdata of current page
|$classData= (Arrayfunctions export) class definition data (if current page and related class definition have a class in ws-base-props)
}} +
{{Base properties
|Class= (text)
|Title= (text)
|Is tag= (optional: true)
|Tags= (optional: comma-separated pages) for example "Tag/1, Tag/2, Tag/3"
|Version history= (multiple instance templates) {{Version history item |Version number=.. |Version description=.. |Version date=..}}
}} +
Note: Please be aware that this page originates from the Open CSP framework . Altering this page will result in difficulties down the line when updates are made to the framework. If you absolutely must alter this page, please consider copying this page to your own version and altering that, instead. For example: a template called 'Template:Foo' can be copied and pasted in a template called 'Template:Foobar'. Now you can reference this template without interrupting future upgrades to the framework. +
This is the "Class definition" template. It should be called in the following format:
{{Class definition
|Defines class= (text) value that is used for Class property in content pages of this type
|Pagetitle format= (value options: title, next_available) the wscreate in "Template:Create page form" will be based on this option, default "next_available"
|Allowed namespaces= (optional: comma-separted namespaces) namespaces in which pages of this class are allowed to be created, e.g. "(Main), Project, Article"
|Short description= (optional: text)
|Has version history= (optional: true) if true, then {{Show version history}} will be added to generated sidebar template code
layout settings (used to order chameleon components)
|Areas= (components) for example 'sidebar main'. Base csp components are: sidebar, sub-header, main
|Columns= (size attribute of components) for example: 15em 2fr
|Rows=
storage templates
|Base properties template= (optional: page) default "Template:Base properties"
|Page properties template (optional: page) default "Template:{{{Defines class|}}} properties"
component templates
|Sidebar template= (optional: page) default "Template:{{{Defines class|}}} sidebar"
|Sidebar form= (optional: page) no default
|Sub header template= (optional: page) no default
|Parameters= (multiple instance template)
{{Parameter definition
|...
|...
}}{{Parameter definition
|...
|...
}}
}}
Pagetitle formats:
title will result in a pagetitle with format Class/title-entered-by-user such as Organization/wikibase-solutions
next_available will result in a pagetitle with format Class/incremental_number such as Organization/1 Organization/2 Organization/3 etc.
Different Chameleon components can be ordered for different page classes
Base csp components are: sidebar, sub-header, main
They are defined in the Chameleon skin XML and the default values are set in layout.css
You can define different layouts on the Areas parameter, see grid-template-areas for syntax
You can define sizes for the columns and rows for this layout, see grid-template-columns and grid-template-rows for syntax
Example
The example below creates to rows on all pages with the Article class
The first row holds the Sidebar and the Sub-header components the Sidebar is set to be 15em wide and the Sub-header is set to 1 fraction, the hieght of this row is set to Auto
The second row holds the Main content component it spans over two columns the height of this row is set to 1 fraction
{{Class definition
|Defines class=Article
|Areas='sidebar sub-header' 'main main'
|Columns=15em 2fr
|Rows=auto 1fr
}}