[Fiware-wpl] Open Specs and Checkpoint 11a

Sandfuchs, Thorsten thorsten.sandfuchs at sap.com
Wed May 15 13:38:07 CEST 2013


Dear colleagues,
While browsing the reviewers checkpoints I was wondering if we already addressed this point in the current version of the open specs "enough" and I think we wanted to take this discussion offline. So here it is:

Checkpoint 11a
Documentation of the final list of GEs for which Open Specifications will be written and the IPR provisions of the individual GE Open Specifications; the IPR provisions should take into account the potential questions and concerns of would be implementers.
Status: Not achieved
Due date: Urgently needed

What will be our positioning here on the next review? Did we achieve this?

Analysis
In general I see this information present in some of the entries of the catalogue - but it is for sure not compiled within the OpenSpecification deliverable and not within the summary page of https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Summary_of_FI-WARE_Open_Specifications and there is no "final list" being exposed somewhere centrally.

Decision need
Firstly we need to decide if we should/still need to fix this. Then if we can even fix this, given the tight schedule, prior to the open spec delivery.

ð  I think we definitely should fix it and try to deliver the solution within this week for the open spec deliverable, if possible (although this might be really tough) - if not then we should have this definitely for the next review ready and released to the public.


Two ways forward

1.       If I got it right, this mainly focuses on open specification and the foreground IP around it.

In general the statements requested potentially would be:

-          This Open Spec is exploitable for proprietary 3rd party products

-          This Open Spec is exploitable for open source 3rd party products

-          This Open Spec is exploitable for FI-PPP members only
But IANAL and I think we would need to start compiling this firstly.

SAP e.g. introduces a text to the Open Specification: SAP strives to make the specifications of this Generic Enabler available under IPR rules that allow for a exploitation and sustainable usage both in Open Source as well as proprietary, closed source products to maximize adoption.
Would that be sufficient already if partners would adopt this or similar text? How can we have the needed "final list" or how can we compile this final list, and how will this be then submitted to the reviewers? As part of the public wiki?

Options I see:

1.A.Introduce the information of IPR statements on the Open Spec wiki page as part of the Template "Open spec brief" or like SAP did it

1.B. Introduce the information on the Summary pages (linked above)

1.C. Introduce a new page which summarizes this information in "one" list

1.D.Introduce a page in the catalogue which displays the relevant information (given that the catalogue pends a lot of edits, this might be not suitable for submission of the deliverable)

I would opt for 1.A.

Next steps:

-          Find a consensus on what statements are requested

-          Decide on where to put them


2.       There might be implications from this checkpoint for the software related IPR and the levels of IPR provisioning. These software components roughly follow this metric (right?):
[] FI-WARE
[] FI-PPP
[] planned for OIL
[] 3rd party on request
[] 3rd party publicly available (free to use)
[] commercially exploitable (free to use, exploit and contribute)
Or something more specific:
[] open source with licence XXXX

                I think for many software related packages, currently there is only the FI-PPP collaboration agreement is relevant - but what is needed here and what some partners can provide is: sustainable software provisioning clearly envisioning usage of the software for 3rd parties other than FI-PPP - for WP3 this is more than 50% of the GEs (and yes, there are some where this is clearly NOT the case)

ð  Would this be part of the exercise as well to compile this list in relation to software related assets and have this finally compiled somewhere, where a human being can find it?

Best,
                                                                /Thorsten

--

Thorsten Sandfuchs

SAP AG | Vincenz-Priessnitz-Strasse 1 | D-76131 Karlsruhe, Germany | www.sap.com<http://www.sap.com/>


Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx

Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielfältigung oder Weitergabe der E-Mail ausdrücklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank.

This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation.

Please consider the environment before printing this mail!


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-wpl/attachments/20130515/2bcbf449/attachment.html>


More information about the Fiware-wpl mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy