Matches in LOV for { ?s <http://www.w3.org/2000/01/rdf-schema#comment> ?o. }
- DataStructureDefinition comment "Defines the structure of a DataSet or slice".
- DimensionProperty comment "The class of components which represent the dimensions of the cube".
- HierarchicalCodeList comment "Represents a generalized hierarchy of concepts which can be used for coding. The hierarchy is defined by one or more roots together with a property which relates concepts in the hierarchy to thier child concept . The same concepts may be members of multiple hierarchies provided that different qb:parentChildProperty values are used for each hierarchy.".
- MeasureProperty comment "The class of components which represent the measured value of the phenomenon being observed".
- Observation comment "A single observation in the cube, may have one or more associated measured values".
- ObservationGroup comment "A, possibly arbitrary, group of observations.".
- Slice comment "Denotes a subset of a DataSet defined by fixing a subset of the dimensional values, component properties on the Slice".
- SliceKey comment "Denotes a subset of the component properties of a DataSet which are fixed in the corresponding slices".
- componentProperty comment "indicates a ComponentProperty (i.e. attribute/dimension) expected on a DataSet, or a dimension fixed in a SliceKey".
- observation comment "indicates a observation contained within this slice of the data set".
- observationGroup comment "Indicates a group of observations. The domain of this property is left open so that a group may be attached to different resources and need not be restricted to a single DataSet".
- structure comment "indicates the structure to which this data set conforms".
- sdmx comment "This vocabulary extends the data cube vocabulary to support publication of statistical data in RDF, using an information model based on SDMX".
- Concept comment "Denotes an SDMX concept, used in the particular SDMX terminological sense, which is in principle narrower than skos:Concept".
- ConceptRole comment "Abstract superclass of classes denoting statistical roles which be played by concepts".
- DataStructureDefinition comment "A specialization of qb:DataStructureDefinition which additional constraints: if there are multiple measures then a MeasureDimensionProperty must be included in the DSD".
- MeasureTypeRole comment "concept for a dimension that plays the role of identifying a type of measure".
- measureTypeConcept comment "The concept corresponding to the generic measure type dimension which indicates which measure is being denoted by the primary measure on an observation".
- Area comment ": This code list provides code values for geographical areas, defined as areas included within the borders of a country, region, group of countries, etc.".
- ConfStatus comment "this code list provides coded information about the sensitivity and confidentiality status of the data.".
- Currency comment "This code list provides code values for currencies.".
- Decimals comment "It provides a list of values showing the number of decimal digits used in the data.".
- Freq comment "It provides a list of values indicating the \"frequency\" of the data (e.g. monthly) and, thus, indirectly, also implying the type of \"time reference\" that could be used for identifying the data with respect time.".
- ObsStatus comment "This code list provides coded information about the \"status\" of an observation (with respect events such as the ones reflected in the codes composing the code list).".
- Sex comment "This code list provides the gender.".
- TimeFormat comment "These codes (based on the ISO 8601 standard) indicate the type of time references used in the data. The numeric codes below (203, 102,...,702) are used only in the SDMX-EDI messages; and the alphanumeric codes (P1D...PT1M) only in the SDMX-ML messages.".
- UnitMult comment "it provides code values for indicating the magnitude in the units of measurements.".
- academia comment "This is used to identify which predicates are related to academia (other than education) so they can be listed separately in the documentation.".
- core comment "This is used to identify which predicates represent a simple core of Linking You".
- education comment "This is used to identify which predicates are related to education so they can be listed separately in the documentation.".
- extended comment "Predicates only useful to UK organisations".
- extended comment "This is used to identify which predicates are outside the the core terms. Still useful but listed in a second section.".
- Tag comment "A Tag consists of an arbitrary text label. Note that tags with the same label are NOT merged in the ontology.".
- Tagging comment "A tagging links a resource to a user account and one or more tags.".
- grantAccess comment "A (usually private) tagging can be linked to one or more user accounts or user groups that should have access to it (apart from the creator). This property can also be used in public tagging to link a user account or user group to a tagging (e.g. if the creator of a tagging wants to suggest the tagging to another user).".
- hasCreator comment "Every tagging is linked to at most one user account. This property can be omitted for automatic taggings. In contrast to its superproperty sioc:has_creator, it is functional and with an explicit domain. Use sioc:member_of to define groups for group tagging or link to foaf:Agent, foaf:Person, or foaf:Group via sioc:account_of.".
- hasTag comment "A tagging consists of a (theoretically unlimited) number of tags. A tagging may also consist of no tags, e.g. if the system allows its users to mark a resource first and add tags later.".
- nextTag comment "This property indicates the tag that follows next in the list of tags. It can be used to describe the order in which the tags have been entered by the user.".
- tagMeaning comment "The meaning of a tag can be expressed by a link to a well-defined resource. This can be any resource that clarifies the meaning of the tag (e.g. some DBpedia resource).".
- taggedResource comment "Every tagging is linked to exactly one resource. This can be any kind of resource (i.e. all subclasses of rdfs:Resource), including tags and taggings.".
- lio comment "A Lightweight Ontology for Describing Images (LIO)".
- lio comment "Authored by Margaret Warren and Pat Hayes for Metadata Authoring Systems, LLC, Metadata Authoring Technologies, LLC and ImageSnippets(tm) 2010".
- Image comment "An image. Any PictorialElement that is considered to be a complete image. Typically the main subject of an ImageSnippets description will be in this class. An image can be a visualPartOf another image.".
- PictorialElement comment "Any visual entity; any graphical item, part, or visual property of an image or part of an image, including the image itself. Examples include lines, areas, colors and textures. Pictorial elements may have arbitrarily complex shapes and may be implicit, e.g. lines of perspective or outlined white spaces. Rectangular regions of an image are pictorial elements, and the entire image is also. Thus, Image is a subclass of PictorialElement. PictorialElements may be included in one another, giving a simple mereology of visual forms, with the property visualPartOf. Non-visual properties such as date or manner of creation are not considered to be PictorialElements. A property or aspect of an image can be considered to be a PictorialElment when it can be apprehended by vision alone.".
- hasVisualPart comment "The inverse of the part-of relation on visual elements.".
- shows comment "Anything in the scene depicted by an image, and which is visible in the image. Meant to include incidental depictions as well as any main subjects. For example, a tree in the background of a portrait, or a person in the crowd at a parade. Images may show many things that the images are not a picture of.".
- bibtex comment "Possible ontology to describe bibTeX entries.".
- Article comment "An article from a journal or magazine.".
- Book comment "A book with an explicit publisher.".
- Entry comment "Base class for all entries".
- Inbook comment "A part of a book, which may be a chapter (or section or whatever) and/or a range of pages.".
- Inproceedings comment "An article in a conference proceedings.".
- Mastersthesis comment "A Master's thesis.".
- Phdthesis comment "A PhD thesis.".
- Proceedings comment "The proceedings of a conference.".
- hasAuthor comment "The name(s) of the author(s), in the format described in the LaTeX book.".
- hasBooktitle comment "Title of a book, part of which is being cited. See the LaTeX book for how to type titles. For book entries, use the title field instead.".
- hasISBN comment "The International Standard Book Number.".
- hasInstitution comment "The sponsoring institution of a technical report.".
- hasJournal comment "A journal name. Abbreviations are provided for many journals; see the Local Guide".
- hasMonth comment "The month in which the work was published or, for an unpublished work, in which it was written. You should use the standard three-letter abbreviation, as described in Appendix B.1.3 of the LaTeX book.".
- hasNote comment "Any additional information that can help the reader. The first word should be capitalized.".
- hasNumber comment "The number of a journal, magazine, technical report, or of a work in a series. An issue of a journal or magazine is usually identified by its volume and number; the organization that issues a technical report usually gives it a number; and sometimes books are given numbers in a named series.".
- hasPages comment "One or more page numbers or range of numbers, such as 42-111 or 7,41,73-97 or 43+ (the `+' in this last example indicates pages following that don't form a simple range). To make it easier to maintain Scribe-compatible databases, the standard styles convert a single dash (as in 7-33) to the double dash used in TeX to denote number ranges (as in 7-33).".
- hasPublisher comment "The publisher's name.".
- hasSchool comment "The name of the school where a thesis was written.".
- hasTitle comment "The work's title, typed as explained in the LaTeX book.".
- hasYear comment "The year of publication or, for an unpublished work, the year it was written. Generally it should consist of four numerals, such as 1984, although the standard styles can handle any year whose last four nonpunctuation characters are numerals, such as '(about 1984)'.".
- humanCreator comment "A generic human creator category, necessary in order to contain both author and editor.".
- pageChapterData comment "A generic property to hold page and/or chapter data.".
- ex comment "Vocabulary to include sample codes in a schema. Can work with XSLT (http://purl.org/net/ns/ns-schema.xsl) to present schema as XHTML list with examples.".
- ex comment "スキーマにサンプルコードを埋め込むための語彙。XSLTを使って、XHTMLの中で例を表示させることができる。".
- Example comment "A class represents one example.".
- Example comment "ひとつの例を表すクラス".
- ontology-annot comment "Vocabulary to define some annotation properties as subproperties of common terms. Because owl:Ontology resource cannot have properties other than annotation, these terms are defined as owl:AnnotationProperty type in dliser.rdf that is to be imported. However, some RDF application might want those properties to be related to well known terms such as Dublin Core. Hence this vocabulary redefines these properties as ordinary RDF/OWL terms and subProperty of others.".
- ontology-annot comment "オントロジーのアノテーションに用いるプロパティを、汎用プロパティと関連付けるための回避策としての語彙".
- Agent comment "Agent is a contextual entity acting as a catalyst of a process, enabling, facilitating, controlling, or affecting its execution.".
- Artifact comment "Artifact is a general concept that represents immutable piece of state, which may have a physical embodiment in a physical object, or a digital representation in a computer system.".
- Process comment "Process refers to an action or series of actions performed on or caused by artifacts, and resulting in new artifacts.".
- used comment "used is an abstract property to express that an artifact was used by a process.".
- wasControlledBy comment "wasControlledBy is an abstract property to express that a process was controlled an agent.".
- wasDerivedFrom comment "wasDerivedFrom is an abstract property to express that an artifact was derived from another artifact.".
- wasGeneratedAt comment "\n wasGeneratedAt is an object property to express that an artifact was generated at a specific time <a xmlns=\"http://www.w3.org/1999/xhtml\" href=\"http://www.w3.org/2006/time#Instant\" xml:lang=\"en\">instant</a>. This property is very similar to <a xmlns=\"http://www.w3.org/1999/xhtml\" href=\"http://purl.org/dc/terms/created\" xml:lang=\"en\">dct:created</a>. Note that in a very fine-grained case the time when an artifact was generated might not be the same as the time when the process producing that artifact finished.\n ".
- wasGeneratedBy comment "wasGeneratedBy is an abstract property to express that an artifact was generated by a process.".
- wasTriggeredBy comment "wasTriggeredBy is an abstract property to express that a process was triggered by another process.".
- p-plan comment "PROV extension for linking Plans and parts of plans to their respective executions. Created by Daniel Garijo and Yolanda Gil".
- Activity comment "A p-plan:Activity represents the execution process planned in a p-plan:Step".
- Playlist comment "A class for representing a playlist. One Playlist instance is connected to one or more PlaylistEntry instances. It contains the name of the playlist and the name of the radio station.".
- PlaylistEntry comment "A class for representing an entry from a playlist. One PlaylistEntry instance is connected to one Song instance and one Playlist instance. It contains information about the 'position' of the Song in the Playlist, for the specific 'week' of the 'year'. It also contains an URL of a 'photo' for the playlist entry.".
- Song comment "A class for representing a song. One Song instance is connected to one or more PlaylistEntry instances. It contains the name of the song and the name of the artist. It can also contain external links to mo:Track and/or mo:MusicArtist instances, for creating Linked Data.".
- CreationGuideline comment "CreationGuideline is a concept that represents a guideline used to guide the execution of a data creation. Examples for creation guidelines are transformation rules, mapping definitions, entailment rules, and database queries.".
- DataAccess comment "DataAccess is a concept that represents the completed execution of an activity by which an immutable data item has been retrieved from the Web.".
- DataCreation comment "DataCreation is a concept that represents the execution of an activity by which data items have been created.".
- DataItem comment "DataItem is a general concept that represents data items of any kind.".
- DataProvidingService comment "DataProvidingService is a concept that represents a non-human agent - usually a Web service or a server - that processes data access requests and actually sends the requested Web representations over the Web.".
- DataPublisher comment "DataPublisher is a concept that represents entities such as persons, groups, or organizations who use a data providing service (see concept prv:DataProvidingService) to publish data on the Web.".
- File comment "File is a general class that represents computer files/documents of any kind.".
- HumanAgent comment "HumanAgent is a general class that represents agents who are social beings such as persons, organizations, companies.".
- Immutable comment "Immutable is a concept that represents entities which are immutable.".
- NonHumanAgent comment "NonHumanAgent is a general class that represents agents who are not social beings.".