FRINK Linked Data Fragments server

Matches in SemOpenAlex for { <https://semopenalex.org/work/W80852954> ?p ?o ?g. }

• W80852954 abstract "Semantic Portals allow for integrated and syndicated data views on information by using ontological knowledge and machine processable semantic descriptions. In particular, Semantic Portals should allow the user to customize the access to information by making advanced use of the semantic descriptions of the information, and should provide individualized views on the data, enhance user awareness and orientation, help the user in detecting relevant informations or relations, etc. In this demonstration, we present the Semantic Portal we have developed for the REWERSE project, and show how portal knowledge can be used to individualize the access to the portal. 1 Motivation Within the scope of the REWERSE project1 we developed a couple of Semantic Web Ontologies, among others: Researcher Ontology: This ontology models persons and their involvements in projects or organizations. Semantic Web Glossary Ontology: models Semantic Web terms and their relations between each other. Bookmark Ontology: contains concepts that are necessary to describe and evaluate websites. These ontologies are already applied to several applications. Such as the Researcher Ontology which is used by the Personal Publication Reader [Baumgartner et al., 2005] to gather additional information about authors of specific publications. The aim of our research work was to build a portal for the REWERSE project, which enables users to access information provided by these ontologies and portal specific data (i. e. News, Appointments, etc.) in a personalized way and further to let the user benefit from the schema information which is defined in the ontologies. These benefits should include context based navigation through the RDF Data and the ability to query the RDF Data in a schema-specific way. REWERSE project: http://rewerse.net/ (07/2005) 2 Our Approach To realize the described kind of portal, we used a portal software which was developed for SWAD-E demonstrator “The Semantic Web Environment Directory” (SWED2) [Reynolds et al., 2004] . Below we give a short introduction to this portal software and point out how we customized and extended the software. 2.1 SWAD-E Semantic Portal A lightly abstracted architecture of the SWAD-E Semantic Portal is illustrated in figure 1. The Content Aggregator (called Harvester) is used to read in distributed RDF Data via the Jena API3. This data is encapsulated in a special model (Datastore), which is accessible through the portal definition (Datasource). Thus the Datasource provides access to the whole dataset including the schema definitions (Domain-specific Ontologies). By use of queries and filters it is possible to extract specific data. The Visualization of these data subsets, which match a special filter, is done by Visualization Templates (Velocity4 Templates). 2.2 Portal Customizat ion To customize the SWAD-E portal software we had to perform three main tasks. The following had to edited in the portal configuration file: SWED: http://www.swed.org.uk/ (07/2005) Jena API: http://jena.sourceforge.net/ (07/2005) Velocity: http://jakarta.apache.org/velocity/ (07/2005) Figure 1 SWAD-E Semantic Portal Architecture User Awareness and Personalization in Semantic Portals Fabian Abel Institute of Information Systems University of Hannover, Germany abel@kbs.uni-hannover.de Nicola Henze Research Center L3S & Institute of Information Systems University of Hannover, Germany henze@kbs.uni-hannover.de 1. Defining the Datasource: Specifying the attributes of the portal (i. e. name) and announcing which Ontologies and Data should be imported (listening 1). 2. Defining Facets: Facets are certain attributes of a filter (matching patterns). A filter is composed of an arbitrary number of stateful facets. The following listening illustrates a facet that allows to filter instances of the Researcher Ontology by rdf:type: In listening 2 we define a portal built-in facet (HierarchicalFacet). Therefore we specify the properties that indicate the type of an instance (line 04), the next broader concept (line 05) and the most general concept (line 06). 3. Defining Visualization Templates: The defined templates can be applied to a special context and a particular type of a RDF Resource. After these three steps are fulfilled and the Look And Feel is adjusted in a Cascading Stylesheet the portal customization is finished. 2.3 Portal Extensions Next to the common portal customization we also extended the functionality of the SWAD-E portal software, e.g. with implementing the Date Facet which is used to filter News according to the creation date (dc:date). In a second iteration we developed own packages to accomplish personalization. These packages provide: User Management: enables the portal to determine which registered users are online. Registered users are associated with the corresponding instance of the Researcher Ontology. Personal Filters: When a user is logged in, he can use predefined personal filters to navigate to e. g. News of Working Groups he is involved in. Radar: The Radar calculates and visualizes the distance between two Persons. We distinguish between: • browsing distance: How many clicks does it take a user to navigate to the same page (RDF Resource) another user has just visited? • professional distance: How much relation has a user to another user? The process of determining the professional distance by using the Researcher Ontology is outlined in Figure 2." @default.
• W80852954 created "2016-06-24" @default.
• W80852954 creator A5080218207 @default.
• W80852954 date "2005-01-01" @default.
• W80852954 modified "2023-09-23" @default.
• W80852954 title "User Awareness and Personalization in Semantic Portals" @default.
• W80852954 cites W1592414382 @default.
• W80852954 hasPublicationYear "2005" @default.
• W80852954 type Work @default.
• W80852954 sameAs 80852954 @default.
• W80852954 citedByCount "4" @default.
• W80852954 crossrefType "journal-article" @default.
• W80852954 hasAuthorship W80852954A5080218207 @default.
• W80852954 hasConcept C111472728 @default.
• W80852954 hasConcept C136764020 @default.
• W80852954 hasConcept C138885662 @default.
• W80852954 hasConcept C148792806 @default.
• W80852954 hasConcept C167379230 @default.
• W80852954 hasConcept C183003079 @default.
• W80852954 hasConcept C192800085 @default.
• W80852954 hasConcept C20136886 @default.
• W80852954 hasConcept C2129575 @default.
• W80852954 hasConcept C23123220 @default.
• W80852954 hasConcept C25810664 @default.
• W80852954 hasConcept C41008148 @default.
• W80852954 hasConcept C50382505 @default.
• W80852954 hasConcept C534406577 @default.
• W80852954 hasConceptScore W80852954C111472728 @default.
• W80852954 hasConceptScore W80852954C136764020 @default.
• W80852954 hasConceptScore W80852954C138885662 @default.
• W80852954 hasConceptScore W80852954C148792806 @default.
• W80852954 hasConceptScore W80852954C167379230 @default.
• W80852954 hasConceptScore W80852954C183003079 @default.
• W80852954 hasConceptScore W80852954C192800085 @default.
• W80852954 hasConceptScore W80852954C20136886 @default.
• W80852954 hasConceptScore W80852954C2129575 @default.
• W80852954 hasConceptScore W80852954C23123220 @default.
• W80852954 hasConceptScore W80852954C25810664 @default.
• W80852954 hasConceptScore W80852954C41008148 @default.
• W80852954 hasConceptScore W80852954C50382505 @default.
• W80852954 hasConceptScore W80852954C534406577 @default.
• W80852954 hasLocation W808529541 @default.
• W80852954 hasOpenAccess W80852954 @default.
• W80852954 hasPrimaryLocation W808529541 @default.
• W80852954 hasRelatedWork W1413595637 @default.
• W80852954 hasRelatedWork W1517602423 @default.
• W80852954 hasRelatedWork W161041371 @default.
• W80852954 hasRelatedWork W2035743201 @default.
• W80852954 hasRelatedWork W2036711052 @default.
• W80852954 hasRelatedWork W2047002499 @default.
• W80852954 hasRelatedWork W2124846565 @default.
• W80852954 hasRelatedWork W2161972571 @default.
• W80852954 hasRelatedWork W2183312258 @default.
• W80852954 hasRelatedWork W2185651056 @default.
• W80852954 hasRelatedWork W2573269958 @default.
• W80852954 hasRelatedWork W2739100009 @default.
• W80852954 hasRelatedWork W2755033765 @default.
• W80852954 hasRelatedWork W2771729147 @default.
• W80852954 hasRelatedWork W2955269344 @default.
• W80852954 hasRelatedWork W3114725854 @default.
• W80852954 hasRelatedWork W3152574421 @default.
• W80852954 hasRelatedWork W2126476214 @default.
• W80852954 hasRelatedWork W2181360947 @default.
• W80852954 hasRelatedWork W2728871208 @default.
• W80852954 isParatext "false" @default.
• W80852954 isRetracted "false" @default.
• W80852954 magId "80852954" @default.
• W80852954 workType "article" @default.