Home » railML newsgroups » railml.misc » Some hints for changes in railwayBaseTypes.xsd
Some hints for changes in railwayBaseTypes.xsd [message #1088] Mon, 23 August 2010 22:10 Go to next message
Carsten Weber is currently offline  Carsten Weber
Messages: 26
Registered: November 2011
Junior Member
Dear RailML-Users,

by implementing RailML-Interface to a vehicle data program I thought some
changes would be helpful:

- The enumeration tTrainProtectionMedium should also include the
value="electric".
This value might be usefull to describe the French "crocodile"-system or
would you use another value of the existing?

- I think it is useful to add the following part:

< !--********************************************************* -- >

<!-- trackGauges for gauge changing axles -->

< !--********************************************************* -- >

<xs:complexType name="tTrackGauge">

<xs:attribute name="trackGauge" type="rail:tLengthMM"/>

</xs:complexType>

This makes it possible to show all possible gauges for gauge changing
vehicles. I know, that there is a way shown by two different values inside
the vehicle.


- The attribute named "count" inside the attribute group aPlaces should
change his type to nonNegativeInteger to differ between known values by zero
and unknown values by a not existing entry inside the list of places.

- The attributeGroup "aService" should be extended by an attribute "count".
Here it can be a tCounter-type.

- Here is also a list of my suggestions for tNationalSystemsType of train
protection systems:

<xs:enumeration value="ALSEN"/>

<xs:enumeration value="ALSN"/>

<xs:enumeration value="ASFA"/>

<xs:enumeration value="ATB"/>

<xs:enumeration value="ATBEG"/>

<xs:enumeration value="ATBEN"/>

<xs:enumeration value="ATC"/>

<xs:enumeration value="ATSP"/>

<xs:enumeration value="AWS"/>

<xs:enumeration value="BACC"/>

<xs:enumeration value="CIR-ELKE"/>

<xs:enumeration value="CIR-ELKE2"/>

<xs:enumeration value="Crocodile"/>

<xs:enumeration value="CSS"/>

<xs:enumeration value="DATC"/>

<xs:enumeration value="EBICAB"/>

<xs:enumeration value="EVM120"/>

<xs:enumeration value="Fahrsp"/>

<xs:enumeration value="GWATP"/>

<xs:enumeration value="Indusi54"/>

<xs:enumeration value="Indusi60"/>

<xs:enumeration value="Indusi60R"/>

<xs:enumeration value="Integra-Signum"/>

<xs:enumeration value="KHP"/>

<xs:enumeration value="KLUBU"/>

<xs:enumeration value="KVB"/>

<xs:enumeration value="LS"/>

<xs:enumeration value="LS90"/>

<xs:enumeration value="LZB"/>

<xs:enumeration value="Memor"/>

<xs:enumeration value="Mirel"/>

<xs:enumeration value="PZ80"/>

<xs:enumeration value="PZB90"/>

<xs:enumeration value="RS4c"/>

<xs:enumeration value="SAUTC"/>

<xs:enumeration value="SAUTCM"/>

<xs:enumeration value="SAUTU"/>

<xs:enumeration value="SCMT"/>

<xs:enumeration value="SELCAB"/>

<xs:enumeration value="SHP"/>

<xs:enumeration value="SSC"/>

<xs:enumeration value="TBL"/>

<xs:enumeration value="TPWS"/>

<xs:enumeration value="TVM300"/>

<xs:enumeration value="TVM400"/>

<xs:enumeration value="TVM430"/>

<xs:enumeration value="ZSL90"/>

<xs:enumeration value="ZUB121"/>

<xs:enumeration value="ZUB122"/>

<xs:enumeration value="ZUB123"/>

<xs:enumeration value="ZUB262"/>



Please do not hesitate to ask me, if there are any questions about my
remarks.

Kind regards



Carsten Weber
Re: Some hints for changes in railwayBaseTypes.xsd [message #1089 is a reply to message #1088] Mon, 30 August 2010 18:32 Go to previous messageGo to next message
Joerg von Lingen is currently offline  Joerg von Lingen
Messages: 59
Registered: May 2011
Member
Find my remarks below.

Regards
Jörg von Lingen.

On 23.08.2010 22:10, Carsten Weber wrote:
> Dear RailML-Users,
>
> by implementing RailML-Interface to a vehicle data program I thought some
> changes would be helpful:
>
> - The enumeration tTrainProtectionMedium should also include the
> value="electric".
> This value might be usefull to describe the French "crocodile"-system or
> would you use another value of the existing?
>
added [299]

> - I think it is useful to add the following part:
>
> < !--********************************************************* -- >
>
> <!-- trackGauges for gauge changing axles -->
>
> < !--********************************************************* -- >
>
> <xs:complexType name="tTrackGauge">
>
> <xs:attribute name="trackGauge" type="rail:tLengthMM"/>
>
> </xs:complexType>
>
> This makes it possible to show all possible gauges for gauge changing
> vehicles. I know, that there is a way shown by two different values inside
> the vehicle.
>
>
> - The attribute named "count" inside the attribute group aPlaces should
> change his type to nonNegativeInteger to differ between known values by zero
> and unknown values by a not existing entry inside the list of places.
Why not changing tCounter completely to nonNegativeInteger?

>
> - The attributeGroup "aService" should be extended by an attribute "count".
> Here it can be a tCounter-type.
Is already included.

>
> - Here is also a list of my suggestions for tNationalSystemsType of train
> protection systems:
>
> <xs:enumeration value="ALSEN"/>
>
> <xs:enumeration value="ALSN"/>
>
> <xs:enumeration value="ASFA"/>
>
> <xs:enumeration value="ATB"/>
>
> <xs:enumeration value="ATBEG"/>
>
> <xs:enumeration value="ATBEN"/>
>
> <xs:enumeration value="ATC"/>
>
> <xs:enumeration value="ATSP"/>
>
> <xs:enumeration value="AWS"/>
>
> <xs:enumeration value="BACC"/>
>
> <xs:enumeration value="CIR-ELKE"/>
>
> <xs:enumeration value="CIR-ELKE2"/>
>
> <xs:enumeration value="Crocodile"/>
>
> <xs:enumeration value="CSS"/>
>
> <xs:enumeration value="DATC"/>
>
> <xs:enumeration value="EBICAB"/>
>
> <xs:enumeration value="EVM120"/>
>
> <xs:enumeration value="Fahrsp"/>
>
> <xs:enumeration value="GWATP"/>
>
> <xs:enumeration value="Indusi54"/>
>
> <xs:enumeration value="Indusi60"/>
>
> <xs:enumeration value="Indusi60R"/>
>
> <xs:enumeration value="Integra-Signum"/>
>
> <xs:enumeration value="KHP"/>
>
> <xs:enumeration value="KLUBU"/>
>
> <xs:enumeration value="KVB"/>
>
> <xs:enumeration value="LS"/>
>
> <xs:enumeration value="LS90"/>
>
> <xs:enumeration value="LZB"/>
>
> <xs:enumeration value="Memor"/>
>
> <xs:enumeration value="Mirel"/>
>
> <xs:enumeration value="PZ80"/>
>
> <xs:enumeration value="PZB90"/>
>
> <xs:enumeration value="RS4c"/>
>
> <xs:enumeration value="SAUTC"/>
>
> <xs:enumeration value="SAUTCM"/>
>
> <xs:enumeration value="SAUTU"/>
>
> <xs:enumeration value="SCMT"/>
>
> <xs:enumeration value="SELCAB"/>
>
> <xs:enumeration value="SHP"/>
>
> <xs:enumeration value="SSC"/>
>
> <xs:enumeration value="TBL"/>
>
> <xs:enumeration value="TPWS"/>
>
> <xs:enumeration value="TVM300"/>
>
> <xs:enumeration value="TVM400"/>
>
> <xs:enumeration value="TVM430"/>
>
> <xs:enumeration value="ZSL90"/>
>
> <xs:enumeration value="ZUB121"/>
>
> <xs:enumeration value="ZUB122"/>
>
> <xs:enumeration value="ZUB123"/>
>
> <xs:enumeration value="ZUB262"/>
Some of them already included.

>
>
>
> Please do not hesitate to ask me, if there are any questions about my
> remarks.
>
> Kind regards
>
>
>
> Carsten Weber
>
>


--
Mit freundlichen Grüßen/Best regards,
-------------------------------------
Jörg von Lingen
Re: Some hints for changes in railwayBaseTypes.xsd [message #1090 is a reply to message #1088] Mon, 30 August 2010 18:56 Go to previous messageGo to next message
Joerg von Lingen is currently offline  Joerg von Lingen
Messages: 59
Registered: May 2011
Member
Hello,

the following values for tNationalSystemsType are new and may need some short
description for explanation (full name, area of use, short description)

<xs:enumeration value="ALSEN" />
<xs:enumeration value="ATBEG" />
<xs:enumeration value="ATBEN" />
<xs:enumeration value="ATSP" />
<xs:enumeration value="BACC" />
<xs:enumeration value="CIR-ELKE2" />
<xs:enumeration value="CSS" />
<xs:enumeration value="DATC" />
<xs:enumeration value="Fahrsp" />
<xs:enumeration value="GWATP" />
<xs:enumeration value="Indusi60" />
<xs:enumeration value="KHP" />
<xs:enumeration value="KLUBU" />
<xs:enumeration value="LS" />
<xs:enumeration value="SAUTC" />
<xs:enumeration value="SAUTCM" />
<xs:enumeration value="SAUTU" />
<xs:enumeration value="TVM400" />
<xs:enumeration value="ZSL90" />
<xs:enumeration value="ZUB123" />
<xs:enumeration value="ZUB262" />

Thanks,
Jörg von Lingen

On 23.08.2010 22:10, Carsten Weber wrote:
> Dear RailML-Users,
>
> by implementing RailML-Interface to a vehicle data program I thought some
> changes would be helpful:
>
> - The enumeration tTrainProtectionMedium should also include the
> value="electric".
> This value might be usefull to describe the French "crocodile"-system or
> would you use another value of the existing?
>
> - I think it is useful to add the following part:
>
> < !--********************************************************* -- >
>
> <!-- trackGauges for gauge changing axles -->
>
> < !--********************************************************* -- >
>
> <xs:complexType name="tTrackGauge">
>
> <xs:attribute name="trackGauge" type="rail:tLengthMM"/>
>
> </xs:complexType>
>
> This makes it possible to show all possible gauges for gauge changing
> vehicles. I know, that there is a way shown by two different values inside
> the vehicle.
>
>
> - The attribute named "count" inside the attribute group aPlaces should
> change his type to nonNegativeInteger to differ between known values by zero
> and unknown values by a not existing entry inside the list of places.
>
> - The attributeGroup "aService" should be extended by an attribute "count".
> Here it can be a tCounter-type.
>
> - Here is also a list of my suggestions for tNationalSystemsType of train
> protection systems:
>
> <xs:enumeration value="ALSEN"/>
>
> <xs:enumeration value="ALSN"/>
>
> <xs:enumeration value="ASFA"/>
>
> <xs:enumeration value="ATB"/>
>
> <xs:enumeration value="ATBEG"/>
>
> <xs:enumeration value="ATBEN"/>
>
> <xs:enumeration value="ATC"/>
>
> <xs:enumeration value="ATSP"/>
>
> <xs:enumeration value="AWS"/>
>
> <xs:enumeration value="BACC"/>
>
> <xs:enumeration value="CIR-ELKE"/>
>
> <xs:enumeration value="CIR-ELKE2"/>
>
> <xs:enumeration value="Crocodile"/>
>
> <xs:enumeration value="CSS"/>
>
> <xs:enumeration value="DATC"/>
>
> <xs:enumeration value="EBICAB"/>
>
> <xs:enumeration value="EVM120"/>
>
> <xs:enumeration value="Fahrsp"/>
>
> <xs:enumeration value="GWATP"/>
>
> <xs:enumeration value="Indusi54"/>
>
> <xs:enumeration value="Indusi60"/>
>
> <xs:enumeration value="Indusi60R"/>
>
> <xs:enumeration value="Integra-Signum"/>
>
> <xs:enumeration value="KHP"/>
>
> <xs:enumeration value="KLUBU"/>
>
> <xs:enumeration value="KVB"/>
>
> <xs:enumeration value="LS"/>
>
> <xs:enumeration value="LS90"/>
>
> <xs:enumeration value="LZB"/>
>
> <xs:enumeration value="Memor"/>
>
> <xs:enumeration value="Mirel"/>
>
> <xs:enumeration value="PZ80"/>
>
> <xs:enumeration value="PZB90"/>
>
> <xs:enumeration value="RS4c"/>
>
> <xs:enumeration value="SAUTC"/>
>
> <xs:enumeration value="SAUTCM"/>
>
> <xs:enumeration value="SAUTU"/>
>
> <xs:enumeration value="SCMT"/>
>
> <xs:enumeration value="SELCAB"/>
>
> <xs:enumeration value="SHP"/>
>
> <xs:enumeration value="SSC"/>
>
> <xs:enumeration value="TBL"/>
>
> <xs:enumeration value="TPWS"/>
>
> <xs:enumeration value="TVM300"/>
>
> <xs:enumeration value="TVM400"/>
>
> <xs:enumeration value="TVM430"/>
>
> <xs:enumeration value="ZSL90"/>
>
> <xs:enumeration value="ZUB121"/>
>
> <xs:enumeration value="ZUB122"/>
>
> <xs:enumeration value="ZUB123"/>
>
> <xs:enumeration value="ZUB262"/>
>
>
>
> Please do not hesitate to ask me, if there are any questions about my
> remarks.
>
> Kind regards
>
>
>
> Carsten Weber
>
>


--
Mit freundlichen Grüßen/Best regards,
-------------------------------------
Jörg von Lingen
Re: Some hints for changes in railwayBaseTypes.xsd [message #1091 is a reply to message #1089] Mon, 30 August 2010 21:15 Go to previous messageGo to next message
Carsten Weber is currently offline  Carsten Weber
Messages: 26
Registered: November 2011
Junior Member
I added my remarks below too.

Regards

Carsten Weber

"Joerg von Lingen" <joergvon_lingendd(at)t-onlinede> schrieb im Newsbeitrag
news:i5g58d$1uc$1(at)sifaivifhgde...
> Find my remarks below.
>
> Regards
> Jrg von Lingen.
>
> On 23.08.2010 22:10, Carsten Weber wrote:
>> Dear RailML-Users,
>>
>> by implementing RailML-Interface to a vehicle data program I thought some
>> changes would be helpful:
>>
>> - The enumeration tTrainProtectionMedium should also include the
>> value="electric".
>> This value might be usefull to describe the French "crocodile"-system or
>> would you use another value of the existing?
>>
> added [299]
>
Thanks.

>> - I think it is useful to add the following part:
>>
>> < !--********************************************************* -- >
>>
>> <!-- trackGauges for gauge changing axles -->
>>
>> < !--********************************************************* -- >
>>
>> <xs:complexType name="tTrackGauge">
>>
>> <xs:attribute name="trackGauge" type="rail:tLengthMM"/>
>>
>> </xs:complexType>
>>
>> This makes it possible to show all possible gauges for gauge changing
>> vehicles. I know, that there is a way shown by two different values
>> inside
>> the vehicle.
>>
>>
>> - The attribute named "count" inside the attribute group aPlaces should
>> change his type to nonNegativeInteger to differ between known values by
>> zero
>> and unknown values by a not existing entry inside the list of places.
> Why not changing tCounter completely to nonNegativeInteger?
>
This is also a solution, but I'm not sure which elements refer to tCounter
and might be in trouble by value zero.
Re: Some hints for changes in railwayBaseTypes.xsd [message #1092 is a reply to message #1090] Mon, 30 August 2010 21:55 Go to previous messageGo to next message
Carsten Weber is currently offline  Carsten Weber
Messages: 26
Registered: November 2011
Junior Member
Hello,

I think it would be the best if I would fill in these systems and some
additional information into the railml wiki.

Best regards.
Carsten Weber

"Joerg von Lingen" <joergvon_lingendd(at)t-onlinede> schrieb im Newsbeitrag
news:i5g6ka$1vu$1(at)sifaivifhgde...
> Hello,
>
> the following values for tNationalSystemsType are new and may need some
> short
> description for explanation (full name, area of use, short description)
>
> <xs:enumeration value="ALSEN" />
> <xs:enumeration value="ATBEG" />
> <xs:enumeration value="ATBEN" />
> <xs:enumeration value="ATSP" />
> <xs:enumeration value="BACC" />
> <xs:enumeration value="CIR-ELKE2" />
> <xs:enumeration value="CSS" />
> <xs:enumeration value="DATC" />
> <xs:enumeration value="Fahrsp" />
> <xs:enumeration value="GWATP" />
> <xs:enumeration value="Indusi60" />
> <xs:enumeration value="KHP" />
> <xs:enumeration value="KLUBU" />
> <xs:enumeration value="LS" />
> <xs:enumeration value="SAUTC" />
> <xs:enumeration value="SAUTCM" />
> <xs:enumeration value="SAUTU" />
> <xs:enumeration value="TVM400" />
> <xs:enumeration value="ZSL90" />
> <xs:enumeration value="ZUB123" />
> <xs:enumeration value="ZUB262" />
>
> Thanks,
> Jrg von Lingen
>
> On 23.08.2010 22:10, Carsten Weber wrote:
>> Dear RailML-Users,
>>
>> by implementing RailML-Interface to a vehicle data program I thought some
>> changes would be helpful:
>>
>> - The enumeration tTrainProtectionMedium should also include the
>> value="electric".
>> This value might be usefull to describe the French "crocodile"-system or
>> would you use another value of the existing?
>>
>> - I think it is useful to add the following part:
>>
>> < !--********************************************************* -- >
>>
>> <!-- trackGauges for gauge changing axles -->
>>
>> < !--********************************************************* -- >
>>
>> <xs:complexType name="tTrackGauge">
>>
>> <xs:attribute name="trackGauge" type="rail:tLengthMM"/>
>>
>> </xs:complexType>
>>
>> This makes it possible to show all possible gauges for gauge changing
>> vehicles. I know, that there is a way shown by two different values
>> inside
>> the vehicle.
>>
>>
>> - The attribute named "count" inside the attribute group aPlaces should
>> change his type to nonNegativeInteger to differ between known values by
>> zero
>> and unknown values by a not existing entry inside the list of places.
>>
>> - The attributeGroup "aService" should be extended by an attribute
>> "count".
>> Here it can be a tCounter-type.
>>
>> - Here is also a list of my suggestions for tNationalSystemsType of train
>> protection systems:
>>
>> <xs:enumeration value="ALSEN"/>
>>
>> <xs:enumeration value="ALSN"/>
>>
>> <xs:enumeration value="ASFA"/>
>>
>> <xs:enumeration value="ATB"/>
>>
>> <xs:enumeration value="ATBEG"/>
>>
>> <xs:enumeration value="ATBEN"/>
>>
>> <xs:enumeration value="ATC"/>
>>
>> <xs:enumeration value="ATSP"/>
>>
>> <xs:enumeration value="AWS"/>
>>
>> <xs:enumeration value="BACC"/>
>>
>> <xs:enumeration value="CIR-ELKE"/>
>>
>> <xs:enumeration value="CIR-ELKE2"/>
>>
>> <xs:enumeration value="Crocodile"/>
>>
>> <xs:enumeration value="CSS"/>
>>
>> <xs:enumeration value="DATC"/>
>>
>> <xs:enumeration value="EBICAB"/>
>>
>> <xs:enumeration value="EVM120"/>
>>
>> <xs:enumeration value="Fahrsp"/>
>>
>> <xs:enumeration value="GWATP"/>
>>
>> <xs:enumeration value="Indusi54"/>
>>
>> <xs:enumeration value="Indusi60"/>
>>
>> <xs:enumeration value="Indusi60R"/>
>>
>> <xs:enumeration value="Integra-Signum"/>
>>
>> <xs:enumeration value="KHP"/>
>>
>> <xs:enumeration value="KLUBU"/>
>>
>> <xs:enumeration value="KVB"/>
>>
>> <xs:enumeration value="LS"/>
>>
>> <xs:enumeration value="LS90"/>
>>
>> <xs:enumeration value="LZB"/>
>>
>> <xs:enumeration value="Memor"/>
>>
>> <xs:enumeration value="Mirel"/>
>>
>> <xs:enumeration value="PZ80"/>
>>
>> <xs:enumeration value="PZB90"/>
>>
>> <xs:enumeration value="RS4c"/>
>>
>> <xs:enumeration value="SAUTC"/>
>>
>> <xs:enumeration value="SAUTCM"/>
>>
>> <xs:enumeration value="SAUTU"/>
>>
>> <xs:enumeration value="SCMT"/>
>>
>> <xs:enumeration value="SELCAB"/>
>>
>> <xs:enumeration value="SHP"/>
>>
>> <xs:enumeration value="SSC"/>
>>
>> <xs:enumeration value="TBL"/>
>>
>> <xs:enumeration value="TPWS"/>
>>
>> <xs:enumeration value="TVM300"/>
>>
>> <xs:enumeration value="TVM400"/>
>>
>> <xs:enumeration value="TVM430"/>
>>
>> <xs:enumeration value="ZSL90"/>
>>
>> <xs:enumeration value="ZUB121"/>
>>
>> <xs:enumeration value="ZUB122"/>
>>
>> <xs:enumeration value="ZUB123"/>
>>
>> <xs:enumeration value="ZUB262"/>
>>
>>
>>
>> Please do not hesitate to ask me, if there are any questions about my
>> remarks.
>>
>> Kind regards
>>
>>
>>
>> Carsten Weber
>>
>>
>
>
> --
> Mit freundlichen Gren/Best regards,
> -------------------------------------
> Jrg von Lingen
Re: Some hints for changes in railwayBaseTypes.xsd [message #1093 is a reply to message #1091] Mon, 30 August 2010 22:17 Go to previous messageGo to next message
Susanne Wunsch is currently offline  Susanne Wunsch
Messages: 180
Registered: March 2008
Senior Member
Hello everybody,

"Carsten Weber" <weber(at)irfpde> writes:
> "Joerg von Lingen" <joergvon_lingendd(at)t-onlinede> schrieb im Newsbeitrag
> news:i5g58d$1uc$1(at)sifaivifhgde...
>>
>> On 23.08.2010 22:10, Carsten Weber wrote:
>>>
>>> - The attribute named "count" inside the attribute group aPlaces should
>>> change his type to nonNegativeInteger to differ between known values by
>>> zero
>>> and unknown values by a not existing entry inside the list of places.
>> Why not changing tCounter completely to nonNegativeInteger?
>>
> This is also a solution, but I'm not sure which elements refer to tCounter
> and might be in trouble by value zero.

I also feel troubles with changing 'tCounter' to
'xs:nonNegativeInteger'. It is sometimes used for 'sequence' attributes,
which start with '1'.

Lot's of RS 'number*' attributes are bound to 'tCounter'. Should they
allow value 'zero'?

I would inheret a new type 'tCounterZero' for positive integer values
starting with zero (means non-negative integer). This way you can choose
that type that covers the meaning best.

I put this trouble in Trac Ticket #65.

http://trac2.assembla.com/railML/ticket/65

I will summarize it, when the solution is clear.

Kind regards...
Susanne

--
Susanne Wunsch
Schema Coordinator: railML.common
Re: Some hints for changes in railwayBaseTypes.xsd [message #1094 is a reply to message #1090] Thu, 02 September 2010 16:48 Go to previous messageGo to next message
Carsten Weber is currently offline  Carsten Weber
Messages: 26
Registered: November 2011
Junior Member
Dear Jrg,

I just filled in these changes into the Railml-wiki.

This system could be removed:
> <xs:enumeration value="TVM400" />

This should be extended:
> <xs:enumeration value="ZSL90" />

to:
<xs:enumeration value="ZST90" />
<xs:enumeration value="ZSL90" />
<xs:enumeration value="ZSI90" />
<xs:enumeration value="ZSI127" />

Thanks a lot.

Best regards.

Carsten
Re: Some hints for changes in railwayBaseTypes.xsd [message #1099 is a reply to message #1094] Sun, 06 March 2011 12:57 Go to previous message
Joerg von Lingen is currently offline  Joerg von Lingen
Messages: 59
Registered: May 2011
Member
On 02.09.2010 16:48, Carsten Weber wrote:
> Dear Jörg,
>
> I just filled in these changes into the Railml-wiki.
>
> This system could be removed:
>> <xs:enumeration value="TVM400" />
>
> This should be extended:
>> <xs:enumeration value="ZSL90" />
>
> to:
> <xs:enumeration value="ZST90" />
> <xs:enumeration value="ZSL90" />
> <xs:enumeration value="ZSI90" />
> <xs:enumeration value="ZSI127" />
>
> Thanks a lot.
>
> Best regards.
>
> Carsten
>
>
update with [348].

--
Mit freundlichen Grüßen/Best regards,
-------------------------------------
Jörg von Lingen
Previous Topic: new template for inherited attributes in wiki
Next Topic: Valid syntax for XML attributes
Goto Forum:
  


Current Time: Sat Jul 22 14:54:45 CEST 2017