/
Enforcing Policies and Guidelines in Web Portals: A Case St Enforcing Policies and Guidelines in Web Portals: A Case St

Enforcing Policies and Guidelines in Web Portals: A Case St - PowerPoint Presentation

min-jolicoeur
min-jolicoeur . @min-jolicoeur
Follow
407 views
Uploaded On 2016-10-16

Enforcing Policies and Guidelines in Web Portals: A Case St - PPT Presentation

Siim Karus Faculty of Mathematics and Computer Science University of Tartu Estonia siim04utee Outline Motivation Enforcing policies Enfo r cing guidelines Lessons learned 2 3 4 Giving the ID: 476434

policies xslt rules req xslt policies req rules guidelines lyhikirjeldus content deviations programm time nimi semantic programmid verification grisbi

Share:

Link:

Embed:

Download Presentation from below link

Download Presentation The PPT/PDF document "Enforcing Policies and Guidelines in Web..." is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.


Presentation Transcript

Slide1

Enforcing Policies and Guidelines in Web Portals: A Case Study

Siim Karus

Faculty of Mathematics and Computer Science

University of Tartu

Estonia

siim04@ut.eeSlide2

Outline

Motivation

Enforcing policies

Enforcing guidelinesLessons learned

2Slide3

3Slide4

4Slide5

Giving the Community the

Power

5Slide6

Let the community create their own presentations

6Slide7

Policies

Guidelines

Do not lose control!

Content preservation or filtering, ensuring correct usage of content

Independence from business components (generality)

Graceful handling of unexpected content

7Slide8

Automatic verification

Can be ignored

Must be preserved

Conditionally preserved

8Slide9

xslt-req

Extension of XML Schema.

Designed to be similar to XSLT.

Specifies restrictions on transformation rules that can be applied on attributes, elements, and groups.

Effective rules can depend on output formats or data element values.

Defines default actions for unqualified entities.

9Slide10

xslt-req transformation rules

10Slide11

xslt-req limitations

Original document may only have one root element in a

ruleset

.Rules can only be defined on elements and structures explicitly defined with XML SchemaVisual hiding (e.g. covering parts of document) is still possible and requires human verification.

11Slide12

Results of using xslt-req

Usually require proofing or aid from administrators.

Detected less than 30% of different types of deviations.

Detected types of deviation were the most common ones (experienced more than half of the time).

12Slide13

Guidelines

13Slide14

Using implicit metadata

XML content contains lot of semantic information in order to be human-readable.

That semantic information and other implicit metadata can be used to detect similar concepts to which the same rules can be applied.

14Slide15

<

artiklid

nimi

="

Artiklid

"

kokku

="

7

"

esimene

="

1

"

viimane

=“

5

"

lk

="

1

"

arv

=“

5

" pide=

">

<

artikkel

pealkiri

="

Kasutajate loodud VabaVaraVeebi teemalised materjalid

"

id

="

6

"

kasutaja_id

="

1330374

"

aeg

="

07.01.2006 01:26

"

kinnitatud

="

N

"

tabamus

="100"/> <artikkel pealkiri="Eesti keele speller Firefoxile ja Thunderbirdile" id="7" kasutaja_id="1050504" aeg="09.11.2006 00:40" kinnitatud="Y" tabamus="100"/> <…/></artiklid>

15Slide16

<

programmid

kokku

="

5

"

esimene

="

1

"

viimane

="

5

"

lk

="

1

"

arv

="

20

"

nimi

="

Programmid

"

pide

="

"

elemendi_tyyp

="

loend

">

<

programm

id

="

390

"

nimi

="

Abassis Finance Manager

"

hinnang

="

pole hinnatud

"

tootja

="

SmartMedia

"

koduleht="http://www.abassis.com/" …>

<

lyhikirjeldus

>

Isiklik arvepidamistarkvara mitmete huvitavate võimalustega.</lyhikirjeldus> </programm> <programm id="463" nimi="Grisbi" hinnang="pole hinnatud" tootja="Grisbi Team" koduleht="http://www.grisbi.org" …> <lyhikirjeldus>Lihtne isiklik arvepidamistarkvara.</lyhikirjeldus> </programm> <…/></programmid>

16Slide17

17Slide18

Suggestive m

ethods

Examples

TemplatesAPIHuman guidance

18Slide19

Results of suggestions

Required additional time spent on documentation and creating of examples.

Discouraged deviations from less intuitive policies.

Less time was needed to explain users the policies

19Slide20

Lessons learned

Post-authoring verification

Usually require proofing or aid from administrators.

Is effective at finding the most common deviations.

Pre-emptive suggestions

Require additional time spent on documentation and creating of examples.

Easy access to suggested patterns discourages deviations from less intuitive policies and guidelines.

More

than 50% decrease in the cost of maintaining the portal.

20Slide21

Future perspectives

xslt-req

can be extended to support more complex and dynamic constructs.

Semantic detections can be improved by studying natural naming patterns used by business logic component programmers.

21Slide22

Discussion

22