Matches in LOV for { ?s <http://www.w3.org/2000/01/rdf-schema#comment> ?o. }
- Supplier comment "An agent who supplies something, such as goods or services.".
- appliesFor comment "An object property linking an agent to something for which that agent applies, for example a job, membership of an organization, or a grant from a funding agency.".
- awards comment "An object property linking an agent to something the agent awards, for example linking a funding agency to a grant, a university to a degree, or an organization to a prize.".
- donates comment "An object property linking a benefactor to a gift.".
- employs comment "An object property relating an employing agent to an employed agent, for example a person or an organization, who is typically employed to undertaking specified work in exchange for payment.".
- enables comment "An object property relating an entity to another entity that it enables, e.g. linking a project to an endeavour that the project enables.".
- evaluates comment "An object property linking an agent to an entity which that agent evaluates, for example a funding agency that is evaluating a grant application to determine whether the proposed project is worthy of funding, or a publisher evaluating a manuscript to determine whether it is suitable for publication.".
- hasAgentInformation comment "A data property linking an agent to information about that agent.".
- hasCode comment "A data property defining a code.".
- hasFundingAgency comment "An object property linking something to a funding agency that provides funding for it.".
- hasIPROwner comment "An object property linking an entity such as a project, an endeavour or an output to an agent who owns the IPR arising from or related to that entity.".
- hasNameSuffix comment "The letters that should be displayed after a person's name.".
- hasOrganizationalInformation comment "It describes information about the organization.".
- hasOutput comment "An object property linking an activity such as a project or endeavour to something that is created or produced as a result of that activity. Examples include a building created as a result of a building project, and a journal article published to describe the results of a research investigation.".
- hasPersonalIdentifier comment "A unique and unambiguous identifier for an individual person within a given context.".
- hasPersonalInformation comment "A data property linking a person to information about that person.".
- initial comment "A data property permitting specification of the initial(s) of a person's name.".
- isFundedBy comment "An object property linking something to the funding that funds it (i.e. that finances or pays for it), or to the funding agency providing that funding. This flexibility is given because of alternative usages of the English word 'funds'. [See also frapo:isAwardedBy and frapo:hasFundingAgency and frapo:isSupportedBy.]".
- isOwnedBy comment "An object property linking an entity to the agent that owns it.".
- isPurchasedBy comment "An object property relating a purchased entity to its purchaser.".
- isSupportedBy comment "An object property linking something to an agent that provides funding or other support for it.".
- manufactures comment "An object property relating a manufacturer to a manufactured entity.".
- owns comment "An object property linking an agent to an entity owned by that agent.".
- purchasesFrom comment "An object property relating a purchaser to a supplier from whom the purchase is made.".
- submits comment "An object property linking an agent to an entity that is submitted to some third party, for example a grant application submitted to a funding agency, a manuscript submitted to a publisher, a quotation submitted by a vendor, or a dataset submitted by a researcher to a data repository.".
- supplies comment "An object property relating a supplier to a supplied entity, or to an agent to whom the entity is supplied.".
- supports comment "An object property linking an agent to something that the agent supports by financial or other means.".
- CatalogueOrIndex comment "A catalogue for, or index of, a collection.".
- CDType comment "A set of types of collection description.".
- Bag comment "Collection that can have a number of copies of each object".
- Collection comment "A group of objects that can be considered as a whole.".
- Item comment "Element belonging to a bag".
- List comment "An ordered array of items, that can be present in multiple copies".
- ListItem comment "element belonging to a list".
- Set comment "A collection that cannot contain duplicate elements.".
- element comment "The link to the members of a collection".
- elementOf comment "The link to a collection in which the object is member.".
- firstItem comment "The link to the first item of the list.".
- followedBy comment "The link to the following item in a list.".
- index comment "A number identifying the position, starting from 1, of a particular list item within a list.".
- item comment "The link to every item of the bag".
- itemContent comment "The link to the actual resource to which the item refers.".
- itemOf comment "The link to a bag in which the item is member.".
- lastItem comment "The link to the last item of the list.".
- nextItem comment "The link to the next item in a list.".
- precededBy comment "The link to the preceding item in a list.".
- previousItem comment "The link to the previous item in a list.".
- size comment "The number of item belonging to a collection.".
- configurationontology comment "Ontology for the description of customizable products. It models the configuration process as the traversal of a graph of partially defined products, or \"Configurations\".\n\nRanges of customizable products are described rather effectively, for human users, by means of dedicated web applications called configurators. A configurator helps a user interactively define a product step by step, each step typically describing a valid partially defined product (or \"Configuration\"), with a start price and a list of remaining choices given all previous selections. Each of these choices links to another configuration until completion. Thus, the configuration process traverses a graph whose nodes are configurations. Now identify each configuration with a URI returning the list of the configurations it is linked to, among other relevant information: what you have is a description of the range as Linked Data.\n\nThe main classes of this ontology are Configuration (a state of the configuration process), Specification (a possible value of a characteristic of the configured product) and ConfigurationLink (which models a change of the state of the configuration process).".
- Configuration comment "A state of the configuration process, assumed to correspond to a valid partially defined product - valid in the sense that it can be completed into an existing fully specified product, one that can be ordered, without changing any of the current selections.\n\nA configuration is defined by a Lexicon (the set of the descriptive attributes of the configured product, cf. the \"lexicon\" property), and by the set of choices that have been made so far (typically selected specifications), cf. the \"definingChoice\" property.\n\nNote: A configurator application may conceivably have to handle “invalid configurations”, that is, combinations of specifications that are impossible. This can happen, for instance, if the user is allowed to begin the configuration process by choosing features without any control of their compatibility; or if she is allowed to choose a feature incompatible with her previous selections. In this case, it is the responsibility of the configurator application to restore the consistency of the configuration, necessarily by excluding some of the previous user selections. This Configuration class excludes such invalid combinations. \n\nRelation with GoodRelations and schema.org vocabularies :\nbecause a configuration mainly describes a Partially Defined Product, it can be seen as a GoodRelations \"ProductOrServiceModel\" (or a schema.org \"ProductModel): \"an intangible entity that specifies some characteristics of a group of similar, usually mass-produced products, in the sense of a prototype\". The suffix \"Model\" may seem misleading when used for a Configuration, as it suggests something such as \"Ford T\", and not \"Ford T with sunroof and climat control (itself not a completely defined product - you still can choose, well, the color: it is a \"prototype of similar products\").\n\nOn the other hand, a Configuration has a price (more precisely, a \"from price\" - the minimum of the \"suggested retail prices\" of all the matching completely defined products). As such, a Configuration may be seen as a commercial offer. It can also be used to represent a customer's wish list, constrained by the definition of the range. It could therefore be considered as a gr:Offering (or a schema:Offer) as well.\n\nBut gr:ProductOrService and gr:Offering are disjoint classes: a given Configuration cannot be both. Depending on the use case, a publisher of configuration data may want to type her Configurations with either of these classes.".
- ConfigurationLink comment "Models the link between a given Configuration and another one (a change of state in the configuration process): typically, the association of a Specification to be selected, and of a resulting Configuration.".
- ConfigurationVariable comment "A variable in a Lexicon, eg. the fuel type, or the body color. Automotive ranges typically only use discrete variables: the possible values corresponding to one ConfigurationVariable are alternative specifications (for instance \"Diesel\", \"Gasoline\", etc. for the fuel type variable)".
- Lexicon comment "The set of specifications (and of their corresponding configuration variables) used in the configuration process: all the possible descriptive attributes of the configured product.".
- Specification comment "Feature, option, any value of a characteristic of a product that can be chosen during the configuration process. For instance: \"Automatic gearbox\", \"Blue body color\", \"CO2 emission value < 100 g of CO2\"".
- completed comment "Links a Configuration to a completely defined one (that is, a Completely Defined Configuration that matches the configuration in question). The price of the linked configuration may be higher than this configuration price. Configurations completed at the same price are given by the completedAtSamePrice property.".
- definingChoice comment "Parent to all properties specifying the choices that define the Configuration: a Configuration is defined by the list of triples it is the subject of, and which have a co:definingChoice as their predicates. ".
- lexicon comment "Used to link a Configuration, a ConfigurationVariable or a Specification to a Lexicon.".
- link comment "Parent property of all the properties linking a Configuration to another one in the configuration process.\nThe HTML display of a cold:ConfigurationLink corresponds to an hypertext link, whose href is the value of the cold:linkedConf property. As for the text of this link, the rdfs:label of the cold:specToBeAdded value is quite adequate. It can be directly included in the RDF as the rdfs:label of the cold: ConfigurationLink".
- linkedConf comment "the linked configuration that contains choices of current Configuration plus the specifications that will be added and listed in the configuration link it belongs to.".
- ns comment "COO: The Car Options Ontology\n \nThe COO provides a vocabulary for exposing available configuration options for car models. It allows indicating choices that can be made as well as compatibility, dependency, and inclusion information. \n\nThe ontology imports and extends the GoodRelations ontology for e-commerce, which provides an abstract framework for product model information via gr:ProductOrServiceModel and ist associated properies.\n\nThe main difference between COO and the default patterns for model data in GoodRelations is that GoodRelations requires the materialization of all choices for features, which can quickly lead to very large amounts of data if features can be combines rather freely, due to the combinatorial effects.\n\nVocabulary: http://purl.org/coo/ns\nNamespace: http://purl.org/coo/ns#\n\nThe Car Options Ontology is designed to be used in combination with GoodRelations, a standard vocabulary for the commercial aspects of offers for sale or rental, and the Vehicle Sales Ontology.\n\nSee http://purl.org/goodrelations/ and http://purl.org/vso/ns for more information.".
- BaseModel comment "A Base Model is an abstract entity specifying the basic features of a group of vehicles.\n\nExamples: VW Golf, VW Polo, VW Passat".
- ChoiceOrComponent comment "A Choice or Component is a component (e.g. engine), add-on, feature (color \"ocean blue\"), or service that can be chosen to be part of a final vehicle configuration.\n\t\nExample: Engine 1.6 l TDI, color ocean blue, trailer hitch".
- CompleteCarModel comment "A Complete Car Model is an abstract entity specifying all features and configuration choices needed for actually producing a vehicle. In other words, it is the gr:ProductOrServiceModel (\"datasheet\") for a completely configured vehicle.\nWhile a Complete Car Model can be defined indepently of a Base Model, Trim, or Derivative, it is usually based on a Derivative plus choices for all mandatory configurational options (coo:SpecItemCollection) of that Derivative.\nA Complete Car Model should be linked to its Derivative via gr:isVariantOf, if available.\n\nExample: VW Golf S 1.6 TDI 3door Manual in ocean blue with air-conditioning, CD player, trailer hitch, power steering, and power windows\n\nNote: A coo:CompleteCarModel is NOT an actual car, but a complete feature description of one or multiple actual cars.".
- ConfigurationInfo comment "A Configuration Info is an abstract entity that gives information on whether a set of Choices Or Components results in a valid configuration. \nUsing coo:compatible, it is possible to indicate either compatibility (true) and incompatibility (false) so that modeling remains efficient, no matter whether most combinations are valid or whether most configurations are invalid.\nIf no such statement is found, the validity of a configuration is unknown.\n\nNote: The two properties coo:includes and coo:dependsOn, attached to coo:ChoiceOrComponent, may contain additional information on the validity of configuration.".
- Derivative comment "A Derivative is an abstract entity specifying (1) the basic features plus (2) a set of functional (e.g. engine type) and non-functional configuration (e.g. upholstery) choices of a group of vehicles.\nA Derivative has often a number of remaining configuration choices (coo:SpecItemCollection attached via coo:hasSpecItems), which will determine the actual properties of the resulting vehicle.\t\t \nA Derivative should be linked to its Trim via gr:isVariantOf, if available.\n\nExamples: VW Golf S 1.6 TDI 3door Manual".
- PropertySpecification comment "A Property Specification is an abstract entity specifying a set of properties for a vehicle that results from a single choice or the combination of two or more choices and that override the individual properties of the resulting vehicle.\n\nExample 1: Power steering and Air conditioning in combination reduce the available engine power from 90 kW to 89 kW.\nExample 2: Choosing the color option \"blue\" changes the color of the car to \"blue\".".
- RelativePriceSpecification comment "A shortcut for indicating the effect of a choice or set of choices on the unit price. Use positive values for a surcharge and negative values for a deduction.\n\nNote: Price information should in general be attached to a gr:Offering node, not to a Base Model, Trim, Derivative, or Complete Car Model. Use this shortcut with care.".
- SpecItemCollection comment "A Spec Item Collection is an entity collating multiple coo:ChoiceOrComponent options for a given coo:Derivative, i.e. the available configurational choices. \nThe default choice can be indicated using a coo:default link. All other choices are attached using coo:availableChoice. The number of coo:ChoiceOrComponent items that can / must be selected for a valid configuration are indicated via coo:min and coo:max.".
- Trim comment "A Trim is an abstract entity specifying (1) the basic features plus (2) a set of configuration choices (mostly non-functional) of a group of vehicles. \nA Trim should be linked to its Base Model via gr:isVariantOf, if available.\n\nExamples: VW Golf S, VW Polo Match, VW Passat SE".
- availableChoice comment "This property links available Choices or Components to a Spec Item.".
- dcat comment "Este vocabulario se utiliza para modelar los catálogos de conjuntos de datos y las relaciones con los datasets".
- dcat comment "This vocabulary is used for modelling catalogs of datasets and its relationships with the datasets".
- Catalog comment "Catalog which have defined datasets in".
- Catalog comment "Catálogo donde se expresan conjuntos de datos".
- Dataset comment "A dataset".
- Dataset comment "Un conjunto de datos".
- accessModeScheme comment "Concept scheme of the different access modes to the information distributions".
- accessModeScheme comment "Taxonomía de los tipos de acceso a las distribuciones de la información".
- statusScheme comment "Concept scheme of the different statuses for a catalog".
- statusScheme comment "Esquema de conceptos de los estados que puede tomar un catálogo".
- oferta comment "El objetivo de este vocabulario es la creación de un esquema que permita definir los contenidos de la información relacionada con la oferta de empleo público. \n\t\t\tSe identifican ciertas variables en el dominio de la oferta de empleo público, que se modelan a través de ciertos tipos de datos y de propiedades relacionadas entre los recursos.".
- AnuncioOferta comment "Un anuncio de una oferta de empleo".
- OfertaEmpleo comment "Una oferta de empleo es un documento que describe los detalles de uno o más trabajos que deben ser cubiertos. Nótese que no es lo mismo un trabajo, que una oferta de trabajo.".
- PlantillaPersonal comment "La plantilla de personal es un grupo de personas contratadas bajo unas condiciones o estatutos similares".
- esquemaCategorias comment "Esquema de conceptos de las diferentes categorías y subcategorías que puede tener una oferta de empleo".
- esquemaTiposContrato comment "Esquema de conceptos de los tipos de contrato que puede tener una oferta de empleo".
- requisito comment "Requisitos generales necesarios y/o deseados para acceder al puesto de trabajo".
- localizacion comment "Este vocabulario se utiliza para modelar las localizaciones físicas de lugares públicos. \n\t\t\tUtiliza elementos de Geonames para identificar las distintas características geográficas.".
- Barrio comment "Cada una de las partes en que se dividen los distritos de los municipios".
- Calle comment "Vía urbana".
- Direccion comment "Dirección postal".
- JuntaAdministrativa comment "Junta administrativa que rige los intereses de un pueblo que, en unión con otros, forma un municipio".
- TramoCalle comment "Tramo parcial o total de una vía pública".
- organizacion comment "El objetivo de este vocabulario es la creación de un esquema que permita definir los contenidos de la información relacionada con los órganos de gobierno y los centros públicos que ofrecen servicios.\nSe identifican ciertas variables en el dominio de los centros públicos, que se modelan a través de ciertos tipos de datos y de propiedades relacionadas entre los recursos. \nSe utiliza Ontologies for e-Government para modelar las principales características.".
- CentroServicios comment "Centro que ofrece servicios públicos".
- Edificio comment "Un edificio donde se encuentra ubicado el centro de servicios".
- OrganoPublico comment "Órgano del que depende".
- elecciones comment "El objetivo de este vocabulario es la creación de un esquema que permita definir los contenidos de información relacionada con procesos electorales y sus resultados. \n\t\t\tSe identifican ciertas variables en el dominio de las elecciones, que se modelan a través de ciertos tipos de datos y de propiedades relacionadas entre los recursos.".
- AreaElectoral comment "Una región o área geográfica donde se lleva a cabo una votación".
- Candidato comment "Candidato de una formación política que se presenta a una votación".