36 | {TBD: remove next sentence before submitting for 37 | approval} This Charter is work in progress. To submit feedback, 38 | please use https://github.com/edrlab/bd-comics-manga Issues 39 | where Charter is being developed. 40 |
41 |55 | Webtoons, Turbomedia, Motion Comics, Web Comics, Visual novels App, Parallax strips,… (native digital comics) on one hand, digitized / homothetic BD, comics and manga on the other hand, are the two faces of a digital visual narrative market that is growing extremely fast in several regions of the world; reading through the Web on smartphones becomes natural for many people. All variants share a common underlying model, which must be clearly expressed before a universal publication format can be designed and released as a Web standard. 56 |
57 |58 | The mission of the BD Comics Manga Community Group (*) is to study and document a conceptual model representing all kinds of visual narratives expressed digitally. 59 |
60 |61 | This Community Group will also be a forum for creators, authors and artists willing to express their core needs. This point is to be considered as capital in a field where the desires of the authors / artists and the technologies used in the publishing world are not always in adequacy. 62 |
63 |64 | (*) Bande dessinée, Comics, Manga are terms broadly used for sequential art in Europe, USA and Asia; this underlies the global scope of the study. 65 |
66 |70 | The BD Comics Manga CG is taking on from the work carried out at the IDPF (www.idpf.org) and at EDRLab (www.edrlab.org, BDCoMa WG). 71 |
72 |73 | It will document the recurring structure and properties expressed in all sorts of visual narratives use cases and define a taxonomy of features such as visual effects and layouts used consistently and repeatedly in current productions (i.e. document the conceptual model of visual narratives). 74 |
75 |76 | It will also set up a catalog of references to particular examples of visual narratives, interesting from a formal point of view, originating from different parts of the world. And it will inform authors and publishers about the documents which could be useful for them and the Web technologies they are likely to use for the creation of digital visual narratives.
77 |78 | This work will then be reviewed by the W3C Publishing Business Group. It may be used as a base for an evolution of Web Publications, their packaged counterpart ("EPUB 4"), HTML, CSS, and SVG among others. 79 |
80 |84 | Any technical work on an extention of EPUB or Web Publications is out scope of this community group. This technical work will certainly be seized by the Publishing Working Group after this CG has delivered its conclusions. 85 |
86 |101 | The CG will liaise with the European Digital Reading Lab (EDRLab, based in Europe) and with the Advanced Publishing Lab (APL, based in Japan), both membership organizations whose members belong to the publishing industry. 102 |
103 |104 | Other organizations may be added to these liaisons in subsequent versions of this charter. 105 |
106 |107 | This CG will report to the W3C Publishing Business Group. It will also exchange information with other groups in W3C such as the CSS Working Group.
108 |112 | The group operates under the Community and Business 114 | Group Process. Terms in this Charter that conflict with those of the 115 | Community and Business Group Process are void. 116 |
117 |118 | As with other Community Groups, W3C seeks organizational licensing 119 | commitments under the W3C Community 121 | Contributor License Agreement (CLA). When people request to 122 | participate without representing their organization's legal interests, 123 | W3C will in general approve those requests for this group with the 124 | following understanding: W3C will seek and expect an organizational 125 | commitment under the CLA starting with the individual's first request to 126 | make a contribution to a group Deliverable. 127 | The section on Contribution Mechanics describes 128 | how W3C expects to monitor these contribution requests. 129 |
130 | 131 |132 | The W3C Code of 133 | Ethics and Professional Conduct applies to participation in 134 | this group. 135 |
136 | 137 |141 | The group will not publish Specifications. See 142 | below for how to modify the charter. 143 |
144 |148 | Reports and other documents created in the Community Group will use the 150 | W3C Software and Document License. 151 |
152 |153 | Community Group participants agree to make all contributions in the 154 | GitHub repo the group is using for the particular document. This may be 155 | in the form of a pull request (preferred), by raising an issue, or by 156 | adding a comment to an existing issue. 157 |
158 |159 | All Github repositories attached to the Community Group must contain a 160 | copy of the CONTRIBUTING 162 | and LICENSE 164 | files. 165 |
166 |170 | The group will conduct all of its work in public. 171 | All technical work will occur in its GitHub repositories 172 | (and not in mailing list discussions). This is to ensure contributions 173 | can be tracked through a software tool. 174 |
175 |176 | Meetings may be restricted to Community Group participants, but a public 177 | summary or minutes must be posted to the group's public mailing list, or 178 | to a GitHub issue if the group uses GitHub. 179 |
180 |184 | This group will seek to make decisions where there is consensus. 185 | The Chairs assess consensus (they are Committers), or where consensus isn't 186 | clear there is a Call for Consensus [CfC] to allow multi-day online 187 | feedback for a proposed course of action. After discussion and 188 | due consideration of different opinions, a decision should be publicly 189 | recorded (where GitHub is used as the resolution of an Issue). 190 |
191 |192 | If substantial disagreement remains (e.g. the group is divided) and the 193 | group needs to decide an Issue in order to continue to make progress, the 194 | Committers will choose an alternative that had substantial support (with 195 | a vote of Committers if necessary). Individuals who disagree with the 196 | choice are strongly encouraged to take ownership of their objection by 197 | taking ownership of an alternative fork. This is explicitly allowed (and 198 | preferred to blocking progress) with a goal of letting implementation 199 | experience inform which spec is ultimately chosen by the group to move 200 | ahead with. 201 |
202 |203 | Any decisions reached at any meeting are tentative and should be recorded 204 | in a GitHub Issue. Any group participant may object to a decision reached 205 | at an online or in-person meeting within 7 days of publication of the 206 | decision provided that they include clear technical reasons for their 207 | objection. The Chairs will facilitate discussion to try to resolve the 208 | objection according to the decision process. 209 |
210 |211 | It is the Chairs' responsibility to ensure that the decision process is 212 | fair, respects the consensus of the CG, and does not unreasonably favour 213 | or discriminate against any group participant or their employer. 214 |
215 |219 | Participants in this group choose their Chair(s) and can replace their 220 | Chair(s) at any time using whatever means they prefer. However, if 5 221 | participants, no two from the same organisation, call for an election, 222 | the group must use the following process to replace any current Chair(s) 223 | with a new Chair, consulting the Community Development Lead on election 224 | operations (e.g., voting infrastructure and using RFC 2777). 226 |
227 |242 | Participants dissatisfied with the outcome of an election may ask the 243 | Community Development Lead to intervene. The Community Development Lead, 244 | after evaluating the election, may take any action including no action. 245 |
246 |250 | The group can decide to work on a proposed amended charter, editing the 251 | text using the Decision Process described above. 252 | The decision on whether to adopt the amended charter is made by 253 | conducting a 30-day vote on the proposed new charter. The new charter, if 254 | approved, takes effect on either the proposed date in the charter itself, 255 | or 7 days after the result of the election is announced, whichever is 256 | later. A new charter must receive 2/3 of the votes cast in the approval 257 | vote to pass. The group may make simple corrections to the charter such 258 | as deliverable dates by the simpler group decision process rather than 259 | this charter amendment process. The group will use the amendment process 260 | for any substantive changes to the goals, scope, deliverables, decision 261 | process or rules for amending the charter. 262 |
263 | 264 | 265 | --------------------------------------------------------------------------------