OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

openc2 message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [openc2] Re: Java Copyright

Re: the four new OpenC2 TC requests for TC Open Repositories, WRT GitHub repository machine-names...

I'm pleased to report that we have a resolution, and I'm planning to spin up the repos as requested.

Thank you all for your patience and understanding.

I'll be in touch with the named Maintainers and TC Officers about any lingering details, if any, though I
don't know of any substantial loose ends at this time.  Dave, I'll coordinate with you on a couple
admin logistics.

Except for one more message likely to be sent here by Jamie Clark, I think this thread on the
TC Discussion can now be considered closed, decisively, as we have principled resolution.

Kindest regards and best wishes

- Robin


On Fri, Mar 16, 2018 at 2:35 PM, Dave Lemire <dave.lemire@g2-inc.com> wrote:
Has anyone fed the lawyers enough java for them to come to a decision about having -java- in a repo name?

Dave

David P. Lemire, CISSP
  OpenC2 Technical Committee Executive Secretary
  OpenC2 Implementation Considerations SC Co-chair
  Contractor support to NSA
Email: dave.lemire@g2-inc.com
Office: 301-575-5190 / Mobile: 240-938-9350

On Wed, Mar 7, 2018 at 1:49 PM, Stefan Hagen <stefan@dilettant.eu> wrote:

Gently from the sidelines of a geographical entity called java and before taking a swim:

It is tough to fight the below counted usage of what-ever-java, as in what-ever-python or python-what-ever naming schemes, but I will await the judgement of the wise lawyers with a cup of java on the beach, I imagine.

All the best,
Stefan

Am 07.03.2018 um 18:24 schrieb Robin Cover <robin@oasis-open.org>:

On Wed, Mar 7, 2018 at 8:22 AM, Chet Ensign <chet.ensign@oasis-open.org> wrote:
Hi Duncan, 

We are researching this now. Just to explain, the issue has to do with trademarks. The OASIS rules do not allow the use of trademarks not owned by OASIS in the name of any Work Product unless granted an exemption by the board. That is to ensure that a third party cannot later come back to OASIS and make a fuss over unauthorized use of their TM. Oracle does claim a trademark for "Java." 

In this case, there is precedence so I don't anticipate a problem.

I don't anticipate a problem either, but I always have to say explicitly "IANAL".  My IANAL observation is that while "java" may have applicable trademark regulations in some usage contexts (as in the Logo), usage of the string "java" in a public repository name isn't prohibited in any common case.  

Just counting pubic GitHub repositories, there are nearly half a million repositories that have "java" or "_javascript_" in the repo identifier.

Here are a few examples from well-known entities


>  
But we do need to clear this with Jamie before proceeding. 


Yep.  I sent him email asking for how we'd think about the TC's preference for 
"openc2-lycan-java", which would yield URI references as identifiers for
issues, code commits, pull relquests, tags, releases, branches, etc


-rcc
 
Hope this helps explain where we're at. 

/chet


On Tue, Mar 6, 2018 at 11:54 PM, Duncan <duncan@sfractal.com> wrote:
Chet,
Can you explain when we can and can’t use the work ‘java’ wrt OASIS policy? If we can’t use it in the repo name, can we still use it in documentation? Can we include java code in the repo? Is there an issue with this email (which used the work java) being in the pubic email archives?

I am aware that Oracle trademarks the Java logo (Java in a particular font with a cup of coffee image) and that it copyrights Oracle code (such as the API’s that are the crux of the longstanding Oracle/Google lawsuits). But we are not using java logo nor are we copying Oracle code. I was not aware of any copyright on the word ‘java’ itself or on java code created by others. For example, I don’t see the copyright on the Oracle webpages encouraging the use of java. Nor do I see it when GitHub marks the programming language of each repo.

Although I’m ok with renaming the repo “-j” instead of “-java”, I do think it will be confusing and make the repo less useful. I’m also not sure why the repo name is different than in the documentation or the code, and if we can’t use java in the documentation nor the code, then it makes the repo virtually useless so I am concerned. 

iPhone, iTypo, iApologize

Duncan Sparrell
sFractal Consulting, LLC
The closer you look, the more you see



On Tue, Mar 6, 2018 at 1:01 PM -0500, "Brule, Joseph M" <jmbrule@radium.ncsc.mil> wrote:

OpenC2 Technical Committee, 

We did not receive any objections to the formation of these three open repositories and the OASIS staff is in the process of creating.  

I do need to identify an issue and please advise if you take issue with the proposed way forward.   The name " OC2Lycan-java " has an issue in that 'java' is actually copyrighted and OASIS has a rule against using copyrighted material in the repository names.  The OASIS staff is going to double check to see if it is OK to have the term 'java' in the repository name.  If so, then the name will be changed to " OC2Lycan-j"

Thank you, and BTW, I didn't know that Java was copyright, otherwise would have caught that in advance.  

VR

Joe B

-----Original Message-----
From: Brule, Joseph M 
Sent: Thursday, February 22, 2018 4:00 PM
To: OASIS OpenC2 List 
Subject: A call for objections: OASIS Open Repositories for OpenC2

OpenC2 Technical Committee,

A proposal to create three open repositories was discussed during the February 21 TC monthly meeting:
OC2Lycan-java:  A java library to be maintained by Mr. Blake Essing.  (Resolution located at https://www.oasis-open.org/committees/download.php/62580/OC2Lycan-Java.pdf )

OC2Lycan-python:  A python library to be maintained by Mr. Michael Stair (Resolution located at https://www.oasis-open.org/committees/download.php/62581/OC2Lycan-Python.pdf )
OC2Compat:  To capture and suggest implementation guidelines to be maintained by M. Michael Stair with Mr. Joshua Brule to act as technical advisor ( https://www.oasis-open.org/committees/download.php/62579/OC2Compat.pdf )

Please review the resolutions and state any objections no later than March 7, 2018.  If no objections are stated, then we will proceed to create the open repositories.

Thank you

Very Respectfully



Joe Brule

---------------------------------------------------------------------
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



--

/chet 
----------------
Chet Ensign
Director of Standards Development and TC Administration 
OASIS: Advancing open standards for the information society
http://www.oasis-open.org

Primary: +1 973-996-2298
Mobile: +1 201-341-1393 



--
Robin Cover





--
Robin Cover

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]