Michel Veillette wrote: > Hi Thomas > > > > To facilitate the creation of this encoding, can you provide an example > of what you want to archive using SQL style statement for example. > > > > For example: > > > > INSERT INTO CellList > > (CellID, SlotframeID, SlotOffset, ChannelOffset, LinkOption, > LinkType, CellType, NodeAddress, TrackID) > > VALUES > > (1, 0, 2, 5, 0x01, 0, 0, ?leafref);
An insert would generally be modeled as a POST in REST, returning the server-chosen URI (which would include the CellID if that is indeed server-chosen) in a set of Location Options. > Couple of comments: > > · CellID > > The CellID need to be unique since it’s the key within the CellList. > > How the assignment of CellIDs is expected to be done? > > To be unique, should the server assign this value and return the value > assigned to the client? (This might require the use of a RPC) > > · TrackID > > Currently, the TrackID is implemented using the datatype leafref which > is not supported by the current COMI draft > > · draft-vanderstok-core-patch-00 > > The current draft introducing patch don’t seem to allow multiple > insertion within a list. If this is not the case, It will be nice to > have an example added to this draft. Merge-Patch indeed does not address insertion into an array, only into a hash. But that is a matter of defining the PATCH format; we are not limited to just RFC 6902 or 7386. Grüße, Carsten _______________________________________________ 6tisch mailing list [email protected] https://www.ietf.org/mailman/listinfo/6tisch
