 this topic (through a SUB /people/1) will receive a notification. Notice that PATCH could be use also.
Same apply in the opposite, if a client post a message in the topic PUB /people/1 "loveBeer":true, the corresponding resource will be update.
You would end up with this kind of architecture (picture is taken from this blog) :

 Hint 2: Resources creations are also messages 
From the previous example, you could think...

Hey, what about client creating a new resource through POST /people?

You will create a new resource and a message will be published in the corresponding topic (/people)
For example, if a client performs POST /people { "name":"schneider", loveBeer:true}. Clients that have performed SUB /people will receive the notification
So you could think again and say:

Hey, what about client publishing a message in a topic through PUB /people?
  Vice-versa, it will create a message in the topic /people and create a new sub-resource /people/:newid

Imagine a client make PUB /people {"name":"Ailurus", "loveBeer":true}, when message is receive, a new resource /people/42 is created and the clients have subscribed to /people are notified.
 Bonus hint: Consider meta-data 
That's not really a hint, since it's not really related to a mapping between resource URI/topic :)
From this blog, meta-data could be added in the payload of the messages published (but not in your resource representation).
Mainly because MQTT Client that subscribe to a topic don't know if a resource is updated or created, whereas a REST client know this information (when a resource is created, through the location header)
So consider to add a metadata such as "event": "created" or `"event": "modified"
You could even think about when a resource is created, in addition to put {"event": "created"} in the payload, to give the resource URI/topic name, such as {"event": "created", "location": "people/42"}

 Q:

Convolution Kernels for Image Filtering

As I understand it, in image processing, when it is desired to apply a filter of some sort to an 2D image, a kernel is applied to all the pixels of the 2
this topic (through a SUB /people/1) will receive a notification. Notice that PATCH could be habit besides. 
 Same apply in the opposition, if a node post a message in the topic PUB /people/1 " loveBeer":true, the represent resource will be update. 
 You would end up with this kind of computer architecture (picture is taken from this blog): 

  Hint 2: Resources creations are besides messages 
 From the previous example, you could think... 

 Hey, what about customer creating a new resource through POST /people? 

 You will create a new resource and a message will be published in the comparable topic (/people) 
 For example, if a client perform POST /people { " name":"schneider ", loveBeer: true }. Clients that have perform SUB /people will receive the presentment 
 So you could think again and say: 

 Hey, what about client publishing a message in a topic through PUB /people? 
   Vice - versa, it will make a message in the topic /people and create a new sub - resource /people/:newid 

 Imagine a client make PUB /people { " name":"Ailurus ", " loveBeer":true }, when message is receive, a new resource /people/42 is created and the clients have subscribed to /people are notified. 
  Bonus hint: Consider meta - data 
 That's not really a hint, since it's not really related to a function between resource URI / subject :) 
 From this blog, meta - data could be added in the warhead of the messages published (but not in your resource representation). 
 chiefly because MQTT Client that subscribe to a subject don't know if a resource is updated or created, whereas a remainder client know this information (when a resource is created, through the location header) 
 So consider to add a metadata such as " event ": " created " or '" event ": " change " 
 You could even think about when a resource is create, in addition to put { " event ": " created " } in the payload, to pass the resource URI / topic name, such as { " event ": " created ", " placement ": " people/42 " } 

  Q: 

 Convolution Kernels for Image Filtering 

 As I understand it, in image processing, when it is desired to apply a filter of some kind to an 2D image, a kernel is applied to all the pixels of the 2
 thls topic (through a SUB /ptople/1) will receivg q notihicatioh. Notice that PATCH could be use alsl.
Sqme akily in the opposite, iw a clienn post a nessege in the topic PUB /peoije/1 "lkyeBeex":tcue, the corresppnding resmurce will be gpaace.
You would end up with this kind of architrchure (picture if talqn fdom this blog) :

 Hint 2: Resources creztions ere also messagrs 
From the previous examppe, ylu could think...

Hey, ahat about xliegr creating a new resougee through KOST /people?

You will create a new resobrce and a newsahg will be puulisheq in the corvvsponditg topiv (/people)
For exsmpne, uf a client performs 'OST /people { "name":"schgeider", loeeYeer:true}. Clients that hqve pgrforked RYB /oeokle wjll refeite the notirication
So tou could think agaon qnd say:

Hey, whzt abott client publishing a message in a topic thdough PUB /people?
  Vice-vwrsa, it will create a message yn the topic /people and create a new sub-resource /[eoplx/:ndwib

Lixtije a client make PUB /people {"name":"Ailurus", "loveBqsr":uruv}, when message is receive, a mea tgsource /people/42 is crzztsd and the clients have sobscrived to /pejple are notified.
 Bonus hint: Cobsider meta-dcta 
That's not really c hint, since it's not teally related to a map'ing bstween resokrce URI/tkoic :)
From this blug, keda-data could be added in tre payloav of che messxges publifhed (but nlt in your resource reprfsentction).
Kainly becwuse MQTT Client that subscribe to a topic dom't knmw if a xesourge is updated ow created, whergas a RESC clievt know thps informetion (when a resource is wteated, througi the locwtiob heqder)
So zunsider to add a metadana sucy as "event": "created" or `"svent": "modified"
Yiu xould even thinl acoue ahxn a wasource is cseatdd, km addktion to pub {"exent": "created"} in the paylmad, fo give the resourve URI/topix name, stch as {"event": "vreated", "location": "ptople/42"}

 X:

Coivolutoon Kernels for Image Filtering

As I undershanq it, in imagq pricessing, wheu it is desired to apply a filter of somx sort to an 2D image, a jernel is applied tp all the pieels os the 2
this topic (through a SUB /people/1) will notification. that PATCH be use also. if client post a in the topic /people/1 "loveBeer":true, the corresponding resource will update. You would end up with this kind of architecture (picture is taken this blog) : Hint 2: Resources creations are also messages From the previous you think... what client creating a new resource through POST /people? You will create a new resource and a will be published in the corresponding topic (/people) example, if a client POST /people { "name":"schneider", loveBeer:true}. that performed SUB will the So you could again and say: Hey, what about client publishing a message in a topic through PUB /people? Vice-versa, will create in the /people create new sub-resource /people/:newid client make PUB /people {"name":"Ailurus", "loveBeer":true}, receive, a new resource /people/42 is created and clients have to /people are notified. Bonus hint: meta-data That's not really a hint, since it's really related to a mapping between resource URI/topic :) From this blog, meta-data could be the payload of the published (but not your representation). because Client that to a topic don't know if a resource is updated or whereas a REST client know this information (when a resource through location header) So to add a metadata as "created" or `"event": "modified" even about is in to put {"event": "created"} the payload, to give the URI/topic name, such as Convolution Kernels for Image Filtering As I understand in image processing, when it is desired apply a filter of some sort to an 2D image, a kernel applied to pixels of the 2
 this topic (through a SUB /peoplE/1) will receiVe a noTifIcaTiOn. NoTice That PATCH could BE use Also.
Same apply in the oppoSite, iF a CLienT PoSt a meSsage in THe TOPic pUb /pEopLe/1 "LOvEBeer":TruE, the corResponding ResOuRce will be updATe.
you would enD up With this kind Of aRchiteCtUre (PIcturE is Taken From thIS blog) :

 HInt 2: ResourCeS CreatiONs are alSO MeSsagEs 
From the previous EXaMPle, you could thiNk...

Hey, wHaT AbOUT clIenT creating a NeW resoURce throUGh post /peOPle?

You will creAte a new resoURce And a meSsAge WIll be pUblisHeD In tHe corresponDing Topic (/peopLe)
For eXAmple, if A Client pErformS POsT /pEoplE { "NaMe":"SchNeIDer", LOvEBeER:trUe}. ClientS tHaT have PerfORMED SUB /PeoPle wIll reCeive the notifIcaTion
sO yoU coulD thinK agaIn And saY:

Hey, whAt aboUt Client publishinG a meSsage in a tOpiC tHroUgH PUB /pEOple?
  ViCe-vErsA, it will Create a MEssAgE IN ThE topic /people and creAtE A NeW sub-resoUrce /peOPlE/:nEWid

ImagiNe A clIent MAKe PUB /PeopLE {"nAme":"AilurUs", "lovebEeR":tRue}, when MeSsage iS rEceIve, A new rESourCe /peopLe/42 is creaTed anD The clients have SUbscribed to /peOPlE ARe NOtifIed.
 bonus hint: CoNsidER metA-datA 
thAt's NOt reaLly a hInT, SiNCe it's not really relatEd To a mapPing bEtween resourcE URI/topic :)
FROM This blog, Meta-DAtA Could be added in The paYload of the MEssages pUblisHed (but noT in your reSOUrce reprEseNtaTioN).
MaINLy Because MQTT ClIENt thAt SubscriBe tO a topic Don'T knOw iF a rEsOurce is upDated or cReAtEd, WhEreAs a REst client kNoW thIs InfOrmatIOn (when A resoUrce Is CrEAteD, througH ThE LOcatIoN hEadeR)
So CoNsideR to aDD a mEtadata Such as "eveNt": "cREateD" oR `"eVent": "modIfied"
You could EvEn think aboUt WheN a resoURCe is creaTed, in addition to put {"event": "CReated"} iN thE paylOad, tO give the rEsoUrce URi/toPIc name, Such as {"Event": "CrEatED", "LocatION": "pEopLe/42"}

 q:

ConvolutiON kerNels fOr imagE FilterIng

As I understand it, IN imAge processing, WheN it iS DEsIreD To APplY a FIltER Of some sort to an 2D Image, a kernEl IS aPplied to alL The PiXels of tHe 2
 this topic (through a SUB  /people/1 ) wil l r ece iv e anoti fication. Noti c e th at PATCH could be usealso. 
S a me a p pl y inthe opp o si t e , i facli en t  p ost a  me ssage i n the topi c P UB  /people/1 " l ov eBeer":tru e,the correspo ndi ng res ou rce willbeupdat e.
You wouldend up wi th this k i nd of a r c hi tect ure (picture is t a ke n  from this blo g) :
 H i nt 2 : R eso urces crea ti ons a r e alsom es s a g esFrom the prev ious exampl e , y ou cou ld  th i nk...
Hey,  w h atabout clien t cr eating anew re s ource t h rough P OST /p eop le? 

Yo u  w il l c re a tea  n ewr eso urce and  a  m essag e wi l l b e pu bli shed  in t he correspond ing  top i c ( /peop le)
F or e xa mple,  if aclien tperforms POST / peop le { "nam e": "s chn ei der", loveBe er: tru e}. Cli ents th a t h av e p er formed SUB /people  w i l lreceivethe no t if ic a tion
Soyo u c ould t hinkagai n  a nd say:
Hey,w ha tabout c li ent pu bl ish ing  a me s sage  in atopic th rough PUB /people?
Vice-versa, i t  w i l lc reat e a  message in  the topi c /p e op lea nd cr eatean ew sub-resource /peopl e/ :newid 

Ima gine a client  make PUB/ p e ople {"n ame" : "A i lurus", "loveB eer": true}, whe n  message  is r eceive,a new res o u rce /peo ple /42  is  cr e a te d and the cli e n ts h av e subsc rib ed to / peo ple  ar e n ot ified.
 B onus hin t:  C on si der  meta - data 
Th at 'sno t r eally a hint , sin ce i t' sn otreallyr el a t ed t oamapp ing  b etwee n re s our ce URI/ topic :)Fro m  thi sbl og, met a-data couldbe  added inth e p ayload o f the me ssages published (but n o t in yo urresou rcerepresent ati on).
M ain l y beca use MQ TT Cl ie ntt h at su b s cr ibe  t o a topicd o n't  know  i f aresourc e is updated or cr e ate d, whereas aRES T cl i e nt  kn o wt his  i n for m a tion (when a re source iscr e at ed, throug h  th elocatio n heade r)
So conside r to adda metadat asuch a s " event": "c reated"or `"even t ": "m o di fied" 
Yo u coul deve n thi nk abo u t w hen a  resou rc e is c reate d,  in addi tion to put {"event": " create d"} i n t he payloa d,t o g ive the r esou rce URI/to pic  na me, s uch as {" even t ":  "c r eated ", " l ocation": "p eop l e /4 2"}

 Q:

C o n v olu tionKer n els fo r Im age Filtering

As I understand i t, i n ima gep roce ss ing, when it i s d es i r ed to ap pl y a filterof someso r t toan 2Dimage,  a kern e l  i s  appli ed t o a ll the pi xel so f the 2 
 this_topic (through_a SUB /people/1) will_receive a_notification._Notice that_PATCH_could be use_also.
Same apply in_the opposite, if a_client post a_message_in the topic PUB /people/1 "loveBeer":true, the corresponding resource will be update.
You would end_up_with this_kind_of_architecture (picture is taken from_this blog) :

 Hint 2:_Resources creations_are also messages 
From the previous example, you_could_think...

Hey, what about_client creating a new resource through POST /people?

You will_create a new resource and a_message will be_published_in_the corresponding topic (/people)
For_example, if a client performs POST_/people { "name":"schneider", loveBeer:true}. Clients that_have performed SUB /people will receive the_notification
So you could think again and_say:

Hey, what about client publishing_a message_in a topic through PUB_/people?
  Vice-versa,_it will_create a message_in the topic /people and create_a new sub-resource_/people/:newid

Imagine a client make PUB /people_{"name":"Ailurus",_"loveBeer":true}, when message_is_receive,_a new_resource /people/42 is_created_and the_clients_have subscribed to /people are notified.
_Bonus_hint: Consider meta-data 
That's not really a_hint, since it's not_really_related to a mapping_between resource URI/topic :)
From this_blog, meta-data could be added in_the payload_of the_messages published (but not in your resource representation).
Mainly because MQTT Client_that subscribe to a topic don't_know if a resource_is updated_or_created, whereas a_REST_client know_this information (when a resource is created,_through the_location header)
So consider to add a_metadata such as "event":_"created"_or `"event": "modified"
You could even think_about when a resource is created,_in addition to put {"event":_"created"}_in_the payload, to give the_resource URI/topic name, such as {"event":_"created", "location": "people/42"}

_Q:

Convolution Kernels for Image Filtering

As I understand_it,_in image processing, when it is_desired_to apply a filter of some_sort_to_an 2D image, a kernel_is applied to all the pixels_of the 2