Internationalized Resource Identifier

On the Internet, the Internationalized Resource Identifier is a generalization of the Uniform Resource Identifier, which is in turn a generalization of the Uniform Resource Locator. While URIs are limited to a subset of the ASCII character set, IRIs may contain characters from the Universal Character Set, including Chinese or Japanese kanji, Korean, Cyrillic characters, and so forth.

Other News:

  • apps-discuss - Peter's Apps Report #3

    IRI (Internationalized Resource Identifiers) Chairs: Marc Blanchet & Addison Philipps Website: http://tools.ietf.org/wg/iri/ Abstract: The IRI WG is revising the definition of Internationalized Resource Identifiers from ...
    www.listware.net
  • Tailoring the Unicode Bidi Algorithm

    Internationalized Resource Identifiers (IRIs) are a generalization of Universal Resource Identifiers (URIs) that can contain many nonASCII characters, such as most alphabetic characters and Chinese characters. ...
    blogs.msdn.com
  • WG Action: Internationalized Resource Identifiers (iri)

    WG Action: Internationalized Resource Identifiers (iri)
    www.spinics.net
  • Tailoring the Unicode Bidi Algorithm - Murray Sargent: Math in ...

    This post considers three such situations: math zones, International Resource Identifiers (IRIs), and HTML spans with a directionality attribute. In each of these cases, tailoring the Unicode Bidi Algorithm improves the result. ...
    blogs.msdn.com

Videos »

  • Google I/O 2008 - Painless Python Part 1 of 2

    Google I/O 2008 - Painless Python Part 1 of 2

    Painless Python for Proficient Programmers Alex Martelli (Google) Python is a popular very-high-level programming language, with a clean and spare syntax, simple and regular semantics, a large standard library and a wealth of third-party extensions, libraries and tools. With several production-quality open-source implementations available, many excellent books, and growing acceptance in both industry and academia, Python can play some useful role within a huge variety of software development projects. Moreover, Python is really easy to learn, particularly (though not exclusively) for programmers who are skilled at such languages as Java, C++ and C. This talk addresses software developers who are experienced in other languages but have had limited or no exposure to Python yet, and offers a rapid overview of the main characteristics of the language, plus a brief synopsis of its main implementations, its standard library, and Python's use with Google App Engine.
  • Google I/O 2010 - Fireside chat with the GWT team

    Google I/O 2010 - Fireside chat with the GWT team

    Google I/O 2010 - Fireside chat with the GWT team Fireside Chats, GWT Bruce Johnson, Joel Webber, Ray Ryan, Amit Manjhi, Jaime Yap, Kathrin Probst, Eric Ayers, lan Stewart, Christian Dupuis, Chris Ramsdale (moderator) If you're interested in what the GWT team has been up to since 2.0, here's your chance. We'll have several of the core engineers available to discuss the new features and frameworks in GWT, as well as to answer any questions that you might have. For all I/O 2010 sessions, please go to code.google.com
  • Greyglers@Google: Vint Cerf

    Greyglers@Google: Vint Cerf

    Googlers are lucky to have among them some great luminaries of computer science, including VP and Chief Internet Evangelist Vint Cerf. If you dont know Vint, you can start by checking out his nearly 380000 mentions on Google, the pivotal roles hes played in developing the web, the significant honors he's received all over the world, and his nickname, father of the Internet. You can learn more by attending a rare tech talk by Vint, presented by the Greyglers*: Reimagining the Internet: If wed known then what we know now, what would we have done differently? Back in the Internet's design phase, Bob Kahn and I spent six months developing concepts and architecture and a year creating the TCP specification, but we didn't know that the idea would work. We concentrated on solving the problems we envisioned, such as networks that couldn't handle each other's packet lengths. Security against direct attacks and authentication of sources weren't high on the agenda. Now that we have spam, DDOS, viruses, and worms, we look back and think about what we might have done differently had we realized that we were creating a global infrastructure for the 21st century!
  • Real Time Search Event

    Real Time Search Event

    Check out Google's latest announcements for desktop and mobile search.
  • Google I/O 2008 - Painless Python Part 1 of 2

  • Google I/O 2010 - Fireside chat with the GWT team

  • Greyglers@Google: Vint Cerf

  • Real Time Search Event

©2010 Copyright Resource-genie - Privacy Policy