Matches in LOV for { ?s <http://www.w3.org/2000/01/rdf-schema#comment> ?o. }
- holder comment "The person holding the position".
- informationResourceIdentifier comment "An unambiguous reference to the information resource within a given context. Recommended best practice is to identify the resource by means of a string or number conforming to a formal identification system. Formal identification systems include but are not limited to the Uniform Resource Identifier (URI) (including the Uniform Resource Locator (URL)), the Digital Object Identifier (DOI), and the International Standard Book Number (ISBN). DC2003ISO.".
- involvedEntityIn comment "The entities related to a given happening. Such entities can be agents, instruments, materials, places, etc.".
- involvedIn comment "The participating entities in a given happening that are agents. Participation is usually via some role.".
- laconicDescription comment "An extremely short (typically, single sentence) description of an entity".
- locatedIn comment "The relation between an object (also some happenings via their participants) and location where the object is.".
- partOf comment "The general part-of relation which takes place between a whole and each of its parts. It has a number of specializations.".
- partiallyControls comment "Any sort of partial control an agent has with respect to an object.".
- partiallyOwns comment "Indicates that an Agent has some ownership over an object. It allows wide interpretations from \"I have a bike\" to \"John has shares in Fujitsu\".".
- roleIn comment "Relates a role to a happening, conditioned and affected by the role. Usually, the participants of a happening 'play' one or more roles in it.".
- socialPositionHolder comment "The relation between a social position and the person who has it. ".
- startTime comment "the starting moment of a happening".
- subRegionOf comment "Relation between two locations where the first is contained within the other.".
- subTopicOf comment "A relation from less general to more general topic. Defined to be transitive via rule.".
- subsidiaryOrganizationOf comment "Indicates that an organization is in some sense part of another organization. This necessarily requires structural and organizational relations and may or may not indicate ownership. Its reverse, parentOrganizationOf, is a special case of partial control.".
- withinOrganization comment "Determines in which organization is the position".
- terms comment "The set of terms provided by the OAI ORE initiative".
- AggregatedResource comment "A resource which is included in an Aggregation. Note that asserting that a resource is a member of the class of Aggregated Resources does not imply anything other than that it is aggregated by at least one Aggregation.".
- Aggregation comment "A set of related resources (Aggregated Resources), grouped together such that the set can be treated as a single resource. This is the entity described within the ORE interoperability framework by a Resource Map.".
- Proxy comment "A Proxy represents an Aggregated Resource as it exists in a specific Aggregation. All assertions made about an entity are globally true, not only within the context of the Aggregation. As such, in order to make assertions which are only true of a resource as it exists in an Aggregation, a Proxy object is required. For example, one might want to cite an article as it appears in a specific journal, or assign aggregation-specific metadata to a Resource.".
- ResourceMap comment "A description of an Aggregation according to the OAI-ORE data model. Resource Maps are serialised to a machine readable format according to the implementation guidelines.".
- aggregates comment "Aggregations, by definition, aggregate resources. The ore:aggregates relationship expresses that the object resource is a member of the set of Aggregated Resources of the subject (the Aggregation). This relationship between the Aggregation and its Aggregated Resources is thus more specific than a simple part/whole relationship, as expressed by dcterms:hasPart for example.".
- describes comment "This relationship asserts that the subject (a Resource Map) describes the object (an Aggregation).".
- isAggregatedBy comment "The inverse relationship of ore:aggregates, ore:isAggregatedBy asserts that an Aggregated Resource is aggregated by an Aggregation.".
- isDescribedBy comment "The inverse relationship of ore:describes, in this case the object of the relationship is the Resource Map and the subject is the Aggregation which it describes.".
- proxyFor comment "Proxy objects are used to represent a Resource as it is aggregated in a particular Aggregation. The ore:proxyFor relationship is used to link the proxy to the Aggregated Resource it is a proxy for. The subject of the relationship is a Proxy object, and the object of the relationship is the Aggregated Resource.".
- Feature comment "This class represents the top-level feature type. This class is \n equivalent to GFI_Feature defined in ISO 19156:2011, and it is \n superclass of all feature types.".
- Geometry comment "The class represents the top-level geometry type. This class is \n equivalent to the UML class GM_Object defined in ISO 19107, and \n it is superclass of all geometry types.".
- SpatialObject comment "The class spatial-object represents everything that can have \n a spatial representation. It is superclass of feature and geometry.".
- gmlLiteral comment "A GML serialization of a geometry object.".
- hasGeometry comment "A spatial representation for a given feature.".
- hasSerialization comment "Connects a geometry object with its text-based serialization.".
- sfContains comment "Exists if the subject SpatialObject spatially contains the \n object SpatialObject. DE-9IM: T*****FF*".
- sfDisjoint comment "Exists if the subject SpatialObject is spatially disjoint \n from the object SpatialObject. DE-9IM: FF*FF****".
- sfEquals comment "Exists if the subject SpatialObject spatially equals the \n object SpatialObject. DE-9IM: TFFFTFFFT".
- sfOverlaps comment "Exists if the subject SpatialObject spatially overlaps the \n object SpatialObject. DE-9IM: T*T***T**".
- sfTouches comment "Exists if the subject SpatialObject spatially touches the \n object SpatialObject.\n DE-9IM: FT******* ^ F**T***** ^ F***T****".
- sfWithin comment "Exists if the subject SpatialObject is spatially within the \n object SpatialObject. DE-9IM: T*F**F***".
- wktLiteral comment "A Well-known Text serialization of a geometry object.".
- Curve comment "A Curve is a 1-dimensional geometric object usually stored as a sequence of Points, with the subtype of Curve specifying the form of the interpolation between Points. This specification defines only one subclass of Curve, LineString, which uses linear interpolation between Points.\nA Curve is a 1-dimensional geometric object that is the homeomorphic image of a real, closed, interval.\nA Curve is simple if it does not pass through the same Point twice with the possible exception of the two end\npoints.\nA Curve is closed if its start Point is equal to its end Point.\nThe boundary of a closed Curve is empty.\nA Curve that is simple and closed is a Ring.\nThe boundary of a non-closed Curve consists of its two end Points.\nA Curve is defined as topologically closed, that is, it contains its endpoints f(a) and f(b).".
- Geometry comment "Geometry is the root class of the hierarchy.\nThe instantiable subclasses of Geometry are restricted to 0, 1 and 2-dimensional geometric objects that exist in 2, 3 or 4-dimensional coordinate space (R2, R3 or R4). Geometry values in R2 have points with coordinate values for x and y. Geometry values in R3 have points with coordinate values for x, y and z or for x, y and m. Geometry values in R4 have points with coordinate values for x, y, z and m.\nThe interpretation of the coordinates is subject to the coordinate reference systems associated to the point. All coordinates within a geometry object should be in the same coordinate reference systems. Each coordinate shall be unambiguously associated to a coordinate reference system either directly or through its containing geometry. The z coordinate of a point is typically, but not necessarily, represents altitude or elevation. The m coordinate represents a measurement.\nAll Geometry classes described in this specification are defined so that instances of Geometry are topologically closed, i.e. all represented geometries include their boundary as point sets. This does not affect their representation, and open version of the same classes may be used in other circumstances, such as topological representations.".
- GeometryCollection comment "A GeometryCollection is a geometric object that is a collection of some number of geometric objects.\nAll the elements in a GeometryCollection shall be in the same Spatial Reference System. This is also the Spatial Reference System for the GeometryCollection.\nGeometryCollection places no other constraints on its elements. Subclasses of GeometryCollection may restrict membership based on dimension and may also place other constraints on the degree of spatial overlap between elements.".
- Line comment "A Line is a LineString with exactly 2 Points.".
- LineString comment "A LineString is a Curve with linear interpolation between Points. Each consecutive pair of Points defines a Line segment.".
- LinearRing comment "A LinearRing is a LineString that is both closed and simple.".
- MultiCurve comment "A MultiCurve is a 1-dimensional GeometryCollection whose elements are Curves.\nA MultiCurve defines a set of methods for its subclasses and is included for reasons of extensibility.\nA MultiCurve is simple if and only if all of its elements are simple and the only intersections between any two elements occur at Points that are on the boundaries of both elements.\nThe boundary of a MultiCurve is obtained by applying the mod 2 union rule: A Point is in the boundary of a MultiCurve if it is in the boundaries of an odd number of elements of the MultiCurve.\nA MultiCurve is closed if all of its elements are closed. The boundary of a closed MultiCurve is always empty.\nA MultiCurve is defined as topologically closed.".
- MultiLineString comment "A MultiLineString is a MultiCurve whose elements are LineStrings.".
- MultiPoint comment "A MultiPoint is a 0-dimensional GeometryCollection. The elements of a MultiPoint are restricted to Points. ThePoints are not connected or ordered in any semantically important way.\nA MultiPoint is simple if no two Points in the MultiPoint are equal (have identical coordinate values in X and Y).\nEvery MultiPoint is spatially equal to a simple Multipoint.\nThe boundary of a MultiPoint is the empty set.".
- MultiPolygon comment "A MultiPolygon is a MultiSurface whose elements are Polygons.\nThe assertions for MultiPolygons are as follows.\na) The interiors of 2 Polygons that are elements of a MultiPolygon may not intersect.\nb) The boundaries of any 2 Polygons that are elements of a MultiPolygon may not cross and may touch at only a finite number of Points.\nc) A MultiPolygon is defined as topologically closed.\nd) A MultiPolygon may not have cut lines, spikes or punctures, a MultiPolygon is a regular closed Point set,\ne) The interior of a MultiPolygon with more than 1 Polygon is not connected; the number of connected components of the interior of a MultiPolygon is equal to the number of Polygons in the MultiPolygon. \nThe boundary of a MultiPolygon is a set of closed Curves (LineStrings) corresponding to the boundaries of its element Polygons. Each Curve in the boundary of the MultiPolygon is in the boundary of exactly 1 element Polygon, and every Curve in the boundary of an element Polygon is in the boundary of the MultiPolygon.".
- MultiSurface comment "A MultiSurface is a 2-dimensional GeometryCollection whose elements are Surfaces, all using coordinates from the same coordinate reference system. The geometric interiors of any two Surfaces in a MultiSurface may not intersect in the full coordinate system. The boundaries of any two coplanar elements in a MultiSurface may intersect, at most, at a finite number of Points. If they were to meet along a curve, they could be merged into a single surface.\nA MultiSurface may be used to represent heterogeneous surfaces collections of polygons and polyhedral surfaces. It defines a set of methods for its subclasses. The subclass of MultiSurface is MultiPolygon corresponding to a collection of Polygons only. Other collections shall use MultiSurface.".
- Point comment "A Point is a 0-dimensional geometric object and represents a single location in coordinate space. \nA Point has an x-coordinate value, a y-coordinate value. If called for by the associated Spatial Reference System, it may also have coordinate values for z and m.\nThe boundary of a Point is the empty set.".
- Polygon comment "A Polygon is a planar Surface defined by 1 exterior boundary and 0 or more interior boundaries. Each interior boundary defines a hole in the Polygon.\nThe exterior boundary LinearRing defines the top of the surface which is the side of the surface from which the exterior boundary appears to traverse the boundary in a counter clockwise direction. The interior LinearRings will have the opposite orientation, and appear as clockwise when viewed from the top,\nThe assertions for Polygons (the rules that define valid Polygons) are as follows:\na) Polygons are topologically closed;\nb) The boundary of a Polygon consists of a set of LinearRings that make up its exterior and interior boundaries;\nc) No two Rings in the boundary cross and the Rings in the boundary of a Polygon may intersect at a Point but only as a tangent.\nd) A Polygon may not have cut lines, spikes or punctures.\ne) The interior of every Polygon is a connected point set;\nf) The exterior of a Polygon with 1 or more holes is not connected. Each hole defines a connected component of the exterior.".
- PolyhedralSurface comment "A PolyhedralSurface is a contiguous collection of polygons, which share common boundary segments. For each pair of polygons that touch, the common boundary shall be expressible as a finite collection of LineStrings. Each such LineString shall be part of the boundary of at most 2 Polygon patches. \nFor any two polygons that share a common boundary, the top of the polygon shall be consistent. This means that when two LinearRings from these two Polygons traverse the common boundary segment, they do so in opposite directions. Since the Polyhedral surface is contiguous, all polygons will be thus consistently oriented. This means that a non-oriented surface (such as Mbius band) shall not have single surface representations. They may be represented by a MultiSurface.\nIf each such LineString is the boundary of exactly 2 Polygon patches, then the PolyhedralSurface is a simple, closed polyhedron and is topologically isomorphic to the surface of a sphere. By the Jordan Surface Theorem (Jordans Theorem for 2-spheres), such polyhedrons enclose a solid topologically isomorphic to the interior of a sphere; the ball. In this case, the top of the surface will either point inward or outward of the enclosed finite solid. If outward, the surface is the exterior boundary of the enclosed surface. If inward, the surface is the interior of the infinite complement of the enclosed solid. A Ball with some number of voids (holes) inside can thus be presented as one exterior boundary shell, and some number in interior boundary shells.".
- Surface comment "A Surface is a 2-dimensional geometric object.\nA simple Surface may consists of a single patch that is associated with one exterior boundary and 0 or more interior boundaries. A single such Surface patch in 3-dimensional space is isometric to planar Surfaces, by a simple affine rotation matrix that rotates the patch onto the plane z = 0. If the patch is not vertical, the projection onto the same plane is an isomorphism, and can be represented as a linear transformation, i.e. an affine.\nPolyhedral Surfaces are formed by stitching together such simple Surfaces patches along their common boundaries. Such polyhedral Surfaces in a 3-dimensional space may not be planar as a whole, depending on the orientation of their planar normals. If all the patches are in alignment (their normals are parallel), then the whole stitched polyhedral surface is co-planar and can be represented as a single patch if it is connected.\nThe boundary of a simple Surface is the set of closed Curves corresponding to its exterior and interior boundaries.\nA Polygon is a simple Surface that is planar. A PolyhedralSurface is a simple surface, consisting of some number of Polygon patches or facets. If a PolyhedralSurface is closed, then it bounds a solid. A MultiSurface containing a set of closed PolyhedralSurfaces can be used to represent a Solid object with holes.".
- ontology comment "OPMW is an OPMV, PROV and P-plan extension to model the executions and definitions of scientific workflows.".
- DataVariable comment "A Data variable is a workflow template artifact that represents a variable in the workflow specification.\n\nExample:\n@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .\n@prefix opmw: <http://www.opmw.org/ontology/> .\n\n<http://www.opmw.org/export/resource/DataVariable/AQUAFLOW_NTM_SUM_CORRDO>\n a opmw:WorkflowTemplateArtifact , opmw:DataVariable ;\n rdfs:label \"Data variable Sum_CorrDO\" ;\n opmw:hasDimensionality \"0\"^^xsd:int ;\n opmw:isGeneratedBy <http://www.opmw.org/export/resource/WorkflowTemplateProcess/AQUAFLOW_NTM_CREATEPLOTS> ;\n opmw:template <http://www.opmw.org/export/resource/WorkflowTemplate/AQUAFLOW_NTM> .".
- ParameterVariable comment "An parameter variable represents a description of an input parameter of a process. Parameter variables can only be used by process.\n\nExample:\n@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .\n@prefix opmw: <http://www.opmw.org/ontology/> .\n\n<http://www.opmw.org/export/resource/ParameterVariable/AQUAFLOW_NTM_LATITUDE>\n a opmw:/WorkflowTemplateArtifact , opmw:ParameterVariable ;\n rdfs:label \"Parameter variable Latitude\" ;\n opmw:template <http://www.opmw.org/export/resource/WorkflowTemplate/AQUAFLOW_NTM> .".
- WorkflowExecutionAccount comment "A workflow execution account represents the execution from the perspective of the system.\n\nExample:\n@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .\n@prefix opmw: <http://www.opmw.org/ontology/> .\n@prefix opmo: <http://openprovenance.org/model/opmo#> .\n\n<http://www.opmw.org/export/resource/WorkflowExecutionAccount/ACCOUNT1335533097598>\n a opmo:Account , opmw:WorkflowExecutionAccount> ;\n rdfs:label \"Execution account created on 1335533097598\" ;\n opmw:executedInWorkflowSystem\n <http://www.opmw.org/export/resource/Agent/SHELL> ;\n opmw:hasEndTime\n \"2012-04-25T07:17:48-07:00\"^^xsd:dateTime ;\n opmw:hasExecutionDiagram \"http://wind.isi.edu/marbles/assets/components/workflow_portal/users/1/Water/runs/run_144.png\"^^xsd:anyURI ;\n opmw:hasStartTime \"2012-04-25T07:17:05-07:00\"^^xsd:dateTime ;\n opmw:hasStatus \"SUCCESS\" ;".
- WorkflowExecutionArtifact comment "A workflow execution artifact represents a resource used or generated in the execution of a workflow.\n\nExample:\n@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .\n@prefix opmw: <http://www.opmw.org/ontology/> .\n@prefix opmv: <http://purl.org/net/opmv/ns#> .\n@prefix opmo: <http://openprovenance.org/model/opmo#> .\n\n<http://www.opmw.org/export/resource/WorkflowExecutionArtifact/25F1016C12EBE301EE7AADBC0B085C45>\n a opmw:WorkflowExecutionArtifact , opmv:Artifact;\n rdfs:label \"Execution artifact with id: 25f1016c12ebe301ee7aadbc0b085c45\" ;\n opmo:account <http://www.opmw.org/export/resource/WorkflowExecutionAccount/ACCOUNT1335533097598> ;\n opmv:wasGeneratedBy <http://www.opmw.org/export/resource/WorkflowExecutionProcess/p1> ;\n opmw:hasLocation \"http://wings.isi.edu/opmexport/resource/1/144/Formatted_SMN_2010_03_10Z\"^^xsd:anyURI ;\n opmw:hasSize \"8618\"^^xsd:int ;\n opmw:hasWorkflowTemplateArtifact <http://www.opmw.org/export/resource/DataVariable/AQUAFLOW_EDM_FORMATTEDDATA>.".
- WorkflowExecutionProcess comment "A workflow execution process represents the execution of a step in workflow template. The execution process also describes the specific method used to acomplish the task described in the proces template.\n\nExample:\n@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .\n@prefix opmw: <http://www.opmw.org/ontology/> .\n@prefix opmv: <http://purl.org/net/opmv/ns#> .\n@prefix opmo: <http://openprovenance.org/model/opmo#> .\n\n<http://www.opmw.org/export/resource/WorkflowExecutionProcess/CONVERTTOSTANDARDFORMAT133553>\n a opmw:/WorkflowExecutionProcess , opmv:Process ;\n rdfs:label \"Execution process ConvertToStandardFormat\" ;\n opmo:account <http://www.opmw.org/export/resource/WorkflowExecutionAccount/ACCOUNT1335533097598> ;\n opmv:used <http://www.opmw.org/export/resource/WorkflowExecutionArtifact/6C7CF277338D9590EE18534D4D78924F> ;\n opmv:wasControlledBy <http://www.opmw.org/export/resource/Agent/ADMIN> ;\n opmw:hasWorkflowTemplateProcess <http://www.opmw.org/export/resource/WorkflowTemplateProcess/AQUAFLOW_EDM_CONVERTTOSTANDARDFORMAT> .".
- WorkflowTemplate comment "A workflow template represents the design of the workflow. In such design, the different steps and inputs don't have to be bound to a specific tool or dataset. It is a generic view of the workflow, which is instantiated in each execution.\n \nExample:\n@prefix dc: <http://purl.org/dc/terms/> .\n@prefix opmw: <http://www.opmw.org/ontology/> .\n<http://www.opmw.org/export/resource/WorkflowTemplate/AQUAFLOW_NTM>\n a opmw:WorkflowTemplate;\n rdfs:label \"AquaFlow_NTM\" ;\n dc.contributor\n <http://www.opmw.org/export/resource/Agent/WATER> ;\n dc:modified\n \"2011-06-08T09:57:12-07:00\"^^xsd:dateTime ;\n opmw:hasVersion \"2\"^^xsd:int .".
- WorkflowTemplateArtifact comment "A workflow template artifact is part of a workflow template. It explains what kind of artifact is used or generated by the process template, along with possible restrictions that it may have.\n\nThere are two different types of workflow template artifacts: data variables and parameter variables.".
- WorkflowTemplateProcess comment "A workflow process template is an abstraction of the workflow execution process step that aims to describe the method followed by the scientist instead of its specific instantiation.\n\nExample:\n@prefix opmw: <http://www.opmw.org/ontology/> .\n@prefix water: <http://www.isi.edu/ac/Water/library.owl#> .\n\n<http://www.opmw.org/export/resource/WorkflowTemplateProcess/AQUAFLOW_NTM_CALCULATEHOURLYAVERAGES>\n a opmw:ProcessTemplate, water:CalculateHourlyAverages;\n opmw:template <http://www.opmw.org/export/resource/WorkflowTemplate/AQUAFLOW_NTM>;\n opmw:uses <http://www.opmw.org/export/resource/DataVariable/AQUAFLOW_NTM_FILTEREDDATA>.".
- Topography.owl comment "This ontology is still under construction".
- ItDepartment comment "A department in the organization that is responsible for the Information Technology (IT) of the organization.".
- ItSupportTask comment "A task is an action associated with tickets during an effort to solve an issue/problem in IT.".
- ItSupportTicket comment "Helpdesk support ticket to record some issue with IT to be diagnosed and resolved.".
- NARA comment "This individual is defined for demonstration purposes only and is linked to existing definitions in other LOGD sets".
- DataObject comment "A unit of data that is created, annotated and processed on the user desktop. It represents a native structure the user works with. The usage of the term 'native' is important. It means that a DataObject can be directly mapped to a data structure maintained by a native application. This may be a file, a set of files or a part of a file. The granularity depends on the user. This class is not intended to be instantiated by itself. Use more specific subclasses.".
- DataSource comment "A superclass for all entities from which DataObjects can be extracted. Each entity represents a native application or some other system that manages information that may be of interest to the user of the Semantic Desktop. Subclasses may include FileSystems, Mailboxes, Calendars, websites etc. The exact choice of subclasses and their properties is considered application-specific. Each data extraction application is supposed to provide it's own DataSource ontology. Such an ontology should contain supported data source types coupled with properties necessary for the application to gain access to the data sources. (paths, urls, passwords etc...)".
- InformationElement comment "A unit of content the user works with. This is a superclass for all interpretations of a DataObject.".
- Mode comment "Representation for a standard set of device/application/service modes, corresponding to various sets of modes that are either inbuilt in a device (e.g. inbuilt phone modes such as silent, loud, general, vibrate, etc.) or available for applications and online services (e.g. IM system modes such as busy, available, invisible, etc.)".
- byteSize comment "The overall size of the data object in bytes. That means the space taken by the DataObject in its container, and not the size of the content that is of interest to the user. For cases where the content size is different (e.g. in compressed files the content is larger, in messages the content excludes headings and is smaller) use more specific properties, not necessarily subproperties of this one.".
- comment comment "A user comment about an InformationElement.".
- contentModified comment "The date of a modification of the original content (not its corresponding DataObject or local copy). Compare with nie:modified.".
- created comment "Date of creation of the DataObject. Note that this date refers to the creation of the DataObject itself (i.e. the physical representation). Compare with nie:contentCreated.".
- description comment "A textual description of the resource. This property may be used for any metadata fields that provide some meta-information or comment about a resource in the form of a passage of text. This property is not to be confused with nie:plainTextContent. Use more specific subproperties wherever possible.".
- generator comment "Software used to \"generate\" the contents. E.g. a word processor name.".
- generatorOption comment "A common superproperty for all settings used by the generating software. This may include compression settings, algorithms, autosave, interlaced/non-interlaced etc. Note that this property has no range specified and therefore should not be used directly. Always use more specific properties.".
- hasLogicalPart comment "Generic property used to express 'logical' containment relationships between InformationElements. NIE extensions are encouraged to provide more specific subproperties of this one. It is advisable for actual instances of InformationElement to use those specific subproperties. Note the difference between 'physical' containment (hasPart) and logical containment (hasLogicalPart)".
- hasPart comment "Generic property used to express 'physical' containment relationships between DataObjects. NIE extensions are encouraged to provide more specific subproperties of this one. It is advisable for actual instances of DataObjects to use those specific subproperties. Note to the developers: Please be aware of the distinction between containment relation and provenance. The hasPart relation models physical containment, an InformationElement (a nmo:Message) can have a 'physical' part (an nfo:Attachment). Also, please note the difference between physical containment (hasPart) and logical containment (hasLogicalPart) the former has more strict meaning. They may occur independently of each other.".
- identifier comment "An unambiguous reference to the InformationElement within a given context. Recommended best practice is to identify the resource by means of a string conforming to a formal identification system.".
- informationElementDate comment "A point or period of time associated with an event in the lifecycle of an Information Element. A common superproperty for all date-related properties of InformationElements in the NIE Framework.".
- interpretedAs comment "Links the DataObject with the InformationElement it is interpreted as.".
- isLogicalPartOf comment "Generic property used to express 'logical' containment relationships between DataObjects. NIE extensions are encouraged to provide more specific subproperties of this one. It is advisable for actual instances of InformationElement to use those specific subproperties. Note the difference between 'physical' containment (isPartOf) and logical containment (isLogicalPartOf)".
- isPartOf comment "Generic property used to express containment relationships between DataObjects. NIE extensions are encouraged to provide more specific subproperties of this one. It is advisable for actual instances of DataObjects to use those specific subproperties. Note to the developers: Please be aware of the distinction between containment relation and provenance. The isPartOf relation models physical containment, a nie:DataObject (e.g. an nfo:Attachment) is a 'physical' part of an nie:InformationElement (a nmo:Message). Also, please note the difference between physical containment (isPartOf) and logical containment (isLogicalPartOf) the former has more strict meaning. They may occur independently of each other.".
- isStoredAs comment "Links the information element with the DataObject it is stored in.".
- lastModified comment "Last modification date of the DataObject. Note that this date refers to the modification of the DataObject itself (i.e. the physical representation). Compare with nie:contentLastModified.".
- legal comment "A common superproperty for all properties that point at legal information about an Information Element".
- links comment "A linking relation. A piece of content links/mentions a piece of data".
- modified comment "Date the DataObject was changed in any way. Note that this date refers to the modification of the DataObject itself (i.e. the physical representation). Compare with nie:contentModified.".
- relatedTo comment "A common superproperty for all relations between a piece of content and other pieces of data (which may be interpreted as other pieces of content).".
- title comment "Name given to an InformationElement".
- url comment "URL of a DataObject. It points to the location of the object. A typial usage is FileDataObject. In cases where creating a simple file:// or http:// URL for a file is difficult (e.g. for files inside compressed archives) the applications are encouraged to use conventions defined by Apache Commons VFS Project at http://jakarta.apache.org/ commons/ vfs/ filesystems.html.".
- Affiliation comment "Aggregates three properties defined in RFC2426. Originally all three were attached directly to a person. One person could have only one title and one role within one organization. This class is intended to lift this limitation.".
- AudioIMAccount comment "Deprecated in favour of nco:imCapabilityAudio.".
- BirthDate comment "A class representing a person contact's birth date information. Possesses various attributes.".
- Contact comment "A Contact. A piece of data that can provide means to identify or communicate with an entity.".
- ContactGroup comment "A group of Contacts. Could be used to express a group in an addressbook or on a contact list of an IM application. One contact can belong to many groups.".
- ContactList comment "A contact list, this class represents an addressbook or a contact list of an IM application. Contacts inside a contact list can belong to contact groups.".
