[Hyperledger Project TSC] Project proposal for Hyperledger Interledger-Java - an interoperability solution for blockchains, DLTs and other types of ledgers


Isaac Arruebarrena <isaac.arruebarrena@...>
 

Dear all,

 

Over the last 14 months we at everis (an NTT DATA Company) have been collaborating with Ripple on the development of the Java implementation of the Interledger protocol stack. The reason why we started this journey is clear in hindsight: we think that interoperability between blockchains, DLTs, existing centralized ledgers and payment networks is one of the most relevant issues to tackle if we aim to see broad adoption of blockchains and DLTs by the public. We believe that frictionless transactions across networks and the advent of blockchain technologies will boost competition in finance and beyond, accelerating innovation and enabling new business models.

 

With this objective, we would like to submit a project proposal to bring Interledger-Java under the Hyperledger Consortium as an incubation project.  For the name we suggest Hyperledger Interledger-Java, but of course we welcome the input of Hyperledger community members and the Hyperledger Technical Steering Committee.

 

The project proposal is available at:

https://docs.google.com/document/d/1KVrakb2JsqgMo2aG-QIYl743VHsU9NWYKxy7n-WeXv4/edit?usp=sharing

 

With this email we would like to invite the members of the TSC to review and comment on this proposal. We welcome all comments from the community members and look forward to continuing with this interoperability project under the umbrella of the Hyperledger Project.

 

To learn more about Interledger please visit interledger.org

 

The Interledger-Java code is currently hosted and openly developed at:

https://github.com/interledger

 

We hope you will find this submission valuable and look forward to hearing your feedback and questions on this mailing-list or elsewhere.

 

Kind regards,

 

Isaac Arruebarrena 
everis an NTT DATA Company 




CONFIDENTIALITY WARNING.
This message and the information contained in or attached to it are private and confidential and intended exclusively for the addressee. everis informs to whom it may receive it in error that it contains privileged information and its use, copy, reproduction or distribution is prohibited. If you are not an intended recipient of this E-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute any portion of this E-mail.


Adrian Hope-Bailie <adrian@...>
 

Hi Isaac,

Thanks for putting this submission together.

I have one minor question. What was the motivation for using the name Hyperledger Interledger-Java? This will be THE reference Java implementation so I don't think it needs to be "namespaced".
Also, if we use the dot notation it would be consistent with the Interledger.JS project which is the reference Javascript implementation hosted at the JS foundation.

My recommendation would be to call the project Interledger.Java (pronounced interledger-dot-java).

Adrian

On 6 September 2017 at 02:40, Isaac Arruebarrena via hyperledger-tsc <hyperledger-tsc@...> wrote:

Dear all,

 

Over the last 14 months we at everis (an NTT DATA Company) have been collaborating with Ripple on the development of the Java implementation of the Interledger protocol stack. The reason why we started this journey is clear in hindsight: we think that interoperability between blockchains, DLTs, existing centralized ledgers and payment networks is one of the most relevant issues to tackle if we aim to see broad adoption of blockchains and DLTs by the public. We believe that frictionless transactions across networks and the advent of blockchain technologies will boost competition in finance and beyond, accelerating innovation and enabling new business models.

 

With this objective, we would like to submit a project proposal to bring Interledger-Java under the Hyperledger Consortium as an incubation project.  For the name we suggest Hyperledger Interledger-Java, but of course we welcome the input of Hyperledger community members and the Hyperledger Technical Steering Committee.

 

The project proposal is available at:

https://docs.google.com/document/d/1KVrakb2JsqgMo2aG-QIYl743VHsU9NWYKxy7n-WeXv4/edit?usp=sharing

 

With this email we would like to invite the members of the TSC to review and comment on this proposal. We welcome all comments from the community members and look forward to continuing with this interoperability project under the umbrella of the Hyperledger Project.

 

To learn more about Interledger please visit interledger.org

 

The Interledger-Java code is currently hosted and openly developed at:

https://github.com/interledger

 

We hope you will find this submission valuable and look forward to hearing your feedback and questions on this mailing-list or elsewhere.

 

Kind regards,

 

Isaac Arruebarrena 
everis an NTT DATA Company 




CONFIDENTIALITY WARNING.
This message and the information contained in or attached to it are private and confidential and intended exclusively for the addressee. everis informs to whom it may receive it in error that it contains privileged information and its use, copy, reproduction or distribution is prohibited. If you are not an intended recipient of this E-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute any portion of this E-mail.

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc



Isaac Arruebarrena <isaac.arruebarrena@...>
 

Hi Adrian,

I agree with you. It sounds better as Interledger.Java

The reason why I added the "Hyperledger" word was that Brian suggested that it should be clearly distinguished from the W3C Interledger project name.

I also prefer to leave it as it was, with its original name: Interledger.Java

Cheers,

Isaac


On 7 Sep 2017, at 22:52, Adrian Hope-Bailie <adrian@...> wrote:

Hi Isaac,

Thanks for putting this submission together.

I have one minor question. What was the motivation for using the name Hyperledger Interledger-Java? This will be THE reference Java implementation so I don't think it needs to be "namespaced".
Also, if we use the dot notation it would be consistent with the Interledger.JS project which is the reference Javascript implementation hosted at the JS foundation.

My recommendation would be to call the project Interledger.Java (pronounced interledger-dot-java).

Adrian

On 6 September 2017 at 02:40, Isaac Arruebarrena via hyperledger-tsc <hyperledger-tsc@...> wrote:

Dear all,

 

Over the last 14 months we at everis (an NTT DATA Company) have been collaborating with Ripple on the development of the Java implementation of the Interledger protocol stack. The reason why we started this journey is clear in hindsight: we think that interoperability between blockchains, DLTs, existing centralized ledgers and payment networks is one of the most relevant issues to tackle if we aim to see broad adoption of blockchains and DLTs by the public. We believe that frictionless transactions across networks and the advent of blockchain technologies will boost competition in finance and beyond, accelerating innovation and enabling new business models.

 

With this objective, we would like to submit a project proposal to bring Interledger-Java under the Hyperledger Consortium as an incubation project.  For the name we suggest Hyperledger Interledger-Java, but of course we welcome the input of Hyperledger community members and the Hyperledger Technical Steering Committee.

 

The project proposal is available at:

https://docs.google.com/document/d/1KVrakb2JsqgMo2aG-QIYl743VHsU9NWYKxy7n-WeXv4/edit?usp=sharing

 

With this email we would like to invite the members of the TSC to review and comment on this proposal. We welcome all comments from the community members and look forward to continuing with this interoperability project under the umbrella of the Hyperledger Project.

 

To learn more about Interledger please visit interledger.org

 

The Interledger-Java code is currently hosted and openly developed at:

https://github.com/interledger

 

We hope you will find this submission valuable and look forward to hearing your feedback and questions on this mailing-list or elsewhere.

 

Kind regards,

 

Isaac Arruebarrena 
everis an NTT DATA Company 




CONFIDENTIALITY WARNING.
This message and the information contained in or attached to it are private and confidential and intended exclusively for the addressee. everis informs to whom it may receive it in error that it contains privileged information and its use, copy, reproduction or distribution is prohibited. If you are not an intended recipient of this E-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute any portion of this E-mail.

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc





CONFIDENTIALITY WARNING.
This message and the information contained in or attached to it are private and confidential and intended exclusively for the addressee. everis informs to whom it may receive it in error that it contains privileged information and its use, copy, reproduction or distribution is prohibited. If you are not an intended recipient of this E-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute any portion of this E-mail.


Brian Behlendorf
 

 
Interledger.Java is a fine alternative to Interledger-Java. 

All Hyperledger projects formally have "Hyperledger" in front of them, so that for example when the press or someone refers to "Fabric", they refer to "Hyperledger Fabric", and then after that can simply say "Fabric".  We have branding guidelines to this extent that I think are on our website (if not let me know).  Clearly, when talking informally, people can use "Fabric", "Sawtooth", "Interledger.Java", etc. Remember that this name is associated not just with an inert body of code, but with human beings too, who are maintainers of the code and part of the broader HL community.  They are the members of the Hyperledger Interledger.Java community.

I had encouraged Isaac to consider a more abstract name, like our other projects have, for better trademark management - we do end up registering trademarks for many of our project names, so that if someone (intentionally or not) ends up trying to confuse the marketplace by e.g. registering a domain name and calling it "FabricBlockchain.io", we have some ability to go to them and ask them not too.  This is one thing that distinguishes us a bit from the Bitcoin and other crowds, which do very poor brand management, and pay a price for it.  Alternately, projects like Apache generally do a really good job of policing their marks.  It's expensive, but more expensive is confusion over where the community lies, or who "the Fabric community" really is (just using Fabric above as an example).

"Interledger.Java" isn't really a trademarkable name by us.  Presumably someone (W3C? Ripple) has registered the Interledger trademark already, and we have to hope they never choose to use it against us.  Maybe that's a pretty safe bet, but I've seen good intentions go awry in open source before.  So long as the Interledger developers are prepared to change names if that ever happens then, OK.  But it's a risk the TSC should be aware of.  Note that "Java" is a trademark owned by someone else, too, and that could also be an issue.

Lastly, the spirit of a code base isn't really about what APIs it implements, but about what problems it solves.  This code base is about building virtual escrow systems that facilitate transactions and the flow of assets across chains.  That it initially implements the Interledger protocol is pretty interesting, but more a "how" than a "what".  Let's say in three years time a fork in the Interledger community emerges, and this fork has a different name; the maintainers of this project should feel free to pursue that fork if they feel it better serves users' needs, even if that means using a protocol that doesn't carry the name "Interledger", and ideally they can do that in a compatible way.  Using someone else's trademark makes those kinds of choices much more difficult.

This may feel like complicating what is otherwise a simple project proposal, and by suggestion awkward situations I don't mean to imply those are anywhere close to likely.  But they do come from seeing the kinds of situations where initial good intentions turned sour, and how simple choices made early on can reduce the cost of dealing with those siituations later.

I don't have a vote on the TSC, but I would support accepting this project with this name, and dealing with these issues later if need be.  But wanted to share some battle-hardened thoughts on naming and community.

Brian

On 09/07/2017 03:30 PM, Isaac Arruebarrena via hyperledger-tsc wrote:
Hi Adrian,

I agree with you. It sounds better as Interledger.Java

The reason why I added the "Hyperledger" word was that Brian suggested that it should be clearly distinguished from the W3C Interledger project name.

I also prefer to leave it as it was, with its original name: Interledger.Java

Cheers,

Isaac


On 7 Sep 2017, at 22:52, Adrian Hope-Bailie <adrian@...> wrote:

Hi Isaac,

Thanks for putting this submission together.

I have one minor question. What was the motivation for using the name Hyperledger Interledger-Java? This will be THE reference Java implementation so I don't think it needs to be "namespaced".
Also, if we use the dot notation it would be consistent with the Interledger.JS project which is the reference Javascript implementation hosted at the JS foundation.

My recommendation would be to call the project Interledger.Java (pronounced interledger-dot-java).

Adrian

On 6 September 2017 at 02:40, Isaac Arruebarrena via hyperledger-tsc <hyperledger-tsc@...> wrote:

Dear all,

 

Over the last 14 months we at everis (an NTT DATA Company) have been collaborating with Ripple on the development of the Java implementation of the Interledger protocol stack. The reason why we started this journey is clear in hindsight: we think that interoperability between blockchains, DLTs, existing centralized ledgers and payment networks is one of the most relevant issues to tackle if we aim to see broad adoption of blockchains and DLTs by the public. We believe that frictionless transactions across networks and the advent of blockchain technologies will boost competition in finance and beyond, accelerating innovation and enabling new business models.

 

With this objective, we would like to submit a project proposal to bring Interledger-Java under the Hyperledger Consortium as an incubation project.  For the name we suggest Hyperledger Interledger-Java, but of course we welcome the input of Hyperledger community members and the Hyperledger Technical Steering Committee.

 

The project proposal is available at:

https://docs.google.com/document/d/1KVrakb2JsqgMo2aG-QIYl743VHsU9NWYKxy7n-WeXv4/edit?usp=sharing

 

With this email we would like to invite the members of the TSC to review and comment on this proposal. We welcome all comments from the community members and look forward to continuing with this interoperability project under the umbrella of the Hyperledger Project.

 

To learn more about Interledger please visit interledger.org

 

The Interledger-Java code is currently hosted and openly developed at:

https://github.com/interledger

 

We hope you will find this submission valuable and look forward to hearing your feedback and questions on this mailing-list or elsewhere.

 

Kind regards,

 

Isaac Arruebarrena 
everis an NTT DATA Company 




CONFIDENTIALITY WARNING.
This message and the information contained in or attached to it are private and confidential and intended exclusively for the addressee. everis informs to whom it may receive it in error that it contains privileged information and its use, copy, reproduction or distribution is prohibited. If you are not an intended recipient of this E-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute any portion of this E-mail.

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc





CONFIDENTIALITY WARNING.
This message and the information contained in or attached to it are private and confidential and intended exclusively for the addressee. everis informs to whom it may receive it in error that it contains privileged information and its use, copy, reproduction or distribution is prohibited. If you are not an intended recipient of this E-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute any portion of this E-mail.


_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc


-- 
Brian Behlendorf
Executive Director, Hyperledger
bbehlendorf@...
Twitter: @brianbehlendorf


Adrian Hope-Bailie <adrian@...>
 

Thanks Brian, that's useful context.

I think positioning this project simply as:

A project focused on creating interoperability between "value networks" is a good approach. Here I define a value network as any network that tracks the movement of something of value such as a blockchain, a bank, payment network etc. These networks could be underpinned by other Hyperledger technologies such as Fabric, Iroha, Sawtooth etc but also Bitcoin, XRP or non-blockchain systems like Paypal or ACH. Initially the project will acheive this through implementing the Interledger protocol and for now the chosen tech stack is Java.

Do we agree on this as the general goal?

In that vein I'm on board with a generic name that is specific to this project and avoids using both the Interledger and Java marks. A suggestion from someone in our team was Quilt. (Alluding to the idea that the goal is interop between, among other things, Hyperledger Fabric and other systems).

@Isaac What do you think about Hyperledger Quilt (an implementation of the Interledger protocol, written Java).

I would hope that through good architectural governance we'd ensure that the code evolves in such a way as to remain de-coupled from specific ledger implementations so that anyone that wanted to connect, for example, a bank ledger and a blockchain system outside of the Hyperledger stable would have the libraries within this project to do that.


On 7 September 2017 at 19:07, Brian Behlendorf via hyperledger-tsc <hyperledger-tsc@...> wrote:
 
Interledger.Java is a fine alternative to Interledger-Java. 

All Hyperledger projects formally have "Hyperledger" in front of them, so that for example when the press or someone refers to "Fabric", they refer to "Hyperledger Fabric", and then after that can simply say "Fabric".  We have branding guidelines to this extent that I think are on our website (if not let me know).  Clearly, when talking informally, people can use "Fabric", "Sawtooth", "Interledger.Java", etc. Remember that this name is associated not just with an inert body of code, but with human beings too, who are maintainers of the code and part of the broader HL community.  They are the members of the Hyperledger Interledger.Java community.

I had encouraged Isaac to consider a more abstract name, like our other projects have, for better trademark management - we do end up registering trademarks for many of our project names, so that if someone (intentionally or not) ends up trying to confuse the marketplace by e.g. registering a domain name and calling it "FabricBlockchain.io", we have some ability to go to them and ask them not too.  This is one thing that distinguishes us a bit from the Bitcoin and other crowds, which do very poor brand management, and pay a price for it.  Alternately, projects like Apache generally do a really good job of policing their marks.  It's expensive, but more expensive is confusion over where the community lies, or who "the Fabric community" really is (just using Fabric above as an example).

"Interledger.Java" isn't really a trademarkable name by us.  Presumably someone (W3C? Ripple) has registered the Interledger trademark already, and we have to hope they never choose to use it against us.  Maybe that's a pretty safe bet, but I've seen good intentions go awry in open source before.  So long as the Interledger developers are prepared to change names if that ever happens then, OK.  But it's a risk the TSC should be aware of.  Note that "Java" is a trademark owned by someone else, too, and that could also be an issue.

Lastly, the spirit of a code base isn't really about what APIs it implements, but about what problems it solves.  This code base is about building virtual escrow systems that facilitate transactions and the flow of assets across chains.  That it initially implements the Interledger protocol is pretty interesting, but more a "how" than a "what".  Let's say in three years time a fork in the Interledger community emerges, and this fork has a different name; the maintainers of this project should feel free to pursue that fork if they feel it better serves users' needs, even if that means using a protocol that doesn't carry the name "Interledger", and ideally they can do that in a compatible way.  Using someone else's trademark makes those kinds of choices much more difficult.

This may feel like complicating what is otherwise a simple project proposal, and by suggestion awkward situations I don't mean to imply those are anywhere close to likely.  But they do come from seeing the kinds of situations where initial good intentions turned sour, and how simple choices made early on can reduce the cost of dealing with those siituations later.

I don't have a vote on the TSC, but I would support accepting this project with this name, and dealing with these issues later if need be.  But wanted to share some battle-hardened thoughts on naming and community.

Brian


On 09/07/2017 03:30 PM, Isaac Arruebarrena via hyperledger-tsc wrote:
Hi Adrian,

I agree with you. It sounds better as Interledger.Java

The reason why I added the "Hyperledger" word was that Brian suggested that it should be clearly distinguished from the W3C Interledger project name.

I also prefer to leave it as it was, with its original name: Interledger.Java

Cheers,

Isaac


On 7 Sep 2017, at 22:52, Adrian Hope-Bailie <adrian@...> wrote:

Hi Isaac,

Thanks for putting this submission together.

I have one minor question. What was the motivation for using the name Hyperledger Interledger-Java? This will be THE reference Java implementation so I don't think it needs to be "namespaced".
Also, if we use the dot notation it would be consistent with the Interledger.JS project which is the reference Javascript implementation hosted at the JS foundation.

My recommendation would be to call the project Interledger.Java (pronounced interledger-dot-java).

Adrian

On 6 September 2017 at 02:40, Isaac Arruebarrena via hyperledger-tsc <hyperledger-tsc@lists.hyperledger.org> wrote:

Dear all,

 

Over the last 14 months we at everis (an NTT DATA Company) have been collaborating with Ripple on the development of the Java implementation of the Interledger protocol stack. The reason why we started this journey is clear in hindsight: we think that interoperability between blockchains, DLTs, existing centralized ledgers and payment networks is one of the most relevant issues to tackle if we aim to see broad adoption of blockchains and DLTs by the public. We believe that frictionless transactions across networks and the advent of blockchain technologies will boost competition in finance and beyond, accelerating innovation and enabling new business models.

 

With this objective, we would like to submit a project proposal to bring Interledger-Java under the Hyperledger Consortium as an incubation project.  For the name we suggest Hyperledger Interledger-Java, but of course we welcome the input of Hyperledger community members and the Hyperledger Technical Steering Committee.

 

The project proposal is available at:

https://docs.google.com/document/d/1KVrakb2JsqgMo2aG-QIYl743VHsU9NWYKxy7n-WeXv4/edit?usp=sharing

 

With this email we would like to invite the members of the TSC to review and comment on this proposal. We welcome all comments from the community members and look forward to continuing with this interoperability project under the umbrella of the Hyperledger Project.

 

To learn more about Interledger please visit interledger.org

 

The Interledger-Java code is currently hosted and openly developed at:

https://github.com/interledger

 

We hope you will find this submission valuable and look forward to hearing your feedback and questions on this mailing-list or elsewhere.

 

Kind regards,

 

Isaac Arruebarrena 
everis an NTT DATA Company 




CONFIDENTIALITY WARNING.
This message and the information contained in or attached to it are private and confidential and intended exclusively for the addressee. everis informs to whom it may receive it in error that it contains privileged information and its use, copy, reproduction or distribution is prohibited. If you are not an intended recipient of this E-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute any portion of this E-mail.

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...ger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc





CONFIDENTIALITY WARNING.
This message and the information contained in or attached to it are private and confidential and intended exclusively for the addressee. everis informs to whom it may receive it in error that it contains privileged information and its use, copy, reproduction or distribution is prohibited. If you are not an intended recipient of this E-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute any portion of this E-mail.


_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc


-- 
Brian Behlendorf
Executive Director, Hyperledger
bbehlendorf@linuxfoundation.org
Twitter: @brianbehlendorf

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc



Vipin Bharathan
 

Hyperledger Nexus


Dan O'Prey <dan@...>
 

Some input from the marketing side for your consideration:

  • Agree with concerns about using trademarks not owned by HL/LF but am a fan of being as specific as possible as there may well be other interoperability style projects in the future, e.g., Lightning Network and others, so tying the name to what it is, a specific implementation of the Interledger protocol is important
  • Less important to me, and not something that we've done with other projects, is including the language in which it's written, so preference is not to include "Java" in the name. It's up to the TSC whether a C++ implementation of Interledger would be its own separate project or not, and if we arrive at that point then perhaps that's something to reconsider.
  • "Hyperledger Interledger [dot] Java" is quite a mouthful and even "Hyperledger Interledger" seems pretty redundant with the double "ledger".
  • So my suggestion would simply be "Hyperledger ILP". Short, describes what it is as "ILP" is reasonably well known acronym for the protocol it implements, and (IANAL) I believe "ILP" will be less of a trademark issue than the full "Interledger".
  • Failing that, "Hyperledger Inter" is descriptive, tied to the brand, but be less problematic.

On Fri, Sep 8, 2017 at 2:23 PM vipin bharathan via hyperledger-tsc <hyperledger-tsc@...> wrote:
Hyperledger Nexus
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
--

Dan O'Prey

Chief Marketing Officer
c: +1 646-647-5957
e: dan@... 
Digital Asset Holdings, LLC
96 Spring Street, 7th Floor
New York, NY 10012
digitalasset.com

This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.digitalasset.com/emaildisclaimer.html. If you are not the intended recipient, please delete this message.


Adrian Hope-Bailie <adrian@...>
 

> there may well be other interoperability style projects in the future e.g., Lightning Network and others, so tying the name to what it is, a specific implementation of the Interledger protocol is important

That does raise the question whether those could fall under this project or would have to stand-alone.

Interledger is intended to be a layer of abstraction above Lightning, as an example. We have actually done some work using the JS implementation to make ILP payments over Lightning (i.e. Lighning is another network that is made interoperable with any others over which an ILP implementation is available). So an outcome of this project could be interop between Lightning and Aroha for example.

For that reason I'm leaning toward a very generic name that does allow the project to evolve and include numerous "integrations" and still make sense.

Personally I like Hyperledger Quilt, also because it's unique and would be difficult to confuse with anything else.

@Isaac: Any other ideas?


On 8 September 2017 at 11:32, Dan O'Prey <dan@...> wrote:
Some input from the marketing side for your consideration:

  • Agree with concerns about using trademarks not owned by HL/LF but am a fan of being as specific as possible as there may well be other interoperability style projects in the future, e.g., Lightning Network and others, so tying the name to what it is, a specific implementation of the Interledger protocol is important
  • Less important to me, and not something that we've done with other projects, is including the language in which it's written, so preference is not to include "Java" in the name. It's up to the TSC whether a C++ implementation of Interledger would be its own separate project or not, and if we arrive at that point then perhaps that's something to reconsider.
  • "Hyperledger Interledger [dot] Java" is quite a mouthful and even "Hyperledger Interledger" seems pretty redundant with the double "ledger".
  • So my suggestion would simply be "Hyperledger ILP". Short, describes what it is as "ILP" is reasonably well known acronym for the protocol it implements, and (IANAL) I believe "ILP" will be less of a trademark issue than the full "Interledger".
  • Failing that, "Hyperledger Inter" is descriptive, tied to the brand, but be less problematic.

On Fri, Sep 8, 2017 at 2:23 PM vipin bharathan via hyperledger-tsc <hyperledger-tsc@lists.hyperledger.org> wrote:
Hyperledger Nexus
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
--

Dan O'Prey

Chief Marketing Officer
c: +1 646-647-5957
e: dan@... 

This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.digitalasset.com/emaildisclaimer.html. If you are not the intended recipient, please delete this message.


binh nguyen <seeyoucansayo@...>
 

Agreed.  I wouldn't like the implementation language on the top level project name either. We could have that on the sub-project name if we end up with multiple implementations. 

If we entertain new names, I would tee up Hyperledger Connect or Hyperledger Mashup (old term from Web 2.0 days) for consideration :-)

- Binh

On Fri, Sep 8, 2017 at 2:32 PM, Dan O'Prey via hyperledger-tsc <hyperledger-tsc@...> wrote:
Some input from the marketing side for your consideration:

  • Agree with concerns about using trademarks not owned by HL/LF but am a fan of being as specific as possible as there may well be other interoperability style projects in the future, e.g., Lightning Network and others, so tying the name to what it is, a specific implementation of the Interledger protocol is important
  • Less important to me, and not something that we've done with other projects, is including the language in which it's written, so preference is not to include "Java" in the name. It's up to the TSC whether a C++ implementation of Interledger would be its own separate project or not, and if we arrive at that point then perhaps that's something to reconsider.
  • "Hyperledger Interledger [dot] Java" is quite a mouthful and even "Hyperledger Interledger" seems pretty redundant with the double "ledger".
  • So my suggestion would simply be "Hyperledger ILP". Short, describes what it is as "ILP" is reasonably well known acronym for the protocol it implements, and (IANAL) I believe "ILP" will be less of a trademark issue than the full "Interledger".
  • Failing that, "Hyperledger Inter" is descriptive, tied to the brand, but be less problematic.

On Fri, Sep 8, 2017 at 2:23 PM vipin bharathan via hyperledger-tsc <hyperledger-tsc@lists.hyperledger.org> wrote:
Hyperledger Nexus
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
--

Dan O'Prey

Chief Marketing Officer
c: +1 646-647-5957
e: dan@... 
Digital Asset Holdings, LLC
96 Spring Street, 7th Floor
New York, NY 10012
digitalasset.com

This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.digitalasset.com/emaildisclaimer.html. If you are not the intended recipient, please delete this message.

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc



Jim Zhang <jzhang@...>
 

I like "Hyperledger Connect".
 
Jim Zhang
STSM, Blockchain
IBM Cloud
Durham, NC, U.S.A.
Tel: 919-254-8587 
 
 

----- Original message -----
From: binh nguyen via hyperledger-tsc <hyperledger-tsc@...>
Sent by: hyperledger-tsc-bounces@...
To: "Dan O'Prey" <dan@...>
Cc: hyperledger-tsc <hyperledger-tsc@...>
Subject: Re: [Hyperledger Project TSC] Project proposal for Hyperledger Interledger-Java - an interoperability solution for blockchains, DLTs and other types of ledgers
Date: Fri, Sep 8, 2017 3:20 PM
 
Agreed.  I wouldn't like the implementation language on the top level project name either. We could have that on the sub-project name if we end up with multiple implementations. 
 
If we entertain new names, I would tee up Hyperledger Connect or Hyperledger Mashup (old term from Web 2.0 days) for consideration :-)
 
- Binh
 
On Fri, Sep 8, 2017 at 2:32 PM, Dan O'Prey via hyperledger-tsc <hyperledger-tsc@...> wrote:
Some input from the marketing side for your consideration:
 
  • Agree with concerns about using trademarks not owned by HL/LF but am a fan of being as specific as possible as there may well be other interoperability style projects in the future, e.g., Lightning Network and others, so tying the name to what it is, a specific implementation of the Interledger protocol is important
  • Less important to me, and not something that we've done with other projects, is including the language in which it's written, so preference is not to include "Java" in the name. It's up to the TSC whether a C++ implementation of Interledger would be its own separate project or not, and if we arrive at that point then perhaps that's something to reconsider.
  • "Hyperledger Interledger [dot] Java" is quite a mouthful and even "Hyperledger Interledger" seems pretty redundant with the double "ledger".
  • So my suggestion would simply be "Hyperledger ILP". Short, describes what it is as "ILP" is reasonably well known acronym for the protocol it implements, and (IANAL) I believe "ILP" will be less of a trademark issue than the full "Interledger".
  • Failing that, "Hyperledger Inter" is descriptive, tied to the brand, but be less problematic.
 
On Fri, Sep 8, 2017 at 2:23 PM vipin bharathan via hyperledger-tsc <hyperledger-tsc@lists.hyperledger.org> wrote:
Hyperledger Nexus
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
--

Dan O'Prey
Chief Marketing Officer
c: +1 646-647-5957
e: dan@... 
Digital Asset Holdings, LLC
96 Spring Street, 7th Floor
New York, NY 10012
digitalasset.com

This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.digitalasset.com/emaildisclaimer.html. If you are not the intended recipient, please delete this message.
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
 
 


Nathan George <nathan.george@...>
 

In the identity space "connect" and "connections" have very different connotations around linking identities, rather than cross ledger value transfer (which inter-ledger better conveys, but has the trademark issues).  Hyperledger Connect as a brand will cause confusion with concepts in Indy.


On Fri, Sep 8, 2017 at 2:08 PM Jim Zhang via hyperledger-tsc <hyperledger-tsc@...> wrote:
I like "Hyperledger Connect".
 
Jim Zhang
STSM, Blockchain
IBM Cloud
Durham, NC, U.S.A.
Tel: 919-254-8587 
 
 
----- Original message -----
From: binh nguyen via hyperledger-tsc <hyperledger-tsc@...>
Sent by: hyperledger-tsc-bounces@...
To: "Dan O'Prey" <dan@...>
Cc: hyperledger-tsc <hyperledger-tsc@...>
Subject: Re: [Hyperledger Project TSC] Project proposal for Hyperledger Interledger-Java - an interoperability solution for blockchains, DLTs and other types of ledgers
Date: Fri, Sep 8, 2017 3:20 PM
 
Agreed.  I wouldn't like the implementation language on the top level project name either. We could have that on the sub-project name if we end up with multiple implementations. 
 
If we entertain new names, I would tee up Hyperledger Connect or Hyperledger Mashup (old term from Web 2.0 days) for consideration :-)
 
- Binh
 
On Fri, Sep 8, 2017 at 2:32 PM, Dan O'Prey via hyperledger-tsc <hyperledger-tsc@...> wrote:
Some input from the marketing side for your consideration:
 
  • Agree with concerns about using trademarks not owned by HL/LF but am a fan of being as specific as possible as there may well be other interoperability style projects in the future, e.g., Lightning Network and others, so tying the name to what it is, a specific implementation of the Interledger protocol is important
  • Less important to me, and not something that we've done with other projects, is including the language in which it's written, so preference is not to include "Java" in the name. It's up to the TSC whether a C++ implementation of Interledger would be its own separate project or not, and if we arrive at that point then perhaps that's something to reconsider.
  • "Hyperledger Interledger [dot] Java" is quite a mouthful and even "Hyperledger Interledger" seems pretty redundant with the double "ledger".
  • So my suggestion would simply be "Hyperledger ILP". Short, describes what it is as "ILP" is reasonably well known acronym for the protocol it implements, and (IANAL) I believe "ILP" will be less of a trademark issue than the full "Interledger".
  • Failing that, "Hyperledger Inter" is descriptive, tied to the brand, but be less problematic.
 
On Fri, Sep 8, 2017 at 2:23 PM vipin bharathan via hyperledger-tsc <hyperledger-tsc@...> wrote:
Hyperledger Nexus
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
--

Dan O'Prey
Chief Marketing Officer
c: +1 646-647-5957
e: dan@... 
Digital Asset Holdings, LLC
96 Spring Street, 7th Floor
New York, NY 10012
digitalasset.com

This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.digitalasset.com/emaildisclaimer.html. If you are not the intended recipient, please delete this message.
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
 
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc


Adrian Hope-Bailie <adrian@...>
 

I like Hyperledger Connect (we have two primary roles in Interledger which we call ledgers and connectors) but appreciate the ambiguity outside of payments.

Is "Connector" different enough? i.e. Hyperledger Connector

Would a more finance-focused name like Liquid (from liquidity) make sense? i.e. Hyperledger Liquid

On 8 September 2017 at 13:15, Nathan George via hyperledger-tsc <hyperledger-tsc@...> wrote:
In the identity space "connect" and "connections" have very different connotations around linking identities, rather than cross ledger value transfer (which inter-ledger better conveys, but has the trademark issues).  Hyperledger Connect as a brand will cause confusion with concepts in Indy.

On Fri, Sep 8, 2017 at 2:08 PM Jim Zhang via hyperledger-tsc <hyperledger-tsc@lists.hyperledger.org> wrote:
I like "Hyperledger Connect".
 
Jim Zhang
STSM, Blockchain
IBM Cloud
Durham, NC, U.S.A.
Tel: 919-254-8587 
 
 
----- Original message -----
From: binh nguyen via hyperledger-tsc <hyperledger-tsc@lists.hyperledger.org>
Sent by: hyperledger-tsc-bounces@lists.hyperledger.org
To: "Dan O'Prey" <dan@...>
Cc: hyperledger-tsc <hyperledger-tsc@lists.hyperledger.org>
Subject: Re: [Hyperledger Project TSC] Project proposal for Hyperledger Interledger-Java - an interoperability solution for blockchains, DLTs and other types of ledgers
Date: Fri, Sep 8, 2017 3:20 PM
 
Agreed.  I wouldn't like the implementation language on the top level project name either. We could have that on the sub-project name if we end up with multiple implementations. 
 
If we entertain new names, I would tee up Hyperledger Connect or Hyperledger Mashup (old term from Web 2.0 days) for consideration :-)
 
- Binh
 
On Fri, Sep 8, 2017 at 2:32 PM, Dan O'Prey via hyperledger-tsc <hyperledger-tsc@lists.hyperledger.org> wrote:
Some input from the marketing side for your consideration:
 
  • Agree with concerns about using trademarks not owned by HL/LF but am a fan of being as specific as possible as there may well be other interoperability style projects in the future, e.g., Lightning Network and others, so tying the name to what it is, a specific implementation of the Interledger protocol is important
  • Less important to me, and not something that we've done with other projects, is including the language in which it's written, so preference is not to include "Java" in the name. It's up to the TSC whether a C++ implementation of Interledger would be its own separate project or not, and if we arrive at that point then perhaps that's something to reconsider.
  • "Hyperledger Interledger [dot] Java" is quite a mouthful and even "Hyperledger Interledger" seems pretty redundant with the double "ledger".
  • So my suggestion would simply be "Hyperledger ILP". Short, describes what it is as "ILP" is reasonably well known acronym for the protocol it implements, and (IANAL) I believe "ILP" will be less of a trademark issue than the full "Interledger".
  • Failing that, "Hyperledger Inter" is descriptive, tied to the brand, but be less problematic.
 
On Fri, Sep 8, 2017 at 2:23 PM vipin bharathan via hyperledger-tsc <hyperledger-tsc@lists.hyperledger.org> wrote:
Hyperledger Nexus
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
--

Dan O'Prey
Chief Marketing Officer
c: +1 646-647-5957
e: dan@... 
Digital Asset Holdings, LLC
96 Spring Street, 7th Floor
New York, NY 10012
digitalasset.com

This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.digitalasset.com/emaildisclaimer.html. If you are not the intended recipient, please delete this message.
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
 
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc



Dan O'Prey <dan@...>
 

Blockstream have a product called Liquid, so I'd suggest avoiding that


On Fri, Sep 8, 2017 at 5:51 PM Adrian Hope-Bailie via hyperledger-tsc <hyperledger-tsc@...> wrote:
I like Hyperledger Connect (we have two primary roles in Interledger which we call ledgers and connectors) but appreciate the ambiguity outside of payments.

Is "Connector" different enough? i.e. Hyperledger Connector

Would a more finance-focused name like Liquid (from liquidity) make sense? i.e. Hyperledger Liquid

On 8 September 2017 at 13:15, Nathan George via hyperledger-tsc <hyperledger-tsc@...> wrote:
In the identity space "connect" and "connections" have very different connotations around linking identities, rather than cross ledger value transfer (which inter-ledger better conveys, but has the trademark issues).  Hyperledger Connect as a brand will cause confusion with concepts in Indy.

On Fri, Sep 8, 2017 at 2:08 PM Jim Zhang via hyperledger-tsc <hyperledger-tsc@...> wrote:
I like "Hyperledger Connect".
 
Jim Zhang
STSM, Blockchain
IBM Cloud
Durham, NC, U.S.A.
Tel: 919-254-8587 
 
 
----- Original message -----
From: binh nguyen via hyperledger-tsc <hyperledger-tsc@...>
Sent by: hyperledger-tsc-bounces@...
To: "Dan O'Prey" <dan@...>
Cc: hyperledger-tsc <hyperledger-tsc@...>
Subject: Re: [Hyperledger Project TSC] Project proposal for Hyperledger Interledger-Java - an interoperability solution for blockchains, DLTs and other types of ledgers
Date: Fri, Sep 8, 2017 3:20 PM
 
Agreed.  I wouldn't like the implementation language on the top level project name either. We could have that on the sub-project name if we end up with multiple implementations. 
 
If we entertain new names, I would tee up Hyperledger Connect or Hyperledger Mashup (old term from Web 2.0 days) for consideration :-)
 
- Binh
 
On Fri, Sep 8, 2017 at 2:32 PM, Dan O'Prey via hyperledger-tsc <hyperledger-tsc@...> wrote:
Some input from the marketing side for your consideration:
 
  • Agree with concerns about using trademarks not owned by HL/LF but am a fan of being as specific as possible as there may well be other interoperability style projects in the future, e.g., Lightning Network and others, so tying the name to what it is, a specific implementation of the Interledger protocol is important
  • Less important to me, and not something that we've done with other projects, is including the language in which it's written, so preference is not to include "Java" in the name. It's up to the TSC whether a C++ implementation of Interledger would be its own separate project or not, and if we arrive at that point then perhaps that's something to reconsider.
  • "Hyperledger Interledger [dot] Java" is quite a mouthful and even "Hyperledger Interledger" seems pretty redundant with the double "ledger".
  • So my suggestion would simply be "Hyperledger ILP". Short, describes what it is as "ILP" is reasonably well known acronym for the protocol it implements, and (IANAL) I believe "ILP" will be less of a trademark issue than the full "Interledger".
  • Failing that, "Hyperledger Inter" is descriptive, tied to the brand, but be less problematic.
 
On Fri, Sep 8, 2017 at 2:23 PM vipin bharathan via hyperledger-tsc <hyperledger-tsc@...> wrote:
Hyperledger Nexus
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
--

Dan O'Prey
Chief Marketing Officer
c: +1 646-647-5957
e: dan@... 
Digital Asset Holdings, LLC
96 Spring Street, 7th Floor
New York, NY 10012
digitalasset.com

This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.digitalasset.com/emaildisclaimer.html. If you are not the intended recipient, please delete this message.
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
 
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc


_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
--

Dan O'Prey

Chief Marketing Officer
c: +1 646-647-5957
e: dan@... 
Digital Asset Holdings, LLC
96 Spring Street, 7th Floor
New York, NY 10012
digitalasset.com

This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.digitalasset.com/emaildisclaimer.html. If you are not the intended recipient, please delete this message.


Adrian Hope-Bailie <adrian@...>
 

I'm tending more and more toward something passive like Quilt :)

On 8 September 2017 at 14:52, Dan O'Prey <dan@...> wrote:
Blockstream have a product called Liquid, so I'd suggest avoiding that

On Fri, Sep 8, 2017 at 5:51 PM Adrian Hope-Bailie via hyperledger-tsc <hyperledger-tsc@lists.hyperledger.org> wrote:
I like Hyperledger Connect (we have two primary roles in Interledger which we call ledgers and connectors) but appreciate the ambiguity outside of payments.

Is "Connector" different enough? i.e. Hyperledger Connector

Would a more finance-focused name like Liquid (from liquidity) make sense? i.e. Hyperledger Liquid

On 8 September 2017 at 13:15, Nathan George via hyperledger-tsc <hyperledger-tsc@lists.hyperledger.org> wrote:
In the identity space "connect" and "connections" have very different connotations around linking identities, rather than cross ledger value transfer (which inter-ledger better conveys, but has the trademark issues).  Hyperledger Connect as a brand will cause confusion with concepts in Indy.

On Fri, Sep 8, 2017 at 2:08 PM Jim Zhang via hyperledger-tsc <hyperledger-tsc@lists.hyperledger.org> wrote:
I like "Hyperledger Connect".
 
Jim Zhang
STSM, Blockchain
IBM Cloud
Durham, NC, U.S.A.
Tel: 919-254-8587 
 
 
----- Original message -----
From: binh nguyen via hyperledger-tsc <hyperledger-tsc@lists.hyperledger.org>
Sent by: hyperledger-tsc-bounces@lists.hyperledger.org
To: "Dan O'Prey" <dan@...>
Cc: hyperledger-tsc <hyperledger-tsc@lists.hyperledger.org>
Subject: Re: [Hyperledger Project TSC] Project proposal for Hyperledger Interledger-Java - an interoperability solution for blockchains, DLTs and other types of ledgers
Date: Fri, Sep 8, 2017 3:20 PM
 
Agreed.  I wouldn't like the implementation language on the top level project name either. We could have that on the sub-project name if we end up with multiple implementations. 
 
If we entertain new names, I would tee up Hyperledger Connect or Hyperledger Mashup (old term from Web 2.0 days) for consideration :-)
 
- Binh
 
On Fri, Sep 8, 2017 at 2:32 PM, Dan O'Prey via hyperledger-tsc <hyperledger-tsc@lists.hyperledger.org> wrote:
Some input from the marketing side for your consideration:
 
  • Agree with concerns about using trademarks not owned by HL/LF but am a fan of being as specific as possible as there may well be other interoperability style projects in the future, e.g., Lightning Network and others, so tying the name to what it is, a specific implementation of the Interledger protocol is important
  • Less important to me, and not something that we've done with other projects, is including the language in which it's written, so preference is not to include "Java" in the name. It's up to the TSC whether a C++ implementation of Interledger would be its own separate project or not, and if we arrive at that point then perhaps that's something to reconsider.
  • "Hyperledger Interledger [dot] Java" is quite a mouthful and even "Hyperledger Interledger" seems pretty redundant with the double "ledger".
  • So my suggestion would simply be "Hyperledger ILP". Short, describes what it is as "ILP" is reasonably well known acronym for the protocol it implements, and (IANAL) I believe "ILP" will be less of a trademark issue than the full "Interledger".
  • Failing that, "Hyperledger Inter" is descriptive, tied to the brand, but be less problematic.
 
On Fri, Sep 8, 2017 at 2:23 PM vipin bharathan via hyperledger-tsc <hyperledger-tsc@lists.hyperledger.org> wrote:
Hyperledger Nexus
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
--

Dan O'Prey
Chief Marketing Officer
c: +1 646-647-5957
e: dan@... 

This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.digitalasset.com/emaildisclaimer.html. If you are not the intended recipient, please delete this message.
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
 
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc


_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
--

Dan O'Prey

Chief Marketing Officer
c: +1 646-647-5957
e: dan@... 

This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.digitalasset.com/emaildisclaimer.html. If you are not the intended recipient, please delete this message.


Middleton, Dan <dan.middleton@...>
 

+1 Hyperledger ILP

 

 

From: hyperledger-tsc-bounces@... [mailto:hyperledger-tsc-bounces@...] On Behalf Of Adrian Hope-Bailie via hyperledger-tsc
Sent: Friday, September 08, 2017 17:01
To: Dan O'Prey <dan@...>
Cc: hyperledger-tsc <hyperledger-tsc@...>
Subject: Re: [Hyperledger Project TSC] Project proposal for Hyperledger Interledger-Java - an interoperability solution for blockchains, DLTs and other types of ledgers

 

I'm tending more and more toward something passive like Quilt :)

 

On 8 September 2017 at 14:52, Dan O'Prey <dan@...> wrote:

Blockstream have a product called Liquid, so I'd suggest avoiding that

 

On Fri, Sep 8, 2017 at 5:51 PM Adrian Hope-Bailie via hyperledger-tsc <hyperledger-tsc@...> wrote:

I like Hyperledger Connect (we have two primary roles in Interledger which we call ledgers and connectors) but appreciate the ambiguity outside of payments.

Is "Connector" different enough? i.e. Hyperledger Connector

Would a more finance-focused name like Liquid (from liquidity) make sense? i.e. Hyperledger Liquid

 

On 8 September 2017 at 13:15, Nathan George via hyperledger-tsc <hyperledger-tsc@...> wrote:

In the identity space "connect" and "connections" have very different connotations around linking identities, rather than cross ledger value transfer (which inter-ledger better conveys, but has the trademark issues).  Hyperledger Connect as a brand will cause confusion with concepts in Indy.

 

On Fri, Sep 8, 2017 at 2:08 PM Jim Zhang via hyperledger-tsc <hyperledger-tsc@...> wrote:

I like "Hyperledger Connect".

 

Jim Zhang


STSM, Blockchain

IBM Cloud
Durham, NC, U.S.A.
Tel: 919-254-8587 

 

 

----- Original message -----
From: binh nguyen via hyperledger-tsc <hyperledger-tsc@...>
Sent by: hyperledger-tsc-bounces@...
To: "Dan O'Prey" <dan@...>
Cc: hyperledger-tsc <hyperledger-tsc@...>
Subject: Re: [Hyperledger Project TSC] Project proposal for Hyperledger Interledger-Java - an interoperability solution for blockchains, DLTs and other types of ledgers
Date: Fri, Sep 8, 2017 3:20 PM
 

Agreed.  I wouldn't like the implementation language on the top level project name either. We could have that on the sub-project name if we end up with multiple implementations. 

 

If we entertain new names, I would tee up Hyperledger Connect or Hyperledger Mashup (old term from Web 2.0 days) for consideration :-)

 

- Binh

 

On Fri, Sep 8, 2017 at 2:32 PM, Dan O'Prey via hyperledger-tsc <hyperledger-tsc@...> wrote:

Some input from the marketing side for your consideration:

 

  • Agree with concerns about using trademarks not owned by HL/LF but am a fan of being as specific as possible as there may well be other interoperability style projects in the future, e.g., Lightning Network and others, so tying the name to what it is, a specific implementation of the Interledger protocol is important
  • Less important to me, and not something that we've done with other projects, is including the language in which it's written, so preference is not to include "Java" in the name. It's up to the TSC whether a C++ implementation of Interledger would be its own separate project or not, and if we arrive at that point then perhaps that's something to reconsider.
  • "Hyperledger Interledger [dot] Java" is quite a mouthful and even "Hyperledger Interledger" seems pretty redundant with the double "ledger".
  • So my suggestion would simply be "Hyperledger ILP". Short, describes what it is as "ILP" is reasonably well known acronym for the protocol it implements, and (IANAL) I believe "ILP" will be less of a trademark issue than the full "Interledger".
  • Failing that, "Hyperledger Inter" is descriptive, tied to the brand, but be less problematic.

 

On Fri, Sep 8, 2017 at 2:23 PM vipin bharathan via hyperledger-tsc <hyperledger-tsc@...> wrote:

Hyperledger Nexus

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc

--


Dan O'Prey
Chief Marketing Officer
c: +1 646-647-5957
e: dan@... 

Error! Filename not specified.Digital Asset Holdings, LLC
96 Spring Street, 7th Floor
New York, NY 10012
digitalasset.com


This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.digitalasset.com/emaildisclaimer.html. If you are not the intended recipient, please delete this message.
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
 

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...


_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc


_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc

 

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc

--


Dan O'Prey

Chief Marketing Officer
c: +1 646-647-5957
e: dan@... 


This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.digitalasset.com/emaildisclaimer.html. If you are not the intended recipient, please delete this message.

 


Brian Behlendorf
 

I like Quilt. It's too bad there aren't many words where "ILP" occur in a simple way, but QuILt can at least contain IL. Or to weave Java into it... Hyperledger Jill?

But I like where this is headed.

Brian

On September 9, 2017 7:00:33 AM GMT+09:00, Adrian Hope-Bailie via hyperledger-tsc <hyperledger-tsc@...> wrote:
I'm tending more and more toward something passive like Quilt :)

On 8 September 2017 at 14:52, Dan O'Prey <dan@...> wrote:
Blockstream have a product called Liquid, so I'd suggest avoiding that

On Fri, Sep 8, 2017 at 5:51 PM Adrian Hope-Bailie via hyperledger-tsc <hyperledger-tsc@lists.hyperledger.org> wrote:
I like Hyperledger Connect (we have two primary roles in Interledger which we call ledgers and connectors) but appreciate the ambiguity outside of payments.

Is "Connector" different enough? i.e. Hyperledger Connector

Would a more finance-focused name like Liquid (from liquidity) make sense? i.e. Hyperledger Liquid

On 8 September 2017 at 13:15, Nathan George via hyperledger-tsc <hyperledger-tsc@lists.hyperledger.org> wrote:
In the identity space "connect" and "connections" have very different connotations around linking identities, rather than cross ledger value transfer (which inter-ledger better conveys, but has the trademark issues).  Hyperledger Connect as a brand will cause confusion with concepts in Indy.

On Fri, Sep 8, 2017 at 2:08 PM Jim Zhang via hyperledger-tsc <hyperledger-tsc@lists.hyperledger.org> wrote:
I like "Hyperledger Connect".
 
Jim Zhang
STSM, Blockchain
IBM Cloud
Durham, NC, U.S.A.
Tel: 919-254-8587 
 
 
----- Original message -----
From: binh nguyen via hyperledger-tsc <hyperledger-tsc@lists.hyperledger.org>
Sent by: hyperledger-tsc-bounces@lists.hyperledger.org
To: "Dan O'Prey" <dan@...>
Cc: hyperledger-tsc <hyperledger-tsc@lists.hyperledger.org>
Subject: Re: [Hyperledger Project TSC] Project proposal for Hyperledger Interledger-Java - an interoperability solution for blockchains, DLTs and other types of ledgers
Date: Fri, Sep 8, 2017 3:20 PM
 
Agreed.  I wouldn't like the implementation language on the top level project name either. We could have that on the sub-project name if we end up with multiple implementations. 
 
If we entertain new names, I would tee up Hyperledger Connect or Hyperledger Mashup (old term from Web 2.0 days) for consideration :-)
 
- Binh
 
On Fri, Sep 8, 2017 at 2:32 PM, Dan O'Prey via hyperledger-tsc <hyperledger-tsc@lists.hyperledger.org> wrote:
Some input from the marketing side for your consideration:
 
  • Agree with concerns about using trademarks not owned by HL/LF but am a fan of being as specific as possible as there may well be other interoperability style projects in the future, e.g., Lightning Network and others, so tying the name to what it is, a specific implementation of the Interledger protocol is important
  • Less important to me, and not something that we've done with other projects, is including the language in which it's written, so preference is not to include "Java" in the name. It's up to the TSC whether a C++ implementation of Interledger would be its own separate project or not, and if we arrive at that point then perhaps that's something to reconsider.
  • "Hyperledger Interledger [dot] Java" is quite a mouthful and even "Hyperledger Interledger" seems pretty redundant with the double "ledger".
  • So my suggestion would simply be "Hyperledger ILP". Short, describes what it is as "ILP" is reasonably well known acronym for the protocol it implements, and (IANAL) I believe "ILP" will be less of a trademark issue than the full "Interledger".
  • Failing that, "Hyperledger Inter" is descriptive, tied to the brand, but be less problematic.
 
On Fri, Sep 8, 2017 at 2:23 PM vipin bharathan via hyperledger-tsc <hyperledger-tsc@lists.hyperledger.org> wrote:
Hyperledger Nexus
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
--

Dan O'Prey
Chief Marketing Officer
c: +1 646-647-5957
e: dan@... 

This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.digitalasset.com/emaildisclaimer.html. If you are not the intended recipient, please delete this message.
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
 
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc


_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
--

Dan O'Prey

Chief Marketing Officer
c: +1 646-647-5957
e: dan@... 

This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.digitalasset.com/emaildisclaimer.html. If you are not the intended recipient, please delete this message.


--
Sent from my Android device with K-9 Mail. Please excuse my brevity.


Baohua Yang
 

Seems the naming attracts lots of discussions (again) -:)

Let's summarize the latest result besides the original interledger.java one:

* Hyperledger ILP
* Hyperledger Nexus
* Hyperledger Quilt
* Hyperledger Connect/Connector


I personally prefer names like Nexus/Quilt, as it's usually hard to include all the meanings using a single word like inter/connect/bridge....

On Sat, Sep 9, 2017 at 10:36 AM, Brian Behlendorf via hyperledger-tsc <hyperledger-tsc@...> wrote:
I like Quilt. It's too bad there aren't many words where "ILP" occur in a simple way, but QuILt can at least contain IL. Or to weave Java into it... Hyperledger Jill?

But I like where this is headed.

Brian


On September 9, 2017 7:00:33 AM GMT+09:00, Adrian Hope-Bailie via hyperledger-tsc <hyperledger-tsc@lists.hyperledger.org> wrote:
I'm tending more and more toward something passive like Quilt :)

On 8 September 2017 at 14:52, Dan O'Prey <dan@...> wrote:
Blockstream have a product called Liquid, so I'd suggest avoiding that

On Fri, Sep 8, 2017 at 5:51 PM Adrian Hope-Bailie via hyperledger-tsc <hyperledger-tsc@...dger.org> wrote:
I like Hyperledger Connect (we have two primary roles in Interledger which we call ledgers and connectors) but appreciate the ambiguity outside of payments.

Is "Connector" different enough? i.e. Hyperledger Connector

Would a more finance-focused name like Liquid (from liquidity) make sense? i.e. Hyperledger Liquid

On 8 September 2017 at 13:15, Nathan George via hyperledger-tsc <hyperledger-tsc@...dger.org> wrote:
In the identity space "connect" and "connections" have very different connotations around linking identities, rather than cross ledger value transfer (which inter-ledger better conveys, but has the trademark issues).  Hyperledger Connect as a brand will cause confusion with concepts in Indy.

On Fri, Sep 8, 2017 at 2:08 PM Jim Zhang via hyperledger-tsc <hyperledger-tsc@...dger.org> wrote:
I like "Hyperledger Connect".
 
Jim Zhang
STSM, Blockchain
IBM Cloud
Durham, NC, U.S.A.
Tel: 919-254-8587 
 
 
----- Original message -----
From: binh nguyen via hyperledger-tsc <hyperledger-tsc@...dger.org>
Sent by: hyperledger-tsc-bounces@lists.hyperledger.org
To: "Dan O'Prey" <dan@...>
Cc: hyperledger-tsc <hyperledger-tsc@...dger.org>
Subject: Re: [Hyperledger Project TSC] Project proposal for Hyperledger Interledger-Java - an interoperability solution for blockchains, DLTs and other types of ledgers
Date: Fri, Sep 8, 2017 3:20 PM
 
Agreed.  I wouldn't like the implementation language on the top level project name either. We could have that on the sub-project name if we end up with multiple implementations. 
 
If we entertain new names, I would tee up Hyperledger Connect or Hyperledger Mashup (old term from Web 2.0 days) for consideration :-)
 
- Binh
 
On Fri, Sep 8, 2017 at 2:32 PM, Dan O'Prey via hyperledger-tsc <hyperledger-tsc@...dger.org> wrote:
Some input from the marketing side for your consideration:
 
  • Agree with concerns about using trademarks not owned by HL/LF but am a fan of being as specific as possible as there may well be other interoperability style projects in the future, e.g., Lightning Network and others, so tying the name to what it is, a specific implementation of the Interledger protocol is important
  • Less important to me, and not something that we've done with other projects, is including the language in which it's written, so preference is not to include "Java" in the name. It's up to the TSC whether a C++ implementation of Interledger would be its own separate project or not, and if we arrive at that point then perhaps that's something to reconsider.
  • "Hyperledger Interledger [dot] Java" is quite a mouthful and even "Hyperledger Interledger" seems pretty redundant with the double "ledger".
  • So my suggestion would simply be "Hyperledger ILP". Short, describes what it is as "ILP" is reasonably well known acronym for the protocol it implements, and (IANAL) I believe "ILP" will be less of a trademark issue than the full "Interledger".
  • Failing that, "Hyperledger Inter" is descriptive, tied to the brand, but be less problematic.
 
On Fri, Sep 8, 2017 at 2:23 PM vipin bharathan via hyperledger-tsc <hyperledger-tsc@...dger.org> wrote:
Hyperledger Nexus
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...ger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
--

Dan O'Prey
Chief Marketing Officer
c: +1 646-647-5957
e: dan@... 

This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.digitalasset.com/emaildisclaimer.html. If you are not the intended recipient, please delete this message.
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...ger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
 
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...ger.org

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...ger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...ger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc


_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...ger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
--

Dan O'Prey

Chief Marketing Officer
c: +1 646-647-5957
e: dan@... 

This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.digitalasset.com/emaildisclaimer.html. If you are not the intended recipient, please delete this message.


--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc




--
Best wishes!

Baohua Yang


bill
 

I am thinking of words that describe joining rope ends together with more of an integral connection than a bulky knot such as interweave or braid.  There are also pretty knots such as Carrick, etc.  just a thought.

Quilt is nice but I get a preconceived vision of a patchwork rather than a deliberate integrated work.  Maybe just me though.

I thought lattice might be nice but most photos of lattices appear to be more layered than woven.

Bill

On Sep 8, 2017, at 9:36 PM, Brian Behlendorf via hyperledger-tsc <hyperledger-tsc@...> wrote:

I like Quilt. It's too bad there aren't many words where "ILP" occur in a simple way, but QuILt can at least contain IL. Or to weave Java into it... Hyperledger Jill?

But I like where this is headed.

Brian

On September 9, 2017 7:00:33 AM GMT+09:00, Adrian Hope-Bailie via hyperledger-tsc <hyperledger-tsc@...> wrote:
I'm tending more and more toward something passive like Quilt :)

On 8 September 2017 at 14:52, Dan O'Prey <dan@...> wrote:
Blockstream have a product called Liquid, so I'd suggest avoiding that

On Fri, Sep 8, 2017 at 5:51 PM Adrian Hope-Bailie via hyperledger-tsc <hyperledger-tsc@lists.hyperledger.org> wrote:
I like Hyperledger Connect (we have two primary roles in Interledger which we call ledgers and connectors) but appreciate the ambiguity outside of payments.

Is "Connector" different enough? i.e. Hyperledger Connector

Would a more finance-focused name like Liquid (from liquidity) make sense? i.e. Hyperledger Liquid

On 8 September 2017 at 13:15, Nathan George via hyperledger-tsc <hyperledger-tsc@lists.hyperledger.org> wrote:
In the identity space "connect" and "connections" have very different connotations around linking identities, rather than cross ledger value transfer (which inter-ledger better conveys, but has the trademark issues).  Hyperledger Connect as a brand will cause confusion with concepts in Indy.

On Fri, Sep 8, 2017 at 2:08 PM Jim Zhang via hyperledger-tsc <hyperledger-tsc@lists.hyperledger.org> wrote:
I like "Hyperledger Connect".
 
Jim Zhang
STSM, Blockchain
IBM Cloud
Durham, NC, U.S.A.
Tel: 919-254-8587 
 
 
----- Original message -----
From: binh nguyen via hyperledger-tsc <hyperledger-tsc@lists.hyperledger.org>
Sent by: hyperledger-tsc-bounces@lists.hyperledger.org
To: "Dan O'Prey" <dan@...>
Cc: hyperledger-tsc <hyperledger-tsc@lists.hyperledger.org>
Subject: Re: [Hyperledger Project TSC] Project proposal for Hyperledger Interledger-Java - an interoperability solution for blockchains, DLTs and other types of ledgers
Date: Fri, Sep 8, 2017 3:20 PM
 
Agreed.  I wouldn't like the implementation language on the top level project name either. We could have that on the sub-project name if we end up with multiple implementations. 
 
If we entertain new names, I would tee up Hyperledger Connect or Hyperledger Mashup (old term from Web 2.0 days) for consideration :-)
 
- Binh
 
On Fri, Sep 8, 2017 at 2:32 PM, Dan O'Prey via hyperledger-tsc <hyperledger-tsc@lists.hyperledger.org> wrote:
Some input from the marketing side for your consideration:
 
  • Agree with concerns about using trademarks not owned by HL/LF but am a fan of being as specific as possible as there may well be other interoperability style projects in the future, e.g., Lightning Network and others, so tying the name to what it is, a specific implementation of the Interledger protocol is important
  • Less important to me, and not something that we've done with other projects, is including the language in which it's written, so preference is not to include "Java" in the name. It's up to the TSC whether a C++ implementation of Interledger would be its own separate project or not, and if we arrive at that point then perhaps that's something to reconsider.
  • "Hyperledger Interledger [dot] Java" is quite a mouthful and even "Hyperledger Interledger" seems pretty redundant with the double "ledger".
  • So my suggestion would simply be "Hyperledger ILP". Short, describes what it is as "ILP" is reasonably well known acronym for the protocol it implements, and (IANAL) I believe "ILP" will be less of a trademark issue than the full "Interledger".
  • Failing that, "Hyperledger Inter" is descriptive, tied to the brand, but be less problematic.
 
On Fri, Sep 8, 2017 at 2:23 PM vipin bharathan via hyperledger-tsc <hyperledger-tsc@lists.hyperledger.org> wrote:
Hyperledger Nexus
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
--

Dan O'Prey
Chief Marketing Officer
c: +1 646-647-5957
e: dan@... 

This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.digitalasset.com/emaildisclaimer.html. If you are not the intended recipient, please delete this message.
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
 
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc


_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
--

Dan O'Prey

Chief Marketing Officer
c: +1 646-647-5957
e: dan@... 

This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.digitalasset.com/emaildisclaimer.html. If you are not the intended recipient, please delete this message.


--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc


Christopher Ferris <chris.ferris@...>
 

I kind of like Hyperledger QuILT - the ILT could be "Interledger Transaction"

Chris

On Fri, Sep 8, 2017 at 10:36 PM, Brian Behlendorf via hyperledger-tsc <hyperledger-tsc@...> wrote:
I like Quilt. It's too bad there aren't many words where "ILP" occur in a simple way, but QuILt can at least contain IL. Or to weave Java into it... Hyperledger Jill?

But I like where this is headed.

Brian


On September 9, 2017 7:00:33 AM GMT+09:00, Adrian Hope-Bailie via hyperledger-tsc <hyperledger-tsc@lists.hyperledger.org> wrote:
I'm tending more and more toward something passive like Quilt :)

On 8 September 2017 at 14:52, Dan O'Prey <dan@...> wrote:
Blockstream have a product called Liquid, so I'd suggest avoiding that

On Fri, Sep 8, 2017 at 5:51 PM Adrian Hope-Bailie via hyperledger-tsc <hyperledger-tsc@...dger.org> wrote:
I like Hyperledger Connect (we have two primary roles in Interledger which we call ledgers and connectors) but appreciate the ambiguity outside of payments.

Is "Connector" different enough? i.e. Hyperledger Connector

Would a more finance-focused name like Liquid (from liquidity) make sense? i.e. Hyperledger Liquid

On 8 September 2017 at 13:15, Nathan George via hyperledger-tsc <hyperledger-tsc@...dger.org> wrote:
In the identity space "connect" and "connections" have very different connotations around linking identities, rather than cross ledger value transfer (which inter-ledger better conveys, but has the trademark issues).  Hyperledger Connect as a brand will cause confusion with concepts in Indy.

On Fri, Sep 8, 2017 at 2:08 PM Jim Zhang via hyperledger-tsc <hyperledger-tsc@...dger.org> wrote:
I like "Hyperledger Connect".
 
Jim Zhang
STSM, Blockchain
IBM Cloud
Durham, NC, U.S.A.
Tel: 919-254-8587 
 
 
----- Original message -----
From: binh nguyen via hyperledger-tsc <hyperledger-tsc@...dger.org>
Sent by: hyperledger-tsc-bounces@lists.hyperledger.org
To: "Dan O'Prey" <dan@...>
Cc: hyperledger-tsc <hyperledger-tsc@...dger.org>
Subject: Re: [Hyperledger Project TSC] Project proposal for Hyperledger Interledger-Java - an interoperability solution for blockchains, DLTs and other types of ledgers
Date: Fri, Sep 8, 2017 3:20 PM
 
Agreed.  I wouldn't like the implementation language on the top level project name either. We could have that on the sub-project name if we end up with multiple implementations. 
 
If we entertain new names, I would tee up Hyperledger Connect or Hyperledger Mashup (old term from Web 2.0 days) for consideration :-)
 
- Binh
 
On Fri, Sep 8, 2017 at 2:32 PM, Dan O'Prey via hyperledger-tsc <hyperledger-tsc@...dger.org> wrote:
Some input from the marketing side for your consideration:
 
  • Agree with concerns about using trademarks not owned by HL/LF but am a fan of being as specific as possible as there may well be other interoperability style projects in the future, e.g., Lightning Network and others, so tying the name to what it is, a specific implementation of the Interledger protocol is important
  • Less important to me, and not something that we've done with other projects, is including the language in which it's written, so preference is not to include "Java" in the name. It's up to the TSC whether a C++ implementation of Interledger would be its own separate project or not, and if we arrive at that point then perhaps that's something to reconsider.
  • "Hyperledger Interledger [dot] Java" is quite a mouthful and even "Hyperledger Interledger" seems pretty redundant with the double "ledger".
  • So my suggestion would simply be "Hyperledger ILP". Short, describes what it is as "ILP" is reasonably well known acronym for the protocol it implements, and (IANAL) I believe "ILP" will be less of a trademark issue than the full "Interledger".
  • Failing that, "Hyperledger Inter" is descriptive, tied to the brand, but be less problematic.
 
On Fri, Sep 8, 2017 at 2:23 PM vipin bharathan via hyperledger-tsc <hyperledger-tsc@...dger.org> wrote:
Hyperledger Nexus
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...ger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
--

Dan O'Prey
Chief Marketing Officer
c: +1 646-647-5957
e: dan@... 

This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.digitalasset.com/emaildisclaimer.html. If you are not the intended recipient, please delete this message.
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...ger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
 
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...ger.org

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...ger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...ger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc


_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...ger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
--

Dan O'Prey

Chief Marketing Officer
c: +1 646-647-5957
e: dan@... 

This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.digitalasset.com/emaildisclaimer.html. If you are not the intended recipient, please delete this message.


--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc



Baohua Yang
 

Agree with the feeling of Quilt.

While better not use "lattice", as it already has special meaning in math and crypto areas.

On Sat, Sep 9, 2017 at 5:08 PM, William Sparks via hyperledger-tsc <hyperledger-tsc@...> wrote:
I am thinking of words that describe joining rope ends together with more of an integral connection than a bulky knot such as interweave or braid.  There are also pretty knots such as Carrick, etc.  just a thought.

Quilt is nice but I get a preconceived vision of a patchwork rather than a deliberate integrated work.  Maybe just me though.

I thought lattice might be nice but most photos of lattices appear to be more layered than woven.

Bill

On Sep 8, 2017, at 9:36 PM, Brian Behlendorf via hyperledger-tsc <hyperledger-tsc@lists.hyperledger.org> wrote:

I like Quilt. It's too bad there aren't many words where "ILP" occur in a simple way, but QuILt can at least contain IL. Or to weave Java into it... Hyperledger Jill?

But I like where this is headed.

Brian

On September 9, 2017 7:00:33 AM GMT+09:00, Adrian Hope-Bailie via hyperledger-tsc <hyperledger-tsc@lists.hyperledger.org> wrote:
I'm tending more and more toward something passive like Quilt :)

On 8 September 2017 at 14:52, Dan O'Prey <dan@...> wrote:
Blockstream have a product called Liquid, so I'd suggest avoiding that

On Fri, Sep 8, 2017 at 5:51 PM Adrian Hope-Bailie via hyperledger-tsc <hyperledger-tsc@...dger.org> wrote:
I like Hyperledger Connect (we have two primary roles in Interledger which we call ledgers and connectors) but appreciate the ambiguity outside of payments.

Is "Connector" different enough? i.e. Hyperledger Connector

Would a more finance-focused name like Liquid (from liquidity) make sense? i.e. Hyperledger Liquid

On 8 September 2017 at 13:15, Nathan George via hyperledger-tsc <hyperledger-tsc@...dger.org> wrote:
In the identity space "connect" and "connections" have very different connotations around linking identities, rather than cross ledger value transfer (which inter-ledger better conveys, but has the trademark issues).  Hyperledger Connect as a brand will cause confusion with concepts in Indy.

On Fri, Sep 8, 2017 at 2:08 PM Jim Zhang via hyperledger-tsc <hyperledger-tsc@...dger.org> wrote:
I like "Hyperledger Connect".
 
Jim Zhang
STSM, Blockchain
IBM Cloud
Durham, NC, U.S.A.
Tel: 919-254-8587 
 
 
----- Original message -----
From: binh nguyen via hyperledger-tsc <hyperledger-tsc@...dger.org>
Sent by: hyperledger-tsc-bounces@lists.hyperledger.org
To: "Dan O'Prey" <dan@...>
Cc: hyperledger-tsc <hyperledger-tsc@...dger.org>
Subject: Re: [Hyperledger Project TSC] Project proposal for Hyperledger Interledger-Java - an interoperability solution for blockchains, DLTs and other types of ledgers
Date: Fri, Sep 8, 2017 3:20 PM
 
Agreed.  I wouldn't like the implementation language on the top level project name either. We could have that on the sub-project name if we end up with multiple implementations. 
 
If we entertain new names, I would tee up Hyperledger Connect or Hyperledger Mashup (old term from Web 2.0 days) for consideration :-)
 
- Binh
 
On Fri, Sep 8, 2017 at 2:32 PM, Dan O'Prey via hyperledger-tsc <hyperledger-tsc@...dger.org> wrote:
Some input from the marketing side for your consideration:
 
  • Agree with concerns about using trademarks not owned by HL/LF but am a fan of being as specific as possible as there may well be other interoperability style projects in the future, e.g., Lightning Network and others, so tying the name to what it is, a specific implementation of the Interledger protocol is important
  • Less important to me, and not something that we've done with other projects, is including the language in which it's written, so preference is not to include "Java" in the name. It's up to the TSC whether a C++ implementation of Interledger would be its own separate project or not, and if we arrive at that point then perhaps that's something to reconsider.
  • "Hyperledger Interledger [dot] Java" is quite a mouthful and even "Hyperledger Interledger" seems pretty redundant with the double "ledger".
  • So my suggestion would simply be "Hyperledger ILP". Short, describes what it is as "ILP" is reasonably well known acronym for the protocol it implements, and (IANAL) I believe "ILP" will be less of a trademark issue than the full "Interledger".
  • Failing that, "Hyperledger Inter" is descriptive, tied to the brand, but be less problematic.
 
On Fri, Sep 8, 2017 at 2:23 PM vipin bharathan via hyperledger-tsc <hyperledger-tsc@...dger.org> wrote:
Hyperledger Nexus
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...ger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
--

Dan O'Prey
Chief Marketing Officer
c: +1 646-647-5957
e: dan@... 

This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.digitalasset.com/emaildisclaimer.html. If you are not the intended recipient, please delete this message.
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...ger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
 
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...ger.org

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...ger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...ger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc


_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@...ger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc
--

Dan O'Prey

Chief Marketing Officer
c: +1 646-647-5957
e: dan@... 

This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.digitalasset.com/emaildisclaimer.html. If you are not the intended recipient, please delete this message.


--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc

_______________________________________________
hyperledger-tsc mailing list
hyperledger-tsc@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-tsc




--
Best wishes!

Baohua Yang