UUID's - First Class Optional Field?

[justinschembri]

Hello all,

I don't particularly enjoy the fact that I need to embed the Universal Unique Identifier (UUID) of my Thing in properties. Somehow it seems as if this should be a first class field, albeit optional. I think this improves the development of STA clients if we always know where the UUID is (or is not).

Wonder if anyone else has similar thoughts? @hylkevds - maybe this came up during v2 development?

[hylkevds]

You are totally correct. That's why, in V2.0, we added a definition field to all entity types (except Observations), to store such an external reference.

Alternatively, if you set up your own server, you can also set the ID type of the Thing EntityType to be UUID, and turn on client-defined ids. Then you can use the UUID as the primary key for Things, and define them yourself instead of having them be server generated.

[justinschembri]

I see, thanks for the insight. Guess I'm not as familiar with v2 as I thought ;)

Do you think you could perhaps introduce v2 at the next public meeting? Is a V2 server still on the table as an option during this testbed?

[hylkevds]

I've just merged my V2 development branch into the main development branch for v2.8, so we can try installing that now.

I can try to say a bit more about V2, but I've got only 20 minutes, and already much to tell... Maybe we need to add a separate call to detail what's new in V2.

[justinschembri]

Hey @hylkevds, we could install it - I could also try to do some local testing ... does the image at dockerhub fraunhoferiosb/frost-server:2.8.0-SNAPSHOT) build OK?

A separate call about v2 would be great provided you have time for this ... would you maybe like to set up a poll for dates? I think my report will have a couple of sections on "difficulties faced" which I'd like to end with "...but V2 fixed this" - so I'd like to test!

[hylkevds]

Yes, the 2.8.0-SNAPSHOT tag has V2 in it now.
You'll need the settings:

• plugins_coreService_enable=true
• plugins_coreServiceV2_enable=true
• plugins_coreModel_enable=false
• plugins_coreModelV2_enable=true
• plugins_modelLoader_enable=true
• plugins_multiDatastream_enable=false

And optionally:

• plugins_modelOM_enable=true
• plugins_modelSampling_enable=true
• plugins_modelRelations_enable=true
• plugins_actuation_enable=true
• plugins_projects_enable=true
• plugins_projects_enableDefaultRules=true

A V1 database can not (yet) be auto-converted to V2, so make sure you run it on a clean database/schema.
I'll set up a poll for a V2 telco.

[hylkevds]

Poll linked in #13