Thanks to all for the pointers, will focus on the 1.3 drafts. Gregg
On Wed, Aug 30, 2017 at 9:36 AM, Mitch Kettrick <[email protected]> wrote: > Hi Gregg, > > > > There are also a lot of auto-generated appendices that form a large part > of the document. Sometimes the appendices have all of the auto-generated > sections, including the Swagger definitions, and sometimes they do not. I > suggest that you not look at the total length of the document. If you look > to see how many pages make up the meat of the document prior to the > appendices, they should be pretty close. > > > > As Jin said, OCF 1.0 is not certifiable; these versions were used the kick > off the ISO process. There are known spec bugs in them that were fixed in > OCF 1.3. > > > > Mitch > > > > *From:* 최진혁 [mailto:[email protected]] > *Sent:* Tuesday, August 29, 2017 10:48 PM > *To:* Gregg Reynolds; JinHyeock Choi > *Cc:* iotivity-dev; Mitch Kettrick > *Subject:* RE: Re: [dev] ocf specs? > > > > Gregg > > > > You can find the change history in > > https://workspace.openconnectivity.org/apps/org/workgroup/architecture_tg/ > document.php?document_id=10901 > > along with intermediate versions. > > > > Among them, the main changes are > > v0.3r06: > > Includes the following BZ integrated for review: > > - BZ #1889 [Batch Interface Clarification ] - Updated > > - BZ #1890 [Query behaviour clarity - multiple parameter support] > > > > v0.3r03: > > This is a 0.3 version of the specification. It additionally includes the > following BZ (CRs) integrated for review: > > - BZ #1626 [Overview of CoAP Native Cloud] > > - BZ #1795 [KeepAlive Mechanism in OCF 1.0 needs to be clarified to > support/enable certification] > > - BZ #1866 [RD update for Amsterdam] > > > > Also some editorial polishing in > > https://workspace.openconnectivity.org/apps/org/workgroup/architecture_tg/ > document.php?document_id=11016 > > > > best regards > > > > JinHyeock > > > > > > --------- *Original Message* --------- > > *Sender* : Gregg Reynolds <[email protected]> > > *Date* : 2017-08-30 11:01 (GMT+9) > > *Title* : Re: [dev] ocf specs? > > > > > > > > On Tue, Aug 29, 2017 at 8:33 PM, JinHyeock Choi <[email protected]> wrote: > > + Mitch Kettrick (CPM) > > OCF 1.3. > > The difference between OCF 1.0 & 1.3 are mostly about clarification > with a few additional features (e.g. Easy Setup) & > the CERT would be based on OCF 1.3 > I ask Mitch, CPM, to correct if I misunderstand. > > Thanks. > > > > Here's what worries me a bit: > > > > OCF 1.0.0 Core: 275 pages > > OCF_Core_Specification_IPR_Candidate_v1.3.0: 294 pages > > > > OCF_Security_Specification_v1.0.0: 203 pages > > OCF_Security_Specification_IPR_Candidate_v1.3.0: 188 pages > > > > That seems like some pretty big changes. Is there a list somewhere? > > > > Thanks again, > > > > Gregg > > > > > > JinHyeock > > p.s. > Taking 2 month IPR review period into consideration, > the change is the 4, 5 month's work. > > > > > On Wed, Aug 30, 2017 at 10:24 AM, Gregg Reynolds <[email protected]> > wrote: > > > > > > On Tue, Aug 29, 2017 at 8:24 PM, Gregg Reynolds <[email protected]> > wrote: > >> > >> OCF 1.0.0 was released on June 27, 2017. > >> > >> On August 18 2017 - not even 1 month later - a draft for OCF 1.3 was > >> released. > >> > > Ok, not even 2 months later. ;) > > > >> > >> Which one should I read? Which one does Iotivity plan to support, and > >> when? > >> > >> Thanks, > >> > >> Gregg > > > > > > > > > _______________________________________________ > > iotivity-dev mailing list > > [email protected] > > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > > > > > > _______________________________________________ > > iotivity-dev mailing list > > [email protected] > > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > > > > > > > > > > <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> > Virus-free. > www.avg.com > <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> > <#m_-3531753834214622843_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >
_______________________________________________ iotivity-dev mailing list [email protected] https://lists.iotivity.org/mailman/listinfo/iotivity-dev
