Does Linked Data need RDF ? Before going any further, let’s get a few things crystal clear; The recent success of the Linked Data meme is long overdue, very welcome, and entirely capable of carrying the Web of Data far beyond its current niche adherents. A lot of my current work involves arguing that more organisations should adopt this approach;The Resource Description Framework, RDF, is a key — and powerful — piece in W3C‘s Semantic Web Architecture. Since its earliest days, I have played various parts in advocating the potential of RDF and will continue to do so;RDF is an obvious means of publishing — and consuming — Linked Data powerfully, flexibly, and interoperably. I will continue to argue this, and to advocate its wider adoption. So far, so good. The problem, I contend, comes when well-meaning and knowledgeable advocates of both Linked Data and RDF conflate the two and infer, imply or assert that ‘Linked Data’ can only be Linked Data if expressed in RDF. Anyway, now let me try to explain what I meant. “1.
Blog de JP Gouigoux | [TechDays2011] OData OData part du problème que, même si on abstrait les formats et les protocoles, il reste que des données ne partagent pas les mêmes schémas. SQL Azure permet d’exposer les données sous forme OData. pour plus de fournisseurs. Des conventions d’URL permettent d’avoir des appels REST standard, et un format standard d’affichage en JSON ou en XML sont utilisés. Du coup, OData n’est pas une technologie, mais plutôt un ensemble de convention d’exposition des données. Pour s’abstraire des schémas, il faut exposer un sommaire, sous forme de service, puis de workspaces, puis de collections. Bref, on est très proche de TJS dans l’esprit. OData peut être utilisé pour exposer de la donnée bien formatée, de manière relativement agnostique, mais sans atteindre la richesse syntaxique d’une ontologie. Il y a des outils génériques pour requêter du OData : OData Explorer fait en Silverlight, et puis Sesame (développé par Fabrice Marguerie), également en Silverlight.
Sweet Accessing data using the API The following types of data are available through the Monitor Service API: To use the Monitor Service OData API, you must be a XenApp or XenDesktop administrator. To call the API, you require read-only privileges; however, the data returned is determined by XenApp or XenDesktop administrator roles and permissions. For example, Delivery Group Administrators can call the Monitor Service API but the data they can obtain is controlled by Delivery Group access set up using Citrix Studio. For more information about XenApp or XenDesktop administrator roles and permissions, see Delegated Administration. The Monitor Service API is a REST-based API that can be accessed using an OData consumer. Every part of the Monitor Service data model is accessible and can be filtered on the URL. The query is processed on the server side and can be filtered further using the OData protocol on the client side. Aggregation of data values Concurrent data evaluation Correlation of summary tables with raw data
OpenAmplify Injects Semantics Into Keyword Targeting Systems [OData] Créer et exposer son propre flux OData , Blog Technique d'Audrey PETIT Publié jeudi 22 avril 2010 23:50 par Audrey OData (Open Data Protocol) est un protocole qui permet d'exposer des données via HTTP pour différents types de clients (RIA, Web, Mobile, etc...) afin de pouvoir utiliser et modifier ces données à distance. Ces données sont alors requêtable avec Linq depuis le client. Grâce à WCF RIA Services, il est possible d'exposer ses propres données facilement. Le fait de cocher cette case apporte les modifications suivantes à notre code : Il suffit ensuite de lancer l'application, et dans le navigateur Internet d'appeler l'adresse qui est composée de cette façon : A noter que si le nom de votre solution et/ou de votre DomainService contiennent des points " Dans notre exemple cela donne cette adresse : Et l'on obtient la liste de l'ensemble de tables que l'on avait sélectionné auparavant : Ce post vous a plu ?
schema.rdfs.org - Tools Programming Languages JavaScript Philip Jägenstedt has developed MicrodataJS, a jQuery plug-in for microdata providing an API similar to the HTML5 Microdata DOM API, as well as the Live Microdata tool that allows you to test your markup in the browser. Lin Clark has developed MicrodataPHP, a PHP library based on MicrodataJS. Alexandru Pruteanu has developed PHPStructuredData, a set of PHP libraries that use the vocabulary to implement and output, based on the context of the page, Microdata or RDFa Lite 1.1 semantics. Ruby Gregg Kellogg has developed the RDF::Microdata gem to parse microdata into RDF using the RDF.rb platform. Lawrence Woodman has developed Mida, a microdata extractor/parser library for Ruby. Python Ed Summers has developed an rdflib plugin that enables to parse Microdata and process the resulting RDF. Perl Toby Inkster has written a "fairly experimental parser for HTML microdata". Java Hitoshi Uchida has developed microdata/RDFa-Lite C library. Publishing Editors
Power Shell XenApp 6.0 and 6.5 The Citrix XenApp 6 and 6.5 PowerShell SDKs enable customers to manage XenApp 6 and 6.5 farms using Microsoft PowerShell scripting. Remoting All the commands now support a -ComputerName parameter which indicates to the cmdlet to execute remotely. This means that the snap-in can be installed anywhere and no additional configurations are needed in the client or server. To accomplish this feature, a new WCF service (Citrix XenApp Commands Remoting) was introduced in XenApp, which essentially implements all the business logic of the cmdlets. Default Computer Name In order to facilitate running existing scripts remotely without having to make significant changes, a default computer name can be set in the client machine. Object IDs Since many cmdlets might be executing remotely, the calls to the back-end are minimized so that the remote execution performance will not degrade significantly when compared to local execution. Citrix XenApp Commands Citrix Group Policy Provider Citrix Common Commands
Semantic Web Database Platform Discussion SWS aproach What is the best ,state of art approach for implementing semantic web services ? I am looking for a complete architecture description. next I'll explain the problems I am facing while i am implementating " Semantics of Web Services application for E-government using owl-s " The structure I am using is : Jena to work with ontology On top of Jena OWL-S API to work with OWL-S files (semantic dexcription of web services ) On top of Jena Empire library to generate bean classes from Ontology and Struts2 for UI 2- For web service composition : The are many algorithms for automatic web service composition but there are some problems : 1- What is the suggested way for monitoring the process of the registered web service , and recovery mechanizem in case of stopped webservice , and make online changes on the internal structure . 4- In case of online web service composition , I need to build the workflow online , so what is the best way to implement this Thanks for any recomendation , links ...
SDKs and APIs Several SDKs and APIs are available with this release. XenApp and XenDesktop SDK: The XenApp and XenDesktop SDK is based on a number of Microsoft Windows PowerShell version 3.0 snap-ins that allow you to perform the same tasks as you would with the Citrix Studio console as well as tasks you cannot do with Studio alone. For more information, see Citrix Developer. Citrix Group Policy SDK: The Citrix Group Policy SDK allows you to display and configure Group Policy settings and filters. Monitor Service OData API: You can use the Monitor Service OData API to: Analyze historical trends for future planningPerform detailed troubleshooting of connection and machine failuresExtract information for feeding into other tools and processes; for example, using Microsoft Excel's PowerPivot tables to display the data in different waysBuild a custom user interface on top of the data that the API provides For details, see the Monitor Service OData API articles. To access and run the cmdlets:
Les petites cases | Fourre-tout personnel virtuel de Got Chapter 1: Introduction and Application Scenarios | EUCLID The last decade has seen a growing interest in the Semantic Web, which extends the web of documents to a web of data. This technology applies web-based standards for encoding datasets and linking them to other published datasets, so that applications can exploit data from many different sources. It also provides standards for encoding general knowledge in ontologies, so allowing enhancements based on automatic reasoning (improved querying, for example). This chapter introduces Linked Data and related semantic technologies, and shows how they can be deployed in web applications. Movie 1: Developing a music portal. Learning outcomes On completing this chapter you should understand the following: the enabling technologies for Linked Data, in particular the RDF data model the current status of Linked Data technology how Linked Data can be applied in a particular scenario related to a music portal Internet