|Subject:||Re: AW: [sdo] Groups - HelperContextCreation - v11.zip (commonj.zip) uploaded|
|From:||Bryan Aupperle (aupp...@us.ibm.com)|
|Date:||Jun 19, 2009 8:18:36 am|
In the SCA-J TC, thee has been some discussion about including version/date information. It has been awhile, but was generally viewed as a good thing, but may not have been done yet.
Bryan Aupperle, Ph.D. STSM, WebSphere Enterprise Platform Software Solution Architect
Research Triangle Park, NC +1 919-254-7508 (T/L 444-7508) Internet Address: aupp...@us.ibm.com
Frank Budinsky <fra...@ca.ibm.com> 06/19/2009 10:59 AM
On the otherhand, I can't imagine why it would be necessary.
Are you saying that the SCA interfaces have nothing in them to indicate what version of SCA they are? What if they want to add a new method in a future version. How will users know which version of the interface they're using?
This really has nothing to do with the copyright notice (legal issue). It's just a question about documenting what version of SDO the interface is from? Maybe we can have another comment block after the copyright comment, if combining the information is a problem.
"Barack, Ron" <ron....@sap.com>
"Barack, Ron" <ron....@sap.com> 06/19/2009 10:29 AM
AW: [sdo] Groups - HelperContextCreation - v11.zip (commonj.zip) uploaded
Hi Frank, Everyone,
The v10 headers look like this:
/** * <copyright> * * Service Data Objects * Version 3.0 * Licensed Materials * * (c) Copyright BEA Systems, Inc., International Business Machines Corporation, * Oracle Corporation, Primeton Technologies Ltd., Rogue Wave Software, SAP AG., * Software AG., Sun Microsystems, Sybase Inc., Xcalia, Zend Technologies, * 2005-2008. All rights reserved. * * </copyright> * */
The headers I used, based on what's used by the SCA Java TC, look like this:
/* * Copyright(C) OASIS(R) 2005,2009. All Rights Reserved. * OASIS trademark, IPR and other policies apply. */ I'm not sure what "Licensed Materials" means, and I think the JavaDoc-like "/**" is just plain wrong, but I can't imagine that there would be a problem with adding SDO 3 to the header, giving
/* * Service Data Objects * Version 3.0 * * Copyright(C) OASIS(R) 2005,2009. All Rights Reserved. * OASIS trademark, IPR and other policies apply. */
On the otherhand, I can't imagine why it would be necessary. And the SCA-J header has already been through all of our legal departments, since SAP, IBM and Oracle are all active members of the SCA-J TC. I'm for whatever settles this ASAP, and with as little discussion as possible. Anyone want to run some permutation of this by their legal department?
Von: Frank Budinsky [mailto:fra...@ca.ibm.com] Gesendet: Freitag, 19. Juni 2009 16:03 An: Barack, Ron Cc: sd...@lists.oasis-open.org Betreff: Re: [sdo] Groups - HelperContextCreation - v11.zip (commonj.zip) uploaded Hi Ron,
Thanks for updating the headers. Legally, I think we're fine now, but I notice that you completely removed the old header including the part that said that it is SDO 3.0. Shouldn't we continue to keep at least that kind of version information in the header?
ron....@sap.com 06/19/2009 07:56 AM
[sdo] Groups - HelperContextCreation - v11.zip (commonj.zip) uploaded
as agreed in the meeting, here is the proposed API, with the headers adjusted to include the OASIS copyright.
-- Mr. Ron Barack
The document named HelperContextCreation - v11.zip (commonj.zip) has been submitted by Mr. Ron Barack to the OASIS Service Data Objects (SDO) TC document repository.
Document Description: The same as v10, with headers adjusted for OASIS copyright.
View Document Details: http://www.oasis-open.org/committees/document.php?document_id=33008
Download Document: http://www.oasis-open.org/committees/download.php/33008/commonj.zip
PLEASE NOTE: If the above links do not work for you, your email application may be breaking the link into two pieces. You may be able to copy and paste the entire link address into the address field of your web browser.
-OASIS Open Administration
--------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php