W3C home > Mailing lists > Public > public-autowebplatform@w3.org > October 2013

Administration around specs and call for action

From: Abramski, Adam M <adam.m.abramski@intel.com>
Date: Thu, 3 Oct 2013 20:26:53 +0000
To: "public-autowebplatform@w3.org" <public-autowebplatform@w3.org>
CC: "Abramski, Adam M" <adam.m.abramski@intel.com>
Message-ID: <6AB32C125D193D47AE66073666ED3B5E34945898@ORSMSX105.amr.corp.intel.com>
Hi all,

So there are some administrative changes that you all should be aware of as it relates to the 4 previously discussed API specs from the various organizations.

I've been advised to change the following page: http://www.w3.org/community/autowebplatform/wiki/Main_Page and specifically to call out that the 4 previously discussed API specs are examples only.  Now this means that these are just example specs and there are copyrights associated with each of them.  So we can't, in our 1st draft of the vehicle API spec, just copy and paste from these example specs to make our own spec unless the owner of these specs contributes it to our group.

If you are the owner or represent the owner/organization of the spec and you want to contribute your spec to the group you must do one of two things, either:

1)      Send an email to: public-autowebplatform-contrib@w3.org<mailto:public-autowebplatform-contrib@w3.org> (no URL's) and attach either a PDF/formatted file or cut and paste of the entire text of the spec you are contributing to the group

2)      Or post your full spec (again no URL's) to our github project (ask Kevron if you need help) and send an email to public-autowebplatform-contrib@w3.org<mailto:public-autowebplatform-contrib@w3.org> to notify the group of the contribution https://github.com/w3c/automotive-bg

Of course the alternative to having not having any contributions is we can always draft our spec from scratch. This goes for the Autosar spec as well since the vehicle signals exposed by the Autosar spec were recently added to our vehicle signals spreadsheet.

On a separate but related note, one of the example specs covers areas like media player, radio, audio mixer, navigation and I just want to remind the group that these are outside the charter of this group and our focus for writing a spec report is on vehicle data.  I also wanted to point out that there are existing final or drafted W3C specs that cover areas the group might be considering as we've discussed in the past and even listed those on our wiki.  A good example of this is the Tizen sample spec, where Intel had defined a location interface and it was called out by a member of our group (on 4/25) that there is an existing W3C geolocation spec that should be used instead.  Intel has since corrected the Tizen sample spec and removed that location API.  Finally, even though our charter states that we are working only on a vehicle data spec report there is nothing stopping the group from creating and documenting use cases and requirements for other automotive specific areas.  I'm sure all of this was obvious to most of you but I felt it needed to be communicated again since the group is driving to have a draft spec very soon and the copyright that will be associated with this work will be http://www.w3.org/community/about/agreements/final/ which allows derivative specs from it and we need to make sure our draft spec report is free of encumbrances.

Sincerely,
Adam

Adam M Abramski
Product Planner
Intel Software & Services Group
503-264-8269 (o)
503-550-7910 (m)
adam.m.abramski@intel.com<mailto:adam.m.abramski@intel.com>
Received on Thursday, 3 October 2013 20:27:29 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:52:51 UTC