The KB on its approach to Web 2.0.


90 views
Uploaded on:
Category: Animals / Pets
Description
The KB on its approach to Web 2.0. Bring down the boundary for clients to remix the yield of administrations . Theo van Veen, ELAG 2006, April 26 . Outline. Objectives Patterns in data recovery How would we upgrade combination Clarification of the idea of administration coordination
Transcripts
Slide 1

The KB on its approach to Web 2.0 Lower the hindrance for clients to remix the yield of administrations . Theo van Veen, ELAG 2006, April 26

Slide 2

The KB on its approach to Web 2.0 Overview Goals Trends in data recovery How would we upgrade incorporation Explanation of the idea of administration joining Demonstration of one arrangement (Ajax) What information and administration suppliers can do Remaining issues

Slide 3

The KB on its approach to Web 2.0 Goals Improve sharing of data and administrations Bring advanced data inside of range of a mouse snap Lower usage obstructions to make new usefulness by consolidating existing administrations Enhance personalization: client picks which administrations to coordinate

Slide 4

The KB on its approach to Web 2.0 Some patterns in data recovery Web 2.0: Let clients (re)mix data and administrations from others and themselves in their own particular manner Ajax (Asynchronous, Javascript and XML): Simultaneous solicitations can be sent from a site page to various targets. Results are recovered nonconcurrently without solidifying the screen and are progressively changed (and blended) to new pages.

Slide 5

The KB on its approach to Web 2.0 How to improve coordination B y: institutionalization of access to administrations distributed standard administration depictions describing so as to make administration s registries But likewise: the non-standard world as it is to make utilization of what is accessible now to encourage the standardi s ation procedure consolidating (the best of) diverse local guidelines to develop into new ones portraying relations in the middle of administrations and the metadata that may trigger those administrations !

Slide 6

The KB on its approach to Web 2.0 Extrapolation of OpenURL idea OpenURL: Vendor particular learning base how to get to administrations User is connected to OpenURL resolver giving connections Links to administrations are controlled by user’s foundation Towards (expected): Service suppliers distribute every one of their administrations User chooses favored administrations put away in an individual learning base User controlled criteria for conjuring the administration Direct connecting to administration, programmed or on client solicitation, in view of user’s inclinations, avoiding the OpenURL resolver

Slide 7

The KB on its approach to Web 2.0 The segments of another idea Any site page, for instance indicating consequences of a hunt The administrations: any application that can be summoned by a URL The client operators, which can be: A program augmentation (Firefox) An entry running in the program (Ajax) A server side application that catches client demands and administration reactions An OpenURL join resolver An information base containing data on administrations, how to get to those administrations, which metadata ought to trigger a connection and the client inclinations as for taking care of administrations

Slide 8

5. Demand with yield from administration An as data Knowledge Base 2. Translation of reaction from administration A 1. Solicitation and reaction 3. Lookup metadata and administrations User specialists The KB on its approach to Web 2.0 Schematic representation of the idea Output from administration An Output from administration An inspires connection to administration B Description of administration B Service B 4. Adjust presentation and include joins e.g. to administration B Service A

Slide 9

Search pictures of this individual in Google The KB on its approach to Web 2.0 Demonstration of idea: include picture hunt down inventor field <h3>HTML:<p/> This html pages shows how the field "<creator>Shakespeare</creator>" can be handled by a client operators. </h3><br/>

Slide 10

The KB on its approach to Web 2.0 COinS (Context Object in Spans) HTML label <span> to be perceived as OpenURL metadata object. Illustration: <span class="Z3988" title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info:ofi/fmt:kev:mtx:journal&amp;rft.issn=1045-4438"></span> Usage: principally OpenURL determination in mix with program augmentation (bookmarklet, greasemonkey) that can change the conduct of the <span> Benefits: meets expectations in many programs in light of the fact that it makes utilization of standard HTML labels and properties Disadvantage: accept OpenURL mindful administrations

Slide 11

The KB on its approach to Web 2.0 Normal reaction structure Google Scholar

Slide 12

The KB on its approach to Web 2.0 OpenURL connection added by client operators to Google Scholar reaction

Slide 13

The KB on its approach to Web 2.0 (self-loader )summon of a SRU look

Slide 14

The KB on its approach to Web 2.0 When discovered the connection is changed

Slide 15

The KB on its approach to Web 2.0 Activation of another connection

Slide 16

Response of the user’s OpenURL server when tapping the connection The KB on its approach to Web 2.0 When it is NOT discovered the connection remains an OpenURL join

Slide 17

SOAP http GET http POST XML information base XSL client specialists The KB on its approach to Web 2.0 Ajax: Asynchronous, Javascript and XML Native convention door SRU XSL and Javascript For Z39.50 not under our control ... … a focal door will be given Add your own particular usefulness and gathering portrayals User inquiry is sent by means of SRU to all objectives ... Combination is in your program! Change XML gathering depictions utilizing XSL Use XSL and Javascript to make a pursuit page Z39.50 targets will utilize a Z39.50-SRU portal TEL XML accumulation portrayals (SRU)

Slide 18

The KB on its approach to Web 2.0 The information database Combination of: Machine decipherable depictions of administration conduct and how to get to benefits: URL punctuation Request parameters Fixed parameters User connection Access component (POST, GET, SOAP) Services in connection to metadata components Which metadata field triggers which benefits? How can it trigger the administration? Demo of Ajax entry

Slide 19

The KB on its approach to Web 2.0

Slide 20

The KB on its approach to Web 2.0

Slide 21

The KB on its approach to Web 2.0

Slide 22

The KB on its approach to Web 2.0

Slide 23

The KB on its approach to Web 2.0

Slide 24

The KB on its approach to Web 2.0

Slide 25

The KB on its approach to Web 2.0

Slide 26

The KB on its approach to Web 2.0 With a tiny bit of creative ability (work to be done) Services can be activated by more perplexing criteria as opposed to the vicinity of a solitary metadata field in an organized metadata record Services can be enacted out of sight and just show up when there is something to indicate as opposed to pestering the client ahead of time Services can trigger different administrations, for instance from area to facilitates to show on a guide Web pages can be broke down (semi-naturally) to find potential administrations and produce new administration portrayals to be added to the administration depictions (like top picks) By formalization of administration depictions clients or client operators may trade “working” administration depictions

Slide 27

The KB on its approach to Web 2.0 What can information/administration suppliers do? Give machine discernable yield (XML) Semantic labeling of HTML pages to perceive metadata in pages( (e.g. COinS, unAPI) Prevent the requirement for complex understanding of yield, be tolerant as for data to make it simple to utilize yield from administrations and to produce information into administrations Use existing norms or make new ones simple to existing ones (e.g. SRU) Provide administration portrayals for any administration that is usable in this connection at a standard area e.g.: http://your.host/services.xml and searchable by Google Create registries with non specific administration depictions

Slide 28

The KB on its approach to Web 2.0 Issues Are suppliers willing to give machine comprehensible information without marking? Indeed, even with semantic labeling there is a probability that client operators will conceal marking data Still much variety in the encoding of metadata Security issue with blending and combining administrations from distinctive spaces in the program Providers may not be mindful that they are putting forth benefits that are valuable for combination Providers and foundations may not yet be prepared for Web 2.0 (insurance of their information)

Slide 29

The KB on its approach to Web 2.0 Thanks Email: theo.vanveen@kb.nl .:tslides

Recommended
View more...