kim sanghoon
건축
문화
Historical TLDs
A .nato was added in the late 1980s by the NIC for the use of NATO, who felt that none of the then existing TLDs adequately reflected their status as an international organization. Soon after this addition, however, the NIC created the .int TLD for the use of international organizations, and persuaded NATO to use nato.int instead. However, the nato TLD, although no longer used, was not deleted until July 1996.
Other historical TLDs are
.cs for Czechoslovakia (now .cz for Czech Republic and .sk for Slovak Republic),
.zr for Zaire (now .cd for Democratic Republic of the Congo),
.oz for Australia (now .au) and
.dd for the German Democratic Republic (now .de for Germany).
In contrast to these, the TLD .su has remained in active use despite the demise of the Soviet Union that it represents, though .ru is most commonly used for Russian domains.
Commercial use of country code TLDs
A number of the world's smallest countries have licensed their TLDs for world-wide commercial use.
For example, Niue, a tiny island in the South Pacific Ocean, has licensed the .nu TLD and it is used various places around the world, for example in Denmark, the Netherlands and Sweden, where the word "nu" means "now".
Similarly, Tuvalu and the Federated States of Micronesia, other small islands in the South Pacific, have partnered with VeriSign and FSM Telecommunications respectively, to sell domain names using the .tv and .fm TLDs to television and radio stations. Cocos (Keeling) Islands of Australia promoted the use of their .cc as "the next .com", which garnered popularity due to its relative cheapness compared to .com registration at the time.
Pseudo-domains
In the past the Internet was just one of many wide-area computer networks.
Computers not connected to the Internet, but connected to another network such as BITNET, CSNET or UUCP, could generally exchange e-mail with the Internet via e-mail gateways. When used on the Internet, addresses on these networks were often placed under pseudo-domains such as .bitnet, .csnet, and .uucp; however these pseudo-domains implemented in mail server configurations such as sendmail.cf and were not real top-level domains and did not exist in DNS.
Most of these networks have long since ceased to exist, and although UUCP still gets significant use in parts of the world where Internet infrastructure has not yet become well-established, it subsequently transitioned to using Internet domain names, so pseudo-domains now largely survive as historical relics. One notable exception is the 2007 emergence of SWIFTNet Mail, which uses the .swift pseudo-domain.[1]
The anonymity network Tor has a pseudo-domain onion, which can only be reached with a Tor client because it uses the Tor-protocol (onion routing) to reach the hidden service in order to protect the anonymity of the domain.
.local deserves special mention as it is required by the Zeroconf protocol. It is also used by many organizations internally, which will become a problem for those users as Zeroconf becomes more popular. Both .site and .internal have been suggested for private usage, but no consensus has yet emerged.
Reserved TLDs
RFC 2606 reserves the following four top-level domain names for various purposes, with the intention that these should never become actual TLDs in the global DNS:
.example — reserved for use in examples
.invalid — reserved for use in obviously invalid domain names
.localhost — reserved to avoid conflict with the traditional use of localhost
.test — reserved for use in tests
Debated TLDs
About the time that ICANN proposed (and finally introduced in 2000[1]) .aero, .biz, .coop, .info, .museum, .name, and .pro TLDs, many sites and USENET users argued that a similar TLD should be made available for adult and pornographic websites to settle the dispute of obscene content on the internet and the responsibility of service providers under the questionable Communications Decency Act of 1996.
Several options were proposed including .xxx, .sex and .adult, but ICANN chose not to create them.
ICANN's unwillingness to create commonly requested TLDs, and the relatively high registration costs associated with several TLDs, has led to the creation of alternate root servers
TLDs in alternative roots
Alternative DNS roots have their own sets of TLDs. See that article for details.
At times, browser plugins have been developed to allow access to some set of "alternative" domain names even when the normal DNS roots are otherwise used.
References
^ SWIFT - About SWIFT - Press room - SWIFTNet Mail now available
Addressing the World: National Identity and Internet Country Code Domains, edited by Erica Schlesinger Wass (Rowman & Littlefield, 2003, ISBN 0-7425-2810-3) [3], examines connections between cultures and their ccTLDs.
Ruling the Root by Milton Mueller (MIT Press, 2001, ISBN 0-262-13412-8) [4], discusses TLDs and domain name policy more generally.
세계고층건물디자인 사진
개인이야기
건축법
2008년 5월 3일 토요일
일반 최상위 도메인 (gTLD)
kim sanghoon
건축
문화
"TLD" redirects here. For other uses, see TLD (disambiguation).
A top-level domain (TLD), sometimes referred to as a top-level domain name (TLDN), is the last part of an Internet domain name; that is, the letters which follow the final dot of any domain name.
For example, in the domain name www.example.com, the top-level domain is com (or COM, as domain names are not case-sensitive).
The Internet Assigned Numbers Authority (IANA) currently classifies top-level domains into three types:
country code top-level domains
(ccTLD): Used by a country or a dependent territory. It is two letters long, for example .us for the United States. With some historical exceptions, the code for any territory is the same as its two-letter ISO 3166 code.
generic top-level domains
(gTLD): Used (at least in theory) by a particular class of organizations (for example, .com for commercial organizations). It is three or more letters long. Most gTLDs are available for use worldwide, but for historical reasons .mil (military) and .gov (governmental) are restricted to use by the respective U.S. authorities. gTLDs are subclassified into sponsored top-level domains
(sTLD), e.g. .aero, .coop and .museum, and unsponsored top-level domains (uTLD), e.g. .biz, .info, and .name.
infrastructure top-level domains (iTLD): The top-level domain .arpa is the only confirmed one. .root has been known to exist without reason.
A full list of currently existing TLDs can be found at the list of Internet top-level domains.
일반 최상위 도메인 (gTLD)는 특정한 조직 계열에 따라 사용되는 최상위 도메인이다. 도메인의 길이는 3 글자 이상이며 조직의 종류에 따라 사용하는 이름이 다르다.
.aero - 항공 회사
.asia - 아시아 지역을 대표
.biz - 사업
.cat - 카탈로니아 언어/문화
.com - 영리 목적의 기업이나 단체
.coop - 조합
.edu - 미국의 4년제 이상 교육기관. 최근에 다른 나라에도 .edu 도메인이 개방되었다.
.eu - 유럽 연합의 회사
.gov - 미국의 연방 정부 조직
.info - 정보 관련 (무제한)
.int - 국제 조약 등으로 만들어진 국제 기관
.jobs - 취업 관련 사이트
.mil - 미국의 군사 조직
.mobi - 휴대 장치를 위한 사이트
.museum - 미술관과 박물관
.name - 개인 사용자
.net - 네트워크를 관리하는 기관
.org - 비영리 기관, 혹은 다른 gTLD에 해당하지 않는 단체.
.pro - 회계사, 의사, 변호사 등의 전문가
.tel - 전화 네트워크와 인터넷 사이의 연결을 관장하는 서비스
.travel - 여행사, 항공사, 호텔 등
다음의 일반 최상위 도메인은 승인이 처리되는 중이며, 앞으로 추가될 가능성이 있다:
.post - 우체국 서비스
.geo - 지질학 관련 사이트
.cym - 웨일스어, 웨일스 문화
세계고층건물디자인 사진
개인이야기
건축법
건축
문화
"TLD" redirects here. For other uses, see TLD (disambiguation).
A top-level domain (TLD), sometimes referred to as a top-level domain name (TLDN), is the last part of an Internet domain name; that is, the letters which follow the final dot of any domain name.
For example, in the domain name www.example.com, the top-level domain is com (or COM, as domain names are not case-sensitive).
The Internet Assigned Numbers Authority (IANA) currently classifies top-level domains into three types:
country code top-level domains
(ccTLD): Used by a country or a dependent territory. It is two letters long, for example .us for the United States. With some historical exceptions, the code for any territory is the same as its two-letter ISO 3166 code.
generic top-level domains
(gTLD): Used (at least in theory) by a particular class of organizations (for example, .com for commercial organizations). It is three or more letters long. Most gTLDs are available for use worldwide, but for historical reasons .mil (military) and .gov (governmental) are restricted to use by the respective U.S. authorities. gTLDs are subclassified into sponsored top-level domains
(sTLD), e.g. .aero, .coop and .museum, and unsponsored top-level domains (uTLD), e.g. .biz, .info, and .name.
infrastructure top-level domains (iTLD): The top-level domain .arpa is the only confirmed one. .root has been known to exist without reason.
A full list of currently existing TLDs can be found at the list of Internet top-level domains.
일반 최상위 도메인 (gTLD)는 특정한 조직 계열에 따라 사용되는 최상위 도메인이다. 도메인의 길이는 3 글자 이상이며 조직의 종류에 따라 사용하는 이름이 다르다.
.aero - 항공 회사
.asia - 아시아 지역을 대표
.biz - 사업
.cat - 카탈로니아 언어/문화
.com - 영리 목적의 기업이나 단체
.coop - 조합
.edu - 미국의 4년제 이상 교육기관. 최근에 다른 나라에도 .edu 도메인이 개방되었다.
.eu - 유럽 연합의 회사
.gov - 미국의 연방 정부 조직
.info - 정보 관련 (무제한)
.int - 국제 조약 등으로 만들어진 국제 기관
.jobs - 취업 관련 사이트
.mil - 미국의 군사 조직
.mobi - 휴대 장치를 위한 사이트
.museum - 미술관과 박물관
.name - 개인 사용자
.net - 네트워크를 관리하는 기관
.org - 비영리 기관, 혹은 다른 gTLD에 해당하지 않는 단체.
.pro - 회계사, 의사, 변호사 등의 전문가
.tel - 전화 네트워크와 인터넷 사이의 연결을 관장하는 서비스
.travel - 여행사, 항공사, 호텔 등
다음의 일반 최상위 도메인은 승인이 처리되는 중이며, 앞으로 추가될 가능성이 있다:
.post - 우체국 서비스
.geo - 지질학 관련 사이트
.cym - 웨일스어, 웨일스 문화
세계고층건물디자인 사진
개인이야기
건축법
www.example.net.net/
kim sanghoon
건축
문화
세계고층건물디자인 사진
개인이야기
www.example.net.net/
Example
The following example is assumed to have been found at http://alice.example.net. For simplicity's sake, we assume the low-bandwidth situation.
Alice Jones
Page maintained by >Eve Ville. Contact >eve@example.net for corrections. (I know I'm not the most trustworthy
of sources.)
The subject of all the XFN links on the page is the hCard for Alice Jones at the top of the page. This is determined in step two of the representative hCard parsing procedure because it contains rel="me".
The next XFN link is the one labelled "Bob Smith". Because the link is part of an hCard, the person described by the hCard is the object of the link.
For the next two XFN links, there exist no hCards that represent the objects. We can gather some information about them from the link element itself: their foaf:name and foaf:page. (Note that FOAF defines foaf:name very loosely, so it's OK if the link text is a nickname.)
Although at first glance the XFN link for Eve Ville looks similar, there is in fact an hCard later on in the page with a UID matching the XFN link target, so using rule #2 for determining the object, we use this hCard as the object of the XFN relationship. Note that "adversary" is not an XFN rel value, so is beyond the scope of this document.
The subject of all the XFN links on the page is the hCard for Alice Jones at the top of the page. This is determined in step two of the representative hCard parsing procedure because it contains rel="me".
The next XFN link is the one labelled "Bob Smith". Because the link is part of an hCard, the person described by the hCard is the object of the link.
For the next two XFN links, there exist no hCards that represent the objects. We can gather some information about them from the link element itself: their foaf:name and foaf:page. (Note that FOAF defines foaf:name very loosely, so it's OK if the link text is a nickname.)
Although at first glance the XFN link for Eve Ville looks similar, there is in fact an hCard later on in the page with a UID matching the XFN link target, so using rule #2 for determining the object, we use this hCard as the object of the XFN relationship. Note that "adversary" is not an XFN rel value, so is beyond the scope of this document.
Note that some personal data for contacts is expressed in the FOAF vocabulary, and some information is expressed in vCard/hCard vocabulary. User agents may use OWL or another technique to draw equivalencies between vocabularies, such as taking hcard:fn to be equivalent to foaf:name.
Organisation hCards and XFN
If either the subject or object hCard represents an organisation (rather than a person), the following relationships are meaningless:
acquaintance
friend
child
parent
sibling
spouse
kin
crush
date
sweetheart
Reverse Relationships
Explicit reverse relationships may be provided by authors using the rev attribute. These should be interpreted by parsers in exactly the same manner as described above, however subject and object must be swapped.
The XFN 1.1 profile (http://gmpg.org/xfn/11) explicitly mentions inverses for some XFN relationships, and lists which relationships are symmetric (i.e. their own inverse). For example, as Alice met Bob, it is implied that Bob met Alice. Parsers may use the information in the profile to make explicit the implicit reverse relationships.
XFN
XFN+hCard supporting friends lists - examples in the wild of XFN usage.
xfn-implementations
xfn-cheatsheet - see http://gmpg.org/xfn/join and existing-rel-values
xfn-faq
xfn-clarifications - should eventually be rolled into XFN info on GMPG.org.
xfn-issues
xfn-brainstorming
xfn-to-foaf - extracting Upper-Case Semantic Web data from XFN and hCard
[edit]Microformats to RDF
XFN → FOAF
xFolk → RDF
See also:
FAQs for RDF
건축법
건축
문화
세계고층건물디자인 사진
개인이야기
www.example.net.net/
Example
The following example is assumed to have been found at http://alice.example.net. For simplicity's sake, we assume the low-bandwidth situation.
Friends & Contacts
Page maintained by >Eve Ville. Contact >eve@example.net for corrections. (I know I'm not the most trustworthy
of sources.)
The subject of all the XFN links on the page is the hCard for Alice Jones at the top of the page. This is determined in step two of the representative hCard parsing procedure because it contains rel="me".
The next XFN link is the one labelled "Bob Smith". Because the link is part of an hCard, the person described by the hCard is the object of the link.
For the next two XFN links, there exist no hCards that represent the objects. We can gather some information about them from the link element itself: their foaf:name and foaf:page. (Note that FOAF defines foaf:name very loosely, so it's OK if the link text is a nickname.)
Although at first glance the XFN link for Eve Ville looks similar, there is in fact an hCard later on in the page with a UID matching the XFN link target, so using rule #2 for determining the object, we use this hCard as the object of the XFN relationship. Note that "adversary" is not an XFN rel value, so is beyond the scope of this document.
The subject of all the XFN links on the page is the hCard for Alice Jones at the top of the page. This is determined in step two of the representative hCard parsing procedure because it contains rel="me".
The next XFN link is the one labelled "Bob Smith". Because the link is part of an hCard, the person described by the hCard is the object of the link.
For the next two XFN links, there exist no hCards that represent the objects. We can gather some information about them from the link element itself: their foaf:name and foaf:page. (Note that FOAF defines foaf:name very loosely, so it's OK if the link text is a nickname.)
Although at first glance the XFN link for Eve Ville looks similar, there is in fact an hCard later on in the page with a UID matching the XFN link target, so using rule #2 for determining the object, we use this hCard as the object of the XFN relationship. Note that "adversary" is not an XFN rel value, so is beyond the scope of this document.
Note that some personal data for contacts is expressed in the FOAF vocabulary, and some information is expressed in vCard/hCard vocabulary. User agents may use OWL or another technique to draw equivalencies between vocabularies, such as taking hcard:fn to be equivalent to foaf:name.
Organisation hCards and XFN
If either the subject or object hCard represents an organisation (rather than a person), the following relationships are meaningless:
acquaintance
friend
child
parent
sibling
spouse
kin
crush
date
sweetheart
Reverse Relationships
Explicit reverse relationships may be provided by authors using the rev attribute. These should be interpreted by parsers in exactly the same manner as described above, however subject and object must be swapped.
The XFN 1.1 profile (http://gmpg.org/xfn/11) explicitly mentions inverses for some XFN relationships, and lists which relationships are symmetric (i.e. their own inverse). For example, as Alice met Bob, it is implied that Bob met Alice. Parsers may use the information in the profile to make explicit the implicit reverse relationships.
XFN
XFN+hCard supporting friends lists - examples in the wild of XFN usage.
xfn-implementations
xfn-cheatsheet - see http://gmpg.org/xfn/join and existing-rel-values
xfn-faq
xfn-clarifications - should eventually be rolled into XFN info on GMPG.org.
xfn-issues
xfn-brainstorming
xfn-to-foaf - extracting Upper-Case Semantic Web data from XFN and hCard
[edit]Microformats to RDF
XFN → FOAF
xFolk → RDF
See also:
FAQs for RDF
건축법
피드 구독하기:
글 (Atom)