Inproceedings3102: Unterschied zwischen den Versionen
Ssp (Diskussion | Beiträge) (Die Seite wurde neu angelegt: „{{Publikation Erster Autor |ErsterAutorNachname=Speiser |ErsterAutorVorname=Sebastian }} {{Publikation Author |Rank=2 |Author=Rudi Studer }} {{Inproceedings |Refe…“) |
Ssp (Diskussion | Beiträge) |
||
| Zeile 11: | Zeile 11: | ||
|Title=A Self-Policing Policy Language | |Title=A Self-Policing Policy Language | ||
|Year=2010 | |Year=2010 | ||
| − | |Booktitle= | + | |Month=November |
| − | |Publisher= | + | |Booktitle=Proceedings of the 9th International Semantic Web Conference (ISWC 2010) |
| + | |Pages=730-746 | ||
| + | |Publisher=Springer | ||
| + | |Series=Lecture Notes in Computer Science | ||
| + | |Number=6496 | ||
}} | }} | ||
{{Publikation Details | {{Publikation Details | ||
|Abstract=Formal policies allow the non-ambiguous definition of situations in which usage of certain entities are allowed, and enable the automatic evaluation whether a situation is compliant. This is useful for example in applications using data provided via standardized interfaces. The low technical barriers of integrating such data sources is in contrast to the manual evaluation of natural language policies as they currently exist. Usage situations can themselves be regulated by policies, which can be restricted by the policy of a used entity. Consider for example the Google Maps API, which requires that applications using the API must be available without a fee, i.e. the application's policy must not require a payment. In this paper we present a policy language that can express such constraints on other policies, i.e. a self-policing policy language. We validate our approach by realizing a use case scenario, using a policy engine developed for our language. | |Abstract=Formal policies allow the non-ambiguous definition of situations in which usage of certain entities are allowed, and enable the automatic evaluation whether a situation is compliant. This is useful for example in applications using data provided via standardized interfaces. The low technical barriers of integrating such data sources is in contrast to the manual evaluation of natural language policies as they currently exist. Usage situations can themselves be regulated by policies, which can be restricted by the policy of a used entity. Consider for example the Google Maps API, which requires that applications using the API must be available without a fee, i.e. the application's policy must not require a payment. In this paper we present a policy language that can express such constraints on other policies, i.e. a self-policing policy language. We validate our approach by realizing a use case scenario, using a policy engine developed for our language. | ||
| − | |Download=ISWC-2010-ssp-rst-a-self-policing-policy-language.pdf, | + | |Download=ISWC-2010-ssp-rst-a-self-policing-policy-language.pdf, |
|Projekt=Graduiertenkolleg IME, SOA4ALL | |Projekt=Graduiertenkolleg IME, SOA4ALL | ||
|Forschungsgruppe=Wissensmanagement | |Forschungsgruppe=Wissensmanagement | ||
}} | }} | ||
Aktuelle Version vom 17. Februar 2011, 12:17 Uhr
A Self-Policing Policy Language
A Self-Policing Policy Language
Published: 2010
November
Buchtitel: Proceedings of the 9th International Semantic Web Conference (ISWC 2010)
Nummer: 6496
Reihe: Lecture Notes in Computer Science
Seiten: 730-746
Verlag: Springer
Referierte Veröffentlichung
BibTeX
Kurzfassung
Formal policies allow the non-ambiguous definition of situations in which usage of certain entities are allowed, and enable the automatic evaluation whether a situation is compliant. This is useful for example in applications using data provided via standardized interfaces. The low technical barriers of integrating such data sources is in contrast to the manual evaluation of natural language policies as they currently exist. Usage situations can themselves be regulated by policies, which can be restricted by the policy of a used entity. Consider for example the Google Maps API, which requires that applications using the API must be available without a fee, i.e. the application's policy must not require a payment. In this paper we present a policy language that can express such constraints on other policies, i.e. a self-policing policy language. We validate our approach by realizing a use case scenario, using a policy engine developed for our language.
Download: Media:ISWC-2010-ssp-rst-a-self-policing-policy-language.pdf
Graduiertenkolleg IME, SOA4ALL