<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="color: rgb(0, 0, 0); font-family: Calibri,Arial,Helvetica,sans-serif,"Apple Color Emoji","Segoe UI Emoji",NotoColorEmoji,"Segoe UI Symbol","Android Emoji",EmojiSymbols; font-size: 12pt;" dir="ltr">
<p></p>
<p>Hello Goffi<br>
<br>
A similar effect, with context-sensitive content in a form can be made using Dynamic Data Forms (XEP-0336).<br>
<a class="OWAAutoLink" id="LPlnk778141" href="https://xmpp.org/extensions/xep-0336.html" previewremoved="true">https://xmpp.org/extensions/xep-0336.html</a><br>
<br>
Best regards,<br>
Peter Waher<br>
</p>
<br>
<br>
<div style="color: rgb(0, 0, 0);">
<div>
<hr tabindex="-1" style="display:inline-block; width:98%">
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Date: Thu, 02 Mar 2017 08:12:05 +0100<br>
From: Goffi <goffi@goffi.org><br>
To: jdev <jdev@jabber.org><br>
Subject: [jdev] data forms with different access models<br>
Message-ID: <1645506.OYax3R7NXg@tazar2><br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
Hello,<br>
<br>
<br>
I would like to have a dataform in a pubsub item with different access models <br>
for the fields, for instance a "body" field would be public while a "email" <br>
field would be only accessible to a white list of jid.<br>
<br>
I think of 2 ways of achieving that with a standard PubSub service:<br>
<br>
- having an intermediate service which open a private node on the pubsub <br>
service, and which know how to handle the fields and permissions.<br>
PROS: simple design<br>
CONS: needs an extra layer, not generic<br>
<br>
- having a way to "compose" data form in several nodes. The main node/item
<br>
would be a list of nodes with different access models (first node is white <br>
list, second is open), the client try all nodes an gather the data it can <br>
access to compose a final form.<br>
PROS: working with current pubsub services, generic, we have fields history
<br>
for free<br>
CONS: more complicated design, difficult to search items, more requests<br>
<br>
<br>
Maybe there is an other way I haven't thought about.<br>
<br>
<br>
What do you think is the best way? Do you have better idea?<br>
<br>
<br>
<br>
Thanks<br>
<br>
Goffi<br>
<br>
</div>
</span></font></div>
</div>
</body>
</html>