-
Notifications
You must be signed in to change notification settings - Fork 2
Expand file tree
/
Copy pathcommunity.html
More file actions
237 lines (214 loc) · 11.8 KB
/
community.html
File metadata and controls
237 lines (214 loc) · 11.8 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="description" content="Common Map Application Progamming Interface">
<meta name="keywords" content="map, communication, pub/sub, channel, widget, owf, ozone">
<meta name="Copyright" content="2014 copyright">
<title>CMAPI - Community</title>
<link rel="stylesheet" type="text/css" href="css/reset.css" />
<link rel="stylesheet" type="text/css" href="css/main.css" />
<!--[if lt IE 9]>
<script src="js/html5shiv.js"></script>
<![endif]-->
<script src="js/jquery-1.2.6.min.js" type="text/javascript"></script>
<script type="text/javascript">
// Add .last class to certain lists
$(document).ready(function() {
$("ul.lst li:last").addClass("last");
});
</script>
</head>
<body>
<a href="https://github.com/CMAPI/cmapi/tree/v1.3.0">
<img style="position: absolute; top: 0; right: 0; border: 0;" src="https://camo.githubusercontent.com/652c5b9acfaddf3a9c326fa6bde407b87f7be0f4/68747470733a2f2f73332e616d617a6f6e6177732e636f6d2f6769746875622f726962626f6e732f666f726b6d655f72696768745f6f72616e67655f6666373630302e706e67" alt="Fork me on GitHub" data-canonical-src="https://s3.amazonaws.com/github/ribbons/forkme_right_orange_ff7600.png">
</a>
<header>
<div class="header-inner">
<div class="header-nav">
<nav class="nav-header">
<ul>
<li class="headerText">
Common Map API
</li>
<li>
<a href="index.html">
<strong>Home</strong>
</a>
</li>
<li>
<a href="versions.html">
<strong>Versions</strong>
</a>
</li>
<li>
<a href="usage.html">
<strong>Usage</strong>
</a>
</li>
<li style="border-right:none;">
<a href="#" style="background-color: #ffffff; color:#008AB8; ">
<strong>Community</strong>
</a>
</li>
</ul>
</nav>
</div>
<!-- /header-nav -->
</div>
<!-- /header-inner -->
</header>
<!-- /header -->
<div class="content">
<div class="content-inner group">
<aside class="aside-right">
<ol class="pod group">
<li class="group">
<div>
<h2>Connect</h2>
<br/>
<p class="indent">Get connected to the CMAPI community with our Google™ Group.</p>
<button class="right" title="Join the CMAPI Google Group" onclick="window.open('https://groups.google.com/forum/#!forum/common-map-widget-api/join')">Join Group</button>
</div>
</li>
<li class="group">
<div>
<h2>Announcements</h2>
<br/>
<ul class="indent">
<li>
<h4>v1.3.0 Completion</h4>
<br/>
<p class="indent">The CMAPI Technical Committee (TC) has moved version 1.3.0 to "Release Candidate". Though not the final specification, the Release Candidate stamp means that the TC believes that the specification is "technically complete" and stable enough for projects to reference and implement.</p>
<hr/>
</li>
<li>
<h4>OGC Adoption</h4>
<br/>
<p class="indent">The CMAPI Technical committee is working with the Open Geospatial Consortium (OGC) on the possibility of CMAPI becoming an OGC standard</p>
</li>
</ul>
</div>
</li>
<li class="group third">
<div>
<h2>Oversight</h2>
<br/>
<ul class="indent">
<li>
<a href="https://www.nga.mil" target="_blanl">National Geospatial Agency (NGA)</a>
</li>
<li>
Defense Intelligence Information Enterprise (DI2E)
</li>
</ul>
<hr/>
<h2>Editors</h2>
<br/>
<ul class="indent">
<li>
<a href="mailto:chris.bashioum@volant-associates.com">Chris Bashioum</a>
</li>
<li>
<a href="mailto:eric.j.briscoe@gmail.com">Eric Briscoe</a>
</li>
</ul>
</div>
</li>
</ol>
</aside>
<section class="main">
<div class="content-outer mashup" style="position: relative">
<img id="mashupimg" src="img/Fotolia_67042461_S_crop.jpg" alt="Teamwork image" title="© treenabeena - Fotolia.com" />
</div>
<div class="content-outer welcome group">
<ul>
<li>
<strong>Process</strong>
</li>
<li style="font-size: 1.2em; line-height: 1.5em;">
The scope of this technical committee is limited to creating a technical specification of the channels, messages, behaviours and other technical details of what is needed to enable interoperability between map widgets and other non-map widgets.
<br/>
<br/>
Note that the 1.0, 1.1, and 1.2 series of the CMAPI specification were targeted to the Ozone Widget Framework (OWF). Not that it was necessarily limited to OWF, but that there was no care taken to ensure that it was usable outside of OWF. Version 1.3 was carefully gone through to ensure that any OWF dependencies (whether explicit or implicit) were removed and that the specification is applicable to all browser-based widgets (e.g., HTML5 based widgets)
<br/>
<br/>The criteria for promulgating a new version of the specification includes:
<ol type="A" style="padding-left: 50px;">
<li>A submission of the JSON Schema for new channels, or updated JSON schema for changes to an existing channel</li>
<li>Agreement via informal voting that the specification is technically complete, and sufficiently stable for implementation - at which time the specification will be moved to "Release Candidate"</li>
<li>At least two implementations of the specification showing interoperability</li>
<li>Agreement via formal voting that the specification is sufficiently complete, with at least 75% of the technical committee voting for approval</li>
</ol>
<br/>
<h2><b>Meeting Mechanisms and Frequency</b>
</h2>
The technical committee will meet on the first and third Thursday of every month, from 1-3 Eastern Time via dial-in. Dial-in information and agenda are sent to the CMAPI mailing list prior to each meeting.
<br/>
<br/>
<h2><b>Communication Mechanisms</b>
</h2>
Outside of the regular meetings, updates, meeting notices, and regular collaboration are expected to occur via email at common-map-widget-api@googlegroups.com. This allows communications to be open and to be recorded for those who might join the group later.
<br/>
<br/>
<h2><b>Technical Committee Members</b>
</h2>
Bi-weekly dial-ins are expected to be no more that two hours in length. Members are expected to participate in the bi-weekly dial-ins and to review materials sent out via the group mailing list.
<br/>
<br/>
<h2><b>Editors</b>
</h2>
The role of editor is currently limited to 3 members of the technical committee. Editors are expected to perform the following functions
<ol type="A" style="padding-left: 50px;">
<li>Lead, and capture minutes from, the bi-weekly dial-ins</li>
<li>Make updates to the specification based on Technical Committee input</li>
<li>Send notifications to the group mailing list as updates are accomplished and ready for TC review</li>
</ol>
<br/>
<br/>
<h2><b>Voting and Participation Rules</b>
</h2>
In order to be able to formerly vote on the specification, a member of the technical committee must regularly attend the TC meetings, and actively participate in the email collaboration. Informal voting will be done on portions of the specification as those portions are completed, and when the specification is ready to be moved to "Release Candidate". A Formal vote on the overall specification will be taken when the editors consider all the criteria for promulgating a new version are complete. Note that voting on the specification applies only to the technical details of the specification itself, and does NOT imply any commitment to implement the specification.
<br/>
<br/>
<h2><b>Anticipated Audience</b>
</h2>
This specification is targeted for widget developers, and developers of libraries to be re-used by widget developers.
</li>
</ul>
</div>
</section>
</div>
</div>
<!-- end content -->
<footer>
<div id="footer-inner">
<p>© 2014 CMAPI</p>
<nav class="nav-footer">
<ul>
<li>
<a href="index.html">
<strong>Home</strong>
</a>
</li>
<li>
<a href="versions.html">
<strong>Versions</strong>
</a>
</li>
<li>
<a href="usage.html">
<strong>Usage</strong>
</a>
</li>
<li style="border-right:none;">
<a href="#" style="background-color: #ffffff; color:#008AB8; ">
<strong>Community</strong>
</a>
</li>
</ul>
</div>
</nav>
</footer>
</body>
</html>