[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [emergency-ms] Re: [emergency] Re: [emergency-ms] updating X.1303 - Common Alerting Protocol
Hi Elysa, I'm including Jamie as he can give you more specifics. Just for everyone's benefit here's a brief overview: OASIS has a Liaison Policy that describes two categories of liaison relationships: Org-to-Org and TC-to-WG/TC/SC/etc. All submissions to another standards body must be done at the OASIS/org-to-org level and follow the procedure given here (sorry, someone really needs to add section numbers to the policy): http://www.oasis-open.org/committees/liaison_policy.php#submitwork Beyond that, there's an established relationship with ITU-T (an MoU or some other sort of agreement between the two orgs) And there's the TC <-> ITU-T WG liaison which is intended to enable communication and input into related work. http://www.oasis-open.org/committees/liaison_policy.php#liaisons As you said, it's completely up to the TC whether they want to invest time in CAP 1.2 to then submit it to ITU-T, or to continue with the current plan of submitting CAP 2.0 when ready. Of course it's always best if a Standard has been approved by a de jure standards body that the two works are kept in sync with each other; if CAP 2.0 is still far off in the distance it may make sense to take the steps necessary to send CAP 1.2 over to ITU-T. Best regards, Mary On Nov 18, 2010, at 1:14 PM, Elysa Jones wrote: > Hi Mary, > > It is my understanding that there is an existing liaison between OASIS and ITU-T. That being given, we ad hear to submission requirements 1a-1c of the liaison policy submission requirements. In an email today, I have asked the EM-TC to consider whether we wish to do this at all. I'm expecting to just get a general sense of the committees interest in our meeting next Tues. If we indeed want to go forward with this, there are a few things we might want to clean up that have been identified since the ratification of CAP 1.2. If an errata is required, I'd rather get that taken care of before attempting any alignment. That topic will be addressed in our meeting on Tues also. If we do agree in general to move forward, I will work through the remaining steps per the liaison policy. > > Thank you as always for keeping us on the right track, > > Elysa Jones, Chair > OASIS EM-TC > CTO, Warning Systems, Inc. > > At 11:53 AM 11/18/2010, Mary McRae wrote: >> Hi Elysa et al, >> >> I do not believe that CAP 1.2 has been submitted to ITU-T; that submission would need to follow the process described in the Liaison Policy before it should be moved forward in any way. >> >> Regards, >> >> Mary >> >> >> >> >> >> On Nov 18, 2010, at 11:56 AM, Elysa Jones wrote: >> >> > Hi Tony, >> > >> > Thank you for your note informing us of the Q4/17 interest in advancing the .1303 to align with CAP 1.2. I appreciate any updates you or additional information/schedule/etc from your meeting next month. >> > >> > Kind regards, >> > >> > Elysa Jones, Chair >> > OASIS EM-TC >> > CTO Warning Systems, Inc. >> > >> > >> > At 11:23 AM 11/16/2010, Tony Rutkowski wrote: >> >> Dear OASIS colleagues, >> >> >> >> The following note/information from the ITU-T >> >> Q4/17 rapporteur group which is meeting in >> >> Geneva in three weeks may be of interest. >> >> We'll keep you updated as this work proceeds. >> >> >> >> best, >> >> tony rutkowski (ITU-T Q4/17 rapporteur) >> >> >> >>> Dear colleagues, >> >>> >> >>> As you may be aware, Q4 is responsible for >> >>> the Common Alerting Protocol standard in >> >>> cooperation with OASIS. X.1303 (09/2007) >> >>> is equivalent to OASIS CAP 1.1 - with the >> >>> added feature of an ASN.1 module. >> >>> >> >>> OASIS revised the specification and the >> >>> 1.2 version was balloted and adopted in >> >>> July 2010. See attached. So X.1303 >> >>> needs to be updated based on the new >> >>> version. >> >>> >> >>> It would be especially useful to know >> >>> if our resident ASN.1 experts in Q12 >> >>> are available to revise the corresponding >> >>> CAP ASN.1 module in clause 8.3 of X.1303. >> >>> >> >>> CAP is now being extensively used worldwide >> >>> by user communities and national authorities. >> >>> Many EU countries, China and the US have >> >>> been especially active. The ITU-T also has >> >>> a close working relationship with WMO in >> >>> providing for CAP implementations, and Q12 >> >>> and Q4 have a joint OID ARC that is available >> >>> with the associated Rec. X.alerting. >> >>> >> >>> It is important for Q4/17 to progress this >> >>> work at our upcoming meeting while we await >> >>> for the formal liaison statement to slowwwwly >> >>> arrive. >> >>> >> >>> thanks, >> >>> tony >> >> >> >> >> >> >> >> >> >> >> >> --------------------------------------------------------------------- >> >> 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]