ANSI INCITS393-2005 Information Technology - Information and Electronic Products through Remote and Alternative Interfaces and Intelligent Agents Resource Description《信息技术.信息和电子产品通.pdf

1、American National StandardDeveloped byfor Information Technology Protocol to Facilitate Operation ofInformation and Electronic Productsthrough Remote and AlternativeInterfaces and Intelligent Agents Resource DescriptionANSI INCITS 393-2005ANSIINCITS393-2005Copyright American National Standards Insti

2、tute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Copyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-ANS

3、IINCITS 393-2005American National Standardfor Information Technology Protocol to Facilitate Operation ofInformation and Electronic Productsthrough Remote and AlternativeInterfaces and Intelligent Agents Resource DescriptionSecretariatInformation Technology Industry CouncilApproved Augusr 12, 2005 Am

4、erican National Standards Institute, Inc.Copyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Approval of an American National Standard requires review by ANSI that therequirements fo

5、r due process, consensus, and other criteria for approval havebeen met by the standards developer.Consensus is established when, in the judgement of the ANSI Board ofStandards Review, substantial agreement has been reached by directly andmaterially affected interests. Substantial agreement means muc

6、h more thana simple majority, but not necessarily unanimity. Consensus requires that allviews and objections be considered, and that a concerted effort be madetowards their resolution.The use of American National Standards is completely voluntary; theirexistence does not in any respect preclude anyo

7、ne, whether he has approvedthe standards or not, from manufacturing, marketing, purchasing, or usingproducts, processes, or procedures not conforming to the standards.The American National Standards Institute does not develop standards andwill in no circumstances give an interpretation of any Americ

8、an NationalStandard. Moreover, no person shall have the right or authority to issue aninterpretation of an American National Standard in the name of the AmericanNational Standards Institute. Requests for interpretations should beaddressed to the secretariat or sponsor whose name appears on the title

9、page of this standard.CAUTION NOTICE: This American National Standard may be revised orwithdrawn at any time. The procedures of the American National StandardsInstitute require that action be taken periodically to reaffirm, revise, orwithdraw this standard. Purchasers of American National Standards

10、mayreceive current information on all standards by calling or writing the AmericanNational Standards Institute.American National StandardPublished byAmerican National Standards Institute, Inc.25 West 43rd Street, New York, NY 10036Copyright 2005 by Information Technology Industry Council (ITI)All ri

11、ghts reserved.No part of this publication may be reproduced in anyform, in an electronic retrieval system or otherwise,without prior written permission of ITI, 1250 Eye Street NW, Washington, DC 20005. Printed in the United States of AmericaCAUTION: The developers of this standard have requested tha

12、t holders of patents that may berequired for the implementation of the standard disclose such patents to the publisher. However,neither the developers nor the publisher have undertaken a patent search in order to identifywhich, if any, patents may apply to this standard. As of the date of publicatio

13、n of this standardand following calls for the identification of patents that may be required for the implementation ofthe standard, no such claims have been made. No further patent search is conducted by the de-veloper or publisher in respect to any standard it processes. No representation is made o

14、r impliedthat licenses are not required to avoid infringement in the use of this standard.Copyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Copyright American National Standards In

15、stitute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-ContentsPageForeword .ivIntroduction .vi1 Scope. 12 Conformance . 13 Normative References . 24 Terms, Definitions and Abbreviated Terms 35 Relation to Other Standards 45.

16、1 Relation to Dublin Core Metadata Element Set . 45.2 Relation to XML . 45.3 Relation to Resource Description Framework (RDF). 56 Overview 57 A Simple Example 78 . 78.1 General 78.2 The rdf:about attribute 88.3 The element. 88.4 The element 98.4.1 General 98.4.2 The rdf:parseType attribute 98.4.3 Th

17、e rdf:datatype attribute. 98.4.4 The element 98.4.4.1 General 98.4.4.2 The xml:lang attribute 98.4.4.3 The title attribute 108.4.4.4 The element . 108.5 The element 108.6 The element 118.7 The element. 118.8 The element 128.8.1 General 128.8.2 The element . 128.8.3 The element 138.8.4 The element .

18、138.8.5 The element 148.8.6 The element. 148.8.7 More examples for 158.9 The element 16i8.10 The element 168.11 The element 16Copyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Page

19、8.12 The element 178.13 The element 178.14 The element . 178.15 The element 178.16 The element . 188.17 The element 188.18 The element 188.19 Other elements from DCMI 199 199.1 General 199.2 The rdf:about attribute . 209.3 The element 219.4 The element. 219.5 The element. 219.6 The element 229.7 The

20、 element. 229.8 The element 229.9 The element. 239.10 The element 239.11 The element . 239.12 Elements from DCMI . 249.13 The element 2410 2510.1 General 2510.2 The rdf:about attribute . 2510.3 The element 2510.4 The element. 2610.5 The element 2610.6 The element 2610.7 The element 2610.8 The elemen

21、t. 2710.9 Elements from DCMI . 2711 . 2811.1 General 28ii11.2 The rdf:about attribute . 28Copyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Page11.3 The element. 2911.4 The element

22、 . 2911.5 The element 2911.6 The element . 3011.7 The element 3011.8 The element 3011.9 The element 3011.10 Elements from DCMI pertaining to the “scent“ of Resources. 3112 . 3112.1 General 3112.2 The rdf:about attribute 3312.3 The element . 3312.4 The element . 3412.5 The element. 3412.6 The element

23、 . 3412.7 The element 3512.8 The element . 3512.9 The element 3512.10 The element 3612.11 The element 3612.12 Elements from DCMI pertaining to the “scent“ of Resources. 3612.13 The element. 3712.14 The element 3712.15 The element 3812.16 The element 38Table 1 Example Atomic Resource Description of a

24、 temperature label for a thermometer. 7AnnexesA RDF Schema for Atomic Resource Descriptions . 39B Sample Resource Sheet File . 44C Bibliography . 50iii-2005.)Copyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted w

25、ithout license from IHS-,-,-Foreword (This foreword is not part of American National Standard ANSI INCITS 393This American National Standard is one in a series on the operation of informationand electronic products through remote and alternative interfaces and intelligentagents. The goal of this sta

26、ndard is to define the syntax for describing Resources rel-evant to the user interface of a device or service (“Target“).This document contains three annexes. They are informative and not consideredpart of the standard.Requests for interpretation, suggestions for improvement or addenda, or defect re

27、-ports are welcome. They should be sent to the InterNational Committee for Informa-tion Technology Standards (INCITS), ITI, 1250 Eye Street, NW, Suite 200,Washington, DC 20005.This standard was processed and approved for submittal to ANSI by INCITS. Com-mittee approval of this standard does not nece

28、ssarily imply that all committee mem-bers voted for its approval. At the time it approved this standard, INCITS had thefollowing members:Karen Higginbottom, ChairJennifer Garner, SecretaryOrganization Represented Name of RepresentativeAIM Global Dan Mullen Charles Biss (Alt.)American National Standa

29、rds Institute . Lisa Rajchel Apple Computer, Inc. David Michael Electronic Industries Alliance Edward Mikoski, Jr. Henry Cuschieri (Alt.)EMC Corporation Gary Robinson Farance, Inc. Frank Farance Hewlett-Packard Company. Karen Higginbottom Steve Mills (Alt.)Scott Jameson (Alt.)IBM Corporation Ronald

30、F. Silletti Institute for Certification of Computer Professionals. Kenneth M. Zemrowski Thomas Kurihara (Alt.)IEEE . Judith Gorman Richard Holleman (Alt.)Robert Pritchard (Alt.)Intel Norbert Mikula Dave Thewlis (Alt.)Philip Wennblom (Alt.)Lexmark International . Don Wright Dwight Lewis (Alt.)Paul Me

31、nard (Alt.)Microsoft Corporation . Isabelle Valet-Harper Don Stanwyck (Alt.)Mike Ksar (Alt.)National Institute of Standards in the con-trol phase, a User Interface Socket Description and a Presentation Template, with la-bels and other Atomic Resources can be used to construct an explorable userinter

32、face that is tailored to the users needs, in any modality (e.g. visual, auditory, tac-tile, multimodal), through which a user can access and control the Target. NOTE: Within the URC framework, there needs to be a common set of resourcetypes and a common format for resource descriptions so that they

33、can be used byany URC. This standard defines both. In this standard, the terms Resources andResource Descriptions (note the first letters are capitalized) includes only those ob-jects and descriptions that conform to the standard formats defined in this standard.It is important to note that URCs can

34、 employ other types of resources and resourcedescriptions beyond those described in this standard.viAMERICAN NATIONAL STANDARD ANSI INCITS 393-2005American National Standard for Information Technology Protocol to Facilitate Operations of Information and Electronic Products through Remote and Alterna

35、tive Interfaces and Intelligent Agents Resource Description 11 Scope This standard is part of a set of standards to facilitate operation of information and electronic products through remote and alternative interfaces and intelligent agents. The purpose of this standard is to define a syntax for des

36、cribing Atomic Resources, Resource Sheets, User Interface Implementation Descriptions, Resource Services, and Resource Directories relevant to the user interface of a device or service (“Target“). This standard is part of a set of related standards, with the other standards being: ANSI INCITS 389-20

37、05, Protocol to Facilitate Operation of Information and Electronic Products through Remote and Alternative Interfaces and Intelligent Agents - Universal Remote Console, ANSI INCITS 392-2005, Protocol to Facilitate Operation of Information and Electronic Products through Remote and Alternative Interf

38、aces and Intelligent Agents - Target Description, ANSI INCITS 390-2005, Protocol to Facilitate Operation of Information and Electronic Products through Remote and Alternative Interfaces and Intelligent Agents - User Interface Socket Description, and ANSI INCITS 391-2005, Protocol to Facilitate Opera

39、tion of Information and Electronic Products through Remote and Alternative Interfaces and Intelligent Agents - Presentation Template. 2 Conformance An eXtensible Markup Language (XML) fragment is an Atomic Resource Description in conformance with this standard if its outer element is (with res: repr

40、esenting the namespace http:/www.incits.org/incits393-2005#) as specified in clause 8. An Atomic Resource Description may use language extensions if the extensions are coded in RDF/XML syntax, and if it follows the syntax and requirements outlined in this standard for all of its nonextension parts.

41、A Resource Description Framework (RDF) / XML file is a Resource Sheet in conformance with this standard if its root element is (with rdf: representing the namespace http:/www.w3.org/TR/1999/REC-rdf-syntax-19990222/) with subelement (with res: representing the namespace http:/www.incits.org/incits393

42、-2005#), as specified in clause 9. A Resource Sheet may use language extensions if the extensions are coded in RDF/XML syntax, and if it follows the syntax and requirements outlined in this standard for all of its nonextension parts. An XML fragment is a User Interface Implementation Description (UI

43、ID) Description in conformance with this standard if its outer element is (with res: representing the namespace http:/www.incits.org/incits393-2005#) as specified in clause 10. A UIID Description may use language extensions if the extensions are coded in RDF/XML syntax, and if it follows the syntax

44、and requirements outlined in this standard for all of its nonextension parts. Copyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-ANSI INCITS 393-2005 2 An XML fragment is a Resource

45、 Service Description in conformance with this standard if its outer element is (with res: representing the namespace http:/www.incits.org/incits393-2005#) as specified in clause 11. A Resource Service Description may use language extensions if the extensions are coded in RDF/XML syntax, and if it fo

46、llows the syntax and requirements outlined in this standard for all of its nonextension parts. An XML fragment is a Resource Directory in conformance with this standard if its outer element is (with res: representing the namespace http:/www.incits.org/incits393-2005#) as specified in clause 12. A Re

47、source Directory may use language extensions if the extensions are coded in RDF/XML syntax, and if it follows the syntax and requirements outlined in this standard for all of its nonextension parts. NOTE URC manufacturers are encouraged to implement their URCs so that unrecognized markup (that may b

48、elong to unknown language extensions) is ignored without failing. 3 Normative References The following standards contain provisions which, through reference in this text, constitute provisions of this American National Standard. At the time of publication, the editions indicated were valid. All stan

49、dards are subject to revision, and parties to agreements based on this American National Standard are encouraged to investigate the possibility of applying the most recent editions of the standards indicated below. ANSI INCITS 389-2005, Protocol to Facilitate Operation of Information and Electronic Products through Remote and Alternative Interfaces and Intelligent Ag