Location data » History » Version 1
Anonymous, 11/05/2015 10:50 AM
| 1 | 1 | Anonymous | h1. Location data |
|---|---|---|---|
| 2 | 1 | Anonymous | |
| 3 | 1 | Anonymous | |
| 4 | 1 | Anonymous | *Aim* : |
| 5 | 1 | Anonymous | |
| 6 | 1 | Anonymous | Add more precise information about the location of a node. |
| 7 | 1 | Anonymous | |
| 8 | 1 | Anonymous | *Description* : |
| 9 | 1 | Anonymous | |
| 10 | 1 | Anonymous | IDMEF class Node already has a location attribute. But it is only a single string, which isn't enough to describe precisely the location of the node. |
| 11 | 1 | Anonymous | |
| 12 | 1 | Anonymous | *Meetings* : |
| 13 | 1 | Anonymous | |
| 14 | 1 | Anonymous | +30/10/2015 Meeting+ : OK ! |
| 15 | 1 | Anonymous | |
| 16 | 1 | Anonymous | _GL : Could be interesting to also add an agency name for enterprises for example._ |
| 17 | 1 | Anonymous | |
| 18 | 1 | Anonymous | _SM : Indeed, this information is available in LEEF._ |
| 19 | 1 | Anonymous | |
| 20 | 1 | Anonymous | _GL : We will have to choose a standard for longitude and latitude, since there are many of them._ |
| 21 | 1 | Anonymous | |
| 22 | 1 | Anonymous | _YV : To be discussed in priority because some changes must be made in Prelude regarding this topic. Should be done *before FIC ! Meeting ASAP !*_ |
| 23 | 1 | Anonymous | |
| 24 | 1 | Anonymous | _VH : Prelude shouldn't really interfere with SECEF and it seems hazardous to me to change the implementation of IDMEF before having set up on a new structure for the format. However, I understand this is necessary, and, since everyone seem to agree on this topic, we could maybe make an exception._ |