[Attempto] Installation of local version of ACE view

[Eddy Vanderlinden]

Hello Kaarel,

Thanks for your time !

I needed some more time to reply since I had to synchronise the ontology via 
the webservice (until I can install it locally) to check what information I 
have today and which one I'm missing.
I'm principally interested in reading at this point in time.
Precisely because of the natural language facility (which is easier to 
"sell" to the end-user) and the limitations in creating the data properties.

The instance currAUD is referenced as follows:
    curr_AUD hasCurrencyAlphaCode "AUD" .
    curr_AUD hasCurrencyCountryCode "AU" .
    curr_AUD hasCurrencyCountryName "AUSTRALIA" .
    curr_AUD hasCurrencyName "Australian Dollar" .
    curr_AUD hasCurrencyNumericalCode 36 .
    curr_AUD is an ISO4217-Currencycodes .

36 being an integer, the other data properties being strings (last sentence 
is class-membership) .
This is more than fine to me.

On the level of the class description, I find the following:
    Every ISO4217-Currencycodes is an ISOCodes .
    Everything that is hasAsFacialCurrencied by something is an 
ISO4217-Currencycodes .
    Everything that is hasAsNationalCurrencied by something is an 
ISO4217-Currencycodes

Compared to the description in Protégé (see here-under) we could say some 
data is missing.

If I may make my list for Santa Claus in order of preference, I would say:
1. Increased performance.
Since the ontology is at only 20 % of the intended normal capacity (with 
only generic individuals unless they are needed as reference data for 
conceptualisation) the first wish would be the performance: probably through 
a local installation, but I leave it to others to judge of the best 
practice.
At today it takes an hour to run the 2MB ontology through the webservice 
with a high speed connection.

2. Operational reliability.
I would feel more confortable without the many external dependencies (see 
local installation topics which involve still external resources).
Perhaps a full installation package with everything needed included could be 
a solution.
At least the feeling of control would be enhanced.

3. In read: the class descriptions including the data properties
The same way as for the instances is fine. The range values could be 
replaced by the datatype e.g.

4. In manipulation modus of the ontology (remark it's the last preference 
since we have Protégé when we leave the manipulation to the specialists) we 
could create all desired properties.

Dear Kaarel, you're not Santa Claus, we know. So we can't expect you to 
provide all this, certainly not in a short notice.
But if I do never tell what my opinion is, no one can argue it. And from 
arguments for other priorities, I can learn too.

Thanks again for the fine tool we may use.

Kind regards

Eddy Vanderlinden

Properties of the ISO4217-Currencycodes class:
  <!-- http://www.fadyart.com/Finance.owl#hasCurrencyAlphaCode -->

    <owl:DatatypeProperty rdf:about="#hasCurrencyAlphaCode">
        <rdf:type rdf:resource="&owl;FunctionalProperty"/>
        <rdfs:comment xml:lang="en"
            >The 3-character alpha code of the currency.</rdfs:comment>
        <rdfs:domain rdf:resource="#ISO4217-Currencycodes"/>
        <rdfs:subPropertyOf rdf:resource="#ISOCurrency"/>
        <rdfs:range rdf:resource="&xsd;string"/>
    </owl:DatatypeProperty>



    <!--  
http://www.fadyart.com/Finance.owl#hasCurrencyAlphaCodeForCountry -->

    <owl:DatatypeProperty rdf:about="#hasCurrencyAlphaCodeForCountry">
        <rdf:type rdf:resource="&owl;FunctionalProperty"/>
        <rdfs:comment xml:lang="en"
            >The alpha code of the national currency for the referred 
country.</rdfs:comment>
        <rdfs:domain rdf:resource="#ISO3166-CountryCode"/>
        <rdfs:subPropertyOf rdf:resource="#ISO3166-CountryCodes"/>
        <rdfs:range rdf:resource="&xsd;string"/>
    </owl:DatatypeProperty>



    <!-- http://www.fadyart.com/Finance.owl#hasCurrencyCountryCode -->

    <owl:DatatypeProperty rdf:about="#hasCurrencyCountryCode">
        <rdf:type rdf:resource="&owl;FunctionalProperty"/>
        <rdfs:comment xml:lang="en"
            >The country ISO-code where the currency is used.</rdfs:comment>
        <rdfs:domain rdf:resource="#ISO4217-Currencycodes"/>
        <rdfs:subPropertyOf rdf:resource="#ISOCurrency"/>
        <rdfs:range rdf:resource="&xsd;string"/>
    </owl:DatatypeProperty>



    <!-- http://www.fadyart.com/Finance.owl#hasCurrencyCountryName -->

    <owl:DatatypeProperty rdf:about="#hasCurrencyCountryName">
        <rdf:type rdf:resource="&owl;FunctionalProperty"/>
        <rdfs:comment xml:lang="en"
            >The country name where the currency is used.</rdfs:comment>
        <rdfs:domain rdf:resource="#ISO4217-Currencycodes"/>
        <rdfs:subPropertyOf rdf:resource="#ISOCurrency"/>
        <rdfs:range rdf:resource="&xsd;string"/>
    </owl:DatatypeProperty>



    <!-- http://www.fadyart.com/Finance.owl#hasCurrencyName -->

    <owl:DatatypeProperty rdf:about="#hasCurrencyName">
        <rdf:type rdf:resource="&owl;FunctionalProperty"/>
        <rdfs:comment xml:lang="en"
            >The currency name</rdfs:comment>
        <rdfs:domain rdf:resource="#ISO4217-Currencycodes"/>
        <rdfs:subPropertyOf rdf:resource="#ISOCurrency"/>
        <rdfs:range rdf:resource="&xsd;string"/>
    </owl:DatatypeProperty>



    <!-- http://www.fadyart.com/Finance.owl#hasCurrencyNumericalCode -->

    <owl:DatatypeProperty rdf:about="#hasCurrencyNumericalCode">
        <rdf:type rdf:resource="&owl;FunctionalProperty"/>
        <rdfs:comment xml:lang="en"
            >The currency numerical code</rdfs:comment>
        <rdfs:domain rdf:resource="#ISO4217-Currencycodes"/>
        <rdfs:subPropertyOf rdf:resource="#ISOCurrency"/>
        <rdfs:range rdf:resource="&xsd;int"/>
    </owl:DatatypeProperty>





----- Original Message ----- 
From: "Kaarel Kaljurand" <kaljurand at gmail.com>
To: <attempto at lists.ifi.uzh.ch>
Cc: "Eddy Vanderlinden" <info at fadyart.com>
Sent: Thursday, April 23, 2009 10:44 PM
Subject: Re: [Attempto] Installation of local version of ACE view


> Hi,
>
> On Tue, Apr 21, 2009 at 05:58, Eddy Vanderlinden <info at fadyart.com> wrote:
>>
>> Would you have a planning for including the data properties in ACE ?
>>
>
> In ACE, there is no notion of data properties, instead there are nouns,
> verbs, of-constructions, etc. As there are in English.
>
> For the ACE->OWL mapping, we have tried to find a bidirectional
> but still natural way to map between the world of OWL and the world
> of ACE (= English), but this doesn't really work out nicely in all the 
> cases,
> e.g. in the case of data properties.
>
> Currently, a transitive verb, of-construction, or transitive adjective
> is mapped to a data property if its argument is a number or a string.
> So, some data property constructs are supported.
> For example:
>
> John's age is 33.
>
> is mapped to:
>
> DataPropertyAssertion(age John "33"^^xsd:integer)
>
> The idea of checking the type of the argument unfortunately
> doesn't work in the case of the functionality, range, etc. axioms.
>
> The ACE View solution is to fall back to whatever Protege provides
> for entering such axioms. E.g. you can tick the functionality checkbox to
> make your data property functional.
>
> To answer your original question: there are no immediate plans to do 
> anything
> about the way the data properties are currently handled.
>
> Questions back to you:
>
> * Which data property constructs are you interested in using?
>
> * Which English sentence would you like to use to express these
> constructs?
>
> --
> kaarel