|
| TITLE: | The HTTPGET 1.1 Topic Map Application Definition |
| SOURCE: | Steven R. Newcomb |
| PROJECT: | Topic Maps |
| PROJECT EDITORS: | Michel Biezunski, Martin Bryan, Steven R. Newcomb |
| STATUS: | Editor's Draft, Revision 1.1 |
| ACTION: | For review and comment |
| DATE: | 23 April 2003 |
| SUMMARY: | |
| DISTRIBUTION: | SC34 and Liaisons |
| REFER TO: | |
| SUPERCEDES: | |
| REPLY TO: | Dr. James David Mason (ISO/IEC JTC1/SC34 Chairman) Y-12 National Security Complex Information Technology Services Bldg. 9113 M.S. 8208 Oak Ridge, TN 37831-8208 U.S.A. Telephone: +1 865 574-6973 Facsimile: +1 865 574-1896 E-mail: mailto:mxm@y12.doe.gov http://www.y12.doe.gov/sgml/sc34/sc34oldhome.htm Ms. Sara Hafele Desautels, ISO/IEC JTC 1/SC 34 Secretariat American National Standards Institute 25 West 43rd Street New York, NY 10036 Tel: +1 212 642-4937 Fax: +1 212 840-2298 E-mail: sdesaute@ansi.org |
23 April 2003
| 0 | Introduction |
The best available introduction to this document is ISO/IEC JTC1 SC34/WG3 N0393.
The Topic Map Application defined by this document is designed to be included as a module in other Topic Map Applications, thus serving as a portion of the logical and semantic foundation of all topic maps that conform to such Topic Map Applications.
The following naming conventions are used in this TM Application Definition:
PR_ is the prefix of all property names.
AT_ is the prefix of all assertion type names.
RL_ is the prefix of all role names.
| 1 | Scope |
This document defines a "Topic Map Application" as that term is defined in ISO/IEC JTC1 SC34/WG3 N0393.
This TM Application Definition defines properties, assertion types, built-in topics, and merging rules for specifying topics whose subjects are:
HTTP addresses,
streams, and fragments of streams, returned by HTTP GET processes,
relationships between HTTP addresses and the streams returned by HTTP GET processes that use them,
interpretations by human beings of streams returned by HTTP GET processes, as to the subjects such streams are meant to indicate, and
relationships between streams returned by HTTP GET processes and the interpretations that human beings make of them as to the subjects they are meant to indicate.
|
| 2 | References |
IETF RFC 2396: Uniform Resource Identifiers (URI): Generic Syntax
IETF RFC 2732: Format for Literal IPv6 Addresses in URLs
IETF RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1
| 3 | Application Name |
The name of the TM Application defined in this document is IS13250-HTTPGET-1.1
| 4 | Included TM Application Definitions |
|
| 5 | Property Classes |
| 5.1 | IS13250-HTTPGET-1.1::PR_httpAddress |
Value type: string
Semantic: If a value has been assigned to this property, the subject of the topic is the string that is value of the property, considered as an HTTP address.
Constraints on values: The value must be suitable for use as the addressing parameter of an HTTP GET process. The value is not suitable if an HTTP GET returns an error or an empty data stream.
Consistency constraints: (None.)
SIDP or OP? SIDP
Topic Merging Rule: Whenever two or more topics both exhibit values for their IS13250-HTTPGET-1.1::PR_httpAddress properties, the topics must be merged if both of the following conditions are met:
Under the rules for URI interpretation specified in IETF RFC 2396: Uniform Resource Identifiers (URI): Generic Syntax, as modified in IETF RFC 2732: Format for Literal IPv6 Addresses in URLs, the two values must be regarded as identifying the same resource; and
Either both values include the same fragment identifier, or neither value includes a fragment identifier.
Effect of merging on values: Whenever two or more topics that exhibit values for their IS13250-HTTPGET-1.1::PR_httpAddress properties are merged, one of the two values must become the value of the same property of the merged topic. If one of the two values is a built-in value, the built-in value becomes the value of the same property of the merged topic.
| 5.2 | IS13250-HTTPGET-1.1::PR_httpStream |
Value type: string
Semantic: The value is a string considered as an HTTP address. If a value has been assigned to this property, the subject of the topic is the stream of characters, if any, that either has resulted or will result from doing an HTTP GET on the value in some processing context and at some point in time. If a fragment identifier is included in the address, the subject is the specified fragment of the stream returned by the HTTP GET process.
Constraints on values: The value must be suitable for use as the addressing parameter of an HTTP GET process.
Consistency constraints: (None.)
SIDP or OP? SIDP
Topic Merging Rule: Whenever two or more topics both exhibit values for their IS13250-HTTPGET-1.1::PR_httpStream properties, the topics must be merged if both of the following conditions are met:
Under the rules for URI interpretation specified in IETF RFC 2396: Uniform Resource Identifiers (URI): Generic Syntax, as modified in IETF RFC 2732: Format for Literal IPv6 Addresses in URLs, the two values must be regarded as identifying the same resource; and
Either both values include the same fragment identifier, or neither value includes a fragment identifier.
Effect of merging on values: Whenever two or more topics that exhibit values for their IS13250-HTTPGET-1.1::PR_httpStream properties are merged, one of the two values must become the value of the same property of the merged topic. If one of the two values is a built-in value, the built-in value becomes the value of the same property of the merged topic.
| 5.3 | IS13250-HTTPGET-1.1::PR_subjectIndicators{ } |
Value type: list of topics treated as a set
Semantic: Each of the topics independently indicates the subject. Each must be rendered for human perception, and the human perceiver is then assumed to understand the identity of the subject. It is incumbent upon topic map authors to provide subject indicators that will unambiguously indicate subjects by this means.
Constraints on values: The subject of each topic must be a stream.
Consistency constraints: Each member of the set must indicate the same subject.
SIDP or OP? SIDP
Topic Merging Rule: Whenever two or more topics both exhibit values for their IS13250-HTTPGET-1.1::PR_subjectIndicators{ } properties, the topics must be merged if the two values (the two sets) have one or more members in common.
Effect of merging on values: Whenever two or more topics that exhibit values for their IS13250-HTTPGET-1.1::PR_subjectIndicators{ } properties are merged, the union of the two sets of topics that are their values becomes the value of the same property of the merged topic.
| 6 | Assertion Types |
| 6.1 | IS13250-HTTPGET-1.1::AT_httpGet |
Semantic: Each instance asserts the correspondence between a given HTTP address and the stream that has resulted or will result from an HTTP GET operation on the given HTTP address.
| 6.1.1 | Role: IS13250-HTTPGET-1.1::RL_address |
Semantic: The HTTP address which, when used as the parameter of an HTTP GET, will result or has resulted in the stream that plays the other role.
Constraints on player: Must be an addressing expression that exhibits a valid value for its IS13250-HTTPGET-1.1::PR_httpAddress property.
(No property values are conferred on the player.)
| 6.1.2 | Role: IS13250-HTTPGET-1.1::RL_stream |
Semantic: The stream that has resulted or that will result from an HTTP GET on the HTTP address that plays the other role.
Constraints on player: (None.)
Value conferred on the IS13250-HTTPGET-1.1::PR_httpStream property of the role player: The value of the IS13250-HTTPGET-1.1::PR_httpAddress property of the player of the other role (IS13250-HTTPGET-1.1::RL_address) is assigned.
| 6.2 | IS13250-HTTPGET-1.1::AT_subjectIndication |
Semantic: Each instance asserts that the subject of the topic that plays the IS13250-HTTPGET-1.1::RL_indicatedSubject role is assumed to be understood by a human perceiver of a rendition of the stream that is the subject of the topic that plays the IS13250-HTTPGET-1.1::RL_subjectIndicator role.
| 6.2.1 | Role: IS13250-HTTPGET-1.1::RL_subjectIndicator |
Semantic: A data stream which, when rendered for human perception, indicates to the perceiver of that rendition the subject of the topic that plays the other role.
Constraints on player: Must be a data stream; must exhibit a valid value for its IS13250-HTTPGET-1.1::PR_httpStream property.
(No property values are conferred on the player.)
| 6.2.2 | Role: IS13250-HTTPGET-1.1::RL_indicatedSubject |
Semantic: (The subject is assumed to be understood by a human perceiver of a rendition of the data stream that plays the other role.)
Constraints on player: (None.)
Value conferred on the IS13250-HTTPGET-1.1::PR_subjectIndicators{ } property of the role player: The value of the IS13250-HTTPGET-1.1::PR_httpStream property of the player of the other role (IS13250-HTTPGET-1.1::RL_subjectIndicator) is assigned.
| 7 | Built-in Topics and Assertions |
|
| 7.1 | In support of the IS13250-HTTPGET-1.1::AT_httpGet assertion type: |
| 7.1.1 | Built-in Topic |
Subject: The published subject address of the IS13250-HTTPGET-1.1::AT_httpGet assertion type
Built-in value of the
| 7.1.2 | Built-in Assertion |
Assertion type: IS13250-HTTPGET-1.1::AT_httpGet, the built-in topic defined in 7.1.5.
Player of the
Player of the
| 7.1.3 | Built-in Topic |
Subject: The stream resulting from an HTTP GET of the address that is the subject of the built-in topic defined in 7.1.1.
Built-in value of the
| 7.1.4 | Built-in Assertion |
Assertion type: IS13250-HTTPGET-1.1::AT_subjectIndication, the built-in topic defined in .
Player of the
Player of the
| 7.1.5 | Built-in Topic |
Subject: The IS13250-HTTPGET-1.1::AT_httpGet assertion type.
Built-in member of the value of the
