tag:blogger.com,1999:blog-44133919505363936152024-03-13T22:12:13.865+00:00ResearchAreebhttp://www.blogger.com/profile/00364345104197856384noreply@blogger.comBlogger27125tag:blogger.com,1999:blog-4413391950536393615.post-38080909820330307052012-04-06T08:27:00.016+01:002012-04-06T09:20:44.005+01:00الدليل المصور لمرحلة الدكتوراههذه ترجمة لمقال في مدونة د.مات مايتتخيل دائرة تحوي كل المعرفة الإنسانيةعندما تنهي المرحلة الإعدادية تكون قد تعلمت قليلاًعندما تنهي المرحلة الثانوية تكون قد تعلمت أكثر بقليلوبشهادة بكالوريوس تكون قد تخصصت في علم معينبشهادة ماجستير تتعمق أكثر في هذا التخصصوبقراءة الأبحاث والأوراق العلمية تكون قد وصلت إلى حدود المعرفة الإنسانيةوعندما تصل للحدود تركز "تفكيرك واهتمامك" ١وتظل تدفع ذلك الحاجز لسنواتحتىAreebhttp://www.blogger.com/profile/00364345104197856384noreply@blogger.com0tag:blogger.com,1999:blog-4413391950536393615.post-18323204766303460392012-01-06T14:45:00.005+00:002012-01-06T14:49:29.524+00:00I can hate writing less nowThis is how I should have use the computer before; I hate interfaces, so I should’ve used it without an interface. I should have taken advantage of what typing with a computer liberates us from, compared to a pen and paper -yes I'm that old I’ve used pen and paper to write essays-. Using a computer enables us to write freely without being distracted about how our writing looks. And I mean how theAreebhttp://www.blogger.com/profile/00364345104197856384noreply@blogger.com0tag:blogger.com,1999:blog-4413391950536393615.post-1167866924334943862011-12-26T17:11:00.003+00:002011-12-26T17:28:15.884+00:00For PhD studentsGreat advice, especially for beginners.Areebhttp://www.blogger.com/profile/00364345104197856384noreply@blogger.com0tag:blogger.com,1999:blog-4413391950536393615.post-40225181091391875692009-05-09T10:42:00.002+01:002009-05-09T10:46:54.447+01:00EXPRESS and the 3-tier ArchitectureWe can picture a mapping between the way EXPRESS does things and the 3-tier architecture. This mapping depends on what type of system EXPRESS is providing an interface for.EXPRESS can provide RESTful Semantic Web Services as an interface for systems that have complex business logic or for systems that have datasets and want to provide them with simple access. In addition to dividing systems into Areebhttp://www.blogger.com/profile/00364345104197856384noreply@blogger.com0tag:blogger.com,1999:blog-4413391950536393615.post-90510345495747683112009-05-09T09:15:00.005+01:002009-05-11T11:32:09.338+01:00EXPRESS the DilemmaAs I started implementation, some ideas are popping into my head, I know this should happen more often :) but anyhow... We can view the Semantic Data in an EXPRESSive system as an interface to the client, which tells it how to interact with the system. The simple CRUD operations affect the Semantic interface in the same way no matter what the system is. What differs however is the business logic Areebhttp://www.blogger.com/profile/00364345104197856384noreply@blogger.com0tag:blogger.com,1999:blog-4413391950536393615.post-69858005387123524822009-05-09T09:02:00.005+01:002009-05-11T11:33:31.052+01:00Cool URIs<!--[if gte mso 9]> Normal 0 false false false EN-US X-NONE AR-SA <![endif]--><!--[if gte mso 9]>Areebhttp://www.blogger.com/profile/00364345104197856384noreply@blogger.com0tag:blogger.com,1999:blog-4413391950536393615.post-70276020099560860052009-05-09T08:43:00.005+01:002009-05-09T08:52:04.720+01:00Ruby on RailsTo show how - and if :) - EXPRESS works, I will implement a prototype of the approach and test it on some use cases. I want to use a REST framework to make things easier. There are some REST frameworks like Ruby on Rails and Restlet. I started by reading about Ruby on Rails, from what I read I understood it has simplifying assumptions that might conflict with my requirements for example:Every Areebhttp://www.blogger.com/profile/00364345104197856384noreply@blogger.com2tag:blogger.com,1999:blog-4413391950536393615.post-90103553970725834502009-05-03T21:15:00.012+01:002009-05-11T11:34:07.116+01:00Is EXPRESS RESTfulFor a system to be RESTful it must adhere to constraints of having a uniform interface and using hypertext as the engine of the application state. In the light of these constraints we will describe how EXPRESS is RESTful, first by showing how it has a uniform interface, then by discussing how it can use hypertext to change states. The examples explained are from EXPRESS. According to Fielding Areebhttp://www.blogger.com/profile/00364345104197856384noreply@blogger.com0tag:blogger.com,1999:blog-4413391950536393615.post-25286784171948808242009-04-16T09:48:00.007+01:002009-05-11T11:32:30.973+01:00Understanding RESTI’ve been reading to answer the questions in my last post, and the picture is a bit clearer.I think I now understand what we gain by HATEOAS. Instead of the client guessing where to go throughout an application by constructing URIs, it is guided by the server by providing it with hyperlinks (representations) to follow.What do we gain from that?More decoupling, thus more reusability, less Areebhttp://www.blogger.com/profile/00364345104197856384noreply@blogger.com0tag:blogger.com,1999:blog-4413391950536393615.post-63185068698153847712009-04-08T15:04:00.007+01:002009-05-11T11:32:52.182+01:00Why HATEOAS ?DisclaimerThis maybe total nonsense I am 90% sure it is but I’m putting it here anyway coz:1-I believe my blog hasn’t been indexed by Google -I haven’t linked it to any website yet- so it doesn’t officially exist on the Web :) The only person that might be reading this besides me is my supervisor. Sorry Dr Dave :).2-If one day I feel like releasing this to the world then hopefully I would have Areebhttp://www.blogger.com/profile/00364345104197856384noreply@blogger.com0tag:blogger.com,1999:blog-4413391950536393615.post-90746615569501835762009-03-10T19:07:00.006+00:002009-03-10T21:36:20.958+00:005 a day !No this isn't the NHS recommendation :)This is how I intend to write my nine month report 5 sentences a day ! I know that is not much but for someone who hates writing it is more than enough. I've been doing it for two days, hopefully I'll keep up the habit.I spent three hours on Sunday writing the table of contents and formatting the report. In my previous life :) this sometimes happened a day Areebhttp://www.blogger.com/profile/00364345104197856384noreply@blogger.com0tag:blogger.com,1999:blog-4413391950536393615.post-55200110325817985862009-03-04T18:53:00.008+00:002009-05-11T11:34:53.288+01:00My Methodology at last...It is amazing how much time I need to finish writing something so simple and short. Well here is the methodology.-----------------------------------------------------------------------------------The aim of my PhD is to offer provide a systematic method for creating RESTful Web Services for Semantic resources which then can be implemented in a system. Since Web Services have great impact on Areebhttp://www.blogger.com/profile/00364345104197856384noreply@blogger.com0tag:blogger.com,1999:blog-4413391950536393615.post-8878202950223154602009-02-16T08:02:00.008+00:002009-02-16T09:06:08.063+00:00Making CRS RESTfulIn the last post I discussed the CRS or Consistent Reference Service, in some places called the Coreference Resolution Service. I this post I will discuss how to make it RESTful and what are the advantages of making it RESTful:-Mapping the service offers a uniform interface to it.-It facilitates exchanging information amongst different CRSs.-Defining a protocol, for example: if CRSs exist that Areebhttp://www.blogger.com/profile/00364345104197856384noreply@blogger.com0tag:blogger.com,1999:blog-4413391950536393615.post-64842391693334088962009-02-15T22:05:00.007+00:002009-05-11T11:35:18.897+01:00RKBExplorer and CRS Consistent Reference Service<!--[if gte mso 9]> Normal 0 false false false EN-US X-NONE AR-SA MicrosoftInternetExplorer4 <![endif]--><!--[if gte mso 9]>Areebhttp://www.blogger.com/profile/00364345104197856384noreply@blogger.com0tag:blogger.com,1999:blog-4413391950536393615.post-82787930327791870232009-01-26T19:11:00.008+00:002009-05-11T11:37:04.526+01:00Thank you VideoLecturesI have been reading specifications and searching for tutorials trying to understand OWL-S, WSMO and IRS II. However I wasn't confident about what I've learned. Recently, I found these lectures on OWL-S,WSMO and IRS II.What is really good is that the lectures are from the people who wrote these specifications so you can trust it.Because it is a presentation they focused on how their work fits in Areebhttp://www.blogger.com/profile/00364345104197856384noreply@blogger.com0tag:blogger.com,1999:blog-4413391950536393615.post-73822114174079744152009-01-22T14:41:00.005+00:002009-05-11T11:36:43.190+01:00Presto!So how similar are you Presto?Let's see:Similarities-They have the same URI structure.-They use GET to query, POST to add assertions-They have suggested content negotiation-They discussed calculated resources. As “Identifiable Query Results” but I am not sure if they are added to the original ontology.Differences-They designed it from knowledge management perspective, not a Web Services Areebhttp://www.blogger.com/profile/00364345104197856384noreply@blogger.com0tag:blogger.com,1999:blog-4413391950536393615.post-53344652432984548262009-01-21T21:30:00.004+00:002009-05-11T11:37:30.322+01:00A detour, or a dead end :)The idea of the deployment of OWL to provide a RESTful API is so straightforward and graceful that somebody should have thought of before. I was kind of surprised yet glad that I didn’t find something similar to it :)I discussed the matter with my supervisor Dr. Dave Millard, and he suggested that I should check the Linked Data research. So I started by searching the Web of Knowledge, didn’t findAreebhttp://www.blogger.com/profile/00364345104197856384noreply@blogger.com0tag:blogger.com,1999:blog-4413391950536393615.post-48447839621760709102009-01-20T11:52:00.005+00:002009-01-20T12:42:56.734+00:00Reasoning about the Book Recommendation example<!--[if gte mso 9]> Normal 0 false false false EN-US X-NONE AR-SA <![endif]--><!--[if gte mso 9]>Areebhttp://www.blogger.com/profile/00364345104197856384noreply@blogger.com0tag:blogger.com,1999:blog-4413391950536393615.post-55820542762119381962009-01-20T10:20:00.001+00:002009-01-20T10:24:35.425+00:00Making a Book Recommendation System RESTful<!--[if gte mso 9]> Normal 0 false false false EN-US X-NONE AR-SA <![endif]--><!--[if gte mso 9]>Areebhttp://www.blogger.com/profile/00364345104197856384noreply@blogger.com0tag:blogger.com,1999:blog-4413391950536393615.post-56675805401293236312009-01-19T11:11:00.001+00:002009-01-19T11:13:58.298+00:00Reflections on the Ticket exampleLast week I did the resource design for ticket example. I modeled a ticket resource, however my supervisor noted that I modeled a ticket and a trip as the same thing. That’s why I got the problem were the ticket URI will change when one wants to change the source and destination. I didn’t think of a solution yet, I may revisit this depending on how things are going. Areebhttp://www.blogger.com/profile/00364345104197856384noreply@blogger.com0tag:blogger.com,1999:blog-4413391950536393615.post-49336355179403380102009-01-14T21:23:00.008+00:002009-05-11T11:38:10.760+01:00Issues and questions about the ticket exampleI forgot to include the price of the ticket in the resource design, I’ve updated it now First issue: Is it RESTful?-Addressability: It is addressable.-Uniform InterfaceGETShould be safe, meaning it doesn’t change the server state, a read-only method. I made a mistake with the confirmation number in the ticket example. It should not be issued by a GET request, it should be issued by a PUT or POSTAreebhttp://www.blogger.com/profile/00364345104197856384noreply@blogger.com0tag:blogger.com,1999:blog-4413391950536393615.post-795534590709682692009-01-13T16:58:00.007+00:002009-01-14T10:55:12.166+00:00The Ticket Ontology Resource Design<!--[if gte mso 9]> Normal 0 false false false EN-US X-NONE AR-SA <![endif]--><!--[if gte mso 9]>Areebhttp://www.blogger.com/profile/00364345104197856384noreply@blogger.com0tag:blogger.com,1999:blog-4413391950536393615.post-90511738014950646282009-01-12T12:19:00.007+00:002009-01-13T15:08:35.163+00:00Modeling a Semantic RESTful Web Service... continuesI've got Jena working, it took some time to figure out the problems but it is ok now.This site might be useful if I choose to implement in JSP http://nicolas-zozol.developpez.com/tutorial/java/rest-jsp-english/I've read the WSMO example which is written in WSML (Web Service Modelling Language) WSML uses ontologies and introduces some conventions such as (nonFunctional Properties, concepts, Areebhttp://www.blogger.com/profile/00364345104197856384noreply@blogger.com0tag:blogger.com,1999:blog-4413391950536393615.post-90127497887579050452009-01-09T10:33:00.007+00:002009-05-11T11:38:37.181+01:00Modeling a Semantic RESTful Web ServiceAfter discussing “Bridging the semantic Web and Web 2.0 with Representational State Transfer (REST)” with my supervisor Dr. David Millard, he suggested that there might be a more straightforward way in applying REST to Semantic Web services, so I'm to take an ontology that represents something that is usually accessed via web services, then access and manipulate it RESTfully.So I installed Jena, Areebhttp://www.blogger.com/profile/00364345104197856384noreply@blogger.com0tag:blogger.com,1999:blog-4413391950536393615.post-68830081401583813952009-01-06T11:11:00.013+00:002009-01-08T17:00:38.651+00:00Work done and some questions <!--[endif]--><!--[if gte mso 9]>Areebhttp://www.blogger.com/profile/00364345104197856384noreply@blogger.com0