ITU-T H 351-2008 Semantic web interface for multimedia terminal and system directories (SWIM-D) (Study Group 16)《多媒体终端和系统目录用语义网接口(SWIM-D)》.pdf

《ITU-T H 351-2008 Semantic web interface for multimedia terminal and system directories (SWIM-D) (Study Group 16)《多媒体终端和系统目录用语义网接口(SWIM-D)》.pdf》由会员分享，可在线阅读，更多相关《ITU-T H 351-2008 Semantic web interface for multimedia terminal and system directories (SWIM-D) (Study Group 16)《多媒体终端和系统目录用语义网接口(SWIM-D)》.pdf（24页珍藏版）》请在麦多课文档分享上搜索。

1、 International Telecommunication Union ITU-T H.351TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (06/2008) SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMSInfrastructure of audiovisual services Directory services architecture for audiovisual and multimedia services Semantic web interface for multimedia

2、 terminal and system directories (SWIM-D) Recommendation ITU-T H.351 ITU-T H-SERIES RECOMMENDATIONS AUDIOVISUAL AND MULTIMEDIA SYSTEMS CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS H.100H.199 INFRASTRUCTURE OF AUDIOVISUAL SERVICES General H.200H.219 Transmission multiplexing and synchronization H.220H

3、.229 Systems aspects H.230H.239 Communication procedures H.240H.259 Coding of moving video H.260H.279 Related systems aspects H.280H.299 Systems and terminal equipment for audiovisual services H.300H.349 Directory services architecture for audiovisual and multimedia services H.350H.359 Quality of se

4、rvice architecture for audiovisual and multimedia services H.360H.369 Supplementary services for multimedia H.450H.499 MOBILITY AND COLLABORATION PROCEDURES Overview of Mobility and Collaboration, definitions, protocols and procedures H.500H.509 Mobility for H-Series multimedia systems and services

5、H.510H.519 Mobile multimedia collaboration applications and services H.520H.529 Security for mobile multimedia systems and services H.530H.539 Security for mobile multimedia collaboration applications and services H.540H.549 Mobility interworking procedures H.550H.559Mobile multimedia collaboration

6、inter-working procedures H.560H.569 BROADBAND AND TRIPLE-PLAY MULTIMEDIA SERVICES Broadband multimedia services over VDSL H.610H.619 Advanced multimedia services and applications H.620H.629 IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV General aspects H.700H.719 IPTV terminal devices H.720H.729

7、 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T H.351 (06/2008) i Recommendation ITU-T H.351 Semantic web interface for multimedia terminal and system directories (SWIM-D) Summary Recommendation ITU-T H.351 describes a semantic web interface in XHTML that can be u

8、sed to provide directory lookup and menu capabilities for multimedia terminals and systems. Source Recommendation ITU-T H.351 was approved on 13 June 2008 by ITU-T Study Group 16 (2005-2008) under Recommendation ITU-T A.8 procedure. Keywords Address book, directory, multimedia, web interface, white

9、pages. ii Rec. ITU-T H.351 (06/2008) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ

10、of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the top

11、ics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are pre

12、pared on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. Compliance with this Recommendation is voluntary. However, the Recommendation m

13、ay contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words “shall“ or some other obligatory language such as “must“ and the negative equivalents are used to ex

14、press requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Pr

15、operty Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommendation, ITU had not received notice

16、of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2009

17、 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T H.351 (06/2008) iii CONTENTS Page 1 Scope 1 2 References. 1 3 Definitions 2 3.1 Terms defined elsewhere 2 3.2 Terms defined in this Recommendation. 2

18、4 Abbreviations and acronyms 3 5 Conventions 3 6 The problem of resource representations in directories 3 7 SWIM-D architecture . 4 8 SWIM-D directory pages 6 8.1 MENU directory pages. 7 8.2 RESULT directory pages . 9 8.3 DETAIL directory pages 11 9 SWIM-D URLs. 12 9.1 MENU directory page URLs 12 9.

19、2 SEARCH directory page URLs 12 9.3 DETAIL directory page URLs . 13 10 General considerations . 13 10.1 Usage of HTTP. 13 10.2 Authentication and authorization . 13 10.3 Directory browsing. 13 10.4 Directory searching 14 10.5 Extensibility 14 Bibliography. 15 iv Rec. ITU-T H.351 (06/2008) Introducti

20、on This Recommendation describes a method by which XHTML documents can be accessed by multimedia terminals, systems, web browsers and middleware systems to recognize, navigate, process and display white pages directory structures. It addresses three primary needs: Representing both people and resour

21、ces in the directory. While people are represented in directories in well known formats, there are not good standards for representing resources in the directory, even though those resources have important contact information. For example “help desk“ and “conference room 112“ are important entities

22、which may contain multimedia conferencing resources that need to be contacted. Diverse display characteristics of systems. Some multimedia terminals, such as IP telephones, have limited user interface and processing capabilities, necessitating a simplified markup scheme for displaying address books

23、and directory information. Advanced terminals, such as web browsers or video conferencing terminals, may have rich display capabilities yet need to formulate a directory display from the same data. Structured navigation. It may be that an organization wishes to control the way that white pages appli

24、cations are served out to terminals and systems. For example, an organization may wish to publish an address book that allows navigation by department, product line, or individual last name. Rec. ITU-T H.351 (06/2008) 1 Recommendation ITU-T H.351 Semantic web interface for multimedia terminal and sy

25、stem directories (SWIM-D) 1 Scope This Recommendation describes a markup vocabulary for XHTML documents representing white pages directory information for multimedia terminals and systems. It describes a uniform resource locator (URL) syntax that supports directory searching. It also enumerates clie

26、nt and server behaviours necessary to support SWIM-D interaction effectively. The purpose of this Recommendation is to provide a framework for structured directory browsing when the underlying data structures are not known, such as when publishing directories of people, places and virtual organizati

27、ons. This Recommendation does not describe directory structures or directory access protocols. This Recommendation is related to other ITU-T H.350-series Recommendations. While Recommendations ITU-T H.350.1 through H.350.7 describe directory schemas for various protocols that can drive call signalli

28、ng engines directly, this Recommendation is intended for higher level access to directory data for white pages browsing only. b-ITU-T E.115 describes a computerized directory assistance protocol for information exchange among service providers in support of assistance/inquiry services. White pages i

29、mplementers should review all of these related Recommendations for applicability. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions ind

30、icated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T

31、Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. IETF RFC 2616 IETF RFC 2616 (1999), Hypertext Transfer Protocol HTTP/1.1. IETF RFC 2617 IETF RFC 2617 (1999), HTTP Authenticatio

32、n: Basic and Digest Access Authentication. IETF RFC 2818 IETF RFC 2818 (2000), HTTP Over TLS. IETF RFC 3986 IETF RFC 3986 (2005), Uniform Resource Identifier (URI): Generic Syntax. W3C XHTML 1.1 W3C Recommendation (2001), XHTML 1.1 Module-based XHTML. 2 Rec. ITU-T H.351 (06/2008) 3 Definitions 3.1 T

33、erms defined elsewhere This Recommendation uses the following terms defined elsewhere: 3.1.1 cascading style sheets (CSS): b-W3C HTML 4.01 A simple mechanism for adding style (e.g., fonts, colours, spacing) to web documents (W3C). 3.1.2 extensible markup language (XML): b-W3C XML 1.0 A generalized t

34、ext format maintained by the World Wide Web Consortium designed as a meta language to describe other markup languages. 3.1.3 hypertext markup language (HTML): b-W3C HTML 4.01 The markup language for the world wide web maintained by the World Wide Web Consortium. 3.1.4 lightweight directory access pr

35、otocol (LDAP): b-IETF RFC 3377 A directory access protocol defined by the Internet Engineering Task Force to interact with X.500 directories. 3.1.5 XHTML: W3C XHTML 1.1 An XML-compliant version of HTML designed to be syntactically rigorous in order to support machine-to-machine communication. Mainta

36、ined by the World Wide Web Consortium. 3.2 Terms defined in this Recommendation This Recommendation defines the following terms: 3.2.1 client: An agent that can access a directory page. A client can be a standard HTML browser or a SWIM-D client. 3.2.2 directory: A canonical collection of attributes

37、about people and resources in an organization, including both the enterprise directory and the endpoints directory. 3.2.3 directory page: An XHTML document containing directory information. Directory pages may provide navigation, search and results in addition to other information. 3.2.4 directory p

38、roxy: A web server that publishes SWIM-D directory pages. Directory proxies have deep knowledge about the directories they access, and format that information into meaningful and useful directory pages for clients. 3.2.5 endpoint directory: A directory of endpoint information when that information i

39、s stored in a standalone directory, such as is the case with b-ITU-T H.35x. 3.2.6 enterprise directory: A directory of people and resources within an organization. 3.2.7 resource: A non-human entity represented in a directory that may have with it associated real-time communications account and addr

40、ess data. Resources may be physical, such as “conference room 12“ or virtual, such as “help desk“, each of which has a voice or video over IP address. 3.2.8 semantic web interface for multimedia directories (SWIM-D): The interface that defines the structure of directory pages and how to access them

41、via their uniform resource locator (URL). 3.2.9 SWIM-D client: A client that is capable of understanding and interpreting SWIM-D directory pages. A SWIM-D client can be an HTML browser that has knowledge of SWIM-D, or it can be an XML-aware agent that processes directory pages for non-HTML purposes,

42、 such as an address book or auto-dialler. 3.2.10 SWIM-D directory page: A directory page that is marked up using SWIM-D metadata. 3.2.11 SWIM-D URL: A uniform resource locator (URL) in the format specified to support access to SWIM-D directory pages. Rec. ITU-T H.351 (06/2008) 3 3.2.12 web browser:

43、A software application capable of rendering HTML and XHTML documents. 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: CSS Cascading Style Sheets DNS Domain Name System HTML HyperText Markup Language HTTP HyperText Transfer Protocol LDAP Lightweight Dir

44、ectory Access Protocol SQL Structured Query Language SWIM-D Semantic Web Interface for Multimedia Directories URL Uniform Resource Locator XML Extensible Markup Language VoIP Voice over Internet Protocol 5 Conventions In this Recommendation, the following conventions are used: “Shall“ indicates a ma

45、ndatory requirement. “Should“ indicates a suggested but optional course of action. “May“ indicates an optional course of action rather than a Recommendation that something take place. References to clauses, annexes and appendices refer to those items within this Recommendation, unless another specif

46、ication is explicitly listed. 6 The problem of resource representations in directories In applications such as voice over IP, video conferencing and instant messaging it is sometimes desirable that many different types of resources have communication accounts. Some examples are listed below: People:

47、 People may have a SIP or H.323 account which they use for voice over IP. Conference rooms: Conference rooms may exist which contain H.323 video conferencing equipment to allow for collaboration. Classrooms: Classrooms may have several different types of audio and video conferencing equipment all op

48、erating simultaneously, such as SIP audio conferencing and H.323 video conferencing. Surveillance sites: H.323, SIP or other remote observation cameras may be deployed throughout an organization to which security staff can connect for remote observation. Medical equipment: A medical cart may contain

49、 multimedia conferencing equipment, along with medical diagnostic equipment. This cart may be mobile and be checked out many times per day and used throughout a hospital. Virtual organizations: It is desirable for a hospital to be able to publish separate numbers for “main hospital number“, “emergency“, “paediatrics“, “paediatric nursing“, and “paediatric doctor on call“. Each of these virtual organizations may have a VoIP account 4 Rec. ITU-T H.351 (06/2008) which is published in both printed and on-line director