Please Note that the issues in red are the ones to be discussed or confirmed in the meeting. Canadian Comments on SC32 N2409 CD4 19763-7 Date: 2013-10-07 Document: 32N2409 Project: ISO/CD4 19763-7

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

CA All All - Ge Canada disapproves of the draft for the reasons Canada will change its vote to Approval if the 00 below. comments below are satisfactorily addressed.

CA 9 1 Scope Para 2, line Ed Clause 1 mentions "some web service descript After the text "some web service description la 01 2 ion language", with no explanation. nguage" add "(see Annex A for examples)" A list of service description languages is given in Annex A. This should be referenced from clause 1. CA 23-24 3.1 Terms Ed Referencing definitions from other standards For all terms used in this standard, include the 02 without actually including them requires the terms and definitions in clause 3.1, with a reader to obtain and access those other reference to the source. standards. This document would be more usable if the required terms and definitions were repeated here, with references to indicate from whence they come. The editor's note at line 70 partially addresses this concern, but a check needs to be made for other terms whose definitions exist elsewhere. CA 72-103 3.2 Terms Ed The MS Word outline level for all terms in clause Change the level for all terms to Level 3 03 3.2 is set to Level 1, as is the definition for OWL- S, QoS, WADL, WSDL and WSMO.

and for all definitions to Body Text This results in a poorly structured navigation pane:

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 1 of 15 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Canadian Comments on SC32 N2409 CD4 19763-7 Date: 2013-10-07 Document: 32N2409 Project: ISO/CD4 19763-7

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

Giving a modified navigation pane:

CA After 95, 3.2 New Ed SWSO is shown in Figure 1 but not listed in Add to clause 3.2: 04 before clause 3.2. 96 SWSO Semantic Web Service Ontology CA 159-160 5.1 Para 3, last Ed Re: 1) At the beginning of the sentence 'Service' s/b 'A 05 sentence service'. "Service can be annotated by user tags which are created by all the people using the 1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 2 of 15 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Canadian Comments on SC32 N2409 CD4 19763-7 Date: 2013-10-07 Document: 32N2409 Project: ISO/CD4 19763-7

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

service." 2) Replace: "are created by all the people" By: "may be created by any person" CA After Ed SWSO is shown in Figure 1 but not listed in the Add an entry in the Bibliography for: 06 299 Bibliography Semantic Web Service Ontology http://www.w3.org/Submission/SWSF-SWSO/ CA Ge If any further problems are discovered before or To be determined at the CRM as required. 99 during the Comment Resolution Meeting, and a consensus can be reached on a solution, then they should be corrected.

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 3 of 15 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 ISO/IEC CD4 19763-7:2013(E) Metamodel for service registration Date: 2013/10/2 Document: 32N2409T Project: 1.32.22.01.07.00

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

JP0 145 5.1 Figure 2 ed The font of characters in this figure is too small. Agree 1 JP0 168 5.2 Figure 3 ed The notation of multiplicity of “involving_service” Replace to “1..1” Agree 2 is “1”.

JP0 168 5.2 Figure 3 ed The notation of multiplicity of “containing_service” Replace to “1..1” Agree 3 is “1”.

JP0 172 5.2 Figure 4 ed “Input” class and “Output” class is wrong? Rename each class. Agree 4 “Input” class is “Input_Message” class? “Output” class is “Output_Message” class?

JP0 172 5.2 Figure 4 te In this figure and legend, the dashed lines with a If these arrows mean subset (specialisation ?) of Agree 5 triangular arrowed means “realization”. (See. association between superclasses, change in OMG UML Superstructure Ver, 2.4.1) accordance with the notation of UML2.4.1 Replace the dashed lines superstructure (see Figure 7.22) , or change into with a triangular arrow with the solid line with a triangular arrowed according the bold lines with a to other parts. triangular arrow JP0 172 5.2 Figure 4 te About the subclasses of “Model_Element (from If these classes have no relation with a subclass Common Problem 6 MFI Core and mapping)” other than “Service”. of "Model" class, remove the generalize relation with "Model_Element" class. Need to be discussed in the These classes have "contained_by" refenece meeting inherited from "Model_Element" Class. And it is necessary to loosen constraint of clause 15.5 of "Modelling guideline". In this situation, The instance of these classes has not forbidden having relation with the instance of the subclass of the "Model class" defined by other parts (such as MFI-5, 8, 12, 13). JP0 183 5.3 ed Hanging paragraph Agree 7 JP0 186 5.3.3 3rd row ed The font of the super class name is bold face. Change into a normal font. Agree 8

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 1 of 15 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 ISO/IEC CD4 19763-7:2013(E) Metamodel for service registration Date: 2013/10/2 Document: 32N2409T Project: 1.32.22.01.07.00

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

JP0 189 5.3.3 6th row ed The heading character of Change into a small letter. Agree 9 "Message_type_description" is a capital letter.

JP1 196 5.3.13 5th row te The "Service_Description_Language" class does If this attribute is necessary, add this attribute into “Language_id” is not 0 not have the "language_id" attribute. the text and Figure. necessary if “name” attribute have existed In the CD3 text (32N2278), the If not, explain reason in the BRM. “Service_Description_Language” class had the “language_id”. Need to be discussed in the meeting JP1 196 5.3.13 7th row ed The multiplicity of “expressed_model” reference is Revise the text or Figure 2. Agree 1 mismatching between Clause 5.3.13 and Figure 2. JP1 200 5.3.17 3rd row ed There is not super class (“Model_Element (from Add the name of super class. Agree 2 MFI Core and mapping)”. JP1 208 Annex A Table A 1 te There is no description about "Other". Add description of “Other”. Common Problem 3 Need to be discussed in the meeting End of comments

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 2 of 15 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 G General ed Line numbering has been used as Ensure line numbers are Agree B requested, but the actual line consistent across versions. 1 numbers are different on both versions available to us. The .pdf version on the SC32 website has the last line as line 296. The .doc version on the SC32 website has the same last line as line 299.

G Foreword ed The title of part 1 has changed. Amend to read “Framework” Agree B 2

G 1 Lines 5-7 ed “This part of ISO/IEC 19763 Amend to read “This part of Agree B (pdf) specifies a metamodel for ISO/IEC 19763 specifies a 3 registering Services that can enable metamodel for registering users to discover appropriate .services, facilitating Services. The metamodel that this interoperability through the part specifies is intended to improve reuse of services.” interoperability through the reuse of services.” Duplication of content.

G 2 Lines 17- ed The title of part 1 has changed. Amend to read “Framework” Agree B 18 (pdf) 4

G 3.1 Line 25 ed Incorrect formatting is used for the Amend to read Agree (pdf) et seq sub-clauses. B 3.1.1 5 atomic expression logical expression that has the unit granularity and similarly throughout.

G 3.1 Line 25 ed It would be helpful to have the Amend to read Agree B (pdf) et seq clause references for terms that are used in the definitions. 3.1.1 6 atomic expression logical expression (3.1.5) that has the unit granularity and similarly throughout.

G 3.1.2 Lines 27- te Incorrect statement made about the Amend to read Agree B 29 (pdf) composition of a composite expression. 3.1.2 7 composite expression logical expression that comprises multiple atomic expressions (3.1.1) and/or other composite expressions (3.1.2) by using connectives such as conjunction, disjunction and negation

G 3.1.4 Lines 33- te This definition is incorrect. Also it Amend to read Agree 34 (pdf) should be expressed in terms of B 3.1.4 8 “operation” and not “service operation” since this applies to both exit condition services and processes. constraint that, if true, will cause an operation to finish unsuccessfully NOTE The operation can be a process or a service operation

G 3.2 Line 71 ed Incorrect formatting Insert line spaces between Agree B (pdf) et seq terms. 9

page 3 of 15 G 3.2 Lines 79- ed Spacing in title is incorrect and an Amend to read Agree 80 (pdf) abbreviation missing. B ISO/IEC 1963-10, Information 1 technology – Metamodel 0 framework for interoperability (MFI) – Part 10: Core model and basic mapping

G 3.2 Lines 82- ed Extra hyphen included in title. Amend to read Agree 83 (pdf) B ISO/IEC 1963-5, Information 1 technology – Metamodel 1 framework for interoperability (MFI) – Part 5: Metamodel for process model registration

G 3.2 Lines 85- ed Spacing in title is incorrect and an Amend to read Agree 86 (pdf) extra hyphen included in title. B ISO/IEC 1963-8, Information 1 technology – Metamodel 2 framework for interoperability (MFI) – Part 8: Metamodel for role and goal registration

G 3.2 Lines 88- ed Extra hyphen included in title. Amend to read Agree 89 (pdf) B ISO/IEC 1963-7, Information 1 technology – Metamodel 3 framework for interoperability (MFI) – Part 7: Metamodel for service registration

G 4.2.2 Lines 118- ed Incorrect statement Amend to read Agree 119 (pdf) B b) shall not use, test, access, 1 or probe for any extension 4 features nor extensions to the metamodel specified in clause 5.

G 4.2.3 Lines 123- ed Incorrect statement Amend to read Agree 124 (pdf) B b) as permitted by the 1 implementation, may use, test, 5 access, or probe for any extension features or extensions to the metamodel specified in clause 5.

G 5.1 Figure 2 - te Although technically correct, the Amend so that both Agree B Line 145 notation used to indicate that Atomic_Expression and 1 (pdf) Atomic_Expression and Composite_Expression are Composite_Expression are linked to Expression using a 6 subclasses of Expression could be single arrowhead. interpreted as if they are in two distinct specialisation hierarchies.

G 5.1 Figure 2 - te The multiplicity, “0..1”, associated Move multiplicity to correct Agree B Line 145 with the role name position.. 1 (pdf) “composed_expression” on the association from 7 Composite_Expression to Expression is shown alongside the wrong line.

G 5.1 Figure 2 - te A service description language Add an attribute to Need to be B Line 145 must have a name (see Annex B) Service_Description_Language discussed in the 1 (pdf) as follows: meeting 8 name [1..1]

G 5.1 Figure 2 - te A service model must have a name Amend attributes of Agree B Line 145 and may have an IRI Service_Model to be: (pdf) 1 name [1..1] 9 described_IRI [0..1]

page 4 of 15 G 5.1 Figure 2 - te A message type must have a name Amend attributes of Agree B Line 145 but may not have a description Message_Type to be: (pdf) 2 name [1..1] 0 message_type_description [0..1]

G 5.1 Lines 151- ed/te Missing indefinite articles and an Amend to read Agree 153 (pdf) incorrect statement. B A pre-condition specifies a 2 constraint that must be true 1 when a service operation is invoked. A post condition specifies a constraint that must be true at the completion of a service operation, and an exit- condition specifies a constraint that, if true, will cause an operation to finish unsuccessfully.

G 5.1 Lines 159- ed “Service can be annotated by user Amend to read Agree 160 (pdf) tags which are created by all the B Each service can be annotated people using the service.” Poor 2 by zero, one or more user tags, English. 2 each of which will be created by a user of the service.

G 5.1 Lines 147- ed There is no description of message Add a description of message Agree B 160 (pdf) type. type. 2 3

G 5.2 Lines 161- ed “Figure 3 shows the associations Amend to read Agree 162 (pdf) between MFI Service registration B Figure 3 shows the and MFI Role and Goal registration, 2 associations between MFI MFI Process model registration.” 4 Service registration (this part) Confusing statement and MFI Role and Goal registration and MFI Process model registration.

G 5.2 Figure 3 - ed The role name Move role name so that the Agree B Line 168 “fully_realizing_service_operation” underscores are not hidden by 2 (pdf) is placed so that the underscores the association line. are hidden by the association line. 5

G 5.2 Lines 166- te In the discussion of service Include the role concept within Agree B 167 (pdf) involvement it would be helpful to this discussion, for example: know what the involvement is with. 2 Similarly, each service involves 6 zero, one or more service involvements, where each service involvement is the involvement of a role with a service, such as actor or beneficiary. Each service involvement indicates that a role is involved in the execution of one and only one service.

G 5.3 Line 182 ed Presentation could be improved by None provided. Agree B (pdf) et seq providing more line spaces and by 2 ensuring that line breaks occur after the underscores in attribute names, 7 reference names and class names.

G 5.3 Line 182 ed All of the description of the None provided. Agree B (pdf) et seq metaclasses, the attributes and the 2 references could be improved. 8

page 5 of 15 G 5.3.2 Attributes te The description of Add a constraint setting out the Agree, but need B “composition_type” includes the allowed values of to be confirmed 2 phrase “such as “conjunction”, “composition_type”. in the meeting “disjunction” and “negation"”. Are 9 these examples (and others are allowed) or are they a constraint?

G 5.3.3 Description te Incorrect definition. Amend to read Agree B Exit_Condition is a metaclass 3 each instance of which 0 specifies the constraint that, if true, will cause the operation to finish unsuccessfully

G 5.3.4 References te Missing reference Add “composed_expression” Agree B and detail. 3 1

G 5.3.6 Attributes te A message type must have a name Amend multiplicity of name to Agree B but may not have a description “1..1” 3 2

G 5.3.7 References te Incorrect name of inverse for Amend “involving_message” to Agree B “involved_output_message_type” “involving_output_message” 3 3

G 5.3.8 References te Incorrect name of inverse for Amend Agree B “postcondition_logical_expression” “expressed_post_condition” to 3 “expressed_postcondition” 4

G 5.3.9 References te Incorrect name of inverse for Amend “expressed_condition” Agree B “precondition_logical_expression” to “expressed_precondition” 3 5

G 5.3.12 References te Incorrect reference name for Amend Agree B “contained_service_operation” “contained_service_operation” 3 to “contained_operation” 6

G 5.3.12 Constraints te Incorrect attribute name used Amend “requestedIRI” to Agree B “requested_IRI” 3 7

G 5.3.13 Attributes te A service description language Add an attribute to Agree B must have a name (see Annex B) Service_Description_Language 3 as follows: 8 name [1..1]

G 5.3.13 References te Incorrect name of inverse for Amend “description_language” Agree B “expressed_model” to “describing_language” 3 9

G 5.3.14 Attributes te A service model must have a name Add a name attribute with Agree B and may have an IRI multiplicity “1..1” and amend 4 the multiplicity of described_IRI to “0..1”. 0

G Annex B B.1 ed The heading uses “WSMO” and Either use “WSMO” or “WSML” Agree B Heading – then this is described as “Web consistently or else explain the 4 Line 212 Service Modelling Ontology” in line relationship between “WSMO” (pdf) et seq 213, but then the “notation” attribute and “WSML”. 1 for the objects in Figure B.1 is shown as “WSML”. This could be confusing.

page 6 of 15 G Annex B Table B.1 – ed This looks more like a figure than a Convert to a figure. Agree B Lines 222- table. 4 223 (pdf) 2

G Annex B Figure B.1 te Object106 – missing reference Add reference Agree B Part 1 – “composed_expression”, 4 Line 226 “Object111” (pdf) 3

G Annex B Figure B.1 te Object107 – missing reference Add reference Agree B Part 1 – “composed_expression”, 4 Line 226 “Object111” (pdf) 4

G Annex B Figure B.1 te Object108 – missing reference Add reference Agree B Part 1 – “composed_expression”, 4 Line 226 “Object110” (pdf) 5

G Annex B Figure B.1 te Object109 – missing reference Add reference Agree B Part 1 – “composed_expression”, 4 Line 226 “Object110” (pdf) 6

G Annex B Figure B.1 te Object110 – missing reference Add reference Agree B Part 1 – “composed_expression”, 4 Line 226 “Object111” (pdf) 7

G Annex B Figure B.1 te Object111 – missing reference Add reference Agree B Part 1 – “expressed_precondition”, 4 Line 226 “Object105” (pdf) 8

G Annex B Figure B.1 te Object112 – missing reference Add”Object121” to Agree B Part 1 – “constrained_output” 4 Line 226 (pdf) 9

G Annex B Figure B.1 te Object113 – missing reference Add reference Agree B Part 1 – “composed_expression”, 5 Line 226 “Object117” (pdf) 0

G Annex B Figure B.1 te Object114 – missing reference Add reference Agree B Part 1 – “composed_expression”, 5 Line 226 “Object117” (pdf) 1

G Annex B Figure B.1 te Object115 – missing reference Add reference Agree B Part 1 – “composed_expression”, 5 Line 226 “Object117” (pdf) 2

G Annex B Figure B.1 te Object116 – missing reference Add reference Agree B Part 1 – “composed_expression”, 5 Line 226 “Object117” (pdf) 3

G Annex B Figure B.1 te Object117 – missing reference Add reference Agree B Part 2 – “expressed_postcondition”, 5 Line 228 “Object112” (pdf) 4

G Annex B Figure B.1 te Object118 – missing reference Add reference Agree B Part 2 – “containing_operation”, 5 Line 228 “Object104” (pdf) 5

page 7 of 15 G Annex B Figure B.1 te Object119 – missing reference Add reference Agree B Part 2 – “containing_operation”, 5 Line 228 “Object104” (pdf) 6

G Annex B Figure B.1 te Object119 – missing reference Add reference Agree B Part 2 – “containing_precondition”, 5 Line 228 “Object105” (pdf) 7

G Annex B Figure B.1 te Object120 – missing reference Add reference Agree B Part 2 – “containing_operation”, 5 Line 228 “Object104” (pdf) 8

G Annex B Figure B.1 te Object120 – missing reference Add reference Agree B Part 2 – “containing_precondition”, 5 Line 228 “Object105” (pdf) 9

G Annex B Figure B.1 te Object121 – missing reference Add reference Agree B Part 2 – “containing_operation”, 6 Line 228 “Object104” (pdf) 0

G Annex B Figure B.1 te Object121 – missing reference Add reference Agree B Part 2 – “containing_postcondition”, 6 Line 228 “Object112” (pdf) 1

G Annex B Figure B.1 te Object122 – missing reference Add reference Agree B Part 2 – “containing_operation”, 6 Line 228 “Object104” (pdf) 2

G Annex B Figure B.1 te Object122 – missing reference Add reference Agree B Part 2 – “containing_postcondition”, 6 Line 228 “Object112” (pdf) 3

G Annex B Figure B.1 te Object123 – missing reference Add reference Agree B Part 2 – “involving_input_message”, 6 Line 228 “Object118” (pdf) 4

G Annex B Figure B.1 te Object124 – missing reference Add reference Agree B Part 2 – “involving_input_message”, 6 Line 228 “Object120” (pdf) 5

G Annex B Figure B.1 te Object125 – missing reference Add reference Agree B Part 2 – “involving_output_message”, 6 Line 228 “Object121” (pdf) 6

G Annex B Figure B.1 te Object126 – missing reference Add reference Agree B Part 2 – “involving_output_message”, 6 Line 228 “Object122” (pdf) 7

G Annex B Remainder The remainder of Annex B has not Agree B – Line 230 been reviewed due to time 6 et seq limitations. 8

page 8 of 15 Template for comments and secretariat observations Date: 20130916 Document: SC 32 N 2409 Project:19763-7 CD 4

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

US 1 8 1 ed "Web Services whose capability is described" is Replace with "Web Services whose capabilities Agree not grammatically correct. are described"

US 2 118 4.2.2 ed The phrase "any extension features nor Remove "any extensions." Agree extensions any extensions to the metamodel " is unclear.

US 3 after 5.3 Figure 4 ed Text is crowded in top line of boxes. Allow more space for text or consider wrapping Agree 172 text. US 4 after 5.3.15 ed "consumed_mess Remove the extra "s" from each phrase. Agree 198 sage" and "generated_messs age" each contain an extra "s"

US 5 233 B.2 ed "Brower" should be "Browser" Make the correction. Agree

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 1 of 15 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03