| tElementWithIDAndName [message #1068] |
Wed, 12 March 2008 16:13  |
Joachim Rubröder railML
Messages: 0
Registered: November 2019
|
|
|
|
Hello,
we diskussed in Bern to use "tElementWithIDAndName" in all sub schemas for
elements to be referenced (elementRefId --> element.id).
I startet to do so in the timetable, here my experiences:
- tElementWithIDAndName should be part of GenericRailML.xsd
- the "name" attribute should be optional because not every element needs
to have a name.
- a "description" attribute is often used in the timetable schema instead
of the "name" and should be added (optional) as well, because it is
something slightly different from a "name"
(e.g. an operating period with id="15", name="Mo-Fr" and
description="driving Monday to Friday on working days")
Best regards,
Joachim Rubröder
|
|
|
|
| Re: tElementWithIDAndName [message #1069 is a reply to message #1068] |
Wed, 12 March 2008 17:05  |
Joachim Rubröder railML
Messages: 0
Registered: November 2019
|
|
|
|
coord(at)timetablerailmlorg writes:
> we diskussed in Bern to use "tElementWithIDAndName" in all sub
> schemas for elements to be referenced (elementRefId --> element.id).
> I startet to do so in the timetable, here my experiences: -
> tElementWithIDAndName should be part of GenericRailML.xsd
I agree. I would move the complexType definition to file
"genericRailML.xsd", if Volker agrees.
> - the "name" attribute should be optional because not every element
> needs to have a name. - a "description" attribute is often used in
> the timetable schema instead of the "name" and should be added
> (optional) as well, because it is something slightly different from
> a "name" (e.g. an operating period with id="15", name="Mo-Fr" and
> description="driving Monday to Friday on working days")
I applied the ideas, mentioned by Joachim:
<xsd:complexType name="tElementWithIDAndName">
<xsd:attribute name="id" type="tGenericID" use="required" />
<xsd:attribute name="name" type="tGenericName"
use="optional" />
<xsd:attribute name="description" type="tElementDescription"
use="optional" />
<!-- Provide an extension point for other attributes-->
<xsd:anyAttribute />
</xsd:complexType>
If needed, I can upload a new version of file "genericRailML.xsd" on
developer page.
Other schema coordinators should apply this type in order to get a
step forward to harmonized railML-schemas.
On the other hand, all references should be renamed e.g. following
way:
<xsd:attribute name="trainRefId" type="tGenericID" use="optional">
<xsd:annotation>
<xsd:documentation>
Reference to "id" attribute in "train"
element, "timetable" subschema
</xsd:documentation>
<xsd:documenation>
Other remarks, e.g. for semantical usage
</xsd:documentation>
</xsd:annotation
</xsd:attribute>
I would prefer to define a new simpleType "tGenericRef" in
"genericRailML.xsd", in order to distinct between "id" and "*refId".
Optional or required use has to be decided in special context of
element usage.
Best regards,
Susanne
--
Susanne Wunsch
Schema Coordinator: railML.common
|
|
|
|
| Re: tElementWithIDAndName [message #1070 is a reply to message #1069] |
Wed, 12 March 2008 17:46 |
Joachim Rubröder railML
Messages: 0
Registered: November 2019
|
|
|
|
Hi,
thanks for the quick reply!
A "tGenericRef" would be fine as type for all xyRefId - Elements!
I'm planing to upload a new timetable version 1.11 with some of the new
features discussed in Berne. If you will upload a new GenericRailml.xsd, I
could already use the new "id" and "RefId" attributes.
Best regards,
Joachim Rubröder
|
|
|
|
| Re: tElementWithIDAndName [message #1071 is a reply to message #1069] |
Fri, 14 March 2008 09:53 |
Joerg von Lingen
Messages: 148
Registered: May 2011
|
Senior Member |
|
|
I will check, where the changes of tElementWithIDAndName and elementRefId can be used in
Rollingstock scheme.
--
Mit freundlichen Grüßen/Best regards,
-------------------------------------
Jörg von Lingen
|
|
|
|
Members
Search
Help
Login
Home
