dc:rights"The LinkedModel DTYPE Ontology is issued under a Creative Commons Attribution Share Alike 3.0 United States License. Attribution should be made to <a href=\"http://www.topquadrant.com\">TopQuadrant, Inc.</a>."^^xsd:string;
dc:subject"Datatypes"^^xsd:string;
dc:title"Datatype Ontology"^^xsd:string;
voag:hasLicenseTypevoag:CC-SHAREALIKE_3PT0-US;
voag:withAttributionTo
voag:TopQuadrantAttribution;
vaem:acronym"DTYPE"^^xsd:string;
vaem:dateCreated"2011-29-05"^^vaem:dateUnion;
vaem:description"The ontology 'dtype' provides a specification of simple data types such as enumerations. These are needed in support of the conversion of XML Schemas and UML Models to OWL. Codelists are also defined in 'dtype'."^^xsd:string;
vaem:intent"To provide a foundation for data types."^^xsd:string;
owl:versionInfo"Created with TopBraid Composer"^^xsd:string.
dtype:CodeList
rdf:typeowl:Class;
rdfs:label"Enumeration"^^xsd:string;
rdfs:subClassOfdtype:Enumeration;
vaem:definition"A codelist is a controlled vocabulary of terms that are used to represent permissible values of a variable in information systems. The representaiton of codes in 'dtype' has been influenced by CCTS and UBL."^^xsd:string.
dtype:CompositeCodeList
rdf:typeowl:Class;
rdfs:label"Composite code list"^^xsd:string;
rdfs:subClassOfdtype:CodeList;
rdfs:subClassOf
[rdf:typeowl:Restriction;
owl:allValuesFromdtype:CodeList;
owl:onPropertydtype:compositeOf
];
vaem:definition"A composite codelist is a codelist made up of other codelists. It does not introduce any new codes."^^xsd:string;
vaem:definition"The base class for datatypes that have values that are restriced to a set of literals or tokens. The members of the restriction may themselve be restriced by facets that apply to scalar data types."^^xsd:string.
dtype:Enumeration
rdf:typeowl:Class;
rdfs:label"VAEM Enumeration"^^xsd:string;
rdfs:subClassOfowl:Thing;
rdfs:subClassOf
[rdf:typeowl:Restriction;
owl:allValuesFromdtype:EnumeratedValue;
owl:onPropertydtype:value
];
rdfs:subClassOf
[rdf:typeowl:Restriction;
owl:allValuesFromdtype:EnumeratedValue;
owl:onPropertydtype:defaultValue
];
rdfs:subClassOf
[rdf:typeowl:Restriction;
owl:maxCardinality"1"^^xsd:nonNegativeInteger;
owl:onPropertydtype:defaultValue
];
vaem:definition"A type that serves as a container for the enumerated values of an enumeration. This enables the enumeration itself to be referenceable. One need for this is in determing the default value of an enumeration , another need is in the management of sub-enumerations and composite enumerations."^^xsd:string.
dtype:SimpleCodeList
rdf:typeowl:Class;
rdfs:label"Simple code list"^^xsd:string;
rdfs:subClassOfdtype:CodeList;
rdfs:subClassOf
[rdf:typeowl:Restriction;
owl:allValuesFromdtype:EnumeratedValue;
owl:onPropertydtype:hasMember
];
vaem:definition"A simple codelist is one made up only of enumerated values."^^xsd:string;
vaem:definition"A value reference is a pointer to an Enumerated Value. The original position of the value can be overridden by the position attribute."^^xsd:string.
dtype:code
rdf:typeowl:DatatypeProperty;
rdfs:label"code"^^xsd:string;
rdfs:rangexsd:anySimpleType;
vaem:definition"A property for expressing an encoded value. The range has been set to 'xsd:anySimpleType' to allow for a variety of scalar datatypes."^^xsd:string.
dtype:compositeOf
rdf:typeowl:ObjectProperty;
rdfs:label"composite of"^^xsd:string;
vaem:definition"Aproperty for constructing composite data structures"^^xsd:string.
dtype:defaultValue
rdf:typerdf:Property;
rdfs:label"default value"^^xsd:string;
vaem:definition"The property 'dtype:defaultValue' is a general property for specifying a value in situations where none is specified, or can be determined. In some cases of use, this property could have a scalar value and in other cases may need to refer to a first class concept that holds a 'value object'. For this reason, the type of this property is set as 'rdf:Property' and the property is rangeless."^^xsd:string.
dtype:derivedFrom
rdf:typeowl:ObjectProperty;
rdfs:label"derived from"^^xsd:string;
vaem:definition"A property for specifying a derivation relationship."^^xsd:string.
dtype:hasMember
rdf:typeowl:ObjectProperty;
rdfs:label"has member"^^xsd:string;
vaem:definition"A property for specifying how member elements make up a data structure."^^xsd:string.
dtype:literal
rdf:typeowl:DatatypeProperty;
rdfs:label"literal"^^xsd:string;
rdfs:rangexsd:string;
vaem:definition"A general purpose property for holding string literals."^^xsd:string.
dtype:order
rdf:typeowl:DatatypeProperty;
rdfs:label"order"^^xsd:string;
rdfs:rangexsd:nonNegativeInteger;
rdfs:seeAlsodtype:orderIndex;
vaem:definition"The property 'dtype:order' provides a means to specify a precedence. One use of order is in specifying ordered enumerations such as 'voag:ConfidentialityLevel'. A similar property, but with an important type difference, is 'vaem:orderIndex'. This is for use on property occurrences in class axioms where it can be placed on a restriction to specify how that property may be transformed into other representations where ordering has some importance, for example, in XML Schema sequences. Whereas 'vaem:order' is a datatype property, 'vaem:orderIndex' is an annotation property."^^xsd:string.
dtype:orderIndex
rdf:typeowl:AnnotationProperty;
rdfs:label"order index"^^xsd:string;
rdfs:rangexsd:nonNegativeInteger;
vaem:definition"The property 'dtype:orderIndex' is an annotation property to specify a position that some value or structure will have. One use is to specify the place that a resource has in a sequence. One use is on property occurrences in class axioms. Here 'vaem:orderIndex' is placed on a restriction to specify how that property may be transformed into a representation where ordering has some importance, for example, in XML Schema sequences."^^xsd:string.
dtype:position
rdf:typeowl:DatatypeProperty;
rdfs:label"code"^^xsd:string;
rdfs:rangexsd:nonNegativeInteger.
dtype:refersTo
rdf:typeowl:ObjectProperty;
rdfs:label"refers to"^^xsd:string;
vaem:definition"An indirection pointer for relating a slot in am occurrence data structure, such as 'dtype:ValueReference' with another resource."^^xsd:string.
dtype:value
rdf:typerdf:Property;
rdfs:label"value"^^xsd:string;
vaem:definition"The property 'dtype:value' is a general property that in some cases could have scalar values and in other cases may refer to a first class concept that is a 'value object'. For this reason, the type of this property is set as 'rdf:Property' and the property is rangeless."^^xsd:string.
rdfs:label"Vocabulary for Attaching Essential Metadata"^^xsd:string;
voag:hasLicenseTypevoag:CC-SHAREALIKE_3PT0-US;
vaem:acronym"VAEM"^^xsd:string;
vaem:dateCreated"2011-04-20"^^vaem:dateUnion;
vaem:description"""VAEM stands for \"Vocabulary for Attaching Essential Metadata\". The purpose of VAEM is to provide, by import, a foundation for commonly needed resources when building an ontology. An effort has been made to restrict these resources to a minimal level. In some ways DC, Dublin Core, could have provided such a foundation. Importing DC unfortunately causes \"ontology glut\", through the import of many DC Terms.
VAEM attaches basic metadata properties and dimension properties, such as domain, discipline, aspect and viewpoint, to the 'owl:Ontology' class to fully qualify the ontology.
What VAEM regards as 'essential metadata' is data about dates and times, confidentiality, and other characterisitic qualifiers of the ontology, but also references to where a ontology is documented and where to find ontology Governance, Attribution and Provenance. For the latter, some properties from the VOAG ontology are used, notably, 'voag:hasGovernance', 'voag:withAttributionTo', and 'voag:hasLicenceType'. VAEM also defines classes for representing enumerations and enumerated values."""^^xsd:string;
vaem:hasCatalogEntry
<vaem:VAEM-CatalogEntry>;
vaem:hasRolevaem:SchemaGraph;
vaem:intent"To provide essential resources and metadata for ontologies and controlled vocabularies so that the provenance, governance and licensing aspects of an ontology can be understand."^^xsd:string;
vaem:lastUpdated"$LastChangedDate: 2011-06-04 04:04:02 -0700 (Sat, 04 Jun 2011) $"^^vaem:dateUnion;
owl:versionInfo"$Id: OSG_vaem-(v1.2).ttl 5016 2011-06-04 11:04:02Z RalphHodgson $"^^xsd:string,"Created with TopBraid Composer"^^xsd:string.
vaem:Aspect
rdf:typeowl:Class;
rdfs:label"Aspect"^^xsd:string;
rdfs:subClassOfvaem:Scope;
vaem:definition"Aspect Scope is used to distinguish among sets of features of a domain or subject area. The term is borrowed from 'aspect-oriented' programming, where it is used to separate concerns. An ontology may be characterized by this dimension so as to parition features that are orthogonal. For example, in an SBFI systems ontology we can distinguish aspects for 'structure', 'function', 'behavior' and 'interface'."^^xsd:string.
vaem:BridgeGraph
rdf:typevaem:GraphRole;
rdfs:label"Bridge graph"^^xsd:string.
vaem:Category
rdf:typeowl:Class;
rdfs:label"Category"^^xsd:string;
rdfs:subClassOfowl:Thing;
vaem:definition"Category is an abstract class for all concepts whose roles are to characterize other concepts in some manner."^^xsd:string.
vaem:CollectionGraph
rdf:typevaem:GraphRole;
rdfs:label"Collection graph"^^xsd:string.
vaem:CurationGraph
rdf:typevaem:GraphRole;
rdfs:label"Curation graph"^^xsd:string;
vaem:definition"A curation graph is one whose purpose is to hold metadata that is needed to describe, govern and provision another graph. A curation graph will likely use voag and vaem for this purpose. The property 'vaem:curationGraph' is used to link to the graph (or graphs) being curated."^^xsd:string.
vaem:DataGraph
rdf:typevaem:GraphRole;
rdfs:label"Data graph"^^xsd:string.
vaem:Discipline
rdf:typeowl:Class;
rdfs:label"Discipline"^^xsd:string;
rdfs:subClassOfvaem:Scope;
vaem:definition"A Discipline is a specific area of work or study. Examples of disciplines in the engineering domain are electrical engineering, mechanical engineering and, in the financial domain, risk assessment, investment analysis. In 'vaem', 'Discipline' is used as a dimension for characterizing an ontology graph."^^xsd:string.
vaem:Domain
rdf:typeowl:Class;
rdfs:label"Domain"^^xsd:string;
rdfs:subClassOfvaem:Scope;
vaem:definition"A domain is a subject area of interest. Examples of domains are 'enterprise', 'process', 'organization' and 'system'. In 'vaem' the notion of 'Domain' is used as a dimension for characterizing an ontology graph."^^xsd:string.
vaem:FunctionsGraph
rdf:typevaem:GraphRole;
rdfs:label"Functions graph"^^xsd:string.
vaem:GraphRole
rdf:typeowl:Class;
rdfs:label"Graph role"^^xsd:string;
rdfs:subClassOfvaem:Category;
vaem:definition"GraphRole is used to characterize how a graph of resources participates in an ontology set. For example, a graph can be a schema, vocabulary, dataset, script, or ruleset."^^xsd:string;
vaem:description"A graph that specifies a transformation of a graph into another graph or graphs. Invariably this is a SPINMap graph using SPARQL Rules (SPIN) to express the transforms."^^xsd:string.
vaem:ProxyGraph
rdf:typevaem:GraphRole;
rdfs:label"Proxy graph"^^xsd:string.
vaem:RulesGraph
rdf:typevaem:GraphRole;
rdfs:label"Rules Graph"^^xsd:string.
vaem:SchemaGraph
rdf:typevaem:GraphRole;
rdfs:label"Schema graph"^^xsd:string.
vaem:Scope
rdf:typeowl:Class;
rdfs:label"Scope"^^xsd:string;
rdfs:subClassOfvaem:Category;
vaem:definition"Scope is used indicate a scope of relevance of an ontology. There are no instances of these properties in VAEM. Each context of use will need specific treatment."^^xsd:string.
vaem:ScriptGraph
rdf:typevaem:GraphRole;
rdfs:label"Script graph"^^xsd:string.
vaem:ViewGraph
rdf:typevaem:GraphRole;
rdfs:label"View graph"^^xsd:string.
vaem:Viewpoint
rdf:typeowl:Class;
rdfs:label"Viewpoint"^^xsd:string;
rdfs:subClassOfvaem:Scope;
vaem:definition"Viewpoint is used to denote how a set of resources, or an individual resource, is relevant to a context of use. The term 'viewpoint' is adopted from the ISO RM-ODP specifications and its more recent use in enterprise architecture descriptions. In 'lmc' the notion of 'Viewpoint' is used as a dimension for characterizing an ontology graph."^^xsd:string.
vaem:VocabularyGraph
rdf:typevaem:GraphRole;
rdfs:label"Vocabulary graph"^^xsd:string;
vaem:description"An RDF/OWL Graph that is a controlled set of instances."^^xsd:string.
vaem:acronym
rdf:typeowl:DatatypeProperty;
rdfs:label"acronym"^^xsd:string;
vaem:definition"The property 'vaem:acronym' provides a common way to define a commonly used abbreviation on a resource."^^xsd:string.
vaem:dateCreated
rdf:typeowl:DatatypeProperty;
rdfs:label"date created"^^xsd:string;
rdfs:rangevaem:dateUnion;
vaem:definition"The property 'vaem:dateCreated' is intended for general use as the name implies. The range of the property is set as 'vaem:dateUnion' so as to allow a value to have a number of forms from a year only to a full timestamp."^^xsd:string.
vaem:dateUnion
rdf:typerdfs:Datatype;
rdfs:label"date union"^^xsd:string;
rdfs:subClassOfrdfs:Resource;
vaem:description"A data type that is the union of xsd:date, xsd:dateTime and xsd:gYear. LMC's 'dateUnion' is equivalent to the xsd specification that uses an xsd:union of memberTypes='xsd:date xsd:dateTime xsd:gYear'."^^xsd:string;
owl:unionOf(xsd:datexsd:dateTimexsd:gYear).
vaem:definition
rdf:typeowl:DatatypeProperty;
rdfs:label"definition"^^xsd:string;
rdfs:rangexsd:string;
vaem:definition"A datatype property that can be freely used on any kind of resource. The range of the property is 'xsd:string'."^^xsd:string.
vaem:description
rdf:typeowl:DatatypeProperty;
rdfs:label"description"^^xsd:string;
rdfs:rangexsd:string;
vaem:definition"The property 'vaem:description' is intended for general use as the name implies. Unlike 'vaem:definition', 'vaem:description' is an 'owl:DatatypeProperty'. As such it can play a stronger role in the model, for example, as a predicate in an axiom."^^xsd:string.
vaem:hasAspectScope
rdf:typerdf:Property;
rdfs:label"has aspect scope"^^xsd:string;
rdfs:subPropertyOfvaem:hasScope;
vaem:definition"The property 'vaem:hasAspectScope' is used to distinguish among sets of features of a domain or subject area. The term is borrowed from 'aspect-oriented' programming, where it is used to separate concerns. An ontology may be characterized by this dimension so as to parition features that are orthogonal. For example, in an SBFI systems ontology we can distinguish aspects for 'structure', 'function', 'behavior' and 'interface'. The property is an 'rdf:Property' to allow both scalar and object values."^^xsd:string.
vaem:hasCatalogEntry
rdf:typeowl:ObjectProperty;
rdfs:label"has catalog entry"^^xsd:string.
vaem:hasDisciplineScope
rdf:typerdf:Property;
rdfs:label"has discipline scope"^^xsd:string;
rdfs:subPropertyOfvaem:hasScope;
vaem:definition"The property 'vaem:hasDisciplineScope' is used to indicate relevance of a set of resources, or a resource itself, to a specific discipline of work or study. Examples of disciplines in the engineering domain are electrical engineering, mechanical engineering and, in the financial domain, risk assessment, investment analysis. In 'vaem' the property is used as a dimension for characterizing an ontology graph. The property is an 'rdf:Property' to allow both scalar and object values."^^xsd:string.
vaem:hasDomainScope
rdf:typerdf:Property;
rdfs:label"has domain scope"^^xsd:string;
rdfs:subPropertyOfvaem:hasScope;
vaem:definition"The property 'vaem:hasDomainScope' is used to specify how a set of resources, or an individual resource is grounded in a domain, that is, a subject area of interest. Examples of domains are 'enterprise', 'process', 'organization' and 'system'. In 'lmc' the property is used as a dimension for characterizing an ontology graph. The property is an 'rdf:Property' to allow both scalar and object values."^^xsd:string.
vaem:hasRole
rdf:typeowl:ObjectProperty;
rdfs:label"has role"^^xsd:string;
vaem:definition"The property 'lms:hasRole' is used to characterize how a resource participates in an ontology set. In 'lmc' the property is used to specify the role that a graph plays, for example, an ontology graph can be a schema, vocabulary, dataset, script, or ruleset."^^xsd:string.
vaem:hasScope
rdf:typerdf:Property;
rdfs:label"has scope"^^xsd:string;
vaem:definition"The property 'vaem:hasScope' is used indicate a scope of relevance of an ontology. In 'vaem' the property is used as a dimension for characterizing an ontology graph. The property is an 'rdf:Property' to allow both scalar and object values."^^xsd:string.
vaem:hasViewpointScope
rdf:typerdf:Property;
rdfs:label"has viewpoint scope"^^xsd:string;
rdfs:subPropertyOfvaem:hasScope;
vaem:definition"The property 'vaem:hasViewpointScope' is used to denote how a set of resources, or an individual resource, is relevant to a context of use. The term 'viewpoint' is adopted from the ISO RM-ODP specifications and its more recent use in enterprise architecture descriptions. In 'lmc' the property is used as a dimension for characterizing an ontology graph. The property is an 'rdf:Property' to allow both scalar and object values."^^xsd:string.
vaem:id
rdf:typerdf:Property;
rdfs:label"id"^^xsd:string;
vaem:definition"The property 'vaem:id' is intended for general use as a means to specifiy an identifier. The type of this property is intentionally set to 'rdf:Property' so that use of the property can allow both object and scaler values. For this reason, the property is rangeless."^^xsd:string.
vaem:integer_1to5
rdf:typerdfs:Datatype;
rdfs:label"integer 1 to 5"^^xsd:string;
rdfs:subClassOfxsd:integer;
owl:equivalentClass
[rdf:typerdfs:Datatype;
owl:onDatatypexsd:positiveInteger;
owl:withRestrictions
([xsd:maxInclusive"5"^^xsd:positiveInteger
])
];
owl:onDatatypexsd:positiveInteger.
vaem:intent
rdf:typeowl:DatatypeProperty;
rdfs:label"intent"^^xsd:string;
rdfs:rangexsd:string;
vaem:definition"The property 'vaem:intent' is used to describe a statement of purpose. This typically takes the form of desired outcomes."^^xsd:string.
vaem:lastUpdated
rdf:typeowl:DatatypeProperty;
rdfs:label"last updated"^^xsd:string;
rdfs:rangevaem:dateUnion;
vaem:definition"The property 'vaem:lastUpdated' is intended for general use as the name implies. The range of the property is set as 'vaem:dateUnion' so as to allow a value to have a number of forms from a year only to a full timestamp."^^xsd:string.
vaem:name
rdf:typeowl:DatatypeProperty;
rdfs:label"name"^^xsd:string;
rdfs:rangexsd:string;
rdfs:subPropertyOfrdfs:label;
vaem:definition"The property 'vaem:name' is intended for general use. In many cases 'rdfs:label' could be used give names to resources. In the case where compliance with a specific naming rule is needed, 'vaem:name' allows a resource to carry a name that is used in more specific contexts. Making 'vaem:name' a sub-property of 'rdfs:label' allows 'vaem:name' to serve in the same way as an 'rdfs:label'."^^xsd:string.
vaem:namespace
rdf:typeowl:DatatypeProperty;
rdfs:label"namespace"^^xsd:string;
rdfs:rangexsd:anyURI;
vaem:definition"The property 'vaem:namespace' provides a means to specify the onotlogy URI with which a graph is primarily associated. The intent is to allow multiple graphs to define statements for resources in the same Ontology namespace. For example, a foundation level graph with the base URI of 'http://www.somesite.com/1.0/schema/OurOntology' may define general concepts for 'OurOntology'. Another graph with the base URI 'http://www.somesite.com/1.0/schema/level2/OurOntology' may add more specific details to the same 'OurOntology'. Each of these two graphs would carry the same value for 'vaem:namespace', that is, 'http://www.somesite.com/schema/OurOntology'. In other words, an ontology URI is the URI associated with the resources of a controlled namespace. On the other hand the graph URIs (the base URIs) identify the graphs that hold resources that make up an ontology."^^xsd:string.
vaem:namespacePrefix
rdf:typeowl:DatatypeProperty;
rdfs:label"namespace prefix"^^xsd:string;
rdfs:rangexsd:string;
vaem:definition"The property 'vaem:namespacePrefix' specifes a short handle or label for the URI of an Ontology. Multiple graphs can define statements for resources in the same Ontololgy namespace. For example, a foundation level graph with the base URI of 'http://www.somesite.com/1.0/schema/OurOntology' may define general concepts for 'OurOntology'. Another graph with the base URI 'http://www.somesite.com/1.0/schema/level2/OurOntology' may add more specific details to the same 'OurOntology'. Each of these two graphs would carry the same value for 'vaem:namespacePrefix', for this example, perhaps, 'ourOntology'."^^xsd:string.
vaem:numericUnion
rdf:typerdfs:Datatype;
rdfs:label"numeric union"^^xsd:string;
rdfs:subClassOfrdfs:Resource;
vaem:description"A datatype that is the union of numeric xsd data types. LMC's 'numericUnion' is equivalent to the xsd specification that uses an xsd:union of memberTypes='xsd:decimal xsd:double xsd:float xsd:integer'."^^xsd:string;
vaem:definition"The property 'vaem:ownedBy' is a general property that in some cases could have scalar values and in other cases may need to refer to some concept of 'Party'. For this reason, the type of this property is set as 'rdf:Property' and the property is rangeless."^^xsd:string.
vaem:releaseDate
rdf:typeowl:DatatypeProperty;
rdfs:label"release date"^^xsd:string;
rdfs:rangevaem:dateUnion;
vaem:definition"The property 'vaem:releaseDate' is intended for general use as the name implies. The range of the property is set as 'vaem:dateUnion' so as to allow a value to have a number of forms from a year only to a full timestamp."^^xsd:string.
vaem:revision
rdf:typeowl:AnnotationProperty;
rdfs:label"revision"^^xsd:string;
rdfs:rangexsd:string;
vaem:definition"The property 'vaem:revision' is an annotation property intended for general use as the name implies. "^^xsd:string.
vaem:revisionDate
rdf:typeowl:DatatypeProperty;
rdfs:label"revision date"^^xsd:string;
rdfs:rangexsd:dateTime;
vaem:definition"The property 'vaem:revisionDate' is intended for general use as the name implies. The range of the property is 'xsd:dateTime'."^^xsd:string.
vaem:revisionNumber
rdf:typeowl:DatatypeProperty;
rdfs:label"revision number"^^xsd:string;
rdfs:rangexsd:string;
vaem:definition"The property 'vaem:revisionNumber' is intended for general use as the name implies."^^xsd:string.
vaem:specificity
rdf:typeowl:DatatypeProperty;
rdfs:label"specificity"^^xsd:string;
rdfs:rangevaem:integer_1to5;
vaem:definition"The property 'vaem:specificity' is intended to specify the level of detail of an ontology. The values that can be set for this property are restriced to an integer from 1 to 5. An ontology at level 1 has concepts of more general applicability than one at level 5. By having graphs at different levels of specificity it is possible to support greater modularity for selective imports."^^xsd:string.
vaem:timestamp
rdf:typeowl:DatatypeProperty;
rdfs:label"timestamp"^^xsd:string;
rdfs:rangexsd:dateTime;
vaem:definition"The property 'vaem:timestamp' is intended for general use as the name implies. The range of the property is an XSD data time."^^xsd:string.
vaem:url
rdf:typeowl:DatatypeProperty;
rdfs:label"url"^^xsd:string;
rdfs:rangexsd:anyURI;
vaem:definition"The property 'vaem:url' is intended for general use as the name implies. The range of the property is set as an XSD URI."^^xsd:string.
vaem:definition"A general property that has multiple uses. In VAEM it is used on owl:Ontology to express dependencies on resources from graphs that are not imported."^^xsd:string.