You can download and open this file to your own computer but DRM prevents opening this file on another computer, including a networked server. PDF Price. Not a Member? This standard is not included in any packages.
Revised By:. We have no amendments or corrections for this standard. Request Proposal Price. This standard contributes to the following Sustainable Development Goal :. CHF Buy. Life cycle Previously Withdrawn. Final text received or FDIS registered for formal approval. Proof sent to secretariat or FDIS ballot initiated: 8 weeks. Close of voting. Proof returned by secretariat. If the datatype is IRI, a locator referring to the information resource that is the variant name; otherwise the string is the variant name.
A locator identifying the datatype of the variant name value. The scope that represents the context in which the variant name is preferred as a label for the topic.
If not null, the topic that reifies the variant name. The item identifiers of the variant name. The topic name to which the variant belongs. Computed value: the topic name item whose [variants] property contains this variant item. Equality rule: Variant items are equal if the values of their [value], [datatype], [scope], and [parent] properties are equal. The value of the [scope] property of each variant item shall be a true superset of the value of the [scope] property of the topic name item in its [parent] property.
An occurrence is a representation of a relationship between a subject and an information resource. The subject in question is that represented by the topic which contains the occurrence. The information resource may either be a value inside the topic map or an external information resource. Occurrences are essentially a specialized kind of association, where one participant in the association shall be an information resource. An occurrence type is a subject describing the nature of the relationship between the subjects and information resources linked by the occurrences of that type.
All occurrences have a scope, which defines the context in which the occurrence relationship between the information resource and the subject is valid. If the datatype is IRI, a locator referring to the information resource the occurrence connects with the subject; otherwise the string is the information resource. A locator identifying the datatype of the occurrence value. The scope that represents the context in which the occurrence relationship is considered valid.
The topic that defines the nature of the occurrence relationship. If not null, the topic that reifies the occurrence. The item identifiers of the occurrence. Computed value: the topic item whose [occurrences] property contains this occurrence item. Equality rule: Occurrence items are equal if the values of their [value], [datatype], [scope], [type], and [parent] properties are equal.
An association is a representation of a relationship between one or more subjects. Associations have an association type , a subject describing the nature of the relationship represented by associations of that type.
An association role is a representation of the involvement of a subject in a relationship represented by an association. An association role connects two pieces of information within an association: the association role player, that is, the topic participating in the association, and the association role type , that is, a subject describing the nature of the participation of an association role player in an association.
An example of an association might be the 'authorship' relationship between Henrik Ibsen and the play 'Peer Gynt'. In this relationship there are two roles: Ibsen plays the role of 'author', while 'Peer Gynt' plays the role of 'work'. Another example might be the 'parenthood' relationship between Hamlet, King Hamlet, and Queen Gertrude. This relationship has three roles: Hamlet plays the role of 'child', the King that of 'father', and the Queen that of 'mother'.
All associations have a scope, which defines the context in which the relationship represented by the association is considered valid.
The scope also applies to the assignment of the roles to the topics playing them; that is, the scope defines the context in which the topics can be said to play the roles in the association.
Association items represent associations. Association items have the following properties:. The topic that defines the nature of the relationship represented by the association. The scope that represents the context in which the association is considered valid. The association roles for all the topics that participate in this relationship. If not null, the topic that reifies the association.
The item identifiers of the association. Computed value: the topic map item whose [associations] property contains this association item. Equality rule: Association items are equal if the values of their [scope], [type], and [roles] properties are equal. See 5. Association role items represent association roles. Association role items have the following properties:.
The topic that represents the nature of the involvement of the association role player in the association. If not null, the topic that reifies the association role. The item identifiers of this association role. The association to which the association role belongs. Computed value: the association item whose [roles] property contains this association role item.
Equality rule: Association role items are equal if the values of their [type], [player], and [parent] properties are equal. A central operation in Topic Maps is that of merging , a process applied to a topic map in order to eliminate redundant topic map constructs in that topic map.
This clause specifies in which situations merging shall occur, but the rules given here are insufficient to ensure that all redundant information is removed from a topic map. Any change to a topic map that causes any set to contain two information items equal to each other shall be followed by the merging of those two information items according to the rules given below for the type of information item to which the two equal information items belong.
The procedure for merging two topic items A and B whose [parent] properties shall contain the same topic map item is given below.
It is an error if A and B both have non-null values in their [reified] properties which are different. Replace A by C wherever it appears in one of the following properties of an information item: [topics], [scope], [type], [player], and [reifier]. Set C's [topic names] property to the union of the values of A and B's [topic names] properties. Set C's [occurrences] property to the union of the values of A and B's [occurrences] properties.
Set C's [subject identifiers] property to the union of the values of A and B's [subject identifiers] properties. Set C's [subject locators] property to the union of the values of A and B's [subject locators] properties.
Set C's [item identifiers] property to the union of the values of A and B's [item identifiers] properties. Set C's [value] property to the value of the [value] property of A.
B's value is equal that of A and need not be taken into account. Set C's [type] property to the value of the [type] property of A. Set C's [scope] property to the value of the [scope] property of A.
Set C's [reifier] property to the value of A's [reifier] property if it is not null, and to the value of B's [reifier] property if A's property is null. If both A and B have non-null values, the topic items shall be merged, and the topic item resulting from the merge be set as the value of C's [reifier] property.
Set C's [item identifiers] property to the union of the value of the [item identifiers] properties of A and B. Remove A and B from the [topic names] property of the topic item in their [parent] properties, and add C. Set C's [value] property to the value of A's [value] property. B's value is equal to that of A and need not be taken into account.
Set C's [datatype] property to the value of A's [datatype] property. Set C's [scope] property to the value of A's [scope] property. If both A and B have non-null values, the topic items shall be merged, and the topic item resulting from the merge set as the value of C's [reifier] property. Set C's [item identifiers] property to the union of the values of A's and B's [item identifiers] properties. Remove A and B from the [variants] property of the topic name item in their [parent] properties, and add C.
Set C's [type] property to the value of A's [type] property. Remove A and B from the [occurrences] property of the topic item in their [parent] properties, and add C. Set C's [roles] property to the value of A's [roles] property. Remove A and B from the [associations] property of the topic map item in their [parent] properties, and add C. Set C's [player] property to the value of A's [player] property.
Remove A and B from the [roles] property of the association item in their [parent] properties, and add C. This clause defines a number of core subject identifiers in order to achieve interoperability through consistent behaviour. A topic type is a subject that captures some commonality in a set of subjects.
Any subject that belongs to the extension of a particular topic type is known as an instance of that topic type. A topic type may itself be an instance of another topic type, and there is no limit to the number of topic types a subject may be an instance of. The type-instance relationship is not transitive. That is, if B is an instance of the type A, and C is an instance of the type B, it does not follow that C is an instance of A.
The type-instance relationship between two topics can be asserted using an association item that conforms to the following rules:. The [player] property will then contain the topic item representing the type. The [player] property will then contain the topic item representing the instance.
Association items that use one or more of the subject identifiers defined in this clause, but which do not conform to these structural rules, are not considered to represent type-instance relationships. Scope applies to this association type in the same way as it does to any other. The supertype-subtype relationship is the relationship between a more general type the supertype and a specialization of that type the subtype.
If B is the subtype of A, it follows that every instance of B is also an instance of A. The converse is not necessarily true. A type may have any number of subtypes and supertypes. The supertype-subtype relationship is transitive, which means that if B is a subtype of A, and C a subtype of B, C is also a subtype of A.
Loops in this relationship are allowed, and should be interpreted to mean that the sets of instances for all types in the loop are the same.
0コメント