Review the specification for Trial
Description
Environment
Activity

takeshi hoshina September 27, 2020 at 10:08 PMEdited
Thank you for your comment, Alan.
We will revise the specifications.
Under construction
Section 1 and Section 3
Since it is a specification for the trial period, it will be V0.1.
V1.0 assumes December 2021.
Section 5.1.1, page 8 Change !
Section 5.1.1, page 8, Change !
Section 6.1.1, page 11 Change !
Section 6.2.2, page 15 and page 18
Change "Rob" to "RoB".
Section 6.2.2, page 16 Change !
Section 6.2.2, page 17
Q: In "The prescribed ones are the system reset, the restart (event occurrence processes) and the occurred event log storing.", should that read the "required", not "prescribed" ones?
A: The action item is selected in Config, but it is required.
Section 6.2.2, page 17 Change !
Section 6.2.3, pages 18 and 19 Change !
Section 6.2.3, pages 19 and 20
Q: What does "RR" stand for?s
A: Round Robin Process
Section 7.1.2, page 23 Change !
Section 7.1.2, page 23 Change !
Section 7.1.2, page 23 Change !
Section 8.1, page 26
Q: You may want to consider changing the abbreviation "NSFW". In some English-speaking countries, the abbreviation refers to Internet content that is "not safe/suitable for work", that is, content that is inappropriate for viewing in an office environment.
A: We will consider it, but it is already defined in-house, so it seems that it cannot be changed.
Section 8.1.2, page 27 Change !
Section 8.1.2, page 27 Change !
Section 8.1.2, page 27 Change !
Section 8.1.2, page 28 Change !
Section 8.1.2, page 28 Change !
Section 8.1.2, page 28 Change !

Alan Perry September 19, 2020 at 12:52 AM
Section 1 and Section 3
The title of the referenced AGL specification is Automotive Grade Linux Requirements Specification, version 1.0. The version references to it should be "v1.0". The actual title of the specification should be stated in either Section 1 and/or Section 3.
Section 5.1.1, page 8
Change "No description" to "The AGL Application Framework provides basic services to all applications regardless of the framework they are implemented in so that there is a standard method providing the services."
Section 5.1.1, page 8, second paragraph after [ivi-ProductReady_spec_V0.1]
Change "IIVI-PR" to "IVI-PR".
Section 6.1.1, page 11
Change "No description" to "AGL Persistent Storage refers to power-safe storage, storage that is not erased when unpowered. There are no specific requirements."
Section 6.2.2, page 15 and page 18
Change "Rob" to "RoB".
Section 6.2.2, page 16
Change "When system_manager detects every kinds of the malfunctions, it executes the various failure processing" to "When system_manager detects any kind of malfunction, it executes the various failure processing."
Section 6.2.2, page 17
In "The prescribed ones are the system reset, the restart (event occurrence processes) and the occurred event log storing.", should that read the "required", not "prescribed" ones?
Section 6.2.2, page 17
Change "It stores the targeted log in USB storage device and SD card etc due to the requests from the applications." to "It stores the targeted log in a USB storage device, SD card, etc. due to the requests from the applications."
Section 6.2.2, pages 16 and 17
Change multiple occurrences of "in Configuration file" to "in the Configuration file".
Section 6.2.3, pages 18 and 19
Change "Issue an event when the residual memory falls below the certain level." to "Issue an event when the residual memory falls below a certain level." or "Issue an event when the residual memory falls below a predetermined level."
Section 6.2.3, pages 19 and 20
What does "RR" stand for?
Section 7.1.2, page 23
Change "can" to "CAN".
Section 7.1.2, page 23
Change "Distrubute" to "Distribute".
Section 7.1.2, page 23
What is "AVN"?
Section 8.1, page 26
You may want to consider changing the abbreviation "NSFW". In some English-speaking countries, the abbreviation refers to Internet content that is "not safe/suitable for work", that is, content that is inappropriate for viewing in an office environment.
Section 8.1.2, page 27
Change "If callback function is registered,when receiving the correspond message and event,Dispatcher willexecute the callback function" to "If callback function is registered, when receiving the correspond message and event, Dispatcher will execute the callback function".
Section 8.1.2, page 27
Change "If cancel the callback function register,Dispatcher will not execute the same callback function." to "If cancelled by the callback function register, Dispatcher will not execute the same callback function."
Section 8.1.2, page 27
Change "Application data is maintained by Dispatcher and be set/get at any time." to "Application data is maintained by Dispatcher and may be set/get at any time."
Section 8.1.2, page 28
Change "This process provides function to build client/server session.Client send session open request to service,then service creates session and return it to client.Client use this session to communicate with service.If Client does not want to use session any more,send session close request to service,then service will delete the session." to "This process provides functions to build a client/server session. Client send a session open request to the service, then the service creates a session and return it to client. Client uses this session to communicate with service. If Client does not want to use a session anymore, send a session close request to service, then the service will delete the session."
Section 8.1.2, page 28
Change "Provide communication in Publish-Subscribe way between build session.Service sends Publish command to Subscribe client." to "Provide communications in Publish-Subscribe manner between build session. The service sends Publish commands to a Subscribe client."
Section 8.1.2, page 28
Change "Sequence of message queue open/close, which is needed when send and receive message.The call API should be spared correspond to send,receive, sync communication etc." to "Sequence to open/close s message queue, which is needed to send and receive messages. The call API should correspond to send, receive, sync communication, etc."
I have not yet completed my review, but I am out of time, so I will post these review comments now.
Details
Details
Assignee

Reporter

Toyota plans to contribute the IVI-PR Trial item.
Could you review the specification on the Jira ticket below in the view point of OSS?
https://confluence.automotivelinux.org/display/IVIPR/ProductReady_Spec_Ver.0.10Draft