<scribe> scribenick: ted

<scribe> Scribe: Ted

Interdependent issues

Gen2 data model

Wildcards

[VSS2] Position-related branches proposal

previous discussion on Gen2

Ted: critical mass to resolve@@
... @rbranch

Ulf: goal was to combine features from both in VSS data model

Ted: different approaches, overloading branch types@@

Daniel: issues are not 100% clear to me on gen2 discussion
... for positioning we opened issue and now we have another for gen2 which addresses some issues with VSS
... we are discussing each issue by itself. we need to clearly identify the problem with VSS wrt gen2
... right now we are stalled because we are stuck in trying to understand
... seem we are in agreement in staying with VSS but there may be problems with tree structure

PatrickLue, will you be available next week? we have a few stuck issues on Gen2/VSS and think they should be taken up together

<PatrickLue> Yes

Daniel traveling but should be available, Benjamin hopefully if not

<PatrickLue> a heads up before via mail is appreciated.

he indicated he will send

PatrickLue, can you elaborate more on the blockers you see on the current data model before call? on an issue, 81 pull request or email?

I am trying to convey your concern of branch typing but cannot

Daniel and Ulf interested in understanding it further

<PatrickLue> I will via mail

Ulf: open to alternative solution but need to understand it better

Benjamin: we were supportive of rbranch for resources, we are reducing node types in the tree and we need clearer requirements to be able to fine tune proposal
... I do not see a clear solution right now or what would best suit developers using Gen2

[discussion on other issues, Magnus F's ID request for commands]

Benjamin: add IDs to nodes could be useful otherwise

Ted: agree, alternate and easier way in some cases than using path
... in some cases you can get a leaf node without understanding path. Benjamin you were thinking of a dot-notation as an identifier iirc

Benjamin: I do not see any reason to have dotted identifiers would be an issue, would be useful for indexing

https://github.com/GENIVI/vehicle_signal_specification/issues/95

@@position_problem

Benjamin: long identifier instead of long paths doesn't gain much from a performance perspective
... good old fashioned numbers are effective identifiers

Daniel: they are useful and comparable to @M2m model. you can have a private branch with its own address space
... public IDs can be under a certain threshold (reserved numbers)

Ted: @@rigid_positions

Daniel: restrained environments use an identifier, @@2 basically has a protocol for handling it
... the positioning is done by instances. as we move position to end, it makes the tree cleaner and where the leaf belongs
... you can request through many languages and protocols easier with the positioning removed from the middle of the path
... the proposal has an accompanying csv file and need to work on tooling so you can visualize it
... I feel we came to a conclusion

Ulf: I agree

Daniel: pbranch aspect is not mandatory, would be fine as an attribute

https://github.com/GENIVI/vehicle_signal_specification/issues/95

agreement on usefulness for numeric IDs

This is scribe.perl Revision: 1.154  of Date: 2018/09/25 16:35:56  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Present: Ted Glenn Benjamin Don Daniel Ulf Magnus Harjot
Regrets: PatrickL(on_irc_only)
Found ScribeNick: ted
Found Scribe: Ted
Inferring ScribeNick: ted

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 12 Mar 2019
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)