RWML Working Group
RWML 0.71a


Road Web Markup Language (RWML)

Specification Ver.0.71a


RWML-WG Draft 1999-12-22



3. Basic Information Structure


Figure 3.1: Basic Information Tree Structure

Contents

3. Basic Information Structure
3.1 Place
3.1.1 Point
3.1.1.1 Latitude
3.1.1.2 Longitude
3.1.1.3 Altitude
3.1.1.4 Point Name
3.1.2 Route
3.1.2.1 Route Name
3.1.2.2 Road Class
3.1.2.3 Toll
3.1.2.4 Route Position
3.1.3 Area
3.1.3.1 Area Name
3.1.3.2 Region Code
3.1.3.3 Mesh Code
3.2 Update
3.2.1 Last Update
3.2.2 Next Update
3.2.3 Update Period
3.2.3.1 Start Time
3.2.3.2 End Time
3.2.3.3 Period
3.3 Authority
3.3.1 Authority Name
3.3.1.1 Country
3.3.1.2 Organization
3.3.1.3 Section
3.3.1.4 Title
3.3.1.5 Administrator Name
3.3.2 Liaison
3.3.2.1 Contact Name
3.3.2.2 Zip Code
3.3.2.3 Address
3.3.2.4 Contact Method
3.4 Condition
3.4.1 Condition Type
3.4.2 Permission
3.4.3 Limitation
3.4.4 Note


3. Basic Information Structure

3.1 Place

Description:

This section describes the information target location. Information pertaining to place consists of either point, route, area, or a combination of these elements depending on the nature of the provided information.

Explanation:

Refer to the notation rules in 2.1 Place unless specific explanations are given.

3.1.1 Point

3.1.1.1 Latitude
Notation Format:

<latitude>Latitude</latitude>

Example:

<latitude>41.500000</latitude>

or

<latitude>41,30,00</latitude>

3.1.1.2 Longitude
Notation Format:

<longitude>Longitude</longitude>

Example:

<longitude>142.250000</longitude>

or

<longitude>142,15,00</longitude>

3.1.1.3 Altitude
Notation Format:

<altitude>Altitude</altitude>

Example:

<altitude>15.3</altitude>

3.1.1.4 Point Name
Notation Format:

<point-name>Point Name</point-name>

Explanation:

The following type names are specified in attribute name-type if required.


formal   

alias    

popular  

Example:

<point-name>Nakayama Toge</point-name>

3.1.2 Route

3.1.2.1 Route Name
Notation Format:

<route-name>Route Name</route-name>

Explanation:

The following type names are specified in attribute name-type if required.


formal   

alias    

popular  

Example:

<route-name name-type="formal">Hokkaido Longitudinal Expressway</route-name>

<route-name name-type="alias">Hokkaido Expressway</route-name>

or,

<route-name>National route 1 Main Road</route-name>

3.1.2.2 Road Class
Notation Format:

<road-class>Road Class</road-class>

Example:

<road-class>Expressway</road-class>

3.1.2.3 Toll
Notation Format:

<toll>Toll Class</toll>

Example:

<toll>Interval Toll</toll>

3.1.2.4 Route Position
Notation Format:

<route-position>Route Position</route-position>

Example:

<route-position>15.0KP</route-position>

<route-position>N5.7KP/Otaru IC</route-position>

<route-position>Suzuran Odori</route-position>

3.1.3 Area

3.1.3.1 Area Name
Notation Format:

<area-name>Area Name</area-name>

Explanation:

The following type names are specified in attribute name-type if required.


formal   

alias    

popular  

Example:

<area-name>Tama, Tokyo</area-name>

or

<area-name name-type="popular">Tama New Town</area-name>

3.1.3.2 Region Code
Notation Format:

<region-code>Region Code</region-code>

Example:

<region-code>01</region-code>

<!-- Hokkaido -->

or

<region-code>01105</region-code>

<!-- Toyohira-ku Sapporo, Hokkaido -->

3.1.3.3 Mesh Code
Notation Format:

<mesh-code>Mesh Code</mesh-code>

Example:

<mesh-code std="JIS-X0140-1976" comment="suburb of Sapporo">6441</mesh-code>

3.2 Update

Description:

This section gives the update time and date, update plan, and update period. Update period is omissible.

Explanation:

Refer to the notation rules in 2.2 Time and Period unless specific explanations are given.

3.2.1 Last Update

Description:

This section gives the date and time on which the presented information was created.

Notation Format:

<last-update>Last Update </last-update>

Example:

<last-update>1999-04-01T16:30+09:00</last-update>

<last-update>1999-11-21</last-update>

3.2.2 Next Update

Description:

This section gives the planed date and time for the next information update.

Notation Format:

<next-update>Next Update</next-update>

Example:

<next-update>1999-04-01T17:00+09:00</next-update>

<next-update>1999-11-28</next-update>

3.2.3 Update Period

Description:

This section describes the period for information updating and the cycle that will be updated within that period.

3.2.3.1 Start Time
Description:

This section gives the date and time on which information provision commences.

Notation Format:

<start-time>Start Time </start-time>

Example:

<start-time>1999-04-01T08:00+09:00</start-time>

3.2.3.2 End Time
Description:

This section gives the date and time on which information provision concludes.

Notation Format:

<end-time>End Time</end-time>

Example:

<end-time>1999-04-01T08:00+09:00</end-time>

3.2.3.3 Period
Description:

This section describes the period in which the provided information is updated.

Update period is described.

Notation Format:

<period>Period</period>

Example:

<period>PT30M</period>

<!-- Update /30minutes  -->

3.3 Authority

Description:

The authority section gives information related to the organization or the individual who manages the information. If several organization names and personal names are required as authority information, list these elements. In the case that there are any restrictions on notation, list the name of the final responsible person in charge of providing information.

Explanation:

Refer to the notation rules in 2.Notation and Use of General Items unless specific explanations are given.

3.3.1 Authority Name

Description:

This section gives the organization name or department name to which the information providing organization or individual belongs.

3.3.1.1 Country
Description:

This section indicates the country to which an information providing organization or individual belongs.

Notation Format:

<country>Country</country>

Example:

<country>JP</country>

<--  JAPAN -->

3.3.1.2 Organization
Description:

This section gives the organization to which an information providing organization or individual belongs is described. Refer to the notation rules in 2.3 Organization.

Notation Format:

<organization>Organization </organization>

Example:

<organization>Hokkaido Development Bureau, Civil Engineering Research Institute</organization>

3.3.1.3 Section
Description:

This section indicates the organization to which an information provider belongs.

Notation Format:

<section>Section Name</section>

Example:
<section>Hokkaido Development Bureau, Civil Engineering Research Institute, 
Road Division, Disaster Prevention and Snow Engineering Section </section>
3.3.1.4 Title
Description:

This section gives the title of the information provider. Refer to the notation rules in 2.4.2 Title.

Notation Format:

<title>Title</title>

Example:

<title>ITS Administer </title>

3.3.1.5 Administrator Name
Description:

This section gives the name of the administrator who provides the information. Refer to the notation rules in 2.4.1 Personal Name.

Notation Format:

<administrator-name>Administrator Name</administrator-name>

Explanation:

Designate the following class names for attribute name-type. If no designation is required, it is acceptable not to provide a designation.


formal   

alias   

popular  

Example:

<administrator-name>Taro Hokkai</administrator-name>

3.3.2 Liaison

Description:

This section gives the method for contacting the information provider in the liaison entry. In the case that there are several liaisons, describe them. At least one liaison or contact method must be listed.

3.3.2.1 Contact Name
Description:

Give a contact name specific to the liazon.

Notation Format:

<contact-name>Contact Name</contact-name>

Explanation:

Input the liaison name using characters.

Example:

<contact-name>Michinoeki Liaison Council</contact-name>

3.3.2.2 Zip Code
Description:

This section gives the zip code of the liaison. Refer to the notation rules in 2.5.1 Zip code.

Notation Format:

<zip-code>Zip Code</zip-code>

Example:

<zip-code>162-8602</zip-code>

3.3.2.3 Address
Description:

Give the liaison's address. Refer to the notation style in 2.5.2 Address.

Notation Format:

<address>Address</address>

Example:

<address>

1 jo, 3 chome, Hiragishi Toyohira-ku Sapporo, Hokkaido</address>

3.3.2.4 Contact Method
Description:

This section describes the method for contacting the liaison. Refer to the notation rules in 2.5.3 Hyper-reference.

Notation Format:

<contact-method>Comment</contact-method>

Example:

<contact-method href="tel:012(345)6789">Main Number</contact-method>

<contact-method href="fax:+81-12-345-6789"/>

<contact-method href="mailto:xxx.ceri.go.jp">For test use</contact-method>

<contact-method href="http://www.ceri.go.jp/test/">Test site</contact-method>

3.4 Condition

Description:

This section lists any limits given by the information provider on presenting the information.

3.4.1 Condition Type

Description:

This section describes the type of information to be given.

Notation Format:

<condition-type>Condition Type </condition-type>

Explanation:

For condition type, record one term from the list of defined terms below.


test   available for test use only

free   available for free

pay    not available for free. Note the information service fee in the "notes" section.

other  Give details in the "notes" section.  



Example:

<condition-type>free</condition-type>

3.4.2 Permission

Description:

This section gives the permission status on the provided information.

Notation Format:

<permission>Permission</permission>

Explanation:

For permission status, record one term from the list of defined terms below.


none		Not required. 

notice		Notice required.  Describe the notice method in the "notes" section.

contract      	Contract required. Describe the contract drafting method in the  "notes" section.

other		Describe the details in the "notes" section.

Example:

<permission>none</permission>

3.4.3 Limitation

Description:

This section gives the liability exemption limitations on the provided information.

Notation Format:

<limitation>Limitation</limitation>

Explanation:

For liability exemption limitations, record one term from the list of defined terms below.


exempt		Information provider is not responsible for damage incurred from the use of the data.

other		Describe the details in the "notes" section.

Example:

<limitation>escape</limitation>

3.4.4 Note

Description:

This section gives notes on the condition of providing information.

Notation Format:

<note>Note</note>

Explanation:

Express the limitations in free style characters or by designating the file's URL.
Format the content like the designated items in 3.4.1 Condition Type, 3.4.2 Permission, 3.4.3 Limitation.

Example:

<note>report usage permission to the e-mail address before the event </note>

<note>http://www.ceri.go.jp/its-win/note001/</note>