Hi Deng hui,
Regarding the modelling delivery, is this expectation in line with the
expectation from the projects about who publishes what, and how do you see that
working? In the expected deliverables, is it the information models or data
models or both?
Could I suggest a few wording changes in the scope. I understand the
intention, but they could be interpreated more broadly.
* Purpose:
* Publish Guidelines
-> publish modelling guidelines
* Facilitate model reviews
* Publish models
* Curate approved models (model lifecycle management, e.g., versioning)
* Coordinate adoption/use across projects ->
coordinate model adoption/use across projects
* Alignment with industry standards ->
Alignment with industry standards for modelling.
Scope:
* I thought that parsers were the responsibility of the ONAP modelling
project, not the sub-committee?
BR,
Steve
From: [email protected] [mailto:[email protected]]
On Behalf Of denghui (L)
Sent: 14 June 2017 12:06
To: [email protected]
Cc: onap-tsc <[email protected]>
Subject: Re: [onap-tsc] Modeling subcommittee proposal
Hello all.
Thanks Chris Donley for kindly help to simplified the wording on the wiki page,
If that is possible, we would like to request an approval in tomorrow during
TSC meeting
https://wiki.onap.org/display/DW/Modeling+sub-committee
Best regards,
DENG Hui
From: denghui (L)
Sent: Friday, June 9, 2017 4:13 PM
To: '[email protected]'
<[email protected]<mailto:[email protected]>>
Cc: onap-tsc <[email protected]<mailto:[email protected]>>
Subject: Modeling subcommittee proposal
Hello all
Based on the modeling project subgroup discussion, we propose Modeling
subcommittee for TSC review,
we separate the scope of modeling project for tools, modeling subcommittee for
modeling specifications across the projects.
https://wiki.onap.org/display/DW/ONAP+Modeling+sub-committee
Thanks a lot for review
Best regards,
DENG Hui
_______________________________________________
ONAP-TSC mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-tsc
