ISO 19142:2010 地理情報—Web機能サービス | ページ 6

4.1

attribute <XML>

name-value pair contained in an element (4.6)

[SOURCE:ISO 19136:2007, definition 4.1.3]

Note 1 to entry: In this International Standard, an attribute is an XML attribute unless otherwise specified.

4.2

client

software component that can invoke an operation (4.17) from a server (4.28)

[SOURCE:ISO 19128:2005, definition 4.1]

4.3

coordinate

one of a sequence of n numbers designating the position of a point in n -dimensional space

[SOURCE:ISO 19111:2007, definition 4.5]

4.4

coordinate reference system

coordinate system (4.5) that is related to an object by a datum

[SOURCE:ISO 19111:2007, definition 4.8]

4.5

coordinate system

set of mathematical rules for specifying how coordinates (4.3) are to be assigned to points

[SOURCE:ISO 19111:2007, definition 4.10]

4.6

element <XML>

basic information item of an XML document containing child elements, attributes (4.1) and character data

[SOURCE:ISO 19136:2007, definition 4.1.23]

4.7

feature

abstraction of real world phenomena

[SOURCE:ISO 19101:2002, definition 4.11]

Note 1 to entry: A feature can occur as a type or an instance. The term"feature type" or"feature instance" should be used when only one is meant.

4.8

feature identifier

identifier that uniquely designates a feature (4.7) instance

4.9

filter expression

predicate expression encoded using XML

[SOURCE:ISO 19143:2010, definition 4.11]

4.10

interface

named set of operations (4.17) that characterize the behaviour of an entity

[SOURCE:ISO 19119:2005, definition 4.2]

4.11

join predicate

filter expression (4.9) that includes one or more clauses that constrain properties from two different entity types

[SOURCE:ISO 19143:2010, definition 4.16]

Note 1 to entry: In this International Standard, the entity types will be feature (4.7) types.

4.12

join tuple

set of two or more object instances that satisfy a filter that includes join predicates (4.11)

Note 1 to entry: In this International Standard, the object instances will be feature (4.7) instances.

4.13

local resource

resource that is under the direct control of a system

Note 1 to entry: In this International Standard, the system is a web feature service and the resource is held in a data store that is directly controlled by that service.

4.14

locator attribute

attribute (4.1) whose value is a reference to a local resource (4.13) or remote resource (4.20)

Note 1 to entry: In XML, this attribute is commonly called an href and contains a URI reference to the remote resource (see W3C XLink).

4.15

Multipurpose Internet Mail Extensions (MIME) type

media type and subtype of data in the body of a message that designates the native representation (canonical form) of such data

[SOURCE:IETF RFC 2045:1996]

4.16

namespace

<XML>

collection of names, identified by a URI reference, which are used in XML documents as element (4.6) names and attribute (4.1) names

[SOURCE:W3C XML Namespaces:1999]

4.17

operation

specification of a transformation or query that an object may be called to execute

[SOURCE:ISO 19119:2005, definition 4.3]

4.18

property

facet or attribute of an object, referenced by a name

[SOURCE:ISO 19143:2010, definition 4.21]

4.19

resource

asset or means that fulfils a requirement

[SOURCE:ISO 19115:2003, definition 4.10]

Note 1 to entry: In this International Standard, the resource is a feature (4.7) , or any identifiable component of a feature (e.g. a property of a feature).

4.20

remote resource

resource that is not under the direct control of a system

Note 1 to entry: In this International Standard, the system is a web feature service. The resource is not held in any data store that is directly controlled by that service and thus cannot be directly retrieved by the service.

4.21

request

invocation of an operation (4.17) by a client (4.2)

[SOURCE:ISO 19128:2005, definition 4.10]

4.22

relocate

update a reference to a resource that has been moved or copied to a new location

4.23

resolve

retrieval of a referenced resource and its insertion into a server-generated response document

Note 1 to entry: The insertion may be accomplished by either replacing the reference inline with a copy of the resource or by relocating the reference to point to a copy of the resource that has been placed in the response document.

4.24

response

result of an operation (4.17) returned from a server (4.28) to a client (4.2)

[SOURCE:ISO 19128:2005, definition 4.11]

4.25

response model

schema (4.26) defining the properties of each feature (4.7) type that can appear in the response (4.24) to a query operation (4.17)

Note 1 to entry: This is the schema of feature types that a client (4.2) can obtain using the DescribeFeatureType operation (see Clause 9).

4.26

schema

formal description of a model

[SOURCE:ISO 19101:2002, definition 4.25]

Note 1 to entry: In general, a schema is an abstract representation of an object's characteristics and relations to other objects. An XML schema represents the relationship between the attributes (4.1) and elements (4.6) of an XML object (for example, a document or a portion of a document).

4.27

schema <XML Schema>

collection of schema (4.26) components within the same target namespace (4.16)

[SOURCE:ISO 19136:2007, definition 4.1.54]

4.28

server

particular instance of a service (4.29)

[SOURCE:ISO 19128:2005, definition 4.12]

4.29

service

distinct part of the functionality that is provided by an entity through interfaces (4.10)

[SOURCE:ISO 19119:2005, definition 4.1]

4.30

service metadata

metadata describing the operations (4.17) and geographic information available at a server (4.28)

[SOURCE:ISO 19128:2005, defintion 4.14]

4.31

traversal

<XML>

using or following an XLink link for any purpose

[SOURCE:W3C XLink:2001]

4.32

tuple

ordered list of values

[SOURCE:ISO 19136:2007, definition 4.1.63]

Note 1 to entry: In this International Standard, the ordered list will generally be a finite sequence of features (4.7) , each of a specific feature type.

4.33

Uniform Resource Identifier

URI

unique identifier for a resource, structured in conformance with IETF RFC 2396

[SOURCE:ISO 19136:2007, definition 4.1.65]

Note 1 to entry: The general syntax is <scheme>::<scheme-specified-part>. The hierarchical syntax with a namespace (4.16) is <scheme>://<authority><path>?<query>.