This wiki has undergone a migration to Confluence found Here
Difference between revisions of "20120115 arb WGM SanAntonio Minutes"
Jump to navigation
Jump to search
(3 intermediate revisions by the same user not shown) | |||
Line 11: | Line 11: | ||
###1 Considered- No action required | ###1 Considered- No action required | ||
###14 not related - an incorrect spreadsheet was uploaded by an affirmative balloter. | ###14 not related - an incorrect spreadsheet was uploaded by an affirmative balloter. | ||
+ | ##Membership changes | ||
+ | ##Glossary | ||
+ | ##Next Steps | ||
+ | ##Revisit Role | ||
+ | ##Architecture Project | ||
+ | ###FIM co-sponsorship | ||
+ | ##OO project and Implications | ||
+ | ###SOA representation | ||
+ | ###Message representation | ||
+ | |||
#Sunday Q2 | #Sunday Q2 | ||
##Call to order | ##Call to order | ||
##Substantivity: | ##Substantivity: | ||
− | ##A substantive change is one that changes the semantics of a given specification, i.e. representational changes should <<not>> be considered substantive in the context of the source specification itself <<unless>> such representational changes could substantively change down-stream derivative products of the specification, including either/both derivative semantics and/or derivative serializations or other wire-format-sensitive constructs. | + | ###This comes up because there is no substantive(ity) definition for non-wire format documents |
+ | ###A substantive change is one that changes the semantics of a given specification, i.e. representational changes should <<not>> be considered substantive in the context of the source specification itself <<unless>> such representational changes could substantively change down-stream derivative products of the specification, including either/both derivative semantics and/or derivative serializations or other wire-format-sensitive constructs. | ||
#Sunday Q3 | #Sunday Q3 | ||
##Call to order | ##Call to order | ||
− | ## | + | ##V3 Substantive changes |
+ | |||
+ | ##TBD | ||
#Tuesday Q4 | #Tuesday Q4 | ||
##Call to order | ##Call to order | ||
##TBD | ##TBD | ||
+ | #Wednesday Q1 | ||
+ | ## - Joint with SOA at SOA | ||
#Thursday Q3 | #Thursday Q3 | ||
##Call to order | ##Call to order |
Latest revision as of 15:29, 15 January 2012
Detailed Agenda
Click here for meeting-at-a-glance
- Sunday Q1
- Call to order
- Agenda and Minute approval
- Saif Canonical Ballot Reconcillation
- 19 comments
- 2 persuasive with mod
- 1 Persuasive
- 1 Considered- No action required
- 14 not related - an incorrect spreadsheet was uploaded by an affirmative balloter.
- Membership changes
- Glossary
- Next Steps
- Revisit Role
- Architecture Project
- FIM co-sponsorship
- OO project and Implications
- SOA representation
- Message representation
- Sunday Q2
- Call to order
- Substantivity:
- This comes up because there is no substantive(ity) definition for non-wire format documents
- A substantive change is one that changes the semantics of a given specification, i.e. representational changes should <<not>> be considered substantive in the context of the source specification itself <<unless>> such representational changes could substantively change down-stream derivative products of the specification, including either/both derivative semantics and/or derivative serializations or other wire-format-sensitive constructs.
- Sunday Q3
- Call to order
- V3 Substantive changes
- TBD
- Tuesday Q4
- Call to order
- TBD
- Wednesday Q1
- - Joint with SOA at SOA
- Thursday Q3
- Call to order
- TBD
- Thursday Q4
- Call to order
- Wrap up
- Agenda for future Telcons, etc.
Tony Julian 17:28, 15 September 2011 (EDT)