ABCDEFGHIJKLMNOPQRSTUV
1
2
3
PresentValues in columns below correspond to MoSCoW priority assigned by the corresponding project. Bear on mind the semantics. I have refined the description depending whether it is a UC project or FI-WARE
4
UC projects:
5
Must - If there is no GE supporting the described functionality, FI-WARE is useless.
6
Should - If there is a GE supporting the described functionality in FI-WARE, the project would use it, but it is not absolute a must (there is a workaround or it won't make the project fail if it's not there).
7
Could - It would be nice that there is a GE supporting the described functionality in FI-WARE because it might be used by the project (despite not currently planned)
8
Wont - the project doesn't require the described functionality.
9
FI-WARE:
10
Must - A GE supporting the described functionality should be part of FI-WARE. FI-WARE would fail to deliver in one or several chapters if not present.
11
Should - Existence of a GE supporting the described functionality is considered important in FI-WARE but it is not absolute a must, overall if no UC project find it is useful.
12
Could - It would be nice that there is a GE supporting the described functionality in FI-WARE.
13
Wont - Availability of a GE supporting the described functionality is considered out of the scope of FI-WARE.
14
15
Request Id (note: should be the Id of the entry in the backlog, e.g., FInest.Epic.IoS.WorkflowExecutionEngine)URL on FI-WARE Wiki (please add whatever is needed to the detailed description)ENVIROFIFINSENYFI-CONTENTFInestINSTANT MOBILITYOUTSMARTSAFECITYSMART AGRIFOODFI-WAREComments
16
1B.1)ENVIROFI.Epic.DeliveryFramework.EnvironmentalARFrameworkhttps://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/ENVIROFI.Epic.DeliveryFramework.EnvironmentalARFrameworkMUSTCOULDSHOULDCOULDSHOULDCOULDsee also https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIContent.Epic.AugmentedReality
and
https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIContent.Epic.3D-Internet%2BServices. Also of interest to SMART Agrifood
17
XENVIROFI.Feature.Security.GeospatialConstraintshttps://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/ENVIROFI.Feature.Security.GeospatialConstraintsSHOULDCOULDWONTSHOULDMUST
18
XENVIROFI.Feature.IoT.MobileSensorAbstractionhttps://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/ENVIROFI.Feature.IoT.MobileSensorAbstractionMUSTCOULDSHOULDCouldCOULDSHOULD
19
C.1)ENVIROFI.Epic.Data.ContextAwareViewServicehttps://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/ENVIROFI.Epic.Data.ContextAwareViewServiceSHOULDCOULDSHOULDCOULDSHOULDCOULDJuanjo means this may be connected with queries on publish/subscribe broker; to be discussed in more details
20
D.1)ENVIROFI.Epic.DeliveryFramework.ResourceRegistryServicehttps://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/ENVIROFI.Epic.DeliveryFramework.ResourceRegistryServiceMUSTCOULDMUSTWON'TENVIROFI partners feel we need to pay more attention to issue of "how to find the resources", and that this is not well covered in FI-Ware yet. FINSENY has a similar requirement.

This will be further discussed, but does not need to be addressed in 1-st open call. (very important, not very urgent)
21
2C.2)EnvironmentalDataUncertaintyManagementServicehttps://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/ENVIROFI.Epic.Data.EnvironmentalDataUncertaintyManagementServiceMUSTCOULDCOULDWONTThis and the next one belong together.

Probably cannot be refined on time for the first open call but certainly is something around which OUTSMART+ENVIROFI can work together with members of the FI-WARE Data/Context Management chapter and try to see whether it leads to identification of GEs that could fit in the second Open Call or are not generic enough as to be part of FI-WARE.		ENVIROFI: we feel the need for explicite uncertainty information attached to all observations (read: "to all data"). Since this will not happen over night, it would be very convenient to have a service capable of assigning this information to third party data.
22
2C.2)ENVIROFI.Epic.Data.ObservationTrustManagementServicehttps://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/ENVIROFI.Epic.Data.ObservationTrustManagementServiceMUSTCOULDMUSTSHOULDENVIROFI will at least need to build some simple version of this; we feel that a more generic & robust solution woudl be very benefitial - not only for us. It will be used by OUTSMART
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100