[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [office-requirements] Starting up ...
Thanks Mary for the clarification. Bob 2008/9/8 Mary McRae <mary.mcrae@oasis-open.org>: > Hi everyone, > > This is actually in reply to Bob's message which I must have missed. > Here's the rules: > > 1. All comments by non-TC members must be submitted via the TC comment list. > In order to post a comment you must first subscribe; confirmation of the > subscription acknowledges the commenter's acceptance of the OASIS feedback > license.* > > 2. Any and all content and systems used by technical committees must be > hosted on OASIS servers, unless otherwise authorized by the OASIS TC > Administrator. > > What that means is: > a) if OASIS provides a particular toolset/app that app must be used. (For > instance, OASIS provides moin-moin wikis for any TC that asks. A TC cannot > set up and use a moinmoin wiki (or any other wiki for that matter) > elsewhere.) > b) if there's no app currently available to meet a particular need, OASIS IT > will evaluate the feasibility of hosting an identified app given our current > infrastructure. > c) if neither a) nor b) are true, a TC can petition the TC Administrator to > make use of an external resource. That resource will need to match all OASIS > requirements with regard to read/write access and visibility as well as > assurances of support, availability, etc. > > Regards, > > Mary > >> -----Original Message----- >> From: Doug Mahugh [mailto:Doug.Mahugh@microsoft.com] >> Sent: Monday, September 08, 2008 9:57 AM >> To: Bob Jolliffe; office-requirements@lists.oasis-open.org >> Subject: RE: [office-requirements] Starting up ... >> >> Bob, >> >> I agree, there does not seem to be an existing system that is tailored >> to the needs of public comment collection. >> >> Regarding your question, there has indeed been a proposal to build a >> system for use by WG4 to automate the collection of comments in >> IS29500. It is a relatively simple web application, and uses a data- >> entry form that is based on the G5 Defect Report form included in the >> JTC 1 Directives. I demonstrated a prototype of this system at the >> London meeting of AHG1/AHG2 in July. The system will be ready to go >> live as of the Jeju plenary on the 1st of October, however that system >> is currently planned for NB/liaison comments only. We discussed a >> public comment collection system in London, and some members were of >> the opinion that such a system should employ other technologies such as >> topic maps, beyond the simple relational model used by the system we >> put together for use by WG4. At this point the public comment >> collection process for IS29500 is an open item that will be >> discussed/decided in Jeju. >> >> Regards, >> Doug >> >> -----Original Message----- >> From: Bob Jolliffe [mailto:bobjolliffe@gmail.com] >> Sent: Friday, September 05, 2008 7:48 AM >> To: office-requirements@lists.oasis-open.org >> Subject: Re: [office-requirements] Starting up ... >> >> Rob, >> >> Thanks for the feedback. I had in mind points 1 and 3 below but I >> think the second item (regarding tooling) is a really important one. >> It has come up on a TC call before and was also a point of discussion >> around DIS29500 processing of comments. >> >> I know ECMA created something for producing the final resolution of >> comments document. Various NBs (including UK and SA) made use - or >> abuse - of a software issue-tracking program called mantis to try to >> organise the work. In both of these cases they were not dealing with >> the front end process of actually collecting the comments. >> >> I think the general conclusion to be made is that (1) tooling is >> really important where there is significant public interest in a >> standard and (2) the specific tools (if it is specific tools which are >> required) don't yet exist. Its also not just an OASIS problem - I know >> SC34 were also considering the issue regarding collection of comments >> for OOXML. >> >> Doug, do you know if there has been any proposal there? >> >> Does anybody know what can or can't be hosted on oasis? Or are we >> restricted to the basic structure which is provided? Would it be >> allowed (or even proper) to host a "tool" outside of oasis? >> >> Regards >> Bob >> >> 2008/9/4 <robert_weir@us.ibm.com>: >> > bobj@dst.gov.za wrote on 09/04/2008 06:24:28 AM: >> > >> >> >> >> Greetings and apologies for the long quietness. I was in Brazil >> >> last week and returned to something of an email blackout. I am back >> >> up and running again now. >> >> >> >> We need to plan for a an inaugural first conference call. Can I >> >> suggest Wednesday in two weeks (17 Sep)? Looking at the current >> >> geographical spread of members of the SC I am guessing that the same >> >> time as the TC call, 14h00 GMT, should be at least workable for most >> > people. >> >> >> > >> > I can make it then. >> > >> >> In the interim I will work on an agenda (and figure out how to set >> >> up the call) so please send through any agenda items you might want >> >> to add. The first call is likely to be a fairly open discussion as >> >> we brainstorm modes of operation. >> >> >> > >> > 1. Appoint editor(s) for the report >> > >> > 2. How do we organize our work, in terms of tooling? We'll be >> dealing >> > with 200-500 ideas if we open this up to public input. We need to >> > classify, short, prioritize these all. A spreadsheet gives the >> > sorting/filtering needed, but limits us to a single editor at a time. >> A >> > wiki is more open, but doesn't have support for sorting and >> filtering. >> > >> > 3. Outreach for feature ideas -- who/how/when? >> > >> > -Rob >> > >> > --------------------------------------------------------------------- >> > To unsubscribe from this mail list, you must leave the OASIS TC that >> > generates this mail. Follow this link to all your TCs in OASIS at: >> > https://www.oasis- >> open.org/apps/org/workgroup/portal/my_workgroups.php >> > >> > >> > >> >> --------------------------------------------------------------------- >> To unsubscribe from this mail list, you must leave the OASIS TC that >> generates this mail. Follow this link to all your TCs in OASIS at: >> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe from this mail list, you must leave the OASIS TC that >> generates this mail. Follow this link to all your TCs in OASIS at: >> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]