[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [cmis] PWC version label
Ok, that totally makes sense. Thanks for sharing your implementation's behavior. Florent On Mon, Jan 7, 2013 at 11:11 PM, Matt Mooty <mamooty@exchange.microsoft.com> wrote: > Florent, > > Sorry, I misspoke. If minor versioning is enabled for that SharePoint repository then the PWC would be 2.1, regardless of your future intentions of major=true/false. If you then check in a major version, the PWC of 2.1 will be checked in as a major version of 3.0. > > Thanks, > Matt > > -----Original Message----- > From: Florent Guillaume [mailto:fg@nuxeo.com] > Sent: Sunday, January 6, 2013 10:48 AM > To: Matt Mooty > Cc: cmis > Subject: Re: [cmis] PWC version label > > Hi, > > But one specifies major=true/false at checkin time, not at the time the PWC is created by checkout. So the PWC cannot reflect something that is not yet done. I'm confused. > > Thanks, > Florent > > On Fri, Jan 4, 2013 at 11:20 PM, Matt Mooty <mamooty@exchange.microsoft.com> wrote: >> Florent, >> >> SharePoint has a notion of minor versions, so if you have major=false and minor versioning is enabled for that SharePoint repository then the PWC would be 2.1 in our example, as you suspected. I hope this helps! >> >> Thanks, >> Matt >> >> -----Original Message----- >> From: Florent Guillaume [mailto:fg@nuxeo.com] >> Sent: Friday, January 4, 2013 12:12 PM >> To: Matt Mooty >> Cc: cmis >> Subject: Re: [cmis] PWC version label >> >> Hi Matt, >> >> Thanks for the info! >> So if the last version is 2.0, and the PWC is therefore 3.0 according to what you said, what happens if you pass major=false when doing the checkIn? Does it become 2.1 nevertheless, or is the notion of non-major versions not used by SharePoint 2013? >> >> Thanks, >> Florent >> >> On Fri, Jan 4, 2013 at 5:49 PM, Matt Mooty <mamooty@exchange.microsoft.com> wrote: >>> Florent, >>> >>> I can tell you that as of SharePoint 2013, our CMIS producer does provide a cmis:versionLabel for the PWC of a document. It is the next version, or what that PWC would become if checked in. For example, if a document has a cmis:versionLabel of 2.0, its PWC would be 3.0. As you said it is somewhat up to interpretation here, but that is the choice we've made. >>> >>> Thanks, >>> Matt Mooty >>> Software Development Engineer >>> Microsoft >>> >>> -----Original Message----- >>> From: cmis@lists.oasis-open.org [mailto:cmis@lists.oasis-open.org] On >>> Behalf Of Florent Guillaume >>> Sent: Friday, January 4, 2013 7:18 AM >>> To: cmis >>> Subject: [cmis] PWC version label >>> >>> Hi, and happy new year! >>> >>> Should a PWC have a cmis:versionLabel? >>> >>> I guess that the spec leaves it open to the server to do anything, so I'd be curious to know for your respective products what has been chosen (i.e. use the version label of the latest version, a special marker, or something else). >>> >>> Thanks, >>> Florent >>> >>> -- >>> Florent Guillaume, Director of R&D, Nuxeo Open Source, Java EE based, Enterprise Content Management (ECM) >>> http://www.nuxeo.com http://www.nuxeo.org +33 1 40 33 79 87 >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: cmis-unsubscribe@lists.oasis-open.org >>> For additional commands, e-mail: cmis-help@lists.oasis-open.org >>> >> >> >> >> -- >> Florent Guillaume, Director of R&D, Nuxeo Open Source, Java EE based, Enterprise Content Management (ECM) >> http://www.nuxeo.com http://www.nuxeo.org +33 1 40 33 79 87 > > > > -- > Florent Guillaume, Director of R&D, Nuxeo Open Source, Java EE based, Enterprise Content Management (ECM) > http://www.nuxeo.com http://www.nuxeo.org +33 1 40 33 79 87 -- Florent Guillaume, Director of R&D, Nuxeo Open Source, Java EE based, Enterprise Content Management (ECM) http://www.nuxeo.com http://www.nuxeo.org +33 1 40 33 79 87
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]