ANSI INCITS392-2005 Information technology - Protocol to Facilitate Operation of Information and Electronic Products through Remote and Alternative Interfaces and Intelligent Agent.pdf

1、American National StandardDeveloped byfor Information Technology Protocol to Facilitate Operation ofInformation and Electronic Productsthrough Remote and AlternativeInterfaces and Intelligent Agents Target DescriptionANSI INCITS 392-2005ANSIINCITS392-2005Copyright American National Standards Institu

2、te 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-,-,-ANSII

3、NCITS 392-2005American National Standardfor Information Technology Protocol to Facilitate Operation ofInformation and Electronic Productsthrough Remote and AlternativeInterfaces and Intelligent Agents Target DescriptionSecretariatInformation Technology Industry CouncilApproved August 12, 2005 Americ

4、an 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 for du

5、e 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 much mo

6、re 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 anyone,

7、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 American N

8、ationalStandard. 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 titlepage

9、 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 mayr

10、eceive 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 rights

11、 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 that ho

12、lders 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 publication of

13、 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 or im

14、pliedthat 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 Instit

15、ute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-ContentsPageForeword . iiiIntroduction v1 Scope. 12 Conformance . 13 Normative References . 14 Terms, Definitions and Abbreviated Terms 25 Relation to XML . 26 Overview 37 Th

16、e element. 37.1 General 37.2 The about attribute. 47.3 The id attribute. 47.4 The hidden attribute. 47.5 The element. 47.6 The element 47.7 The element . 57.7.1 General 57.7.2 The id Attribute. 57.7.3 The element . 57.8 The element. 67.8.1 General 67.8.2 The type attribute. 67.8.3 The id attribute.

17、67.8.4 The element 67.9 Target properties from DCMI . 67.10 The element . 77.10.1 General 77.10.2 The id attribute. 77.10.3 The name attribute. 77.10.4 The type attribute. 87.10.5 The hidden attribute. 87.10.6 The element . 87.10.7 The element 97.10.8 The element 97.10.9 Socket properties from DCMI.

18、 97.11 Resource Directory 97.12 Extensions for Security and Privacy 10iCopyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-PageAnnexesA XML Schema for Target Description. 11B Example

19、 Target Description 16C Bibliography . 18iiCopyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHSForeword (This foreword is not part of American National Standard ANSI INCITS 392-2005.)This

20、 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 standard is to define an XML language for the description ofcompliant Targets and their Sockets, as used within the

21、URC framework for discov-ery purposes. A document conforming to this language is a Target Description.This document contains three annexes, which are informative and not consideredpart of the standard.Requests for interpretation, suggestions for improvement or addenda, or defect re-ports are welcome

22、. 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 necessarily imply that

23、 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 Standards Institute . Li

24、sa 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 F. Silletti Instit

25、ute 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 Menard (Alt.)Microso

26、ft Corporation . Isabelle Valet-Harper Don Stanwyck (Alt.)Mike Ksar (Alt.)National Institute of Standards its use is recommended. It specifies a URI that indicates the content type that is used for the text content of the element. For example, when using the UNSPSC classification schema, the value h

27、ttp:/www.unspsc.org can be used. 7.10.8 The element may occur any number of times as a subelement of . It may contain (as subelements) preconditions on the use of the Socket, for example constraints on the users location in order to let the user control the Target. NOTE The element is defined as a p

28、laceholder in this standard, so that subsequent versions of this standard or Target vendors can add subelements to , possibly by using vocabularies from other standards. 7.10.9 Socket properties from DCMI Additionally any element and element refinement from the set of Dublin Core Metadata Initiative

29、 (DCMI) Metadata Terms may be used to describe a Socket, if appropriate. Each of them may occur multiple times within a element. In particular, the following DCMI terms may be applied to a Socket. specifying the product code (or instance code) of the Socket specifying the manufacturer of the Socket

30、specifying the provider of the Socket specifying co-manufacturers of the Socket It is recommended to use the xsi:type attribute to identify the coding schema, if appropriate. In general, a Socket inherits a Targets properties. If specified both on Target and Socket level, the Socket property overwri

31、tes the Targets property. 7.11 Resource Directory A Target Description shall contain exactly one Resource Directory, as defined by ANSI INCITS 393-2005. Copyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted withou

32、t license from IHS-,-,-ANSI INCITS 392-2005 10 EXAMPLE A Resource Directory references the documents and resources that are available from the Target, and that are related to the discovery and control of the Target. The Resource Directory may contain references to subdirectories of resources (in the

33、 form of lower-level Resource Directories) on the Target, to Resource Sheets on the Target, to User Interface Implementation Descriptions (UIIDs) on the Target, and to external Resource Services. Annex B provides a sample Target Description with a complete Resource Directory, contained in the elemen

34、t of the TD. 7.12 Extensions for Security and Privacy For applications and environments where security and privacy mechanisms are implemented above the level of transport security, additional elements in the TD may be introduced for specific networking platforms and environments. For example, new su

35、belements of or may be specified in networking specific guidelines. However, these extensions should be kept as minimal as possible, to minimize the platform-dependence of the TD. Copyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or

36、networking permitted without license from IHS-,-,-ANSI INCITS 392-2005 11Annex A (informative) XML Schema for Target Description Target Description schema International Committee for Information Technology Standards (INCITS) This is the XML schema for a Target Description. See http:/www.incits.org/t

37、c_home/v2.htm. English 2003-12-12 2004-12-19 Copyright 2003 INCITS Root element. Type of a target element. Element containing information related to the location of the target. Copyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or net

38、working permitted without license from IHS-,-,-ANSI INCITS 392-2005 12 Any element and element refinement from the Dublin Core Metadata Initiative (DCMI) Metadata Terms document may be used to describe a Target, if appropriate. Each of them may occur multiple times within a target element. In partic

39、ular, the following DCMI terms may be applied: dc:identifier specifying the product code (or instance code) of the Target; dc:creator specifying the manufacturer of the Target; dc:publisher specifying the provider of the Target; dc:contributor specifying co-manufacturers of the Target. It is recomme

40、nded to use the xsi:type attribute to identify the coding schema, if appropriate. NOTE In general, a Socket inherits a Targets properties. If specified both on Target and Socket level, the Sockets property overwrites the Targets property. Any element and element refinement from the Dublin Core Metad

41、ata Initiative (DCMI) Metadata Terms document may be used to describe a Target, if appropriate. Each of them may occur multiple times within a target element, except for the dcterms:modified element which, if present, shall only occur once. In particular, the following DCMI terms may be applied: dct

42、erms:conformsTo to specify conformance to this standard; dcterms:modified to identify TD versions. NOTE In general, a Socket inherits a Targets properties. If specified both on Target and Socket level, the Sockets property overwrites the Targets property. The RDF elements inserted here shall follow

43、the resource sheet RDF schema, in the namespace http:/www.incits.org/incits393-2005# For applications and environments where security and privacy mechanisms are implemented above the level of transport security, additional elements in the TD may be introduced for specific networking platforms and en

44、vironments. For example, new subelements of target or socket may be specified in networking specific guidelines. However, these extensions should be kept as minimal as possible, to minimize the platform-dependence of the TD. The URI may not be resolvable, but it shall be globally unique. The hidden

45、attribute can be specified on Target and Socket level. The Socket inherits the setting from the Target. If specified on both levels, the Sockets hidden attribute overrides the one of the Target. Type of a location element. Describes the location of the target. Copyright American National Standards I

46、nstitute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-ANSI INCITS 392-2005 13Type giving geocoordinates for a target. srsName attribute shall be present. Type of a locator element. Describes a locator function. Type of a so

47、cket element. The URI shall be local to the Target-URC Network. Typically this URI is relative, in which case it is based on the URI of the Target Description (or based on a base URI provided by the Target in some other platform-specific way). The category element can be repeated with different valu

48、es. This is useful if the classification schema allows for multiple values, or if multiple classification schemas are employed. Copyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-AN

49、SI INCITS 392-2005 14 Any element and element refinement from the set of Dublin Core Metadata Initiative (DCMI) Metadata Terms may be used to describe a Socket, if appropriate. Each of them may occur multiple times within a socket element. In particular, the following DCMI terms may be applied to a Socket: dc:identifier