Minutes
Opening
roll - Quorate with 21 of 22 voting members present
Resolution: Minutes of 2009-03-02 approved w/o
proposal is to close with no action
Motion: m:Booz s:Wells close Assembly-102 with no action
Resolution: m:Booz s:Wells close Assembly-102 with no action w/o
Motion: m:Edwards s:MischkinskyDefer Assembly-80
Resolution: m:Edwards s:Mischkinsky Defer Assembly-80 w/o
Chapman discusses his proposal
<Martin C>
proposed text:
<Martin C>
12.1 SCA Documents
For a document to be a valid SCA Document, it MUST comply with one of the SCA document types below:
SCA Composite Document:
An SCA Composite Document is a file that MUST have an SCA <composite/> element as its root element and MUST conform to the
sca-core-1.1.xsd schema and MUST comply with the additional constraints on the document contents as defined in Appendix C.
SCA ComponentType Document:
An SCA ComponentType Document is a file that MUST have an SCA <componentType/> element as its root element and MUST conform
to the sca-core-1.1.xsd schema and MUST comply with the additional constraints on the document contents as defined in
Appendix C.
SCA ConstrainingType Document:
An SCA ConstrainingType Document is a file that MUST have an SCA <constrainingType/> element as its root element and MUST
conform to the sca-core-1.1.xsd schema and MUST comply with the additional constraints on the document contents as defined
in Appendix C.
SCA Definitions Document:
An SCA Definitions Document is a file that MUST have an SCA <definitions/> element as its root and MUST conform to the sca-definition-1.1.xsd
schema and MUST comply with the additional constraints on the document contents as defined in Appendix C.
SCA Contribution Document:
An SCA Contribution Document is a file that MUST have an SCA <contributution/> element as its root element and MUST conform
to the sca-contribution-1.1.xsd schema and MUST comply with the additional constraints on the document contents as defined
in Appendix C.
SCA Interoperable Packaging Document:
A ZIP file containing SCA Documents and other related artifacts. The ZIP file MAY contain a top-level "META-INF" directory,
and MAY contain a "META-INF/sca-contribution.xml" file, and MAY contain a "META-INF/sca-contribution-generated.xml" file.
12.2 SCA Runtime
An implementation that claims to conform to the requirements of an SCA Runtime defined in this specification MUST meet the
following conditions:
1.The implementation MUST comply with all statements in Appendix C: Conformance Items related to an SCA Runtime, notably all
MUST statements have to be implemented.
2.The implementation MUST conform to the SCA Policy Framework v 1.1 Specification [Policy].
3.The implementation MUST support and comply with at least one of the OpenCSA Member Section adopted implementation types.4.The implementation MUST support binding.sca and MUST support and conform to the SCA Web Service Binding Specification v
1.1. Other OpenCSA Member Section adopted bindings MAY also be supported.
<anish>
do we need a concept of 'SCA document"?
<anish>
it seems that it would be enuf to have 'sca composite document', 'sca CT document' etc
<anish>
but it is a minor point
Motion: m:Chapman s:Malhotra Resolve Assembly-101 with text above
<Martin C>
The ZIP file SHOULD contain a top-level "META-INF" directory, and SHOULD contain a "META-INF/sca-contribution.xml" file, and
SHOULD contain a "META-INF/sca-contribution-generated.xml" file.
<Martin C>
The ZIP file MAY contain a top-level "META-INF" directory, and SHOULD contain a "META-INF/sca-contribution.xml" file, and
MAY contain a "META-INF/sca-contribution-generated.xml" file.
<Simon Nash>
The ZIP file SHOULD contain a top-level "META-INF" directory, and SHOULD contain a "META-INF/sca-contribution.xml" file, and
MAY contain a "META-INF/sca-contribution-generated.xml" file.
Motion: to amend m:Mischkinsky s:Booz change the text to read The ZIP file SHOULD contain a top-level "META-INF" directory, and SHOULD
contain a "META-INF/sca-contribution.xml" file, and MAY contain a "META-INF/sca-contribution-generated.xml" file.
motion to amend passes w/o
Motion: m:Nash s:Aupperle in point Nr. 4 in 12.2 strike the final sentence
motion to amend passes w/o
<Martin C>
12.1 SCA Documents
For a document to be a valid SCA Document, it MUST comply with one of the SCA document types below:
SCA Composite Document:
An SCA Composite Document is a file that MUST have an SCA <composite/> element as its root element and MUST conform to the
sca-core-1.1.xsd schema and MUST comply with the additional constraints on the document contents as defined in Appendix C.
SCA ComponentType Document:
An SCA ComponentType Document is a file that MUST have an SCA <componentType/> element as its root element and MUST conform
to the sca-core-1.1.xsd schema and MUST comply with the additional constraints on the document contents as defined in
Appendix C.
SCA ConstrainingType Document:
An SCA ConstrainingType Document is a file that MUST have an SCA <constrainingType/> element as its root element and MUST
conform to the sca-core-1.1.xsd schema and MUST comply with the additional constraints on the document contents as defined
in Appendix C.
SCA Definitions Document:
An SCA Definitions Document is a file that MUST have an SCA <definitions/> element as its root and MUST conform to the sca-definition-1.1.xsd
schema and MUST comply with the additional constraints on the document contents as defined in Appendix C.
SCA Contribution Document:
An SCA Contribution Document is a file that MUST have an SCA <contributution/> element as its root element and MUST conform
to the sca-contribution-1.1.xsd schema and MUST comply with the additional constraints on the document contents as defined
in Appendix C.
SCA Interoperable Packaging Document:
A ZIP file containing SCA Documents and other related artifacts. The ZIP file SHOULD contain a top-level "META-INF" directory,
and SHOULD contain a "META-INF/sca-contribution.xml" file, and MAY contain a "META-INF/sca-contribution-generated.xml" file.
12.2 SCA Runtime
An implementation that claims to conform to the requirements of an SCA Runtime defined in this specification MUST meet the
following conditions:
1.The implementation MUST comply with all statements in Appendix C: Conformance Items related to an SCA Runtime, notably all
MUST statements have to be implemented.
2.The implementation MUST conform to the SCA Policy Framework v 1.1 Specification [Policy].
3.The implementation MUST support and comply with at least one of the OpenCSA Member Section adopted implementation types.4.The implementation MUST support binding.sca and MUST support and conform to the SCA Web Service Binding Specification v
1.1.
motion as amended is above
Resolution: resolve Assembly-101 with amended motion as above w/o
New Issues
Edwards reads the issue from the Jira
Motion: m:Karmarkar s:Nash Defer Assembly-115 until the Policy TC deals with the issue and go to PR without it
Resolution: m:Karmarkar s:Nash Defer Assembly-115 until the Policy TC deals with the issue and go to PR without it w/o
Motion: m:Karmarker s:Edwards Open Assembly-116
Resolution: Assembly-116 opened w/o
Karmarkar discusses proposed resolutions
<Mike Edwards>
Mikes email
<jeff.mischkinsky>
simon: are you ok with deferring this?
Motion: m:Mischkinsky s:Nash Defer Assembly-116
Resolution: m:Mischkinsky s:Nash Defer Assembly-116 w/o
<jeff.mischkinsky>
can i suggest that we simply open and defer the proposed new issues and get on with PR
<jeff.mischkinsky>
if we don't do that, it will take at least until next week
Motion: m:Edwards s:Nash open Assembly-117
<anish>
116 and 117 are related
<jeff.mischkinsky>
nice try bob
Motion: m:Mischkinsky s:Edwards defer Assembly-117
Resolution: defer Assembly-117 w/o
<anish>
this is really a cross-TC co-ordination issue/AI
<jeff.mischkinsky>
if these are editorial, then lets not open the issue
Motion: m:Edwards s:Mischkinsky Close Issue 118 and 119 with no action and give an action to Edwards to sort out the SCA xsd files
Resolution: m:Edwards s:Mischkinsky Close Issue 118 and 119 with no action and give an action to Edwards to sort out the SCA xsd files
w/o
New Issue Assembly-120
<EricW>
1st paragraph in section 8
<jeff.mischkinsky>
i'll second
Motion: m:Edwards s:Mischkinsky Open Issue-120 and to resolve it by removing line 2675 in cd06 rev6
Resolution: m:Edwards s:Mischkinsky Open Issue-120 and to resolve it by removing line 2675 in cd06 rev6
CD03 decision
<anish>
what is the list of issues we would be 'closing' when CD03 is approved?
Motion: m:Edwards Adopt as CD03 the result of the application to CD02 Rev 6 of all of the resolutions made since CD02 Rev6 was prepared
and instruct the editors to prepare the text
<anish>
i.e., which issues were incorporated between CD02 and CD03
<Mike Edwards>
Apply resolutions to Issues 109, 101, 120 on top of CD02 Rev6 to make CD03
<jeff.mischkinsky>
aren't all the resovled issues contained in the minutes
Motion: m:Edwards s:Mischkinsky Adopt as CD03 the result of the application to CD02 Rev 6 of all of the resolutions made since CD02
Rev6 (109, 101, and 120) was prepared and instruct the editors to prepare the text
Chapman:
Since the time has run out, the motion expires
AOB
Schreiber diagnostics output
[Delete this section before publishing the minutes]
final validation: Chair not specified, default chair was assumed
statistics: Schreiber found 93 input lines
edits: Schreiber found the following text-edit commands:
edits: Line 25: s/must/MUST/
edits: Line 30: s/MAY/SHOULD/
edits: Line 34: s/test/text
edits: Line 88: s/byRemove/by removing
command-scribe: Line 4: Since the line number is less than or equal to 20 we will interpret this as a scribename command,
note that the scribe command is deprecated
command-scribe: Line 4: Bob Freund is recognized
command-scribe: Line 4: Bob Freund's nick Bob has been selected
edit-substitute: command on line 25 succeeded, changed line 23 from 'must' to 'MUST'
edit-delete: Line 25 was deleted
edit-substitute: command on line 30 succeeded, changed line 29 from 'MAY' to 'SHOULD'
edit-delete: Line 30 was deleted
edit-substitute: command on line 34 succeeded, changed line 33 from 'test' to 'text'
edit-delete: Line 34 was deleted
edit-substitute: command on line 88 succeeded, changed line 87 from 'byRemove' to 'by removing'
edit-delete: Line 88 was deleted
command-oasisroll: Line 100: Attempting to fetch roll from http://www.oasis-open.org/apps/org/workgroup/sca-assembly/event.php?event_id=16081
system: Transformer: SAXON 9.0.0.6
[End of Schreiber diagnostic output]