LOV |

LOV

Matches in LOV for { ?s <http://www.w3.org/2000/01/rdf-schema#comment> ?o. }

Showing items 801 to 900 of ±25,039 with 100 items per page.

first
previous
next

PostcodeUnit comment "An area covered by a particular postcode. Postcodes are an alphanumeric abbreviated form of address. Postcode units are unique references and identify an average of 15 addresses. In some cases, where an address receives a substantial amount of mail, a postcode will apply to only one address (a large-user postcode). The maximum number of addresses in a postcode is 100.\n\nA sub-area of a postcode sector, indicated by the two letters of the inward postcode, which identifies one or more small-user postcode delivery points or an individual large-user postcode. There are approximately 1.7 million postcode units in the UK.".
nhsHA comment "English Strategic Health Authority or Scottish Health Board in which Code-Point Open location coordinate falls.".
nhsRegionalHA comment "English Pan Strategic Health Authority in which Code-Point Open location coordinate falls.".
positionalQualityIndicator comment "Indicates the source of the data indicator used and, hence, the quality of the\ncoordinates provided for each record. It is determined by the best available\ndata in ADDRESS-POINT.".
10 comment "Within the building of the matched address closest to the postcode mean determined automatically by Ordnance Survey.".
20 comment "As above, but determined by visual inspection by NRS.".
30 comment "Approximate to within 50 m of true position (postcodes relating to developing sites may be within 100 m of true position).".
40 comment "The mean of the positions of addresses previously matched in ADDRESS-POINT but that have subsequently been deleted or recoded (very rarely used).".
50 comment "Estimated position based on surrounding postcode coordinates, usually to 100m resolution, but 10 m in Scotland.".
60 comment "Postcode sector mean (direct copy from ADDRESS-POINT).".
90 comment "No coordinates available.".
contains comment "The interior of one object completely contains the interior of the other. Their boundaries may or may not intersect.".
disjoint comment "The boundaries and interiors of the two objects do not intersect, i.e. they have no points in common.".
equals comment "The two objects have the same boundary and the same interior.".
partiallyOverlaps comment "The boundaries and interiors of the two objects intersect.".
touches comment "The boundaries of the two objects intersect but their interiors do not.".
within comment "The interior of one object is completely within the interior of the other object. Their boundaries may or may not intersect.".
asset comment "The Asset Ontology describes news assets (text, images, video, data, etc), the relationships between them and how assets can be classified and semantically annotated.".
Asset comment "Generic News Asset Class".
Image comment "Image Asset Class".
Text comment "Text Asset Class".
Video comment "Video Asset Class".
associatedAsset comment "Property that associates one asset with another asset".
classification comment "The Classification Ontology allows assets to be holistically classified using a controlled vocabulary or taxonomy.".
Classifiable comment "Generic Classifiable Class - inheriting from this makes the descendant Classifiable by a Classification".
Classification comment "Generic Classification Class. Vocabulary instances would be of this type.".
subClassificationOf comment "Transitive property that allows classifications to be related to parent classifications".
event comment "The Event Ontology models news-worthy events and their relationship to news assets and stuff (simple entities) in the world.".
Event comment "Generic Event Class, a subclass of event:Event. The Event class also subclasses pnt:Stuff as it is a Compound domain entity, this inheritance means news assets can be tagged with Events".
identifier comment "The Identifier Ontology models non-RDF based Identifiers for resources. The enables us to maintain a mapping between RDF resources identifiers and their equivalent IDs in an alternate, non-RDF based domain.".
Authority comment "The Authority for an Identifier, for example the domain or namespace within which an ID is contained".
Identifiable comment "An instance that is Identifiable can have an Identifier associated with it.".
Identifier comment "An ID for a given resource. For example a literal ID from a legacy system".
stuff comment "The Stuff Ontology models real world entities. There are two kinds of stuff: tangibles and intangibles. Tangible stuff includes persons, locations and organizations. Intangibles are abstract concepts such as smoking, feminism or love.".
Intangible comment "A base class for all intangible stuff (eg love, conservatism, fashion)".
Location comment "A Location - a base class for Locations. Also a subclass of geo:SpatialThing".
Person comment "A Person - a base class for people instances. Also a subclass of foaf:Person".
Stuff comment "Generic Stuff Class - a base class for all domain stuff".
Tangible comment "A base class for all tangible stuff (eg people, places, physical things)".
comment comment "String property that indicates the definitive description of a Stuff instance.".
hasAsset comment "Property that associates assets directly with domain entities, e.g. official biography, corporate logo".
label comment "String property that indicates the definitive label of a Stuff instance. This might be the full name of a Person, Organization or something Intangible".
notablyAssociatedWith comment "Property that notably associates stuff together, for example Karl Lagerfeld is notably associated with Fashion".
tag comment "The Tag Ontology defines relationships for semantically annotating taggable things (for example news assets) with domain entities (stuff) and events.".
Tag comment "Generic Tag Class - Taggables are tagged with a Tag".
Taggable comment "Generic Taggable Class - Taggable things can be tagged".
isTaggedWith comment "Property that associates Tags with Taggables: Taggable X isTaggedWith Tag Y".
01_introduction comment "\n\t\t\t\n\t\t\t\tThe Semantic Web Conference ontology (SWC) is an ontology for describing academic conferences. \n\t\t\t\tIt was initially designed to support the European Semantic Web Conference,\n\t\t\t\tESWC2007, and later extended for both the following conferences in the ESWC series,\n\t\t\t\tas well as in the ISWC series.\n\t\t\t\tHistorically, the SWC ontology also draws heavily on ontologies developed for\n\t\t\t\tESWC2006 and ISWC2006.\n\t\t\t\n\t\t\t\n\t\t\t\tSWC is mainly a convention of how to use classes and properties from other ontologies, most prominently \n\t\t\t\t<a href=\"http://xmlns.com/foaf/0.1\">FOAF</a> (for people) and <a href=\"http://ontoware.org/projects/swrc/\">SWRC</a> \n\t\t\t\t(their BibTeX elements, for the papers). We are also throwing in some <a href=\"http://sioc-project.org/\">SIOC</a>, \n\t\t\t\t<a href=\"http://dublincore.org/documents/dc-rdf/index.shtml\">Dublin Core</a> and \n\t\t\t\t<a href=\"http://www.w3.org/TR/rdfcal/\">iCal/RDF Calendar</a>. Our own \n\t\t\t\t<a href=\"http://data.semanticweb.org/ns/swc/ontology\">swc namespace</a> provides the glue for all this, as well as \n\t\t\t\tspecialised classes for things that have to do with conferences.\n\t\t\t\n\t\t\t\n\t\t\t\tThis version of SWC has been slimmed down significantly (hence the revision name). A total of 59 classes and 19 properties have been deprecated (deprecated terms can be found at the bottom of this document). This was mostly done with the intention to remove the countless sub-classes of generic classes such as <a href=\"#Chair\">Chair</a> or <a href=\"#SessionEvent\">SessionEvent</a>, which were deemed to be too specific for a general-purpose conference ontology such as SWC. Elsewhere, classes and properties which had never been used and seemed to fall under the heading of \"over-engineering\" were removed. Finally, all CfP related terms were removed. Instead, we suggest to use a dedicated ontology such as the <a href=\"http://sw.deri.org/2005/08/conf/cfp\">CfP ontology</a>.\n\t\t\t\n\t\t\t\n\t\t".
02_describing_papers comment "\n\t\t\tFor the basic use case of describing papers, the figure below shows how the main kinds of resources are connected: the paper itself, the authors and their affiliations, and the talk where the paper was presented.\n\t\t\t\n\t\t\t<div align=\"center\">\n\t\t\t\t<a href=\"documentation/20070921-ISWC+ASWC2007PublicationGraph.pdf\"><img src=\"documentation/20070921-ISWC+ASWC2007PublicationGraph.png\" /></a>\n\t\t\t</div>\n\t\t\t\n\t\t\t\tThe next figure shows in more detail the kinds of things that can be said about each of the four main entities surrounding a paper.\n\t\t\t\n\t\t\t<div align=\"center\">\n\t\t\t\t<a href=\"documentation/20071002-Properties.pdf\"><img src=\"documentation/20071002-Properties.png\" /></a>\n\t\t\t</div>\n\t\t\t\n\t\t".
03_roles comment "\n\t\t\t\n\t\t\t\tOne of the basic design choices in SWC is to use role modelling for describing the different functions at a conference, such as chairs, reviewers, etc. For any particular role at a given conference, the <code>swc:Role</code> class or a sub-class will be instantiated. This role instance stands in relation to a person (who plays the role) and an event. The figure below gives an example showing how to model the role of the metadata chair (or \"dog food tsar\") at ISWC+ASWC2007, which was held by Knud Möller (together with Tom Heath, not shown in the figure).\n\t\t\t\n\t\t\t\n\t\t\t\tNote that the metadata chair role is not modelled with its own dedicated class (although it could have been). Instead, an instance of the generic <a href=\"#Chair\">Chair</a> class is used and labelled accordingly.\n\t\t\t\n\t\t\t<div align=\"center\">\n\t\t\t\t<a href=\"documentation/20090510-Roles_new.pdf\"><img src=\"documentation/20090510-Roles_new.png\" /></a>\n\t\t\t</div>\n\t\t\t\n\t\t".
AcademicEvent comment "\n\t\t\t\n\t\t\tAcademic events are e.g. conferences and conference-like events, and all the sub-events of those which are about the topic or theme of the conference, such as talks or panels.\n\t\t\t\n\t\t".
ArgumentativeDocument comment "\n\t\t\tAn argumentative document is a document which uses analytical reasoning and evidence in order to argue for a point of view. Typical examples are scientific papers or political pamphlets. Negative examples are novels or plays (even though a novel might also try to sway the reader to a certain point of view).\n\t\t\tAccording to <a href=\"http://en.wikipedia.org/wiki/Text_types\">Text Types</a>, an argumentative document is based \"on the evaluation and the subsequent subjective judgement in answer to a problem. It refers to the reasons advanced for or against a matter\".\n\t\t\t\n\t\t".
Artefact comment "\n\t\t\t<emph>Artefact</emph> here means a document which can have a physical manifestation, like a paper or the proceedings of a conference.\n\t\t\t\n\t\t".
BreakEvent comment "\n\t\t\t\n\t\t\t\n\t\t\t\tAny kind of break at the super-event, such as a coffee break.\n\t\t\t\n\t\t\t\n\t\t".
Call comment "\n\t\t\tThe call classes have been deprecated in SWC. Instead, we suggest to use the <a href=\"http://sw.deri.org/2005/08/conf/cfp\">CfP ontology</a>.\n\t\t\tA <emph>call</emph> is a public announcement, asking for contribution of some kind to events such as conferences or workshops, or to a publication such as a journal or book.\n\t\t\t\n\t\t".
MealEvent comment "\n\t\t\t\n\t\t\t\n\t\t\t\tA lunch, dinner or similar event at a conference or conference-like event.\n\t\t\t\n\t\t\t\n\t\t".
NonAcademicEvent comment "\n\t\t\t\n\t\t\t\n\t\t\t\tIn the context of SWC, a non-academic event is any kind or <a href=\"#OrganisedEvent\">organised event</a> which does not concern the topic or theme of the conference as such. Examples are breaks, dinners, parties, etc.\n\t\t\t\n\t\t\t\n\t\t".
OrganisedEvent comment "\n\t\t\t\n\t\t\tAn event in time and space which is planned and organised, as opposed to something which 'just happens', such as a car accident or sunset.\n\t\t\t\n\t\t".
Paper comment "\n\t\t\tA scientific/scholarly paper, e.g., an article in a scientific journal, or a paper at a conference or workshop. A paper could also be unpublished formally, as long as it has the form of a scientific paper (introduction, conclusion, related work, etc.).\n\t\t\t\n\t\t".
Place comment "\n\t\t\t\n\t\t\t\n\t\t\t\tDeprecated: no real need to have an internal super-class for locations, we can just use the <a href=\"&geo;SpatialThing\">SpatialThing</a>.\n\t\t\t\n\t\t\t\n\t\t".
Proceedings comment "\n\t\t\tThe proceedings of a conference or workshop, which contain the papers presented there.\n\t\t\t\n\t\t".
Programme comment "\n\t\t\tA document containing the programme of an event such as a conference or workshop. Typically, the programme would list the times and dates for the individual sub-events, e.g., talks, dinners, panel discussions, etc.\n\t\t\t\n\t\t".
Role comment "\n\t\t\t\n\t\t\t\tRole is the super-class of all the different roles performed at a conference or workshop. Examples are the various conference chairs, the delegates, presenters, PC members, etc. The intended use of this class is that an instance of Role will be related to the event at which it is performed, and to the person which performs it.\n\t\t\t\n\t\t\t\n\t\t\t\tSince the set of roles is slightly different for each event, and since it would therefore be impossible to provide sub-classes for all needs and circumstances, the SWC ontology only contains a very basic set of Role classes. Rather than diversifying the set of Role classes to cater for all needs, users should instead instantiate the small set of different Role classes and cover the roles at a specific event in this way. E.g., instead of sub-classing the Chair role with MainChair, WorkshopChair, TutorialChair, etc., the different kinds of chairs should simply be instances of the generic Chair class and be labelled appropriately.\n\t\t\t\n\t\t\t\n\t\t".
SessionEvent comment "\n\t\t\t\n\t\t\t\n\t\t\t\tA session dedicated to a specific topic at a conference. This could be a session with talks, or also a poster session, a demo session, or any other kind of session.\n\t\t\t\n\t\t\t\n\t\t".
SocialEvent comment "\n\t\t\t\n\t\t\t\n\t\t\t\tExamples for social events are parties or excursions.\n\t\t\t\n\t\t\t\n\t\t".
Sponsorship comment "\n\t\t\tDeprecated because it has never been used and in order to reduce the inflation of ontology terms.\n\t\t\t\n\t\t".
TalkEvent comment "\n\t\t\t\n\t\t\t\n\t\t\t\tA speaker giving a talk. This could be the presentation of a paper, but also keynote speech or any other kind of talk.\n\t\t\t\n\t\t\t\n\t\t".
TrackEvent comment "\n\t\t\t\n\t\t\t\n\t\t\t\tA track groups all those sessions or events at a conference or workshop that belong to a common, overall theme. Depending on the conference, tracks can be quite generic, such as \"Research\" or \"Industrial\", but can also be more specific, such as \"Semantic Web\" or \"Numismatics\". SWC does not define any specific tracks, since conferences often differ so much with respect to how they structure their tracks, that it would be pointless to try and find a set of tracks that would suit all conferences.\n\t\t\t\n\t\t\tSub-classes of TrackEvent which were defined in previous versions of the SWC ontology are now deprecated.\n\t\t\t\n\t\t".
attendeeAt comment "\n\t\t\tInstead of this property, use the <a href=\"#Delegate\">Delegate</a> role.\n\t\t\t\n\t\t".
forEvent comment "\n\t\t\tThe call classes have been deprecated in SWC. Instead, we suggest to use the <a href=\"http://sw.deri.org/2005/08/conf/cfp\">CfP ontology</a>.\n\t\t\t\n\t\t".
hasAttendee comment "\n\t\t\tInstead of this property, use the <a href=\"#Delegate\">Delegate</a> role.\n\t\t\t\n\t\t".
hasCall comment "\n\t\t\tThe call classes have been deprecated in SWC. Instead, we suggest to use the <a href=\"http://sw.deri.org/2005/08/conf/cfp\">CfP ontology</a>.\n\t\t\t\n\t\t".
hasRelatedDocument comment "\n\t\t\t\n\t\t\t\tRelates an <a href=\"#AcademicEvent\">event</a> such as a conference, workshop, etc. to a <a href=\"#ArgumentativeDocument\">document</a>.\n\t\t\t\n\t\t\t\n\t\t".
hasRole comment "\n\t\t\t\n\t\t\t\tPart of the <a href=\"#Role\">role</a> modelling machinery of SWC. This property relates an event (e.g. a conference) to a role at the event (e.g. a conference chair).\n\t\t\t\n\t\t\t\n\t\t".
heldBy comment "\n\t\t\t\n\t\t\t\tPart of the <a href=\"#Role\">role</a> modelling machinery of SWC. This property relates a role at an event (e.g. a conference chair) to the person who actually holds the role.\n\t\t\t\n\t\t\t\n\t\t".
holdsRole comment "\n\t\t\t\n\t\t\t\tPart of the <a href=\"#Role\">role</a> modelling machinery of SWC. This property relates a person to the role (e.g. a conference chair) it holds at an event.\n\t\t\t\n\t\t\t\n\t\t".
isProvidedBy comment "\n\t\t\tDeprecated because it has never been used and in order to reduce the inflation of ontology terms.\n\t\t\t\n\t\t".
isProviderOf comment "\n\t\t\tDeprecated because it has never been used and in order to reduce the inflation of ontology terms.\n\t\t\t\n\t\t".
isRoleAt comment "\n\t\t\t\n\t\t\t\tPart of the <a href=\"#Role\">role</a> modelling machinery of SWC. This property relates a role at an event (e.g. a conference chair) to the event (e.g. a conference).\n\t\t\t\n\t\t\t\n\t\t".
isSubEventOf comment "Events can be sub-events of other events. E.g., a talk can be a sub-event of a session, which in turn can be a sub-event of a conference. The relation is transitive - the talk is also a sub-event of the conference.".
isSuperEventOf comment "Events can be super-events of other events. E.g., a conference can be the super-event of a session, which in turn can be the super-event of a talk. The relation is transitive - the conference is also the super-event of the talk.".
license_doc comment "\n\t\t\t\n\t\t\t\n\t\t\t\tCopyright © 2007-2009 Knud Möller, Sean Bechhofer and Tom Heath. \n\t\t\t\t \n\t\t\t\t<a href=\"http://creativecommons.org/licenses/by/3.0/\"><img alt=\"Creative Commons License\" style=\"border: 0; float: right; padding: 10px;\" src=\"somerights.gif\" /></a>\n\t\t\t\tThis work is licensed under a <a href=\"http://creativecommons.org/licenses/by/3.0/\">Creative Commons Attribution License</a>. \n\t\t\t\tThis copyright applies to the Semantic Web Conference Ontology (SWC) Specification and accompanying documentation in RDF.\n\t\t\t\tRegarding underlying technology, SWC uses W3C's <a href=\"http://www.w3.org/RDF/\">RDF</a> technology, an\n\t\t\t\topen Web standard that can be freely used by anyone.\n\t\t\t\n\t\t\t\n\t\t".
relatedToEvent comment "\n\t\t\t\n\t\t\t\tRelates a <a href=\"#ArgumentativeDocument\">document</a> to an <a href=\"#AcademicEvent\">event</a> such as a conference, workshop, etc.\n\t\t\t\n\t\t\t\n\t\t".
Game comment "A Game type, such as go or chess.".
Location comment "A location in a game, such as a square or the players hand.".
LocationState comment "The state of a location on a specific game state.".
Move comment "An action which creates a new game state.".
PieceCount comment "A number of pieces of the same type. In games where money (fake or real) is used, then it should be treated as one piece per dollar (or the currency it works in). One piece per cent if subdivisions are possible.".
PieceType comment "A distinct type of piece. Interchangable with any other piece of the same type.".
Pieces comment "Don't use piecetype and piececount interchangeably. If a location MAY contain multiple pieces of the same type, it should always use piececount.".
Player comment "A player in a game. Only indicates an abstract side for the type of game, not a specific player in a single game.".
State comment "The state of a game.".
Status comment "A status of a game.".
captures comment "The pieces captured in a move.".
moveLocation comment "A location involved in the move.".
removes comment "The pieces removed completel from play in a move.".
DOC comment "la classe contiene i documenti parlamentari stampati dalla Camera dei deputati, i cosiddetti \"DOC\" in numero romano: documenti e relazioni, trasmessi alla Camera dal Governo o da altri soggetti istituzionali ovvero predisposti da organi della Camera stessa".
abbinamento comment "abbinamento di un atto camera con altri atti".
adesioneGruppo comment "questa classe è stata creata per gestire le adesioni dei deputati ai gruppi parlamentari".
adesioneGruppoMisto comment "questa classe è stata creata per gestire le adesioni del Gruppo Misto".

first
previous
next