Re: [core] CoRE Pub/Sub proposal to resolve the one remaining major issue

[Jim Schaad <[e-mail]>]

I have a couple of clarifications that I would to get on this proposal:

1.  It is not clear from the document, but I assume that the concept of
topics as children of topics is still supported.    Thus  GET
</ps/topic/1234/5677>  is a viable thing.

2.  Are we completely dumping link format in favor of CoRAL at this point?
This is not something that I would object to I just want to be clear.

3.  The picture in the overview and the examples given do not present the
same picture.  I assume that there does not need to be any link between the
path where the data exists and the path for the topic description.  It could
be a child, as in the picture in the overview, in a parallel tree with the
same naming, as in the examples in the document, or it could have a
completely different location - including a URL to a different RS.  Is this
right?

Jim


From: core <[e-mail]> On Behalf Of Michael Koster
Sent: Monday, July 8, 2019 1:42 PM
To: core <[e-mail]>
Subject: [core] CoRE Pub/Sub proposal to resolve the one remaining major
issue

Hi,

Klaus, Ari, and I created a proposal to resolve the "empty topic" issue (and
others) without using a new status code or multipart content format.

Rather than update the draft, which technically requires WG consensus, we
decided to publish the proposal and collect review comments between now and
Montreal:
https://github.com/core-wg/pubsub/blob/master/proposal.txt

We will take time at the WISHI hackathon to further refine it, and prepare a
summary for the CoRE WG session.

We would like implementers in particular to review the proposal.

Best regards,

Michael