Archive for August, 2008
by Chuck Kisselburg
ICANNWiki.org
There is no doubt I continue to be fascinated by this community of ours. It is rare to find a community that involves the growth of an in industry before our very eyes! An industry that affects large numbers of this globe’s population; whether directly or indirectly. You’ve heard me mention this several times, but I get energized by the entrepreneurial spirit found in the overall ICANN community.
When thinking about this further, it all seems to boil down to (for me, anyway) the name space or the domain name. What IS a domain name? This is where I like to also use the term name space as we are all using the Internet based on how we name the space of our destinations.
What does such a “name space” consist of? Is it the simple URL followed by the traditional .com, .net, .biz, .info, .org, etc… ? For many the term “name space” can mean “brand”. It is because of such branding that we see the various UDRP cases to clear up who owns the brand, or the “name” for such a brand, or any “names” that may be “confusingly similar” to such brands.
For me it goes deeper than brand. For me it means identity. Not only does our industry help define identity within this virtual universe we call the Internet, it can be used to identify to this virtual universe who “WE” are. Who I am. Who you are. So in my earlier reference of how we name the space of our destinations, that is only part true. There is a whole emerging industry that focuses on the other half of the name space and that is the space that identifies NOT the destination, but the originator. In other words, the part of the industry where the name space identifies who YOU, the individual, are.
OpenID is one such aspect of the industry that is growing rapidly. As stated in my earlier post from this year many large organizations have adopted the use of OpenID. Two camps have been helping identify the OpenID movement. While you have one camp, called “OpenID” you have another that provides a more secure form of OpenID known as the iname.
The whole purpose of OpenID is to allow you to use your same OpenID, or iname at any site that supports the general OpenID specification. The roadmap for the whole OpenID movement is for you to be able to customize attributes of YOUR OpenID or iname so not only can sites learn more about you with only the information you provide in your various attributes, it becomes YOUR identity, or trusted name space when accessing destinations around our virtual universe. It also serves as a way for people you know who tend to visit the same sites as you, they will see input from the use of your iname or OpenID. Being that you can use the same iname or OpenID across many sites, it is a good way for your friends to validate information that came from YOU, a trusted source.
So just as the ICANN community “traditionally” thinks of the name space as a domain name for a destination on the net, we need to start thinking about the name space for the originator on the net. The nice thing about inames is you can acquire your iname just like you can with destination name spaces, or domain names. Earlier I mentioned the iname concept being more secure than the original OpenID movement. This is true because inames were developed with security in mind. Meaning, once you acquire your iname, the secure number generated with that iname is yours forever. If you allow your iname to lapse where it is later picked up by someone else, that “someone else” receives a newly generated identification number. This way when that “someone else” uses the iname you allowed to lapse, it can never be fully tied to you as the generated secure ID numbers are different, and will forever be different.
The other thing that inames allows is for multiple structures for the use of an iname. For example NeuStar and 1id are allowing ICANNWiki users to pick up their own ICANNWiki community iname. So, for example, my ICANNWiki community iname is “@icannwiki*chuck”. So as part of the ICANNWiki community I specify myself (“*chuck”) as being a member of the ICANNWiki community (“@icannwiki”). Now I can go to any site that supports the general OpenID movement and use my ICANNWiki community iname to log in. Sweet!
If you don’t already have your iname, check it out for yourself and use the other half of our virtual universe’s name space! Obtain your ICANNWiki community iname by going here or obtain your own personal iname by going here.
August 25th, 2008
by Chuck Kisselburg
ICANNWiki.org
As you can see from information about the wiki, ICANNWiki.org is based in the city of Portland, in the state of Oregon.
Oregon is one of the world leaders for the Open Source community. In fact, it is not uncommon for companies from around the globe to open up a research and development arm here in Oregon to take advantage of Oregon’s Open Source community.
Portland, Oregon’s largest city, is home to many people who actively work with and develop for the Open Source community. As such there are many ideas and conversations regarding community. From my perspective, with my position at ICANNWiki, I can not think of a better city in which to be located to have active, ongoing conversations with other members of the Open Source community.
With that said I was at an informal after-hours event a couple of days ago where I had an interesting conversation with a gentleman whose business profession is that of copy writing. I have always viewed copy writers of any country as the unofficial keepers of their respective language. A good copy writer ensures what we read not only conveys the message properly, they ensure that what is conveyed is grammatically correct.
After learning about ICANNWiki.org and how it is a neutral resource for the various communities that make up the overall ICANN community, those being ICANN academics, registries, registrars and domainers, he could not help but refer to this community as “Your Community”. He was not referring to “Your Community” in a bad way, just his way of referencing the whole ICANN community in our conversation.
The reason I thought this conversation was interesting enough for a separate post is every language, in some way or another is adaptable over time. English is one of the more flexible, or adaptable languages out there. He noted that as time has progressed the English language has evolved very rapidly in the last decade. True, the advent of computers have brought English terms to English and other languages, such as “PC”, “hard disk” and “mouse”, to name a few. Also, through “Your Community” new words have emerged, such as “Google”, “Twitter” and “Yelp”, also to name a few. However this gentleman felt that “Your Community”, or the overall ICANN community, has done more for bringing change to, or “influencing” the English language than any other such “influencer”. What he was referring to was how the Internet has brought people together, locally as well as globally and how communication can take place NOW as opposed to later. People can text, call, IM (instant message), e-mail, play games, connect with other networks, etc… FAR more easily than they could a little over a decade ago. Think back to your communication habits or capabilities back in 1995.
ICANN has created the standards and stability for the Internet. Companies and domainers, through development, provide the content and applications people use while registries and registrars provide the naming conventions people use to access applications. So, in a nut shell, “Your Community” has done a lot to advance the evolution of the English language.
With that said I could not help but wonder if a person, whose profession is copy writer in the English language, has already seen a quicker evolution of English, what will other copy writers experience of their respective languages once IDNs have been implemented for 5 years?
So while he kept referring to “Your Community” in our conversation, I couldn’t help but think about “Our Community” and how often can you be part of something where “Your Community” can have such an influence on the evolution of languages and how people communicate. So, hat’s off to “Our Community”!
August 18th, 2008
By Chuck Kisselburg
ICANNWiki.org
The below is what was printed in today’s Sedo newsletter, with content assembled by Crystal Peterson of The Public Interest Registry.
With the increased focus on the importance of corporate social responsibility and green issues, businesses are reaping the rewards of maintaining a separate .org website alongside their commercial .com.
What better way to clearly differentiate charitable and social initiatives from commercial initiatives than by operating a .org to highlight a corporate foundation’s mission?
Just look at these leading companies for examples of the trend to utilize their .org for corporate foundations:
• WholeFoodsMarket.com runs the WholePlanetFoundation.org to provide “innovative assistance for entrepreneurship - including direct microcredit loans and tangible support for other community partnership projects…to create wealth and prosperity in emerging economies;” and
• Google.com operates Google.org, which “aspires to use the power of information and technology to address the global challenges of our age: climate change, poverty and emerging disease.”
“Google and Whole Foods are just two of the innovative corporations that are branding their green initiatives, philanthropic efforts and outreach activities behind the Trustmark of .org to gain more attention and traffic,” says Alexa Raad, CEO of .org, The Public Interest Registry.
Most organizations, who have a .org in conjunction with other TLDs, point their .org to their principle TLD to maximize the number of eyeballs to their core product. However, with ICANNWiki.org’s focus being “community”, many organizations miss a golden opportunity – the opportunity to enhance their brand and loyalty through highlighting their involvement with the community.
How does your business interact with the community? Utilizing a .org is the best way to highlight the community-minded aspect of your business!
August 13th, 2008
Conversation with Edmon Chung of DotAsia
by Chuck Kisselburg
ICANNWiki.org
The month of May proved to be a disastrous month for many living along Myanmar’s coast and in China’s Sichuan province. It was during this time we saw Relief.Asia, through the DotAsia Organisation, mobilize to help provide relief efforts to those in the disaster areas.
Today the Sichuan province was struck by a 6.0 aftershock of May’s original quake.
Because of this I wanted to talk with Edmon Chung, DotAsia’s CEO, as such efforts not only shed light on what others within the ICANN Community can do, but what the ICANN “Community” can do in providing international relief efforts.
What is “Relief.Asia”?
Relief.Asia is a platform bringing together the Internet community around Asia for relief and rebuild efforts. While the portal itself is being built into a social network site, Relief.Asia is more than an online information or discussion forum. Relief.Asia is also a platform bringing together open source and open knowledge technologies to support relief and rebuild efforts. Today, a number of technologies such as SAHANA — a web-based disaster relief management system (with features such as missing people registry, victims registry, inventory system, aid request/pledge/procurement system, etc.), DUMBO — an emergency mobile network infrastructure, as well as GPS tracking and SOS devices, are being coordinated through Relief.Asia and deployed into Myanmar and Sichuan to help relief teams in the field.
Furthermore, Relief.Asia is a platform for driving online donations. As we progress, Relief.Asia intends not only to be facilitating the deployment of these technologies but also become a platform for open development, sharing and enhancement of software, technologies and experiences on relief and rebuild efforts.
The vision for Relief.Asia is that information technology saves lives. In the wake of natural or other disasters, information technology can deliver the efficiency and effectiveness at a time when it matters most, and at a time when it could mean life or death. The previous experiences of disaster recovery had often been local and seldom shared. Technologies were often built for specific tasks on ad hoc basis. Relief.Asia hopes to provide a platform for integrating and learning from these experiences. It is also meant to be a social network which could help in driving volunteers as well as ongoing support such as psychological support which is not always well planned at the initial often chaotic rescue phase.
Relief.Asia is an Internet platform that facilitates relief response, rebuild efforts and knowledge sharing for disaster recovery by leveraging the social and technological networks of the Internet community.
Who started Relief.Asia?
DotAsia could be said to be the host and coordinator for Relief.Asia. The DotAsia team grafted together the platform in the wake of Cyclone Nargis that hit Myanmar during May 2-3, 2008. Without the collaborative efforts from organisations and institutions from around Asia, or the open technologies already being developed since the 2004 Asia Tsunami, for which the origins of Relief.Asia owes its conception, it could not have happened nevertheless. Most notably the participation and help from Charles Mok of ISOC HK, the Asia Institute of Technology (AIT), APNG (Asia Pacific Networking Group), APNIC and the Museum of World Religion (MWR) has been instrumental to the early developments of Relief.Asia.
While running a relief effort can take a major effort, why start Relief.Asia?
Relief.Asia exemplifies DotAsia’s commitment to the Asia community. It is a major and ongoing effort. As mentioned, the vision of Relief.Asia is to build a platform that can deliver open technologies and expertise when it matters most in relief and rebuild efforts. We feel that Relief.Asia is a meaningful project and the whole team at DotAsia was working overtime from our already packed launch schedule for the ongoing auctions and our commitments such as at www.think.asia, yet we all felt it was well worth our time as we were truly able to provide help, leveraging our expertise and network, to the relief efforts in Myanmar and Sichuan. Through the partnership with the Museum of World Religion (MWR), who was a .Asia Pioneer, we have been able to secure cargo space and channels into the hardest hit areas in Myanmar and were one of the very few international efforts being able to deliver relief materials in. The project while demanding was refreshing for our morale. This would be one of the first times DotAsia really made some difference for the Asia community.
I see there are several partnerships in place for Relief.Asia. Were the partnerships in place prior to the Myanmar and China natural disasters or were they established during the creation of Relief.Asia?
The origins of Relief.Asia can be traced back to the 2004 Asia Tsunami.
DotAsia at that time was still organized around volunteer efforts and toiling through the ICANN TLD process. The team at that time nevertheless still tried to facilitate and drive donations where possible. Some of the core technologies being coordinated through DotAsia to Myanmar and Sichuan also had its roots from the aftermath of the 2004 Asia Tsunami. For donation drives, we work specifically with partners when disasters hit.
While Relief.Asia quickly integrated in the wake of the Myanmar Cyclone, plans have been in place throughout the preparatory phases at DotAsia even as we were launching the .Asia registry, as can be evidenced by our own pioneer domain application for the domain “relief.asia”.
The DotAsia footprint is quite large. Given the natural disasters that occurred in both Myanmar and China, would Relief.Asia be able to handle other disasters in Bangladesh, Iran and New Zealand? If so have the relationships been developed with the various organizations in countries throughout the whole DotAsia footprint?
We certainly hope that disasters would not hit so often and so closely with each other. The Myanmar Cyclone and then the Sichuan Earthquake did present great challenge for us. Just as we had put together the platform for Myanmar, the Sichuan Earthquake hit. It was not an easy decision, but one which I believe is correct, when we made commitments to exert as much efforts to both disaster areas. Besides working with local and international charities and NGO, DotAsia will continue to utilize its relationship with its member ccTLDs and other ccTLDs in the region. For our efforts in Myanmar, we had, with the help of the .MM registry been able to better deliver materials into the affected areas. As for Sichuan, we worked with CNNIC (.CN) and the Internet Society of China. In the future, we will continue to use this model to reach out to the local communities when and if disasters hit. On top of which, we intend to strengthen our relationships with international organisations such as World Vision, Oxfam and Red Cross to leverage their footprint around the world as well. But as the case in Myanmar shows, being able to leverage local presence through our online platform can be extremely critical for relief and rebuild efforts.
Have other regionally-based TLDs created a formalized relief effort before?
I am not sure. For DotAsia, this is consistent with our mandate and vision.
For others who wish to do the same, what were the major barriers you encountered that made establishing Relief.Asia difficult? In other words, if you had to do it all over again, what would you do differently?
A major barrier is driving online donations. Both setting it up as well as driving actual donations. In setting up the system, the payment gateway and processing was troublesome and expensive. This cascades to the issue of driving donations as well because of the high overhead. As a new online platform, there will of course be an issue of trust, which we understand. Nevertheless, we are glad that there are people who believe in our cause and also we were able to drive donations through our partners as well.
For regionally-based TLDs, existing and new, do you foresee the need for such organizations to budget for, if not have a person covering a “Relief Coordinator” role?
I think it really depends on the mission and vision of a TLD.
While there are many aspects to a complete relief effort, what can Relief.Asia do well and what should one NOT expect Relief.Asia to handle?
The vision of Relief.Asia is that information technology can save lives.
Relief.Asia leverages the technology and social network over the Internet community to bring together people and open technology to contribute to relief and rebuild efforts. Also, Relief.Asia is a platform that facilitates collaboration and sharing, and is focused on supporting relief and rebuild teams with technology. We will continue to work with other organisations such as World Vision, Oxfam and Red Cross to drive donations and support their operations for more general relief work.
I have heard of many organizations that organize relief efforts around natural disasters. This is the first time I have personally heard of any organization within the general ICANN community organizing a relief effort. What might organizations within the general ICANN community bring to disaster relief that traditional organizations struggle with?
Many organisations in the ICANN community has extensive networks within their locality and industry. Often, great work can be built from these social and technological networks. I think those are the types of thing the ICANN community can really make a difference. I believe there has been different initiatives in the past as well. As I recall, Afilias and PIR also contributed efforts in the wake of the 2004 Asia Tsunami.
Anything else I may not have covered that you wish to be told?
If you feel that Relief.Asia is a meaningful project, please support us by adding a button or ribbon to your website! See http://support.relief.asia.
The children of the disaster ridden areas need your help! Relief.Asia will focus not only on relief efforts but also rebuild and through your help, we can bring better technology to these deprived children, and give them a better hope for a better future!
August 5th, 2008