ISO/IEC JTC 1/SC34 N259

ISO/IEC logo

 

ISO/IEC JTC 1/SC34

Information Technology --

Document Description and Processing Languages

 

TITLE:

 

Summary of Voting on SC 34 N 226 - CD Ballot for Topic Map Constraint Language -

(New JTC 1 NP Number - ISO/IEC 19756)

SOURCE:

SC 34 Secretariat

PROJECT:

 

PROJECT EDITOR:

S. Pepper

STATUS:

 

ACTION:

The results of this ballot being forwarded to WG 3 to address the national body comments received and submit a revised text using the new JTC 1 NP Number ISO/IEC 19756.

DATE:

 

DISTRIBUTION:

SC34 and Liaisons

REFER TO:

 

REPLY TO:

Dr. James David Mason
(ISO/IEC JTC1/SC34 Chairman)
Y-12 National Security Complex
Information Technology Services
Bldg. 9113 M.S. 8208
Oak Ridge, TN 37831-8208 U.S.A.
Telephone: +1 865 574-6973
Facsimile: +1 865 574-1896
E-mail: mailto:[email protected]
http://www.y12.doe.gov/sgml/sc34/sc34oldhome.htm

Ms. Sara Hafele, ISO/IEC JTC 1/SC 34 Secretariat
American National Standards Institute
25 West 43rd Street
New York, NY 10036
Tel: +1 212 642 4937
Fax: +1 212 840 2298
E-mail: [email protected]


SC 34 N 259

2001-10-04

 

 

 

SC 34 Voting Summary on JTC 1/SC 34 N 226

CD Ballot for Topic Map Constraint Language

 

P-Member

APPROVAL OF THE DRAFT AS PRESENTED

APPROVAL OF THE DRAFT WITH COMMENTS AS GIVEN ON THE ATTACHED

DISAPPROVAL OF THE DRAFT FOR REASONS ON THE ATTACHED

Acceptance of these reasons and appropriate changes in the text will change our vote to approval

ABSTENTION (For Reasons Below):

Brazil

 

 

 

 

 

Canada

X

 

 

 

 

China

X

 

 

 

 

Denmark

 

 

 

 

 

France

 

 

 

 

 

Ireland

 

 

 

 

 

Italy

 

 

 

 

X

(comments)

Japan

 

X

(editorial and technical)

 

 

 

Republic of Korea

 

 

 

 

 

Netherlands

X

 

 

 

 

Norway

X

 

 

 

 

United Kingdom

 

X

(general and technical)

 

 

 

United States

X

 

 

 

 

 

 

According to the JTC 1 Directives, Section 9.4.3

 

Consideration of successive CD/PDAM/PDISP/PDTRs (types 2 and 3) shall continue until the substantial support of the P-members of the committee has been obtained or a decision to abandon or defer the project has been reached.

 

 

 

 

 

 

 

 

 

 

SC 34 National Body Comments on N 226

 

 

 

Italy

Abstention due to the lack of experts.

 

Japan

 

1. Add the clause of Scope, which should include the description in the scope field of NP(SC34 N221): mechanisms for expressing constraints on classes of topic maps conforming to ISO/IEC 13250:2000.

 

2. The Title should be "Topic Map Constraint Language", as shown in the NP, rather than "Draft requirements, examples, and a "low bar" proposal for Topic Map Constraint Language (TMCL)".

 

3. Add the clause of Normative References. It should include DAML/OIL, KIF, OKBC, OCL, PAL (Protege Axiom Language), which are referred to in 1. of N226.

 

United Kingdom

 

It is unnecessary to define "ontology" as a term within the constraint language. (The term is defined is

such a way as to clash with the definition of this term as used in other international standards.)

 

Clause 3.1

Add the following:

Valid Facets

and

Example 1.7 Constrain the relationship between two or more facets

Example: The value of the effectiveStartDate facent must precede that to the effectiveEndDate facet

 

Clause 3.3.

Add the following:

Example 3.5 Occurrences of type "0" must have a facet whose value matches an expression

Example: Occurrences of type "map" must have a DatePublished facet whose value is greater than

1st January 1995.

 

Clause 3.4

Replace ??? by

- which topics may only be used for typing association rules

- which topics may not be used for typing association rules

and add:

Example 4.1 Constrain the topic "T" so that it cannot be used for typing associations

Example: The topic "Martin Bryan" cannot be used as the type of an association

 

Clause 3.5

Change "which topics can be used for scoping" to "which topics can be used as added themes"

In examples 5.1 and 5.2 change "themes" to "added themes"

 

Clause 5, A simple low bar proposal

It must be possible to distinguish constraint language statements from topic maps. At the least

constraint statements should be enclosed in a <tcml> element or be assigned a tcml namespace.

In the examples the only reference to tcml is via subjectIndicatorRefs that point to concepts that

would presumably be defined in the standard.

 

This seems inadequate to distinguish constraint rules from other topics. The UK strongly believes that XML element contents should not place constraints on their parents.