<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi,<br>
<br>
On 11/03/2017 06:26 AM, Knight, Alexander wrote:<br>
<blockquote type="cite"
cite="mid:CEEB6E51351381489D6F5114B21174C95B5293@EXUAU182FRM150.oceania.corp.anz.com">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal">At the Deepsec conference Sebastian
mentioned updating the harmonization to allow for fields with
multiple values. Has this issue been progressed at all?</p>
</div>
</blockquote>
The use case was the field abuse_contact which could be a list and
then be concatenated (if necessary) with commas.<br>
Technically it is not hard to do it. In the develop branch I already
have something similar (and more complex): a dictionary type named
JSONDict.<br>
So, not directly, but some changes that should make a change easier.<br>
<br>
There are some questions popping up that need to be clarified first:<br>
* How to define the types of the values inside the list? E.g. for
the abuse_contact it has to be a list of strings/email addresses<br>
* How should the "API" look like, or in other words: what should
happen for the in and setitem-operations etc<br>
* When should the list be converted to a string (or maybe also a
JSON-list)? E.g. for postgres output the abuse_contact could either
be a json-list or a comma separated list, depending on the table's
definition, but for NoSQL-databases and files it can be just the
list itself.<br>
<br>
And: what use cases do we have? That's good to know before thinking
about how we implement that all:<br>
<blockquote type="cite"
cite="mid:CEEB6E51351381489D6F5114B21174C95B5293@EXUAU182FRM150.oceania.corp.anz.com">
<div class="WordSection1">
<p class="MsoNormal">We will require multiple values for some
fields in our events,</p>
</div>
</blockquote>
What is in these fields? (type and/or example values) Where do you
put that that and how do you want to work with in (inside intelmq)?<br>
<br>
I'd like to hear opinions of other users and developers too!<br>
<br>
Sebastian<br>
P.S.: I do have specific ideas, but don't want to bias others ;)<br>
<pre class="moz-signature" cols="72">--
// Sebastian Wagner <a class="moz-txt-link-rfc2396E" href="mailto:wagner@cert.at"><wagner@cert.at></a> - T: +43 1 5056416 7201
// CERT Austria - <a class="moz-txt-link-freetext" href="https://www.cert.at/">https://www.cert.at/</a>
// Eine Initiative der nic.at GmbH - <a class="moz-txt-link-freetext" href="https://www.nic.at/">https://www.nic.at/</a>
// Firmenbuchnummer 172568b, LG Salzburg</pre>
</body>
</html>