Changes for page 13 Structure Mapping

Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 3 added, 0 removed)
  • 1750074822764-573.png
  • 1750074865924-797.png
  • 1750074994887-415.png

Details

Page properties

Content

...	...	@@ -311,58 +311,55 @@
311	311	Examples
312	312
313	313	22/06/1981 would be described as dd/MM/YYYY, with locale en-GB
314		-
315	315	2008-mars-12 would be described as YYYY-MMM-DD, with locale fr-FR
316		-
317	317	22 July 1981 would be described as dd MMMM YYYY, with locale en-US
318		-
319	319	22 Jul 1981 would be described as dd MMM YYYY
320		-
321	321	2010 D62 would be described as YYYYDnn (day 62 of the year 2010)
322	322
323	323	The following pattern letters are defined (all other characters from 'A' to 'Z' and from 'a' to 'z' are reserved):
324	324
325		-|Letter|Date or Time Component|Presentation|Examples
326		-|G|Era designator|[[Text>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#text]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#text]]|AD
327		-|yy|Year short (upper case is Year of Week{{footnote}}yyyy represents the calendar year while YYYY represents the year of the week, which is only relevant for 53 week years{{/footnote}})|[[Year>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#year]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#year]]|96
328		-|yyyy|Year Full (upper case is Year of Week)|Year|1996
329		-|MM|Month number in year starting with 1|Month|07
330		-|MMM|Month name short|Month|Jul
331		-|MMMM|Month name full|Month|July
332		-|ww|Week in year|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|27
333		-|W|Week in month|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|2
334		-|DD|Day in year|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|189
335		-|dd|Day in month|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|10
336		-|F|Day of week in month|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|2
337		-|E|Day name in week|[[Text>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#text]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#text]]|Tuesday; Tue
338		-|U|Day number of week (1 = Monday, ..., 7 = Sunday)|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|1
339		-|HH|Hour in day (0-23)|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|0
340		-|kk|Hour in day (1-24)|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|24
341		-|KK|Hour in am/pm (0-11)|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|0
342		-|hh|Hour in am/pm (1-12)|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|12
343		-|mm|Minute in hour|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|30
344		-|ss|Second in minute|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|55
345		-|S|Millisecond|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|978
346		-|n|(((
	321	+(% style="width:850.294px" %)
	322	+|(% style="width:125px" %)**Letter**|(% style="width:385px" %)**Date or Time Component**|(% style="width:180px" %)**Presentation**|(% style="width:157px" %)**Examples**
	323	+|(% style="width:125px" %)G|(% style="width:385px" %)Era designator|(% style="width:180px" %)Text|(% style="width:157px" %)AD
	324	+|(% style="width:125px" %)yy|(% style="width:385px" %)Year short (upper case is Year of Week{{footnote}}yyyy represents the calendar year while YYYY represents the year of the week, which is only relevant for 53 week years{{/footnote}})|(% style="width:180px" %)Year|(% style="width:157px" %)96
	325	+|(% style="width:125px" %)yyyy|(% style="width:385px" %)Year Full (upper case is Year of Week)|(% style="width:180px" %)Year|(% style="width:157px" %)1996
	326	+|(% style="width:125px" %)MM|(% style="width:385px" %)Month number in year starting with 1|(% style="width:180px" %)Month|(% style="width:157px" %)07
	327	+|(% style="width:125px" %)MMM|(% style="width:385px" %)Month name short|(% style="width:180px" %)Month|(% style="width:157px" %)Jul
	328	+|(% style="width:125px" %)MMMM|(% style="width:385px" %)Month name full|(% style="width:180px" %)Month|(% style="width:157px" %)July
	329	+|(% style="width:125px" %)ww|(% style="width:385px" %)Week in year|(% style="width:180px" %)Number|(% style="width:157px" %)27
	330	+|(% style="width:125px" %)W|(% style="width:385px" %)Week in month|(% style="width:180px" %)Number|(% style="width:157px" %)2
	331	+|(% style="width:125px" %)DD|(% style="width:385px" %)Day in year|(% style="width:180px" %)Number|(% style="width:157px" %)189
	332	+|(% style="width:125px" %)dd|(% style="width:385px" %)Day in month|(% style="width:180px" %)Number|(% style="width:157px" %)10
	333	+|(% style="width:125px" %)F|(% style="width:385px" %)Day of week in month|(% style="width:180px" %)Number|(% style="width:157px" %)2
	334	+|(% style="width:125px" %)E|(% style="width:385px" %)Day name in week|(% style="width:180px" %)Text|(% style="width:157px" %)Tuesday; Tue
	335	+|(% style="width:125px" %)U|(% style="width:385px" %)Day number of week (1 = Monday, ..., 7 = Sunday)|(% style="width:180px" %)Number|(% style="width:157px" %)1
	336	+|(% style="width:125px" %)HH|(% style="width:385px" %)Hour in day (0-23)|(% style="width:180px" %)Number|(% style="width:157px" %)0
	337	+|(% style="width:125px" %)kk|(% style="width:385px" %)Hour in day (1-24)|(% style="width:180px" %)Number|(% style="width:157px" %)24
	338	+|(% style="width:125px" %)KK|(% style="width:385px" %)Hour in am/pm (0-11)|(% style="width:180px" %)Number|(% style="width:157px" %)0
	339	+|(% style="width:125px" %)hh|(% style="width:385px" %)Hour in am/pm (1-12)|(% style="width:180px" %)Number|(% style="width:157px" %)12
	340	+|(% style="width:125px" %)mm|(% style="width:385px" %)Minute in hour|(% style="width:180px" %)Number|(% style="width:157px" %)30
	341	+|(% style="width:125px" %)ss|(% style="width:385px" %)Second in minute|(% style="width:180px" %)Number|(% style="width:157px" %)55
	342	+|(% style="width:125px" %)S|(% style="width:385px" %)Millisecond|(% style="width:180px" %)Number|(% style="width:157px" %)978
	343	+|(% style="width:125px" %)n|(% style="width:385px" %)(((
347	347	Number of periods, used after a SDMX
348		-
349	349	Frequency Identifier such as M, Q, D (month, quarter, day)
350		-)))|[[Number>>url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]][[url:https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#number]]|12
	346	+)))|(% style="width:180px" %)Number|(% style="width:157px" %)12
351	351
352	352	The model is illustrated below:
353	353
	350	+[[image:1750074822764-573.png]]
354	354
355		-
356	356	**Figure 24 showing the component map mapping the SOURCE_DATE Dimension to the TIME_PERIOD dimension with the additional information on the component map to describe the time format?**
357	357
	354	+[[image:1750074865924-797.png]]
358	358
	356	+(% class="wikigeneratedid" id="HFigure25showinganinputdateformat2CwhoseoutputfrequencyisderivedfromtheoutputvalueoftheFREQDimension" %)
	357	+**Figure 25 showing an input date format, whose output frequency is derived from the output value of the FREQ Dimension**
359	359
360		-==== Figure 25 showing an input date format, whose output frequency is derived from the output value of the FREQ Dimension ====
	359	+=== 13.7.2 Numerical based datetime ===
361	361
362		-=== 13.3.6 Numerical based datetime ===
	361	+Where the source datetime input is purely numerical, the mapping rules are defined by the **Base** as a valid [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[Time Period>>doc:sdmx:Glossary.Time period.WebHome]], and the **Period** which must take one of the following enumerated values:
363	363
364		-Where the source datetime input is purely numerical, the mapping rules are defined by the **Base** as a valid SDMX Time Period, and the **Period** which must take one of the following enumerated values:
365		-
366	366	* day
367	367	* second
368	368	* millisecond
...	...	@@ -369,75 +369,63 @@
369	369	* microsecond
370	370	* nanosecond
371	371
372		-|Numerical datetime systems|Base|Period
373		-|(((
	369	+(% style="width:545.294px" %)
	370	+|(% style="width:268px" %)Numerical datetime systems|(% style="width:121px" %)Base|(% style="width:153px" %)Period
	371	+|(% style="width:268px" %)(((
374	374	Epoch Time (UNIX)
375		-
376	376	Milliseconds since 01 Jan 1970
377		-)))|1970|millisecond
378		-|(((
	374	+)))|(% style="width:121px" %)1970|(% style="width:153px" %)millisecond
	375	+|(% style="width:268px" %)(((
379	379	Windows System Time
380		-
381	381	Milliseconds since 01 Jan 1601
382		-)))|1601|millisecond
	378	+)))|(% style="width:121px" %)1601|(% style="width:153px" %)millisecond
383	383
384	384	The example above illustrates numerical based datetime mapping rules for two commonly used time standards.
385	385
386	386	The model is illustrated below:
387	387
388		-[[image:1750072341491-790.jpeg]]
	384	+[[image:1750074994887-415.png]]
389	389
390		-**Figure 26 showing the component map mapping the SOURCE_DATE Dimension to the**
	386	+**Figure 26 showing the component map mapping the SOURCE_DATE Dimension to the TIME_PERIOD Dimension with the additional information on the component map to describe the numerical datetime system in use **
391	391
392		-==== TIME_PERIOD Dimension with the additional information on the component map to describe the numerical datetime system in use ====
	388	+=== 13.7.3 Mapping more complex time inputs ===
393	393
394		-=== Mapping more complex time inputs ===
	390	+[[VTL>>doc:sdmx:Glossary.Validation and transformation language.WebHome]] should be used for more complex time inputs that cannot be interpreted using the pattern based on numerical methods.
395	395
396		-VTL should be used for more complex time inputs that cannot be interpreted using the pattern based on numerical methods.
	392	+== 13.8 Using TIME_PERIOD in mapping rules ==
397	397
398		-== Using TIME_PERIOD in mapping rules ==
	394	+The source TIME_PERIOD [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] can be used in conjunction with other input [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] to create discrete mapping rules where the output is conditional on the [[time period>>doc:sdmx:Glossary.Time period.WebHome]] value.
399	399
400		-The source TIME_PERIOD Dimension can be used in conjunction with other input Dimensions to create discrete mapping rules where the output is conditional on the time period value.
	396	+The main use case is setting the value of Observation [[Attributes>>doc:sdmx:Glossary.Attribute.WebHome]] in the target [[dataset>>doc:sdmx:Glossary.Data set.WebHome]].
401	401
402		-The main use case is setting the value of Observation Attributes in the target dataset.
403		-
404		-|Rule|Source|Target
405		-|1|(((
	398	+(% style="width:709.294px" %)
	399	+|(% style="width:103px" %)**Rule**|(% style="width:405px" %)**Source**|(% style="width:198px" %)**Target**
	400	+|(% style="width:103px" %)1|(% style="width:405px" %)(((
406	406	If
407		-
408	408	INDICATOR=XULADS; and TIME_PERIOD=2007.
409		-)))|(((
410		-Set
411		-
412		-OBS_CONF=F
	403	+)))|(% style="width:198px" %)(((
	404	+Set OBS_CONF=F
413	413	)))
414		-|2|(((
	406	+|(% style="width:103px" %)2|(% style="width:405px" %)(((
415	415	If
416		-
417	417	INDICATOR=XULADS; and TIME_PERIOD=2008.
418		-)))|Set OBS_CONF=F
419		-|3|(((
	409	+)))|(% style="width:198px" %)Set OBS_CONF=F
	410	+|(% style="width:103px" %)3|(% style="width:405px" %)(((
420	420	If
421		-
422	422	INDICATOR=XULADS; and TIME_PERIOD=2009.
423		-)))|(((
424		-Set
425		-
426		-OBS_CONF=F
	413	+)))|(% style="width:198px" %)(((
	414	+Set OBS_CONF=F
427	427	)))
428		-|4|(((
	416	+|(% style="width:103px" %)4|(% style="width:405px" %)(((
429	429	If
430		-
431	431	INDICATOR=XULADS; and TIME_PERIOD=2010.
432		-)))|(((
433		-Set
434		-
435		-OBS_CONF=**C**
	419	+)))|(% style="width:198px" %)(((
	420	+Set OBS_CONF=**C**
436	436	)))
437	437
438		-In the example above, OBS_CONF is an Observation Attribute.
	423	+In the example above, OBS_CONF is an Observation [[Attribute>>doc:sdmx:Glossary.Attribute.WebHome]].
439	439
440		-== 13. Time span mapping rules using validity periods ==
	425	+== 13.9 Time span mapping rules using validity periods ==
441	441
442	442	Creating discrete mapping rules for each TIME_PERIOD is impractical where rules need to cover a specific span of time regardless of frequency, and for high-frequency data.
443	443
...	...	@@ -445,25 +445,22 @@
445	445
446	446	By specifying validity periods, the example from Section 13.8 can be re-written using two rules as follows:
447	447
448		-|Rule|Source|Target
449		-|1|(((
	433	+(% style="width:516.294px" %)
	434	+|(% style="width:74px" %)Rule|(% style="width:215px" %)Source|(% style="width:223px" %)Target
	435	+|(% style="width:74px" %)1|(% style="width:215px" %)(((
450	450	If
451		-
452	452	INDICATOR=XULADS.
453		-
454		-
455		-Validity Period start period=2007 end period=2009
456		-)))|Set OBS_CONF=F
457		-|2|(((
	438	+Validity Period
	439	+start period=2007
	440	+end period=2009
	441	+)))|(% style="width:223px" %)Set OBS_CONF=F
	442	+|(% style="width:74px" %)2|(% style="width:215px" %)(((
458	458	If
459		-
460	460	INDICATOR=XULADS.
461		-
462		-
463		-Validity Period start period=2010
464		-)))|(((
	445	+Validity Period
	446	+start period=2010
	447	+)))|(% style="width:223px" %)(((
465	465	Set
466		-
467	467	OBS_CONF=F
468	468	)))
469	469
...	...	@@ -471,70 +471,61 @@
471	471
472	472	In Rule 2, no end period is specified so remains in effect from the start of the period (2010-01-01T00:00:00) until the end of time. Any observations reporting data for the Indicator XULADS that fall into that time range will have an OBS_CONF value of C.
473	473
474		-== 13. Mapping examples ==
	456	+In Rule 2, no end period is specified so remains in effect from the start of the period (2010-01-01T00:00:00) until the end of time. Any observations reporting data for the Indicator XULADS that fall into that time range will have an OBS_CONF value of C.
475	475
476		-=== 13. Many to one mapping (N-1) ===
	458	+== 13.10 Mapping examples ==
477	477
478		-|Source|Map To
479		-|(((
480		-**FREQ**="A"
	460	+=== 13.10.1 Many to one mapping (N3513 -1) ===
481	481
	462	+(% style="width:542.294px" %)
	463	+|(% style="width:274px" %)**Source**|(% style="width:265px" %)**Map To**
	464	+|(% style="width:274px" %)(((
	465	+(% style="color:#8e44ad" %)**FREQ**="A"
482	482	ADJUSTMENT="N"
483		-
484	484	**REF_AREA**="PL"
485		-
486	486	**COUNTERPART_AREA**="W0"
487		-
488	488	REF_SECTOR="S1"
489		-
490	490	COUNTERPART_SECTOR="S1"
491		-
492	492	ACCOUNTING_ENTRY="B"
493		-
494	494	STO="B5G"
495		-)))|(((
496		-FREQ="A"
497		-
	473	+)))|(% style="width:265px" %)(((
	474	+(% style="color:#8e44ad" %)FREQ="A"
498	498	REF_AREA="PL"
499		-
500	500	COUNTERPART_AREA="W0"
501		-INDICATOR="IND_ABC"
	477	+INDICATOR="IND_ABC"(%%)
502	502
503	503	)))
504	504
505		-The bold Dimensions map from source to target verbatim. The mapping simply specifies:
	481	+The bold [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] (% style="color:#e74c3c" %)map(%%) from source to target verbatim. The mapping simply specifies:
506	506
507		-FREQ => FREQ
	483	+> FREQ => FREQ
	484	+> REF_AREA=> REF_AREA
	485	+> COUNTERPART_AREA=> COUNTERPART _AREA
508	508
509		-REF_AREA=> REF_AREA
	487	+No [[Representation>>doc:sdmx:Glossary.Representation.WebHome]] Mapping is required. The source value simply copies across unmodified.
510	510
511		-COUNTERPART_AREA=> COUNTERPART _AREA
	489	+The remaining [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] all (% style="color:#e74c3c" %)map(%%) to the Indicator [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]]. This is an example of many [[Dimensions>>doc:sdmx:Glossary.Dimension.WebHome]] mapping to one [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]]. In this case a [[Representation>>doc:sdmx:Glossary.Representation.WebHome]] Mapping is required, and the mapping first describes the input 'partial key' and how this (% style="color:#e74c3c" %)maps(%%) to the target indicator:
512	512
513		-No Representation Mapping is required. The source value simply copies across unmodified.
	491	+> N:S1:S1:B:B5G => IND_ABC
514	514
515		-The remaining Dimensions all map to the Indicator Dimension. This is an example of many Dimensions mapping to one Dimension. In this case a Representation Mapping is required, and the mapping first describes the input 'partial key' and how this maps to the target indicator:
	493	+Where the key sequence is based on the order specified in the (% style="color:#e74c3c" %)mapping(%%) (i.e [[ADJUSTMENT>>doc:sdmx:Glossary.Adjustment.WebHome]], REF_SECTOR, etc will result in the first value N being taken from [[ADJUSTMENT>>doc:sdmx:Glossary.Adjustment.WebHome]] as this was the first item in the source [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] list.
516	516
517		-N:S1:S1:B:B5G => IND_ABC
	495	+**Note**: The key order is NOT based on the [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] order of the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]], as the (% style="color:#e74c3c" %)mapping(%%) needs to be resilient to the [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] changing.
518	518
519		-Where the key sequence is based on the order specified in the mapping (i.e ADJUSTMENT, REF_SECTOR, etc will result in the first value N being taken from ADJUSTMENT as this was the first item in the source Dimension list.
	497	+=== 13.10.2 Mapping other data types to Code Id ===
520	520
521		-**Note**: The key order is NOT based on the Dimension order of the DSD, as the mapping needs to be resilient to the DSD changing.
	499	+In the case where the incoming data type is not a string and not a [[code>>doc:sdmx:Glossary.Code.WebHome]] identifier i.e. the source [[Dimension>>doc:sdmx:Glossary.Dimension.WebHome]] is of type Integer and the target is Codelist. This is supported by the RepresentationMap. The RepresentationMap source can reference a Codelist, Valuelist, or be free text, the free text can include regular expressions.
522	522
523		-1.
524		-11.
525		-111. Mapping other data types to Code Id
	501	+The following [[representation>>doc:sdmx:Glossary.Representation.WebHome]] (% style="color:#e74c3c" %)mapping(%%) can be used to explicitly (% style="color:#e74c3c" %)map(%%) each [[age>>doc:sdmx:Glossary.Age.WebHome]] to an output [[code>>doc:sdmx:Glossary.Code.WebHome]].
526	526
527		-In the case where the incoming data type is not a string and not a code identifier i.e. the source Dimension is of type Integer and the target is Codelist. This is supported by the RepresentationMap. The RepresentationMap source can reference a Codelist, Valuelist, or be free text, the free text can include regular expressions.
	503	+(% style="width:402.294px" %)
	504	+|(% style="width:188px" %)**Source Input Free Text**|(% style="width:211px" %)**Desired Output Code Id**
	505	+|(% style="width:188px" %)0|(% style="width:211px" %)A
	506	+|(% style="width:188px" %)1|(% style="width:211px" %)A
	507	+|(% style="width:188px" %)2|(% style="width:211px" %)A
	508	+|(% style="width:188px" %)3|(% style="width:211px" %)B
	509	+|(% style="width:188px" %)4|(% style="width:211px" %)B
528	528
529		-The following representation mapping can be used to explicitly map each age to an output code.
530		-
531		-|Source Input Free Text|Desired Output Code Id
532		-|0|A
533		-|1|A
534		-|2|A
535		-|3|B
536		-|4|B
537		-
538	538	If this mapping takes advantage of regular expressions it can be expressed in two rules:
539	539
540	540

1750074822764-573.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+xwiki:XWiki.helena

Size

...	...	@@ -1,0 +1,1 @@
	1	+25.1 KB

Content

1750074865924-797.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+xwiki:XWiki.helena

Size

...	...	@@ -1,0 +1,1 @@
	1	+46.8 KB

Content

1750074994887-415.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+xwiki:XWiki.helena

Size

...	...	@@ -1,0 +1,1 @@
	1	+12.4 KB

Content