Re: Updating Maintenance type

I do too.

Paul J. Boyes
--------------------------------
Mobile:   206-276-9675
Skype:  pauljboyes




On Feb 26, 2014, at 1:57 PM, Rees, Kevron <kevron.m.rees@intel.com<mailto:kevron.m.rees@intel.com>> wrote:

I agree also with Justin's remarks.

On Tue, Feb 25, 2014 at 3:02 AM, 박종선(Justin Park) <jongseon.park@lge.com<mailto:jongseon.park@lge.com>> wrote:
Hi Paul,

Could you please review the link below?
https://rawgithub.com/w3c/automotive-bg/master/draft_specs/VehicleAPI_Maintenance.htm

https://github.com/w3c/automotive-bg/commit/4427639092009e7f31e7969f07bb5134747a77f1 (diff)

I've updated your work a little bit according to the Kevron's common interfaces.
I didn't delete your 'Issue' section yet. Here are my quick answers.

Issue1) Grouping
It makes sense.

Issue2) distanceSinceStart
I vote to keep it. But I prefers to separate it from tripmeter.

Issue3) TransmissionOil temperature, wear.
I vote to keep it. I'm sure it's real.

Issue4) TransmissionClutch wear
I vote to keep it. It seems real.

Issue5) Tire Pressure Low
It's a kind of high level wrapper for who wants to know just whether it's ok or not rather than exact pressure value.

Issue6) tirePressureThresholdFrontAxle and tirePressureThresholdRearAxle
Issue7) wheelSpeedWarningIndication
I agreed on removing those.

You noted most of interfaces as optional.
I totally agreed that those are optional, but not sure that we need to note 'optional' explicitly.
Because W3C specifications seem not to note it.

Please review and give comments.

Regards,
Justin

--------------------------------------------------------------
Justin(Jong-Seon) Park
WMT Team, S/W Platform Lab.,
LG Electronics Inc.
221 YangJae-Dong, Seocho-Gu, Seoul 137-130, Korea

Phone : +82-2-526-4183
Fax   : +82-2-6912-6358