Re: equivalent classes
kala devi ramar <[email protected]> Thu, 14 Nov 2013 20:12:45 -0800 (PST)
| Newsgroups | gmane.comp.misc.ontology.protege.general |
|---|---|
| Message-ID | <[email protected]> |
--===============3683522324575210160== Content-Type: multipart/alternative; boundary="1024699347-1270459326-1384488765=:60593" --1024699347-1270459326-1384488765=:60593 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Dear sir=0Ain prot=E9g=E9 4.2 alpha I have assigned equivalent classes. but= some classes are assigned as equivalent classes, but it is not processed b= y code as equivalent classes.=A0 i have assign the equivalent relation in b= oth direction( low to minimum, minimum to low).what is the =A0mistake in th= is context?. Please clarify my doubt=0A=A0=0AThank you=0AR.Kaladevi=0A=0AFr= om: "[email protected]" <protege-discussion-req= [email protected]>=0ATo: [email protected] =0ASen= t: Tuesday, November 12, 2013 1:34 AM=0ASubject: protege-discussion Digest,= Vol 88, Issue 5=0A=0A=0ASend protege-discussion mailing list submissions t= o=0A=A0=A0=A0 [email protected]=0A=0ATo subscribe or un= subscribe via the World Wide Web, visit=0A=A0=A0=A0 https://mailman.stanfor= d.edu/mailman/listinfo/protege-discussion=0Aor, via email, send a message w= ith subject or body 'help' to=0A=A0=A0=A0 protege-discussion-request@lists.= stanford.edu=0A=0AYou can reach the person managing the list at=0A=A0=A0=A0= [email protected]=0A=0AWhen replying, please edi= t your Subject line so it is more specific=0Athan "Re: Contents of protege-= discussion digest..."=0A=0A=0AToday's Topics:=0A=0A=A0 1. subsumption of pr= operties? (Michael DeBellis)=0A=A0 2. Re: subsumption of properties? (Timot= hy Redmond)=0A=A0 3. ESWC 2014 Second Call for Tutorials ([email protected].= it)=0A=0A=0A---------------------------------------------------------------= -------=0A=0AMessage: 1=0ADate: Mon, 11 Nov 2013 08:52:20 -0800 (PST)=0AFro= m: Michael DeBellis <[email protected]>=0ATo: "protege-discussion@mailm= an.stanford.edu"=0A=A0=A0=A0 <[email protected]>=0ASu= bject: [protege-discussion] subsumption of properties?=0AMessage-ID:=0A=A0= =A0=A0 <[email protected]>=0AConte= nt-Type: text/plain; charset=3D"iso-8859-1"=0A=0AI've been using Protege fo= r a while now and one thing I'm still not clear on is when and why do you s= ubclass a property?? All the other capabilities make perfect sense but I've= never come across a system where you make sublcasses of properties or rela= tions before. Can someone give a brief couple of sentences that explains th= is or point me to the appropriate place in the documentation? =0A=0A=0AOne = thing that would help is understanding the formal definition of what it mea= ns to say one property is a subclass of another. Looking at properties as r= elations it seems to me a necessary requirement for property X to be a subc= lass? of property Y is that the domain and range of X must be subsets of th= e domain and range of Y. But that doesn't seem like a sufficient definition= , I think I could create examples where that was true but it doesn't seem a= ppropriate to have the two properties be sub-properties.=0A=0AMichael DeBel= lis=0A-------------- next part --------------=0AAn HTML attachment was scru= bbed...=0AURL: <http://mailman.stanford.edu/pipermail/protege-discussion/at= tachments/20131111/4ba801be/attachment-0001.html>=0A=0A--------------------= ----------=0A=0AMessage: 2=0ADate: Mon, 11 Nov 2013 09:36:23 -0800=0AFrom: = Timothy Redmond <[email protected]>=0ATo: [email protected]= ford.edu=0ASubject: Re: [protege-discussion] subsumption of properties?=0AM= essage-ID: <[email protected]>=0AContent-Type: text/plain; char= set=3D"iso-8859-1"; Format=3D"flowed"=0A=0AOn 11/11/2013 08:52 AM, Michael = DeBellis wrote:=0A> I've been using Protege for a while now and one thing I= 'm still not =0A> clear on is when and why do you subclass a property?=A0 A= ll the other =0A> capabilities make perfect sense but I've never come acros= s a system =0A> where you make sublcasses of properties or relations before= . Can =0A> someone give a brief couple of sentences that explains this or p= oint =0A> me to the appropriate place in the documentation?=0A=0A=0AA simpl= e example comes from the pizza ontology wherein hasTopping and =0AhasBase a= re sub-object-properties of hasIngredient.=0A=0AInformally, p is a sub obje= ct property of q if for any pair of =0Aindiivduals, x and y, if p maps x to= y then q maps x to y.=A0 This can be =0Aformalized by introducing the noti= on of an interpretation of a language =0Awhich is done for owl 2 here:=0A= =0A=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 http://www.w3.org/TR/2012/REC-owl2-direc= t-semantics-20121211/=0A=0A=0AThe formal definition of subObjectProperty is= given here (the first =0Aentry at the top of table 6):=0A=0A=A0 =A0 =A0 = =A0 =A0 =A0 =A0 http://www.w3.org/TR/2012/REC-owl2-direct-semantics-2012121= 1/#Object_Property_Expression_Axioms=0A=0A=0AData sub properties are simila= r.=A0 r is a sub data property of s if for =0Aany individual, x, and any da= ta value, d, if r maps x to d then s maps x =0Ato d.=0A=0A=0A>=0A> One thin= g that would help is understanding the formal definition of =0A> what it me= ans to say one property is a subclass of another. Looking at =0A> propertie= s as relations it seems to me a necessary requirement for =0A> property X t= o be a subclass=A0 of property Y is that the domain and =0A> range of X mus= t be subsets of the domain and range of Y. But that =0A> doesn't seem like = a sufficient definition,=0A=0AThis is a necessary but not a sufficient cond= ition.=0A=0A=0A-Timothy=0A=0A> I think I could create examples where that w= as true but it doesn't =0A> seem appropriate to have the two properties be = sub-properties.=0A>=0A> Michael DeBellis=0A>=0A>=0A> ______________________= _________________________=0A> protege-discussion mailing list=0A> protege-d= [email protected]=0A> https://mailman.stanford.edu/mailman/listi= nfo/protege-discussion=0A>=0A> Instructions for unsubscribing: http://prote= ge.stanford.edu/doc/faq.html#01a.03=0A=0A-------------- next part ---------= -----=0AAn HTML attachment was scrubbed...=0AURL: <http://mailman.stanford.= edu/pipermail/protege-discussion/attachments/20131111/99f0aeef/attachment-0= 001.html>=0A=0A------------------------------=0A=0AMessage: 3=0ADate: Mon, = 11 Nov 2013 10:47:33 -0800 (PST)=0AFrom: [email protected]=0ATo: protege-= [email protected]=0ASubject: [protege-discussion] ESWC 2014 Sec= ond Call for Tutorials=0AMessage-ID: <[email protected]= anford.edu>=0AContent-Type: text/plain; charset=3D"us-ascii"=0A=0A=0A** apo= logies for cross-posting **=0A=0A=3D=3D=3D=3D Second Call for Tutorials =3D= =3D=3D=3D=0Ahttp://2014.eswc-conferences.org/important-dates/call-tutorials= =0A=0AESWC 2014 invites tutorials that address the interests of its varied = audience: people new to the Semantic Web, Semantic Web researchers and prac= titioners that wish to learn new technologies, users of Semantic Web techno= logies, and representatives of government and funding agencies as well as p= otential private investors in Semantic Web technologies. We welcome submiss= ions of tutorial proposals on all major topics related to semantic technolo= gies.=0A=0AWe especially solicit proposals for tutorials of the following t= ypes:=0A=0A- Tutorials with a coherent theme providing an introduction to n= ew semantic technologies and trends.=0A- Tutorials describing the applicati= on of semantic technologies in specific domains (e.g., life-sciences, e-gov= ernment, e-commerce, cultural heritage, etc.).=0A- Tutorials presenting tec= hniques from other research fields that are of relevance for Semantic Web r= esearch especially in relationship to the tracks of the conference (e.g., t= echniques from social science, database techniques, NLP techniques etc.).= =0A=0ATutorials can be half a day or a full day.=0A=0AWe advise having more= than one presenter and no more than three, preferably from different insti= tutions, bringing different perspectives to the tutorial topic.=0A=0ATutori= als may focus entirely on theoretical aspects; however, we encourage organi= sers to incorporate hands-on sessions where appropriate. The tutorials shou= ld reach a good balance between the topic coverage and its relevance to the= community.=A0 =A0 =0A=0ATimeline for Tutorials=0A-----------=0AProposals d= ue: Nov 22, 2013 - 23:59 Hawaii Time=0ANotification of acceptance: Dec 6, 2= 013 - 23:59 Hawaii Time=0ATutorial Web site due: Dec 16, 2013 - 23:59 Hawai= i Time=0ACamera-ready material due: Apr 25, 2014 - 23:59 Hawaii Time=0ATuto= rial days: May 25 and May 26, 2014=0A=0AResponsibilities=0A-----------=0AOr= ganizers of accepted tutorials are responsible for preparing and maintainin= g a Web site that describes the tutorial and includes all relevant informat= ion. Organizers are also responsible for submitting the material for attend= ees (slide sets, additional teaching material, software installation and us= age guides for practical hands-on sessions, etc.) to the Tutorial Chair. Th= e ESWC 2014 Organizing Committee is responsible for providing publicity for= the tutorials as part of the conference publicity activities, and on-site = logistical support to the organizers and attendees. Tutorial attendees must= pay the ESWC 2014 workshop registration fee, as well as the conference reg= istration fee.=0A=0A=0AGeneral Information=0A-----------=0AEach tutorial wi= ll have one reduced registration fee (pre-conference days registration will= be free i.e. one of the chairs will only have to pay the main conference f= ees).=0AIn the interest of the overall quality of the conference, the Tutor= ial Chair reserves the right to merge tutorials and/or adjust the scope the= reof in case a mimimum number of registrations is not reached by the early = registration deadline.=0A=0ASubmission details=0A-----------=0ATutorial pro= posals should not exceed 5 pages, using an 11 pt font for the body of the t= ext of the proposal and should contain the following information:=0A=0A- Ab= stract (200 words maximum, for inclusion on the ESWC 2014 website).=0A=0A- = Tutorial description: More specifically, it should specify the objectives o= f the tutorial and relevance to ESWC 2014, include enough details on the sc= ope of the material to be covered and the depth to which it will be covered= and specify the intended audience and any prerequisite knowledge. Appropri= ate references to the material to be covered by the tutorial must be includ= ed.=0A=0A- Tutorial length. The tutorial can be full or half day (if the tu= torial can be either length, please be sure to identify which material is i= ncluded for each length).=0A=0A- Specify other venues to which the tutorial= or part thereof has or will be presented, in addition to explaining how th= e current tutorial differs from the other editions. Links to the slides of = those tutorial editions should be included in the proposal.=0A=0A- Brief pr= ofessional biography of the presenter(s) indicating previous training and s= peaking experience (such as teaching and tutorial presentation).=0A=0AEach = proposal will be reviewed by the members of the tutorial programme committe= e, and ranked based on the overall quality of the proposal and the tutorial= 's fit to the conference. Their recommendation will determine the final dec= ision on the acceptance/rejection of each proposal. =0A=0ASubmission=0A----= -------=0ASubmission will be through the Easychair system (please note that= it is the same site to submit workshops and tutorials)=A0 https://www.easy= chair.org/conferences/?conf=3Deswc2014workshops-tutorials=0A=0A=0ATutorials= Chair=0ANathalie Aussenac-Gilles (IRIT-CNRS, Toulouse, Fr)=0Aemail: aussen= [email protected]=0A=0A=0A------------------------------=0A=0A____________________= ___________________________=0Aprotege-discussion mailing list=0Aprotege-dis= [email protected]=0Ahttps://mailman.stanford.edu/mailman/listinfo/= protege-discussion=0A=0A=0AEnd of protege-discussion Digest, Vol 88, Issue = 5=0A************************************************* --1024699347-1270459326-1384488765=:60593 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable <html><body><div style=3D"color:#000; background-color:#fff; font-family:bo= okman old style, new york, times, serif;font-size:12pt"><div style=3D"RIGHT= : auto"><SPAN style=3D"RIGHT: auto">Dear sir</SPAN></div> <div style=3D"FONT-SIZE: 16px; FONT-FAMILY: bookman old style, new york, ti= mes, serif; RIGHT: auto; COLOR: rgb(0,0,0); FONT-STYLE: normal; BACKGROUND-= COLOR: transparent"><SPAN style=3D"RIGHT: auto">in prot=E9g=E9 4.2 alpha I = have assigned equivalent classes. but some classes are assigned as equivale= nt classes, but it is not processed by code as equivalent classes. i = have assign the equivalent relation in both direction( low to minimum, mini= mum to low).what is the mistake in this context?. Please clarify my d= oubt</SPAN></div> <div style=3D"RIGHT: auto"><SPAN style=3D"RIGHT: auto"></SPAN> </div> <div style=3D"RIGHT: auto"><SPAN style=3D"RIGHT: auto">Thank you</SPAN></di= v> <div style=3D"RIGHT: auto"><SPAN style=3D"RIGHT: auto">R.Kaladevi<VAR id=3D= yui-ie-cursor></VAR></SPAN></div> <div><BR></div> <DIV style=3D"FONT-SIZE: 12pt; FONT-FAMILY: bookman old style, new york, ti= mes, serif"> <DIV style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman, new york, time= s, serif"> <DIV dir=3Dltr> <DIV class=3Dhr style=3D"FONT-SIZE: 0px; BORDER-TOP: #ccc 1px solid; HEIGHT= : 0px; BORDER-RIGHT: #ccc 1px solid; BORDER-BOTTOM: #ccc 1px solid; PADDING= -BOTTOM: 0px; PADDING-TOP: 0px; PADDING-LEFT: 0px; MARGIN: 5px 0px; BORDER-= LEFT: #ccc 1px solid; LINE-HEIGHT: 0; PADDING-RIGHT: 0px" readonly=3D"true"= contenteditable=3D"false"></DIV><FONT size=3D2 face=3DArial><B><SPAN style= =3D"FONT-WEIGHT: bold">From:</SPAN></B> "[email protected]= tanford.edu" <[email protected]><BR><B><S= PAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> [email protected]= nford.edu <BR><B><SPAN style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Tuesday= , November 12, 2013 1:34 AM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Subject= :</SPAN></B> protege-discussion Digest, Vol 88, Issue 5<BR></FONT></DIV> <DIV class=3Dy_msg_container><BR>Send protege-discussion mailing list submi= ssions to<BR> <A href=3D"mailto:protege-discussion@lists.= stanford.edu" ymailto=3D"mailto:[email protected]">prot= [email protected]</A><BR><BR>To subscribe or unsubscribe vi= a the World Wide Web, visit<BR> <A href=3D"https://mailma= n.stanford.edu/mailman/listinfo/protege-discussion" target=3D_blank>https:/= /mailman.stanford.edu/mailman/listinfo/protege-discussion</A><BR>or, via em= ail, send a message with subject or body 'help' to<BR> <A= href=3D"mailto:[email protected]" ymailto=3D"m= ailto:[email protected]">protege-discussion-req= [email protected]</A><BR><BR>You can reach the person managing the li= st at<BR> <A href=3D"mailto:protege-discussion-owner@list= s.stanford.edu" ymailto=3D"mailto:[email protected]">protege-dis= [email protected]</A><BR><BR>When replying, please edit your= Subject line so it is more specific<BR>than "Re: Contents of protege-discu= ssion digest..."<BR><BR><BR>Today's Topics:<BR><BR> 1. subsumption of= properties? (Michael DeBellis)<BR> 2. Re: subsumption of properties?= (Timothy Redmond)<BR> 3. ESWC 2014 Second Call for Tutorials (<A hre= f=3D"mailto:[email protected]" ymailto=3D"mailto:[email protected]">spe= [email protected]</A>)<BR><BR><BR>------------------------------------------= ----------------------------<BR><BR>Message: 1<BR>Date: Mon, 11 Nov 2013 08= :52:20 -0800 (PST)<BR>From: Michael DeBellis <<A href=3D"mailto:mdebelli= [email protected]" ymailto=3D"mailto:[email protected]">[email protected]= et</A>><BR>To: "<A href=3D"mailto:[email protected]= u" ymailto=3D"mailto:[email protected]">protege-discuss= [email protected]</A>"<BR> <<A href=3D"mailto:p= [email protected]" ymailto=3D"mailto:protege-discussio= [email protected]">[email protected]</A>><BR>= Subject: [protege-discussion] subsumption of properties?<BR>Message-ID:<BR>= <<A href=3D"mailto:1384188740.97990.YahooMailNeo@web1= 85002.mail.gq1.yahoo.com" ymailto=3D"mailto:1384188740.97990.YahooMailNeo@w= eb185002.mail.gq1.yahoo.com">[email protected]= q1.yahoo.com</A>><BR>Content-Type: text/plain; charset=3D"iso-8859-1"<BR= ><BR>I've been using Protege for a while now and one thing I'm still not cl= ear on is when and why do you subclass a property?? All the other capabilit= ies make perfect sense but I've never come across a system where you make s= ublcasses of properties or relations before. Can someone give a brief coupl= e of sentences that explains this or point me to the appropriate place in the d= ocumentation? <BR><BR><BR>One thing that would help is understanding the fo= rmal definition of what it means to say one property is a subclass of anoth= er. Looking at properties as relations it seems to me a necessary requireme= nt for property X to be a subclass? of property Y is that the domain and ra= nge of X must be subsets of the domain and range of Y. But that doesn't see= m like a sufficient definition, I think I could create examples where that = was true but it doesn't seem appropriate to have the two properties be sub-= properties.<BR><BR>Michael DeBellis<BR>-------------- next part -----------= ---<BR>An HTML attachment was scrubbed...<BR>URL: <<A href=3D"http://mai= lman.stanford.edu/pipermail/protege-discussion/attachments/20131111/4ba801b= e/attachment-0001.html" target=3D_blank>http://mailman.stanford.edu/pipermail/protege-discussion/a= ttachments/20131111/4ba801be/attachment-0001.html</A>><BR><BR>----------= --------------------<BR><BR>Message: 2<BR>Date: Mon, 11 Nov 2013 09:36:23 -= 0800<BR>From: Timothy Redmond <<A href=3D"mailto:[email protected]" = ymailto=3D"mailto:[email protected]">[email protected]</A>><BR>T= o: <A href=3D"mailto:[email protected]" ymailto=3D"mail= to:[email protected]">[email protected]= .edu</A><BR>Subject: Re: [protege-discussion] subsumption of properties?<BR= >Message-ID: <<A href=3D"mailto:[email protected]" ymailto= =3D"mailto:[email protected]">[email protected]</A>= ><BR>Content-Type: text/plain; charset=3D"iso-8859-1"; Format=3D"flowed"= <BR><BR>On 11/11/2013 08:52 AM, Michael DeBellis wrote:<BR>> I've been u= sing Protege for a while now and one thing I'm still not <BR>> clear on = is when and why do you subclass a property? All the other <BR>> capabilities = make perfect sense but I've never come across a system <BR>> where you m= ake sublcasses of properties or relations before. Can <BR>> someone give= a brief couple of sentences that explains this or point <BR>> me to the= appropriate place in the documentation?<BR><BR><BR>A simple example comes = from the pizza ontology wherein hasTopping and <BR>hasBase are sub-object-p= roperties of hasIngredient.<BR><BR>Informally, p is a sub object property o= f q if for any pair of <BR>indiivduals, x and y, if p maps x to y then q ma= ps x to y. This can be <BR>formalized by introducing the notion of an= interpretation of a language <BR>which is done for owl 2 here:<BR><BR>&nbs= p; <A href=3D"http://www.w= 3.org/TR/2012/REC-owl2-direct-semantics-20121211/" target=3D_blank>http://w= ww.w3.org/TR/2012/REC-owl2-direct-semantics-20121211/</A><BR><BR><BR>The formal definition of subObjectProperty is given here (the first <BR>entry = at the top of table 6):<BR><BR> &n= bsp; <A href=3D"http://www.w3.org/TR/2012/REC-owl2-direct-semantics-2012121= 1/#Object_Property_Expression_Axioms" target=3D_blank>http://www.w3.org/TR/= 2012/REC-owl2-direct-semantics-20121211/#Object_Property_Expression_Axioms<= /A><BR><BR><BR>Data sub properties are similar. r is a sub data prope= rty of s if for <BR>any individual, x, and any data value, d, if r maps x t= o d then s maps x <BR>to d.<BR><BR><BR>><BR>> One thing that would he= lp is understanding the formal definition of <BR>> what it means to say = one property is a subclass of another. Looking at <BR>> properties as re= lations it seems to me a necessary requirement for <BR>> property X to b= e a subclass of property Y is that the domain and <BR>> range of X= must be subsets of the domain and range of Y. But that <BR>> doesn't seem like a sufficient definition,<BR><BR>This is a necessary but not a su= fficient condition.<BR><BR><BR>-Timothy<BR><BR>> I think I could create = examples where that was true but it doesn't <BR>> seem appropriate to ha= ve the two properties be sub-properties.<BR>><BR>> Michael DeBellis<B= R>><BR>><BR>> _______________________________________________<BR>&= gt; protege-discussion mailing list<BR>> <A href=3D"mailto:protege-discu= [email protected]" ymailto=3D"mailto:[email protected]= rd.edu">[email protected]</A><BR>> <A href=3D"https:= //mailman.stanford.edu/mailman/listinfo/protege-discussion" target=3D_blank= >https://mailman.stanford.edu/mailman/listinfo/protege-discussion</A><BR>&g= t;<BR>> Instructions for unsubscribing: <A href=3D"http://protege.stanfo= rd.edu/doc/faq.html#01a.03" target=3D_blank>http://protege.stanford.edu/doc= /faq.html#01a.03</A><BR><BR>-------------- next part --------------<BR>An H= TML attachment was scrubbed...<BR>URL: <<A href=3D"http://mailman.stanford.= edu/pipermail/protege-discussion/attachments/20131111/99f0aeef/attachment-0= 001.html" target=3D_blank>http://mailman.stanford.edu/pipermail/protege-dis= cussion/attachments/20131111/99f0aeef/attachment-0001.html</A>><BR><BR>-= -----------------------------<BR><BR>Message: 3<BR>Date: Mon, 11 Nov 2013 1= 0:47:33 -0800 (PST)<BR>From: <A href=3D"mailto:[email protected]" ymailto= =3D"mailto:[email protected]">[email protected]</A><BR>To: <A href=3D"m= ailto:[email protected]" ymailto=3D"mailto:protege-disc= [email protected]">[email protected]</A><BR>Sub= ject: [protege-discussion] ESWC 2014 Second Call for Tutorials<BR>Message-I= D: <<A href=3D"mailto:[email protected]" y= mailto=3D"mailto:[email protected]">201311111= [email protected]</A>><BR>Content-Type: text/plain; charset=3D"us-ascii"<BR><BR><BR>** apologies for cross-posting **<BR><BR>= =3D=3D=3D=3D Second Call for Tutorials =3D=3D=3D=3D<BR><A href=3D"http://20= 14.eswc-conferences.org/important-dates/call-tutorials" target=3D_blank>htt= p://2014.eswc-conferences.org/important-dates/call-tutorials</A><BR><BR>ESW= C 2014 invites tutorials that address the interests of its varied audience:= people new to the Semantic Web, Semantic Web researchers and practitioners= that wish to learn new technologies, users of Semantic Web technologies, a= nd representatives of government and funding agencies as well as potential = private investors in Semantic Web technologies. We welcome submissions of t= utorial proposals on all major topics related to semantic technologies.<BR>= <BR>We especially solicit proposals for tutorials of the following types:<B= R><BR>- Tutorials with a coherent theme providing an introduction to new se= mantic technologies and trends.<BR>- Tutorials describing the application o= f semantic technologies in specific domains (e.g., life-sciences, e-government, e-com= merce, cultural heritage, etc.).<BR>- Tutorials presenting techniques from = other research fields that are of relevance for Semantic Web research espec= ially in relationship to the tracks of the conference (e.g., techniques fro= m social science, database techniques, NLP techniques etc.).<BR><BR>Tutoria= ls can be half a day or a full day.<BR><BR>We advise having more than one p= resenter and no more than three, preferably from different institutions, br= inging different perspectives to the tutorial topic.<BR><BR>Tutorials may f= ocus entirely on theoretical aspects; however, we encourage organisers to i= ncorporate hands-on sessions where appropriate. The tutorials should reach = a good balance between the topic coverage and its relevance to the communit= y. <BR><BR>Timeline for Tutorials<BR>-----------<BR>Proposals = due: Nov 22, 2013 - 23:59 Hawaii Time<BR>Notification of acceptance: Dec 6, 2013 - 23:59 Hawaii Time<BR>Tutorial Web site due: Dec 16, 2013 - 2= 3:59 Hawaii Time<BR>Camera-ready material due: Apr 25, 2014 - 23:59 Hawaii = Time<BR>Tutorial days: May 25 and May 26, 2014<BR><BR>Responsibilities<BR>-= ----------<BR>Organizers of accepted tutorials are responsible for preparin= g and maintaining a Web site that describes the tutorial and includes all r= elevant information. Organizers are also responsible for submitting the mat= erial for attendees (slide sets, additional teaching material, software ins= tallation and usage guides for practical hands-on sessions, etc.) to the Tu= torial Chair. The ESWC 2014 Organizing Committee is responsible for providi= ng publicity for the tutorials as part of the conference publicity activiti= es, and on-site logistical support to the organizers and attendees. Tutoria= l attendees must pay the ESWC 2014 workshop registration fee, as well as th= e conference registration fee.<BR><BR><BR>General Information<BR>-----------<BR>Each tutorial will have one reduced registra= tion fee (pre-conference days registration will be free i.e. one of the cha= irs will only have to pay the main conference fees).<BR>In the interest of = the overall quality of the conference, the Tutorial Chair reserves the righ= t to merge tutorials and/or adjust the scope thereof in case a mimimum numb= er of registrations is not reached by the early registration deadline.<BR><= BR>Submission details<BR>-----------<BR>Tutorial proposals should not excee= d 5 pages, using an 11 pt font for the body of the text of the proposal and= should contain the following information:<BR><BR>- Abstract (200 words max= imum, for inclusion on the ESWC 2014 website).<BR><BR>- Tutorial descriptio= n: More specifically, it should specify the objectives of the tutorial and = relevance to ESWC 2014, include enough details on the scope of the material= to be covered and the depth to which it will be covered and specify the intended audience and any prerequisite knowledge. Appropriate referenc= es to the material to be covered by the tutorial must be included.<BR><BR>-= Tutorial length. The tutorial can be full or half day (if the tutorial can= be either length, please be sure to identify which material is included fo= r each length).<BR><BR>- Specify other venues to which the tutorial or part= thereof has or will be presented, in addition to explaining how the curren= t tutorial differs from the other editions. Links to the slides of those tu= torial editions should be included in the proposal.<BR><BR>- Brief professi= onal biography of the presenter(s) indicating previous training and speakin= g experience (such as teaching and tutorial presentation).<BR><BR>Each prop= osal will be reviewed by the members of the tutorial programme committee, a= nd ranked based on the overall quality of the proposal and the tutorial's f= it to the conference. Their recommendation will determine the final decision on the acceptance/rejection of each proposal. <BR><BR>Submission<= BR>-----------<BR>Submission will be through the Easychair system (please n= ote that it is the same site to submit workshops and tutorials) <A hr= ef=3D"https://www.easychair.org/conferences/?conf=3Deswc2014workshops-tutor= ials" target=3D_blank>https://www.easychair.org/conferences/?conf=3Deswc201= 4workshops-tutorials</A><BR><BR><BR>Tutorials Chair<BR>Nathalie Aussenac-Gi= lles (IRIT-CNRS, Toulouse, Fr)<BR>email: <A href=3D"mailto:[email protected]= " ymailto=3D"mailto:[email protected]">[email protected]</A><BR><BR><BR>-----= -------------------------<BR><BR>__________________________________________= _____<BR>protege-discussion mailing list<BR><A href=3D"mailto:protege-discu= [email protected]" ymailto=3D"mailto:[email protected]= rd.edu">[email protected]</A><BR><A href=3D"https://mai= lman.stanford.edu/mailman/listinfo/protege-discussion" target=3D_blank>https://mailman.stanford.edu/mailman/listinfo/protege-disc= ussion</A><BR><BR><BR>End of protege-discussion Digest, Vol 88, Issue 5<BR>= *************************************************<BR><BR><BR></DIV></DIV></= DIV></div></body></html> --1024699347-1270459326-1384488765=:60593-- --===============3683522324575210160== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ protege-discussion mailing list [email protected] https://mailman.stanford.edu/mailman/listinfo/protege-discussion Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03 --===============3683522324575210160==--