Matches in LOV for { ?s <http://www.w3.org/2000/01/rdf-schema#comment> ?o. }
- needs comment "The property linking a workflow step to anything required to undertake that step.".
- produces comment "The property linking a workflow step to the thing that the step produces, creates or results in.".
- scoro comment "SCoRO is written in OWL 2 DL, and imports FOAF, the Friend of a Friend Ontology (http://xmlns.com/foaf/spec/) and PRO the Publishing Roles Ontology (http://purl.org/spar/pro/). This ontology is available at http://purl.org/spar/scoro/, and uses the namespace prefix 'scoro'.\n\nIt is designed to be used in conjunction with FRAPO, the Funding, Research Administration and Projects Ontology (http://purl.org/spar/frapo/), and with FaBiO, the FRBR-aligned Bibliographic Ontology (http://purl.org/spar/fabio/).\n\nA Web-based scholarly contributions report form based on this ontology, for use in creating metadata to describe authorship roles and scholarly contributions to journal articles and their underlying research, is available from http://purl.org/spar/scoro/**** (to be created).\n\nAlternatively, an Excel Scholarly Contributions Report Form based on this ontology, created using RightField (http://www.sysmo-db.org/rightfield) also for use in creating metadata to describe authorship roles and scholarly contributions to journal articles and their underlying research, is available from http://purl.org/spar/scoro/SCoRF.xls.".
- AuthorshipContribution comment "Defines the type or nature of a contribution made with respect to the authorship of a publication such as a journal article. Individual members of this class are used to specify particular authorship contributions.".
- AuthorshipRole comment "A role that a person might hold as an author of a publication or the creator of a work. Individual members of this class are used to specify particular roles.".
- Contribution comment "Defines the type or nature of a contribution made by an agent. Individual members of this class or its sub-classes are used to specify particular contributions.".
- ContributionEffort comment "Defines the effort expended in making a contribution.".
- ContributionSituation comment "The situation an agent has of making a contribution to realizing a goal or completing a task relating to a scholarly activity or entity such as journal article. The type or nature of the contribution is defined by the object of the object property scoro:withContribution, which is an individual in the class scoro:Contribution or one of its sub-classes. The entity to which the contribution relates is specified using the object property scoro:relatesToEntity or one of its sub-properties, and the effort expended in making that contribution is specified using the object property scoro:withContributionEffort.".
- DataRole comment "A role that an agent might hold with respect to data. Individual members of this class are used to specify particular roles.".
- EducationalRole comment "A role that an agent might hold with respect to an educational organization or activity. Individual members of this class are used to specify particular educational roles.".
- ExperimentalContribution comment "Defines the type or nature of a practical or experimental contribution made to the research. Individual members of this class are used to specify particular contributions.".
- FinancialRole comment "A role that an agent might hold with respect to academic and project finance. Individual members of this class are used to specify particular roles.".
- IntellectualContribution comment "Defines the type or nature of an intellectual contribution made to the research described in a journal article. Individual members of this class are used to specify particular contributions.".
- InvestigationRole comment "A role that an agent might hold with respect to an investigation. Individual members of this class are used to specify particular roles.".
- OrganizationalContribution comment "Defines the type or nature of an organizational or administrative contribution. Individual members of this class are used to specify particular contributions.".
- OrganizationalRole comment "A role that an agent might hold with respect to an organization and its administration, particularly within an academic context. Individual members of this class are used to specify particular roles.".
- ProjectRole comment "A role that an agent might hold with respect to a project. Individual members of this class are used to specify particular roles.".
- article-guarantor comment "The role of a person who takes responsibility for the integrity of the work as a whole, from the inception of the research investigation to the published research article.".
- hasContributionContext comment "A property relating a contribution situation to an entity representing the context for that situation.".
- hasPersonalIdentifier comment "A data property specifying a unique and unambiguous identifier for an individual person within a given context, specified by the object property scoro:usesPersonalIdentifierScheme and an individual member of the class scoro:PersonalIdentifierScheme.".
- makesContribution comment "An object property linking an agent to a contribution. This is done via the indirection: foaf:Agent scoro:makesContribution [ a scoro:ContributionSituation ; scoro:withContribution scoro:Contribution ; scoro:withEffort scoro:ContributionEffort ] . The ontology permits one to specify the time period over which a contribution is made, and the other contextual entities to which that agent's contribution relates.".
- withContribution comment "An object property connecting an agent's contribution situation to a definition of the contribution made by this agent, specified as an instance of the class scoro:Contribution or of one of its sub-classes.".
- Comment comment "A comment on a review".
- Feedback comment "Feedback on the review. Expresses whether the review was useful or not".
- Review comment "A review of an work".
- maxRating comment "A numeric value".
- minRating comment "A numeric value".
- discourse-relationships comment "These relationships don't have range and domains defined as they are meant to be reused in different contexts".
- refersTo comment "It connects an entity with another entity in an \n\t\t\t\tunidirectional way".
- relatesTo comment "The most generic relationship: it expresses connection \n\t\t\tbetween two resources without specifying the nature of such connection".
- respondsTo comment "".
- theatre comment "A vocabulary for theatrical data. It defines concepts such as shows, productions, seasons etc.".
- AccessibilityProvision comment "A Provision which makes an ev:Event more accessible".
- Portrayal comment "A Position which involes portraying a Character.".
- Position comment "A set of responibilities.".
- Production comment "The realisation of a theatrical work.".
- ProductionCompany comment "An Organisation which puts on Productions.".
- Season comment "A collection of Productions and/or Performances".
- Venue comment "A Nestable Spatial Thing used for Theatrical Events.".
- Voice comment "The voice classification for a Singer or singing part.".
- credit comment "Associates a Project with a Role.".
- event comment "Associates a Project with an Event.".
- performance comment "Associates a Production with a Performance.".
- performance_of comment "Associates a Production with a Performance.".
- premiere comment "Indicates the first performance of a Show or Production in a particular area.".
- project comment "Associates a Role with a Project.".
- ns comment "TIO: The TIckets Ontology\n \nA vocabulary for describing tickets for events, transportation, or points of interest for e-commerce.\n\nVocabulary: http://purl.org/tio/ns#\nNamespace: http://purl.org/tio/ns#\n\nThe Tickets Ontology is designed to be used in combination with GoodRelations, a standard vocabulary for the commercial aspects of offers of tickets.\n\nSee http://purl.org/goodrelations/ for more information.".
- ActualTicket comment "An actual ticket is single, identifiable right to access a particular event, location, or transportation service.".
- BusinessClass comment "Business class as a service level / fare class for transportation by aircraft\n\nNote: The exact character of a particular fare class may vary by carrier or country. \nYou can create individual instances of tio:ServiceLevel for a particular fare class for a particular airline.".
- CoachService comment "A regular or individual service to transport passengers or cargo from one location to another location by means of a coach or bus.".
- DiscountType comment "The class of qualitative values indicating a discount type, audience, or group type - e.g. students, military personnel, etc.\n\nNote: Discount types that solely represent age ranges (e.g. children, senior citizens, ...) are better expressed using tio:ageRange.".
- Economy comment "Economy class as a service level / fare class for transportation by aircraft\n\nNote: The exact character of a particular fare class may vary by carrier or country. \nYou can create individual instances of tio:ServiceLevel for a particular fare class for a particular airline.".
- Event comment "An event, e.g. a concert, a show, etc. You can also safely use the following external classes for describing the respective event:\n\nhttp://linkedevents.org/ontology/Event (lode:Event)\nhttp://purl.org/NET/c4dm/event.owl#Event (event:Event)\nhttp://www.loa-cnr.it/ontologies/DUL.owl#Event (dul:Event)\n\nNote: You can attach the time and date of the event using tio:starts and tio:ends as simple datatype properties, even if lode:Event and event:Event recommend other, more sophisticated ways of modeling the temporal aspects of events.".
- Flight comment "A regular or individual service to transport passengers or cargo from one location to another location by means of an aircraft\n\nNote: By design, the Tickets Ontology does not provide mechanisms for modeling rules for recurring patterns of transportation services (e.g. every Monday at 8:00). Instead, it expects that you materialize each individual connection on a given day.\nMost flight schedule applications are complex databases, so they will have to be exposed as SPARQL endpoints anyway.".
- POI comment "A point or area of interest, e.g. a museum, a train station, an airport, a bus stop, a store, a box office, etc.\n\nNote 1: Use existing vocabularies like vcard or geo to attach address and geoposition (lat/long) details to the location.\nNote 2: You can safely re-use any existing location, area, or point of interest from other data sources, e.g. DBPedia.".
- ScopeOfAccess comment "This is a conceptual entity that collates all properties defining the type of access a ticket provides to a particular event, location, or transportation.".
- SeatOrSeatCategory comment "The class of qualitative values indicating a seat position (e.g. the seat 4B in a given plane) or a seat category (e.g. window seat). \n Note that the same vessel or building may have multiple seating layouts.".
- SeatingLayout comment "A seating layout for a particular location, vessel, or single transportation service".
- ServiceLevel comment "The class of qualitative values indicating a service level oder fare class (e.g. Business Class).".
- Stop comment "The initial, final, or any intermediate point in time and space of a particular tio:TransportationService, \ncharacterized by its location (tio:at), arrival time (tio:arrives), and departure time (tio:departs). \nEach tio:TransportationService has at least one tio:Stop for the point and time of departure and another one for the final destination.".
- Taxi comment "A taxi service to transport passengers from one location to another location".
- Ticket comment "A ticket is a tradeable right to access a particular event or location, or to use a particular transportation service.".
- TicketPlaceholder comment "A ticket placeholder is a dummy for multiple tickets that are themselves not exposed as data.".
- TrainService comment "A regular or individual service to transport passengers or cargo from one location to another location by means of a train, subway, or other railroad vehicle\n\nNote: By design, the Tickets Ontology does not provide mechanisms for modeling rules for recurring patterns of transportation services (e.g. every Monday at 8:00). Instead, it expects that you materialize each individual connection on a given day.\nMost train schedule applications are complex databases, so they will have to be exposed as SPARQL endpoints anyway.".
- TransportationService comment "A service to transport passengers or cargo from one location to another location, with optionally intermediate stops\n\nNote: By design, the Tickets Ontology does not provide mechanisms for modeling rules for recurring patterns of transportation services (e.g. every Monday at 8:00). Instead, it expects that you materialize each individual connection on a given day.\nMost timetable applications are complex databases, so they will have to be exposed as SPARQL endpoints anyway.".
- Quality comment "The conceputal representation of anything that is a property (a thing that is inherent in an entity, like eye color) or an attribute (a thing that has been assigned, or attributed, to an entity, like name or identification number).".
- Relation comment "A concept representing the relationship between two independent entities.".
- Type comment "An abstract or general idea inferred or derived from specific instances, representing a set of those instances.".
- Universal comment "Entities that describe the objects, processes, qualities, states, \netc. in reality (for example on the side of the patient); (from http://ontology.buffalo.edu/bfo/Terminology_for_Ontologies.pdf)".
- hasQuality comment "A conceptual type can have qualities that describe it.".
- representedBy comment "Things in the real world can be represented by concepts. This is a link between the concepts and the things those concepts represent. Things, including sets of things, are represented by concepts.".
- represents comment "Things in the real world can be represented by concepts. This is a link from the concepts and the things those concepts represent. Concepts represent things.".
- cdm.owl comment "".
- conceptual_depth comment "A measure of how universal/accepted/popular a URI is.".
- conversion comment "This ontology is used by the csv2rdf4lod project.".
- AbstractDataset comment "Dataset with source and dataset identifiers, but not version. Before any version is materialized (captured in time), and the union of all VersionedDatasets.".
- Dataset comment "Asserted by the converter.".
- DatasetSample comment "A potentially incomplete subset of a void:Dataset".
- DatatypePromotionEnhancement comment "Promotes the raw literal value to a datatyped literal using the datatype specified with the conversion:range property.".
- DatePromotionEnhancement comment "Casts raw literal values into W3CDTF values typed as xsd:date based on a strftime pattern specified with the conversion:date_pattern. If the property values follow different patterns, multiple conversion:date_pattern values may specified.".
- DatePromotionEnhancement comment "For each value, all DateTimePromotionEnhancement patterns are attempted before attempting any DatePromotionEnhancement patterns specified for the same property.".
- DateTimePromotionEnhancement comment "Casts raw literal values into W3CDTF values typed as xsd:dateTime based on a strftime pattern specified with the conversion:datetime_pattern. If the property values follow different patterns, multiple conversion:datetime_pattern values may specified. The first matching pattern (of a nondeterministic ordering) will be applied. An optional conversion:datetime_timezone may be specified if no timezone information is present in the datetime pattern.".
- DirectSameAsEnhancement comment "For any Resource that became owl:sameAs another Resource in an external LOD bubble, use ALL external URIs instead of the local resource.".
- ImplicitBundle comment "Represents the structural template for an implicit bundle enhancement. The conversion:property_name specifies the property name by which a bundle is attached to an instance. An optional conversion:type_name may be specified for the bundle to indicate the rdf:type of the new resource.".
- ImplicitBundleEnhancement comment "Reasserts the property-value pair to belong to a new resource specified by the conversion:bundled_by property. An example of this enhancement would be the introduction of a geo:Point instance based on latitude and longitude properties.".
- IndirectSameAsEnhancement comment "Refer to a local URI, which then has a single owl:sameAs triple pointing to external LOD bubbles. Depends on owl:sameAs inference OR extra graph patterns in SPARQL queries.".
- LODLinks comment "An RDF Graph of resources with identifiers (dcterms:identifer, etc) that is used to link to resources created during conversion.".
- LabelRenameEnhancement comment "Renames an existing property in the dataset.".
- LayerDataset comment "A conversion of a VersionedDataset using a particular set of conversion parameters.".
- MetaDataset comment "Data about another Dataset. Can contain VoID, PML, OPM, provenance, Dublin Core, etc.".
- MultiplierEnhancement comment "After datatype promotion to an XSD numeric type, multiplies the value by the multiplicand specified with the conversion:multiplier property.".
- ObjectEnhancement comment "An Enhancement that modifies the object of the resulting triple.".
- ObjectEnhancement comment "Superclass of enhancements which promote values from a plain literal to more complex terms (resources or typed literals).".
- ObjectSameAsEnhancement comment "Asserts owl:sameAs relationships between resources and external URIs based on the instances' values of a specific property and their interpretation by a mapping specified by conversion:linksVia. How this mapping is performed based on this value is unspecified, but may be based on aligning with (e.g. SKOS) labels or the edit distance between the property value and instances in a known ontology.".
- PredicateEnhancement comment "An Enhancement that modifies the predicate of the resulting triple.".
- PropertyCommentEnhancement comment "Uses the object of the conversion:comment property and asserts it as the value of rdfs:comment on the property definition. The value of conversion:comment typically comes from the original csv header (that was too long), or from an ancillary file accompanying the csv file.".
- ResourcePromotionEnhancement comment "Superclass of enhancements which promote values from a plain literal to a resource.".
- SameAsDataset comment "".
- ServiceEndpoint comment "http://www.w3.org/TR/sparql11-service-description/ does not specify a range, but we want to refer to it".
- Source comment "A person, organization, or agent from which a dataset is retrieved.".