Matches in LOV for { ?s <http://www.w3.org/2000/01/rdf-schema#comment> ?o. }
- oclcnum comment "OCLC Identifier".
- pageEnd comment "Ending page number within a continuous page range.".
- pageStart comment "Starting page number within a continuous page range.".
- pages comment "A string of non-contiguous page spans that locate a Document within a Collection. Example: 23-25, 34, 54-56. For continuous page ranges, use the pageStart and pageEnd properties.".
- presentedAt comment "Relates a document to an event; for example, a paper to a conference.".
- presents comment "Relates an event to associated documents; for example, conference to a paper.".
- reproducedIn comment "The resource in which another resource is reproduced.".
- subsequentLegalDecision comment "A legal decision on appeal that takes action on a case (affirming it, reversing it, etc.).".
- translationOf comment "Relates a translated document to the original document.".
- volume comment "A volume number".
- CharacteristicDynamics comment "An event concept for describing dynamics of characteristics, e.g. weight changes, periods of interest.".
- CognitiveCharacteristic comment "A cognitive characteristic object, which also can have weightings and characteristic dynamics etc. for describing a cognitive pattern.".
- attention_duration comment "An interval of attention for a cognitive pattern.".
- cognitive_characteristic comment "This is the super property to describe cognitive characteristics of the user of the cognitive pattern dimension, e.g. interests, skills, or expertise.".
- competence comment "The competence to (be able to) do or know something. That means abilities, skills, knowledge, expertise, beliefs etc.".
- habit comment "A link between an agent and a cognitive characteristic description".
- topic comment "A topic of the cognitive characteristic.".
- Chord comment "Two or more notes played together.".
- ChordEvent comment "A chord being played.".
- Interval comment "An interval above the root of a chord.".
- Modifier comment "A modifier applied to a note to change its pitch.".
- Natural comment "One of the seven natural notes of the Western music system.".
- Note comment "FIXME".
- ScaleInterval comment "An interval in the root scale, made up of the degree of the scale and optional modifier.".
- SemitoneInterval comment "A semitone interval.".
- Counter comment "Counter of a given object/ given objects, which are related to that counter.".
- ScrobbleEvent comment "An event corresponding to a scrobbling (counting an activity, which includes at least a specific factor and \na specific agent), e.g. a track being played by someone, a video watched by someone, a book read by \nsomeone, a sporting activity by someone, ...".
- count comment "Links a counter resource to the actual count".
- counter comment "Links an object to a counter resource. Please feel free to create further sub properties with more restricted domains.".
- event_counter comment "Links events to a counter resource, where they where counted in.".
- object comment "Links a counter resource to an object. Please feel free to create further sub properties with more restricted ranges.".
- scrobble_object comment "A scrobble object of a scrobble event, e.g. a music track, a video or a described activity. That means a specific thing that is involved in this scrobbling action.".
- Limitation comment "A Limitation is something that limits the the availability of an Item.".
- Response comment "A Respone contains information about document availability for a specific time and institution.".
- Service comment "A Service is something that is provided by an Institution, typically related to an Item, for instance the service of loaning the Item.".
- availableFor comment "Relates an Item to a Service which the Item is available for. This property is disjoint with the unavailable property; however an Item can be available and unavailable for two different Services of the same class at the same time.".
- broaderExemplar comment "Relates a Document to an Item that contains an exemplar of the Document as part.".
- broaderExemplar comment "Relates an Item to a Document which is partly exemplified by the Item.".
- collectedBy comment "Relates a Document to an Institution which helds an iten of the Document.".
- exemplar comment "Relates a Document to an Item that is an exemplar of the Document. This property is similar to frbr:exemplar but does not refer to the class frbr:Manifestation.".
- exemplarOf comment "Relates an Item to the Document that is exemplified by the Item.".
- heldBy comment "Relates an Item to an Institution that holds the Item.".
- holds comment "Relates an Institution to an Item which the Institution holds.".
- inCollection comment "Relates an Institution to a Document which the Institution helds an item of.".
- limits comment "Relates a Limitation to a Service.".
- narrowerExemplar comment "Relates a Document to an Item that is an exemplar of a part of the Document.".
- narrowerExemplar comment "Relates an Item to a Document which is partly exemplified by the Item.".
- providedBy comment "Relates a Service to an Institution that provides the Service.".
- provides comment "Relates an Institution to a Service that is provided by the Institution.".
- unavailableFor comment "Relates an Item to a Service which the Item is not available for. This property is disjoint with the available property; however an Item can be available and unavailable for two different Services of the same class at the same time.".
- dvia comment "dvia is an RDF vocabulary designed to facilitate interoperability between visualization applications published on the Web.".
- Application comment "The aplication or the mashup developed for demo-ing or consuming data in LD fashion".
- Platform comment "The platform where to host or use the application, could be on the web (firefox, chrome, IE, etc..) or mobile (android, etc..) or event desktop".
- VisualTool comment "The tool or library used to build the application".
- platform comment "This property links the application to a platform to actually use the application.".
- InfoService comment "Extended definition:\n\n\t\"An Information Service is this part of an Information System that serves data/knowledge/information to customers and collects it \n\tfrom its contributors, to manage and store it by optionally using administrators.\"\n\nPlease refer also this article[1] about the definition of the term 'Information Service'.\n\nThis concept is for linking a piece of information of a specific concept instance (or at least website links or other data representations \nof this concept instance), e.g. a foaf:Agent, a mo:Track or a mo:MusicArtist to a related website of a specific information service (modelled \nas individual of is:InfoService), e.g. Wikipedia, MySpace, MusicBrainz, Discogs, Last.fm, Pandora, BBC, ... . With this concept it is possible \nto describe the underlying information services of that knowledge representation more in detail, so that the client, which consumes that \n'linked data' could choose, which source it likes to use by evaluating the description of the information service of that website link or \nother data representation.\nPlease use for further is:InfoService instances the namespace \"http://purl.org/ontology/is/inst/\".\n\n\n[1] https://infoserviceonto.wordpress.com/2010/06/23/what-is-an-information-service/".
- InfoServiceContributorType comment "This concept is for describing the different contributor types of information services, e.g. expert, \ncommunity or mixed. Please feel free to define further information service contributor types.\nPlease use therefore the namespace \"http://purl.org/ontology/is/ctypes/\".".
- InfoServiceQuality comment "This concept is for describing specific quality levels or ratings, e.g. good or bad or more detailed ones, of \ninformation services. Please feel free to use this concept as hook for more complex and detailed information service quality description \nmodellings in sub ontologies. Please use therefore the domain \"http://purl.org/ontology/is/quality/\". Futhermore, such information \nservice ratings could be done by different information service rating agencies, so that the customer of such ratings could select \nits information service ratings agency of choice.".
- InfoServiceType comment "This concept is for describing the type of an information service, e.g. 'social network service', \n'recommender service' or 'encyclopedia'. Please feel free to define further information service types for categorization.\nPlease use therefore the namespace \"http://purl.org/ontology/is/types/\".".
- Activity comment "\n An activity period, defining when an artist was musically active.\n ".
- AnalogSignal comment "\n An analog signal.\n ".
- Arrangement comment "\n An arrangement event.\n Takes as agent the arranger, and produces a score (informational object, not the actually published score).\n ".
- AudioFile comment "An audio file, which may be available on a local file system or through http, ftp, etc.".
- Composition comment "\n A composition event.\n Takes as agent the composer himself.\n It produces a MusicalWork, or a MusicalExpression (when the initial \"product\" is a score, for example), or both...\n ".
- CorporateBody comment "Organization or group of individuals and/or other organizations involved in the music market.".
- DigitalSignal comment "\n A digital signal\n ".
- Genre comment "\n An expressive style of music.\n \n Any taxonomy can be plug-in here. You can either define a genre by yourself, like this:\n\n :mygenre a mo:Genre; dc:title \"electro rock\".\n\n Or you can refer to a DBPedia genre (such as http://dbpedia.org/resource/Baroque_music), allowing semantic web\n clients to access easily really detailed structured information about the genre you are refering to.\n ".
- Instrument comment "\n Any of various devices or contrivances that can be used to produce musical tones or sound.\n \n Any taxonomy can be used to subsume this concept. The default one is one extracted by Ivan Herman\n from the Musicbrainz instrument taxonomy, conforming to SKOS. This concept holds a seeAlso link \n towards this taxonomy.\n ".
- Label comment "Trade name of a company that produces musical works or expression of musical works.".
- Lyrics comment "\n Lyrics\n ".
- Medium comment "A means or instrumentality for storing or communicating musical manifestation.".
- Membership comment "A membership event, where one or several people belongs to a group during a particular time period.".
- Movement comment "A movement is a self-contained part of a musical work. While individual or selected movements from a composition are sometimes performed separately, a performance of the complete work requires all the movements to be performed in succession.\n\nOften a composer attempts to interrelate the movements thematically, or sometimes in more subtle ways, in order that the individual\nmovements exert a cumulative effect. In some forms, composers sometimes link the movements, or ask for them to be played without a\npause between them.\n ".
- MusicArtist comment "\n A person or a group of people (or a computer :-) ), whose musical \n creative work shows sensitivity and imagination \n ".
- MusicGroup comment "Group of musicians, or musical ensemble, usually popular or folk, playing parts of or improvising off of a musical arrangement. ".
- MusicalExpression comment "\nThe intellectual or artistic realization of a work in the form of alpha-numeric, musical, or choreographic notation, sound, etc., or any combination of such forms. \n\n\nFor example:\n\nWork #1 Franz Schubert's Trout quintet\n\n * Expression #1 the composer's score\n * Expression #2 sound issued from the performance by the Amadeus Quartet and Hephzibah Menuhin on piano\n * Expression #3 sound issued from the performance by the Cleveland Quartet and Yo-Yo Ma on the cello\n * . . . . \n\nThe Music Ontology defines the following sub-concepts of a MusicalExpression, which should be used instead of MusicalExpression itself: Score (the\nresult of an arrangement), Sound (produced during a performance), Signal. However, it is possible to stick to FRBR and bypass the worflow\nmechanism this ontology defines by using the core FRBR properties on such objects. But it is often better to use events to interconnect such \nexpressions (allowing to go deeply into the production process - `this performer was playing this particular instrument at that\nparticular time').\n \n ".
- MusicalItem comment "A single exemplar of a musical expression.\n \nFor example, it could be a single exemplar of a CD. This is normally an single object (a CD) possessed by somebody.\n\nFrom the FRBR final report: The entity defined as item is a concrete entity. It is in many instances a single physical object (e.g., a copy of a one-volume monograph, a single audio cassette, etc.). There are instances, however, where the entity defined as item comprises more than one physical object (e.g., a monograph issued as two separately bound volumes, a recording issued on three separate compact discs, etc.).\n\nIn terms of intellectual content and physical form, an item exemplifying a manifestation is normally the same as the manifestation itself. However, variations may occur from one item to another, even when the items exemplify the same manifestation, where those variations are the result of actions external to the intent of the producer of the manifestation (e.g., damage occurring after the item was produced, binding performed by a library, etc.). \n ".
- MusicalManifestation comment "\n\nThis entity is related to the edition/production/publication of a musical expression (musical manifestation are closely related with the music industry (their terms, concepts, definitions, methods (production, publication, etc.), etc.)\n \nFrom the FRBR final report: The entity defined as manifestation encompasses a wide range of materials, including manuscripts, books, periodicals, maps, posters, sound recordings, films, video recordings, CD-ROMs, multimedia kits, etc. As an entity, manifestation represents all the physical objects that bear the same characteristics, in respect to both intellectual content and physical form.\n\n\nWork #1 J. S. Bach's Six suites for unaccompanied cello\n\n * Expression #1 sound issued during the performance by Janos Starker recorded in 1963 and 1965\n o Manifestation #1 recordings released on 33 1/3 rpm sound discs in 1965 by Mercury\n o Manifestation #2 recordings re-released on compact disc in 1991 by Mercury \n * Expression #2 sound issued during the performances by Yo-Yo Ma recorded in 1983\n o Manifestation #1 recordings released on 33 1/3 rpm sound discs in 1983 by CBS Records\n o Manifestation #2 recordings re-released on compact disc in 1992 by CBS Records \n\n \nChanges that occur deliberately or even inadvertently in the production process that affect the copies result, strictly speaking, in a new manifestation. A manifestation resulting from such a change may be identified as a particular \"state\" or \"issue\" of the publication.\n\nChanges that occur to an individual copy after the production process is complete (e.g., the loss of a page, rebinding, etc.) are not considered to result in a new manifestation. That copy is simply considered to be an exemplar (or item) of the manifestation that deviates from the copy as produced.\n\nWith the entity defined as manifestation we can describe the physical characteristics of a set of items and the characteristics associated with the production and distribution of that set of items that may be important factors in enabling users to choose a manifestation appropriate to their physical needs and constraints, and to identify and acquire a copy of that manifestation.\n\nDefining manifestation as an entity also enables us to draw relationships between specific manifestations of a work. We can use the relationships between manifestations to identify, for example, the specific publication that was used to create a microreproduction. \n\n".
- MusicalWork comment "\n Distinct intellectual or artistic musical creation.\n \nFrom the FRBR final report: A work is an abstract entity; there is no single material object one can point to as the work. We recognize the work through individual realizations or expressions of the work, but the work itself exists only in the commonality of\ncontent between and among the various expressions of the work. When we speak of Homer's Iliad as a work, our point of reference is not a particular recitation or text of the work, but the intellectual creation that lies behind all the various expressions of the work. \n\nFor example:\n\nwork #1 J. S. Bach's The art of the fugue\n\n \n ".
- Performance comment "\n A performance event. \n It might include as agents performers, engineers, conductors, or even listeners.\n It might include as factors a score, a MusicalWork, musical instruments. \n It might produce a sound:-)\n ".
- PublishedLibretto comment "A published libretto".
- PublishedLyrics comment "Published lyrics, as a book or as a text file, for example".
- PublishedScore comment "A published score (subclass of MusicalManifestation)".
- Record comment "A published record (manifestation which first aim is to render the product of a recording)".
- Recording comment "\n A recording event.\n Takes a sound as a factor to produce a signal (analog or digital).\n The location of such events (if any) is the actual location of the corresponding\n microphone or the \"recording device\".\n ".
- RecordingSession comment "A set of performances/recordings/mastering events. This event can be decomposed in its constituent events using event:sub_event".
- Release comment "A specific release, with barcode, box, liner notes, cover art, and a number of records".
- ReleaseEvent comment "A release event, in a particular place (e.g. a country) at a particular time. Other factors of this event might include cover art, liner notes, box, etc. or a release grouping all these.".
- ReleaseStatus comment "Musical manifestation release status.".
- ReleaseType comment "\n Release type of a particular manifestation, such as \"album\" or \"interview\"...\n ".
- Score comment "\n Here, we are dealing with the informational object (the MusicalExpression), not the actually \"published\" score.\n This may be, for example, the product of an arrangement process.\n ".
- Signal comment "\n A subclass of MusicalExpression, representing a signal, for example a master signal produced by a performance and a recording.\n ".
- SignalGroup comment "\n A musical expression representing a group of signals, for example a set of masters resulting from a whole recording/mastering session.\n ".
- Sound comment "\n A subclass of MusicalExpression, representing a sound. Realisation of a MusicalWork during a musical Performance.\n ".
- Track comment "A track on a particular record".
- arranged_in comment "\n Associates a work to an arrangement event where it was arranged\n ".
- arrangement_of comment "\n Associates an arrangement event to a work\n ".
- available_as comment "\n Relates a musical manifestation to a musical item (this album, and my particular cd). By using\n this property, there is no assumption on wether the full content is available on the linked item.\n To be explicit about this, you can use a sub-property, such as mo:item (the full manifestation\n is available on that item) or mo:preview (only a part of the manifestation is available on\n that item).\n\n This is a subproperty of frbr:examplar.\n ".
- compiled comment "Used to relate an person or a group of person who compiled the manifestation of a musical work.".
- compiler comment "Used to relate the manifestation of a musical work to a person or a group of person who compiled it.".