Re: protege-discussion Digest, Vol 88, Issue 7

unsubscribe
________________________________________
From: [email protected] [[email protected]] on behalf of [email protected] [[email protected]]
Sent: Thursday, November 14, 2013 11:12 PM
To: [email protected]
Subject: protege-discussion Digest, Vol 88, Issue 7

Send protege-discussion mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        https://mailman.stanford.edu/mailman/listinfo/protege-discussion
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of protege-discussion digest..."


Today's Topics:

   1. Re: equivalent classes (kala devi ramar)


----------------------------------------------------------------------

Message: 1
Date: Thu, 14 Nov 2013 20:12:45 -0800 (PST)
From: kala devi ramar <[email protected]>
To: "[email protected]"
        <[email protected]>
Subject: Re: [protege-discussion] equivalent classes
Message-ID:
        <[email protected]>
Content-Type: text/plain; charset="iso-8859-1"

Dear sir
in prot?g? 4.2 alpha I have assigned equivalent classes. but some classes are assigned as equivalent classes, but it is not processed by code as equivalent classes.? i have assign the equivalent relation in both direction( low to minimum, minimum to low).what is the ?mistake in this context?. Please clarify my doubt
?
Thank you
R.Kaladevi

From: "[email protected]" <[email protected]>
To: [email protected]
Sent: Tuesday, November 12, 2013 1:34 AM
Subject: protege-discussion Digest, Vol 88, Issue 5


Send protege-discussion mailing list submissions to
??? [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
??? https://mailman.stanford.edu/mailman/listinfo/protege-discussion
or, via email, send a message with subject or body 'help' to
??? [email protected]

You can reach the person managing the list at
??? [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of protege-discussion digest..."


Today's Topics:

? 1. subsumption of properties? (Michael DeBellis)
? 2. Re: subsumption of properties? (Timothy Redmond)
? 3. ESWC 2014 Second Call for Tutorials ([email protected])


----------------------------------------------------------------------

Message: 1
Date: Mon, 11 Nov 2013 08:52:20 -0800 (PST)
From: Michael DeBellis <[email protected]>
To: "[email protected]"
??? <[email protected]>
Subject: [protege-discussion] subsumption of properties?
Message-ID:
??? <[email protected]>
Content-Type: text/plain; charset="iso-8859-1"

I've been using Protege for a while now and one thing I'm still not clear on is when and why do you subclass a property?? All the other capabilities make perfect sense but I've never come across a system where you make sublcasses of properties or relations before. Can someone give a brief couple of sentences that explains this or point me to the appropriate place in the documentation?


One thing that would help is understanding the formal definition of what it means to say one property is a subclass of another. Looking at properties as relations it seems to me a necessary requirement for property X to be a subclass? of property Y is that the domain and range of X must be subsets of the 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 appropriate to have the two properties be sub-properties.

Michael DeBellis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.stanford.edu/pipermail/protege-discussion/attachments/20131111/4ba801be/attachment-0001.html>

------------------------------

Message: 2
Date: Mon, 11 Nov 2013 09:36:23 -0800
From: Timothy Redmond <[email protected]>
To: [email protected]
Subject: Re: [protege-discussion] subsumption of properties?
Message-ID: <[email protected]>
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"

On 11/11/2013 08:52 AM, Michael DeBellis wrote:
> I've been using Protege for a while now and one thing I'm still not
> clear on is when and why do you subclass a property?? All the other
> capabilities make perfect sense but I've never come across a system
> where you make sublcasses of properties or relations before. Can
> someone give a brief couple of sentences that explains this or point
> me to the appropriate place in the documentation?


A simple example comes from the pizza ontology wherein hasTopping and
hasBase are sub-object-properties of hasIngredient.

Informally, p is a sub object property of q if for any pair of
indiivduals, x and y, if p maps x to y then q maps x to y.? This can be
formalized by introducing the notion of an interpretation of a language
which is done for owl 2 here:

? ? ? ? ? ? ? ? http://www.w3.org/TR/2012/REC-owl2-direct-semantics-20121211/


The formal definition of subObjectProperty is given here (the first
entry at the top of table 6):

? ? ? ? ? ? ? http://www.w3.org/TR/2012/REC-owl2-direct-semantics-20121211/#Object_Property_Expression_Axioms


Data sub properties are similar.? r is a sub data property of s if for
any individual, x, and any data value, d, if r maps x to d then s maps x
to d.


>
> One thing that would help is understanding the formal definition of
> what it means to say one property is a subclass of another. Looking at
> properties as relations it seems to me a necessary requirement for
> property X to be a subclass? of property Y is that the domain and
> range of X must be subsets of the domain and range of Y. But that
> doesn't seem like a sufficient definition,

This is a necessary but not a sufficient condition.


-Timothy

> I think I could create examples where that was true but it doesn't
> seem appropriate to have the two properties be sub-properties.
>
> Michael DeBellis
>
>
> _______________________________________________
> 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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.stanford.edu/pipermail/protege-discussion/attachments/20131111/99f0aeef/attachment-0001.html>

------------------------------

Message: 3
Date: Mon, 11 Nov 2013 10:47:33 -0800 (PST)
From: [email protected]
To: [email protected]
Subject: [protege-discussion] ESWC 2014 Second Call for Tutorials
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"


** apologies for cross-posting **

==== Second Call for Tutorials ====
http://2014.eswc-conferences.org/important-dates/call-tutorials

ESWC 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, and representatives of government and funding agencies as well as potential private investors in Semantic Web technologies. We welcome submissions of tutorial proposals on all major topics related to semantic technologies.

We especially solicit proposals for tutorials of the following types:

- Tutorials with a coherent theme providing an introduction to new semantic technologies and trends.
- Tutorials describing the application of semantic technologies in specific domains (e.g., life-sciences, e-government, e-commerce, cultural heritage, etc.).
- Tutorials presenting techniques from other research fields that are of relevance for Semantic Web research especially in relationship to the tracks of the conference (e.g., techniques from social science, database techniques, NLP techniques etc.).

Tutorials can be half a day or a full day.

We advise having more than one presenter and no more than three, preferably from different institutions, bringing different perspectives to the tutorial topic.

Tutorials may focus entirely on theoretical aspects; however, we encourage organisers to incorporate hands-on sessions where appropriate. The tutorials should reach a good balance between the topic coverage and its relevance to the community.? ?

Timeline for Tutorials
-----------
Proposals due: Nov 22, 2013 - 23:59 Hawaii Time
Notification of acceptance: Dec 6, 2013 - 23:59 Hawaii Time
Tutorial Web site due: Dec 16, 2013 - 23:59 Hawaii Time
Camera-ready material due: Apr 25, 2014 - 23:59 Hawaii Time
Tutorial days: May 25 and May 26, 2014

Responsibilities
-----------
Organizers of accepted tutorials are responsible for preparing and maintaining a Web site that describes the tutorial and includes all relevant information. Organizers are also responsible for submitting the material for attendees (slide sets, additional teaching material, software installation and usage guides for practical hands-on sessions, etc.) to the Tutorial Chair. The 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 registration fee.


General Information
-----------
Each tutorial will 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 fees).
In the interest of the overall quality of the conference, the Tutorial Chair reserves the right to merge tutorials and/or adjust the scope thereof in case a mimimum number of registrations is not reached by the early registration deadline.

Submission details
-----------
Tutorial proposals should not exceed 5 pages, using an 11 pt font for the body of the text of the proposal and should contain the following information:

- Abstract (200 words maximum, for inclusion on the ESWC 2014 website).

- Tutorial description: 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 references to the material to be covered by the tutorial must be included.

- 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 for each length).

- Specify other venues to which the tutorial or part thereof has or will be presented, in addition to explaining how the current tutorial differs from the other editions. Links to the slides of those tutorial editions should be included in the proposal.

- Brief professional biography of the presenter(s) indicating previous training and speaking experience (such as teaching and tutorial presentation).

Each proposal will be reviewed by the members of the tutorial programme committee, and ranked based on the overall quality of the proposal and the tutorial's fit to the conference. Their recommendation will determine the final decision on the acceptance/rejection of each proposal.

Submission
-----------
Submission will be through the Easychair system (please note that it is the same site to submit workshops and tutorials)? https://www.easychair.org/conferences/?conf=eswc2014workshops-tutorials


Tutorials Chair
Nathalie Aussenac-Gilles (IRIT-CNRS, Toulouse, Fr)
email: [email protected]


------------------------------

_______________________________________________
protege-discussion mailing list
[email protected]
https://mailman.stanford.edu/mailman/listinfo/protege-discussion


End of protege-discussion Digest, Vol 88, Issue 5
*************************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.stanford.edu/pipermail/protege-discussion/attachments/20131114/a919f43e/attachment.html>

------------------------------

_______________________________________________
protege-discussion mailing list
[email protected]
https://mailman.stanford.edu/mailman/listinfo/protege-discussion


End of protege-discussion Digest, Vol 88, Issue 7
*************************************************
_______________________________________________
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