Software Development

intraVnews tip: Changing presentation of RSS feed

<intraVnews installation directory>/itemstyles.css을 원하는대로 수정해두면,
다음 피드부터 해당 스타일이 적용된다.
 
outlook쪽에 저장되는 형태는 html이고 RSS를 피딩하면서 itemstyles.css를 병합하는 것 같다. 따라서, 이미 피드된 article들은 적용안되는 듯 하다. 필요하다면 다 지우고 다시 피딩받기.

 

intraVnews tip: Changing presentation of RSS feed 더 읽기"

Services and Semantics: Web Architecture

http://www.w3.org/2001/04/30-tbl
 
웹 기술의 두가지 orthogonal한 방향인 semantic web과 web service에 대해 기술하고 있다.
2001년 4월에 HTML을 발명한 Tim Berners-Lee에 의해 쓰여졌다.
오래된 글이지만, Semantic Web과 Web Service가 대략 무엇인지 감을 잡기에는 부족하지 않은 article인 듯 하다. 더불어 각 기술들의 현재의 activity에 알고 싶다면 아래 페이지를 방문하면 될 것이다.
 
Semantic Web: http://www.w3.org/2001/sw/
Web Service: http://www.w3.org/2002/ws/
 
Semantic Web이란 현재 인간이 ‘읽기’ 위한 용도의 웹 문서들을 기계적으로 처리할 수 있는 표현력을 가진 정보의 형태로 변경하는 노력을 말한다. 객체 자체와 객체들간의 관계를 표현할 수 있는 XML application인 RDF와, abstract class를 정의하기 위한 RDF Schema (XML-XML Schema의 관계로 생각하면 될 듯), Ontology layer concept (DAML+OIL,OWL) 에 의해 구현되고 있다. rule language, query language, logic language에 대한 논의도 있다.
 
Web Service란 웹 문서가 제공하는 서비스를 표현하고 기계적으로 처리할 수 있는 의사소통 수단 (프로토콜)을 제공하는 것에 가깝다. Web Service에서 중요한 기능들은 다음과 같다.
 
– Remote Operations (SOAP, XML Protocol)
– Ontology of services (WSDL – providing a mapping to RDF in an XML schema)
– Context (RDF-based CC/PP, P3P): 메시지를 보내고 받는 agent에 관한 context
– Flow: 메시지를 처리하는 process flow
– Directories of services
 
대체로 위의 웹기술들이 extensiblility를 중요한 requirement로 내세우고 있으며 XML 기술 (esp. RDF)을 중요한 구현 방법으로 내세우고 있는 것도 중요한 측면이라고 보인다.
 
 

Services and Semantics: Web Architecture 더 읽기"

Slashdot Today

Ridgelift writes “CRN is reporting the release of Linux 2.6.0 in mid-December. ‘Torvalds, Linux’s lead developer and now an OSDL Fellow, and Linux kernel …
 
An anonymous reader writes “Linus Torvalds has released his final 2.6.0-test kernel, calling it the ‘Beaver In Detox’. Following this release, Linus says that …
 
이제 얼마 안남았군, second PC setup해서 설치해보아야 할 듯.
 
An anonymous reader writes “Swedish media report that 22-year-old Elin Oxenhielm, a student at Stockholm University, has solved a chunk of one of the major …
 
  • More on Hilbert’s 23 problems: hilbert/problems.html
  • More on David Hilbert: Mathematicians/Hilbert.html
  • More on Elin Oxenhielm: www.math.su.se/~elin/
  •  
    Kulic writes “Wired is running a story about using subdermal RFID microchips to pay for goods. Applied Digital Solutions are marketing the VeriChip as the …
     
    electronic device의 Implants가 이제 대중들에게 보급될 것인가.
    아니면 바코드가 될 것인가. =_=
     
    Martin Berger writes “Turing Award (1991) winner Robin Milner is one of the most influential computer scientists. He may not be as well-known as he deserves to …
     
     
    CowboyRobot writes “ACM Queue has an interview with Peter Ford, chief architect for MSN Messenger, by Eric Allman, CTO of Sendmail. They discuss the present …
     
    A Conversation with Peter Ford
     
    XMPP in IETF
     

    Slashdot Today 더 읽기"

    Slashdot Today

    rduke15 writes “You think you know how to parse a domain name for validity? Well, in case you haven’t noticed, things are getting tougher as registrars keep …
     
    IDN에서 사용하려고 하는 Punycode를 언급하고 있는 RFC 3492 [RFC3492]는
    특정 encoding의 requirement에 대해 다음과 같은 이유를 들고 있다.
     
       *  Efficient encoding:  The ratio of basic string length to extended
          string length is small.  This is important in the context of
          domain names because RFC 1034 [RFC1034] restricts the length of a
          domain label to 63 characters.
     
    기사에서 ‘weird’하다고 표현하고 있는 인코딩의 예는 다음과 같다.
     
       (H) Korean (Hangul syllables):
           u+C138 u+ACC4 u+C758 u+BAA8 u+B4E0 u+C0AC u+B78C u+B4E4 u+C774
           u+D55C u+AD6D u+C5B4 u+B97C u+C774 u+D574 u+D55C u+B2E4 u+BA74
           u+C5BC u+B9C8 u+B098 u+C88B u+C744 u+AE4C
           Punycode: 989aomsvi5e83db1d2a355cv1e0vak1dwrv93d5xbh15a0dt30a5j
                     psd879ccm6fea98c
     
    Simon P. Chappell writes “Life is busy enough without writing your own infrastructure code. With all of the high-quality frameworks available today, it’s no …
     
    Life is busy enough without writing your own infrastructure code. With all of the high-quality frameworks available today, it’s no longer necessary to even think about writing low-level code (except as a technical exercise, or to express your inner geek :-) Our problem today, is to review and select the best available framework for our needs.
     
    몇년 전만 해도 ‘자신의 라이브러리를 구축하라’는 조언이 절대적인 진리였지만,
    현재는 그렇지않다. 인터넷 환경에 힘입어 product-quality를 가진 framework와 component들이
    무료로 배포되고 있다. reusability와 팀 환경을 감안했을 때,
    ‘자신만의 라이브러리’는 무용지물이 될 수도 있다.
     
    따라서, 현재까지 개발해오던 습성을 어느 정도는 버리기 시작해야할 것이다.
    이러한 습성의 변화는 직관적으로 두가지 국면에서 발생할 것이다.
     
    – 자신만의 라이브러리를 구축하기 보다는 좋은 품질의 라이브러리를 찾을 것.
    (우리는 이미 많은 시간을 좋은 툴과 라이브러리를 ‘찾는’ 데에 시간을 들이고 있다.)
    – 라이브러리를 구축할 때, 자신만의 용도로 만들기 보다는 개발/사용의 공유를 통해 발전시킬 것.
    (물론 ‘자신만의 라이브러리’의 필요가 완전히 사라지지는 않는다.)
     
    raptor21 writes “Ace’s hardware has an article with feature list of technologies in Solaris 10 or whatever it is called today. Interesting stuff like DTrace, …
     
    눈에 띄는 feature들..
     
    “Fire Engine” TCP/IP stack

    A complete re-write of Sun’s TCP/IP stack, with more features from IPv6 and more performance and scalability. Fire Engine will also support TCP/IP Offload Engines (TOEs) – it is expected that Sun’s 8-core Niagara processor will feature this. Without hardware optimisation, the processor demands are quite painful for multiple 1Gbit channels or single 10Gbit Ethernet channels, so expect TOEs to become a common feature of future servers. This article from The Register has good information on Fire Engine.

     
    Gigabit 환경을 위한 중요한 도약인 듯.
     

    Solaris Zones (“Project Kevlar”)
    A next generation of the software based partitions in Solaris, which aim for high isolation – they can be individually re-booted, dynamically created and faults outside the kernel won’t affect other zones. Future UltraSPARC processors are expected to have (unspecified) hardware features to improve upon this.

     
    소프트웨어의 안정성을 격리하기 위해서 machine을 분리할 필요가 없어지는 것인가?

     
    ZFS (Zettabyte File System)

    ZFS is a completely new POSIX-compliant Unix file-system that aims to push not only performance, scalability and reliability into the next generation, but also manageability – Sun presented two papers at the Self Manage ’03 conference. The first is about ZFS’s self-tuning abilities and some features that make it simpler to administer in the first place – storage can be very complex to setup and administer, and improving on this is a major goal of ZFS. The second paper is about ZFS’s Existential QoS for Storage, a simpler way of specifying QoS (Quality of Service) requirements for storage. Note: a Zettabyte is 270 bytes, or 1,180,591,620,717,411,303,424 bytes.

     
    paper를 봐야할 겠지만, self-tuning에 QoS라니. 2^70 = (2^10)^7 = (10^3)^7 bytes = (10^3) ^ 4) GB인가…

    Slashdot Today 더 읽기"

    Slashdot Today

    Slashdot Today 더 읽기"

    Slashdot Today

    Google Rebuffs Microsoft Takeover Bid
     
    http://www.smh.com.au/articles/2003/11/02/1067708070338.html
    http://slashdot.org/articles/03/11/02/2218220.shtml?tid=95
     
    Google rebuffs Microsoft
     
    Internet search leader Google has rejected a takeover bid from Microsoft in favour of selling its shares directly to the public, The New York Times has reported.
    Microsoft’s bid for the privately held company was termed a merger and underscored the huge value attached to Google, which was founded just five years ago by two Stanford University graduates, Sergey Brin and Larry Page.
    They and other senior executives have in recent weeks been interviewing investment banks with a view to taking the company public at a valuation of $US15 billion to $US25 billion ($21 billion to $36 billion).
    According to The New York Times, Google wishes to sell only about $US2 billion worth of shares to the public.
    The company wants to fund expansion and reward company workers and early investors.
    DPA

    Slashdot Today 더 읽기"

    Slashdot Today

    Slashdot Today 더 읽기"

    Slashdot Today

    Slashdot Today 더 읽기"

    Why Functional Programming Language Matters

  • Modulartity is the key to sucessful programming.
  • Our ability to decompose a problem into parts depends directly on our ability to glue solutions together. To assist modular programming, a language must provide good glue.
  • Functional programming languages provide two new kinds of glue – higher-order functions and lazy evaluation.
     
    http://cestlavie.neowiz.com/tWiki/pub/Main/HaskellProgrammingLanguage/whyfp.pdf
  • Why Functional Programming Language Matters 더 읽기"