[step-manufacturing] First day minutes

[Martin Hardwick]

Let me know if you have any additional feedback.

Will try to call before the end of the day,

Martin
-------------- next part --------------
Martin Hardwick, USA
Mikael Hedlind, Sweden
Nicolas Figay, France
Atsuto Soma, Japan


Japan comments
1. Add a section describing the different types of idnetifiers
   GUID/UUID/URI/IRI and how they can be mapped into anchor names.

2. Style sheet issue in Section 12.1.5

3. In Table 2 change entity_name back to entity_instance_name
   Make value_name into value_instance_name

4. Other comments are editorial resolve as suggested

France comments

1. Remove support for EXPRESS constants

2. Define levels to enable staged implementation

	Level 1 - Digital signature, UTF8 and single file zips
	Level 2 - Anchor section
	Level 3 - Reference section without value references
	Level 4 - Value references, ZIP files, ECCMAScript binding

3. Default as anchor will be removed by replacing with wording stating that every
   URL in the reference section must have a fragment identifier.

4. A conforming implementation can give the user options on how to process missing 
   connections due to missing connectivity (e.g use a cache if available). The standard
   defines the value to be used (null) if nothing is found and the system wishes to
   continue processing.

5. Part 21 edition 3 requires the server to deliver data in the Part 21 format but
   allows the server to store the data in any format. The same should be true for 
   a future version of Part 28 so if the Part 28 references a Part 21 root file then
   the server will be required to convert it to Part 21 before transmission.

6. Previous editions supported multiple EXPRESS schemas in multiple data sections but
   this feature has not been used in practice so unless there are objectsions
   its use shall be depracated in Edition 3.

7. Document some use cases for the ECCMAScript binding.