[step-manufacturing] Minutes of Part 21 Edition 3 Pre-DIS Review
Martin Hardwick
hardwick at steptools.com
Wed Jun 5 02:33:15 EDT 2013
Minutes of Part 21 Edition 3 Pre-DIS Review
Monday June 3, 2013
AFNOR, Paris, France
Attendees
Allison Bernard Feeney, NIST, USA
Alexandre Fournier, Boost-Conseil, France
Jochen Haenisch, EPM, Norway
Martin Hardwick, STEP Tools, USA
Mikael Hedlind, KTH, Sweden
Keith Hunten, Lockheed Martin, USA
Lothar Klein, LKSoft, Germany
Ed Paff, ITI, USA
Max Ungerer, ProSTEP, Germany
Martin Hardwick gave a brief overview of the goals of the new edition.
http://www.steptools.com/library/standard/p21e3_dis_preview.pptx
The team then discussed the latest draft of the new edition.
http://www.steptools.com/library/standard/p21e3_dis_preview.html
The team resolved to make the following edits and submit the document
for Draft International Standard (DIS) review.
1.The ISO-10303-21.txt directory file should be required to have the
extension ".p21" instead of ".txt" to conform to an SC4 resolution on
file extension names.
2.An informative annex should be added to describe the file extension
names recommended by SC4.
3.The CAX-IF recommends using PKZIP algorithm 2.05 for compression but
the current draft recommends using 2.04 so check if there is any difference.
4.Annex A.4 should include a reference to the normative document for the
ZIP algorithm.
5.Because of security concerns a Part 21 file must not reference an
ECMAScript file so remove the ECMAScript_population entity from the
Schema header
6.Entity instance names must be numeric in case applications infer
meaning from alpha-numeric names so return the entity instance naming to
the Edition 2 rules and change all the examples to conform to this standard.
7.Delete the BNF for TAG from Table 3 and remove Sections 9.2 and 10.4.
8.Make the distinction between entity instance names and literal
instance names clear by giving the latter a name that begins with the
'@' symbol.
9.Extend the syntax to allow a literal instance to be defined from an
EXPRESS constant. For example
@10 = MATHEMATICAL_FUNCTIONS_SCHEMA.THE_NEG_PI_INTERVAL;
10.To avoid security concerns delete all examples that use URI query
strings.
11.Change the definition for implicit anchors so that numeric anchor
names are assumed to be references to entity instances with that entity
id number.
12.Verify that the Byte Order Mark (BOM) is not necessary for UTF-8.
13.In Section 12.1 explain why the Data section has been made optional.
14.In Section 8.1 explain why the Header section has been made optional
for exchange structures that have a root file in the directory.
15.In Section D.1.3 clarify which implementation levels are relevant for
each string encoding.
16.In Section D.2 ask if the entity instance identifiers are limited to
a 32 bit address space, 64 bit address space or if it is unlimited.
Action Items
Lothar Klein to send a copy of the SC4 resolution on file name
extensions to Martin Hardwick.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.steptools.com/pipermail/step-manufacturing/attachments/20130605/bca07b0a/attachment.html>
More information about the step-manufacturing
mailing list