Data Portal @ linkeddatafragments.org

Matches in LOV for { ?s ?p ?o. }

• ontology logo bones_256.png.
• ontology maker sean-bechhofer.
• ontology maker me.
• ontology maker me.
• 01_introduction comment "\n\t\t\t<p>\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</p>\n\t\t\t<p>\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</p>\n\t\t\t<p>\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</p>\n\t\t\t\n\t\t".
• 01_introduction label "Introduction".
• 02_describing_papers comment "\n\t\t\t<p>For 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</p>\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<p>\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</p>\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".
• 02_describing_papers label "Describing Papers".
• 03_roles comment "\n\t\t\t<p>\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</p>\n\t\t\t<p>\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</p>\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".
• 03_roles label "Roles".
• AcademicEvent subject AcademicEvent.
• AcademicEvent type Class.
• AcademicEvent comment "\n\t\t\t\n\t\t\t<p>Academic 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.</p>\n\t\t\t\n\t\t".
• AcademicEvent label "Academic Event".
• AcademicEvent subClassOf OrganisedEvent.
• AcademicEvent term_status "testing".
• ArgumentativeDocument subject Document.
• ArgumentativeDocument type Class.
• ArgumentativeDocument comment "\n\t\t\t<p>An 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).</p>\n\t\t\t<p>According 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\".</p>\n\t\t\t\n\t\t".
• ArgumentativeDocument label "Argumentative Document".
• ArgumentativeDocument seeAlso Text_types.
• ArgumentativeDocument subClassOf Document.
• ArgumentativeDocument term_status "testing".
• Artefact subject Document.
• Artefact type Class.
• Artefact comment "\n\t\t\t<p><emph>Artefact</emph> here means a document which can have a physical manifestation, like a paper or the proceedings of a conference.</p>\n\t\t\t\n\t\t".
• Artefact label "Artefact".
• Artefact subClassOf Document.
• Artefact term_status "testing".
• BreakEvent subject Event.
• BreakEvent type Class.
• BreakEvent comment "\n\t\t\t\n\t\t\t<p>\n\t\t\t\tAny kind of break at the super-event, such as a coffee break.\n\t\t\t</p>\n\t\t\t\n\t\t".
• BreakEvent label "Break Event".
• BreakEvent subClassOf NonAcademicEvent.
• BreakEvent term_status "testing".
• Call subject Call.
• Call type DeprecatedClass.
• Call comment "\n\t\t\t<p>The 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>.</p>\n\t\t\t<p>A <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.</p>\n\t\t\t\n\t\t".
• Call label "Call".
• Call subClassOf Announcement.
• Call term_status "deprecated".
• MealEvent subject Event.
• MealEvent type Class.
• MealEvent comment "\n\t\t\t\n\t\t\t<p>\n\t\t\t\tA lunch, dinner or similar event at a conference or conference-like event.\n\t\t\t</p>\n\t\t\t\n\t\t".
• MealEvent label "Meal Event".
• MealEvent subClassOf NonAcademicEvent.
• MealEvent term_status "testing".
• NonAcademicEvent subject Event.
• NonAcademicEvent type Class.
• NonAcademicEvent comment "\n\t\t\t\n\t\t\t<p>\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</p>\n\t\t\t\n\t\t".
• NonAcademicEvent label "Non-academic Event".
• NonAcademicEvent subClassOf OrganisedEvent.
• NonAcademicEvent term_status "testing".
• OrganisedEvent subject Event.
• OrganisedEvent type Class.
• OrganisedEvent comment "\n\t\t\t\n\t\t\t<p>An event in time and space which is planned and organised, as opposed to something which 'just happens', such as a car accident or sunset.</p>\n\t\t\t\n\t\t".
• OrganisedEvent label "Organised Event".
• OrganisedEvent subClassOf Vevent.
• OrganisedEvent subClassOf Event-1.
• OrganisedEvent term_status "testing".
• Paper subject Document.
• Paper type Class.
• Paper comment "\n\t\t\t<p>A 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.).</p>\n\t\t\t\n\t\t".
• Paper label "Paper".
• Paper subClassOf ArgumentativeDocument.
• Paper subClassOf Artefact.
• Paper term_status "testing".
• Place subject Place.
• Place type DeprecatedClass.
• Place comment "\n\t\t\t\n\t\t\t<p>\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</p>\n\t\t\t\n\t\t".
• Place label "Place".
• Place subClassOf SpatialThing.
• Place term_status "deprecated".
• Proceedings subject Document.
• Proceedings type Class.
• Proceedings comment "\n\t\t\t<p>The proceedings of a conference or workshop, which contain the papers presented there.</p>\n\t\t\t\n\t\t".
• Proceedings label "Proceedings".
• Proceedings subClassOf Artefact.
• Proceedings subClassOf Document.
• Proceedings term_status "testing".
• Programme subject Document.
• Programme type Class.
• Programme comment "\n\t\t\t<p>A 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.</p>\n\t\t\t\n\t\t".
• Programme label "Programme".
• Programme subClassOf Artefact.
• Programme subClassOf Document.
• Programme term_status "testing".
• Role subject Role.
• Role type Class.
• Role comment "\n\t\t\t<p>\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</p>\n\t\t\t<p>\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</p>\n\t\t\t\n\t\t".
• Role label "Role".
• Role subClassOf Role-1.
• Role term_status "testing".
• SessionEvent subject AcademicEvent.
• SessionEvent type Class.
• SessionEvent comment "\n\t\t\t\n\t\t\t<p>\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</p>\n\t\t\t\n\t\t".
• SessionEvent label "Session Event".
• SessionEvent subClassOf AcademicEvent.
• SessionEvent term_status "testing".
• SocialEvent subject Event.

• first
• previous
• next