Build 318 still has problem with hasValue restriction editing

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Build 318 still has problem with hasValue restriction editing

Mark Feblowitz
It looks like selecting a hasValue restriction is still broken.
Navigating to the selected value results in the value being placed in
the "Filler" dialog, but an error is reported:
       
        Error: Encountered "Processed" at line 1, column 1. Was expecting
one of: <CLASS_ID> ... "*" ... "?" ... ">" ... "<" ... "=" ... "!"
... "{" ... at ""

("Processed" is the name of the Individual that was selected via the
Instance browser).

I am able to insert the hasValue restriction in the Owl file, and it
is displayed correctly, so I suspect the problem is with editing.

BTW, the Owl Plugin build number is reported as 311, while the
Protege build number is 318.

-------------------------------------------------------------------------
To unsubscribe go to http://protege.stanford.edu/community/subscribe.html

Reply | Threaded
Open this post in threaded view
|

Re: Build 318 still has problem with hasValue restriction editing

Nick Drummond
Mark,

I'm not quite sure what you are doing to cause this problem. Could you
please clarify. I tried creating a hasValue restriction using the Logic
view and "Create restriction" and it was fine. I tried this with both
Obj and DT props. What do you mean by "navigating to the selected value"?

BTW - the build scripts should increment this automatically - I suspect
something has gone awry.

Nick

Mark Feblowitz wrote:

> It looks like selecting a hasValue restriction is still broken.
> Navigating to the selected value results in the value being placed in
> the "Filler" dialog, but an error is reported:
>    
>     Error: Encountered "Processed" at line 1, column 1. Was expecting
> one of: <CLASS_ID> ... "*" ... "?" ... ">" ... "<" ... "=" ... "!" ...
> "{" ... at ""
>
> ("Processed" is the name of the Individual that was selected via the
> Instance browser).
>
> I am able to insert the hasValue restriction in the Owl file, and it
> is displayed correctly, so I suspect the problem is with editing.
>
> BTW, the Owl Plugin build number is reported as 311, while the Protege
> build number is 318.
>
> -------------------------------------------------------------------------
> To unsubscribe go to http://protege.stanford.edu/community/subscribe.html
>
>

--

Nick Drummond

http://www.cs.man.ac.uk/~drummond/ <http://www.cs.man.ac.uk/%7Edrummond/>
-------------------------------------------------------------------------
To unsubscribe go to http://protege.stanford.edu/community/subscribe.html

Reply | Threaded
Open this post in threaded view
|

Re: Build 318 still has problem with hasValue restriction editing

Mark Feblowitz
I'm not sure what's different. I go through what I would expect to be
the "normal" steps. In the Properties view I select a property, add a
restriction, select the "hasValue" restriction, press the instance
icon, select an individual for the hasValue restriction, and that
value is flagged as an error, with a message that indicates that the
value is not a class (or a number of other options that lead me to
believe that the value is being parsed/interpreted as if it were,
e.g., allValuesFrom restriction. I am able to type in a class name
and that class name is accepted. I then have to edit the source to
replace the class name with the name of an individual.

If I'm the only one seeing this behavior, then there must be some
other characteristic of my configuration (some errant plugin?) or my
ontologies (the types of imports?) triggering this behavior. I'll
check and see if there's an exception generated when this happens (I doubt it).

What else can I tell/show you to demonstrate what's going on?

Mark


At 07:56 AM 4/21/2006, you wrote:

>Mark,
>
>I'm not quite sure what you are doing to cause this problem. Could
>you please clarify. I tried creating a hasValue restriction using
>the Logic view and "Create restriction" and it was fine. I tried
>this with both Obj and DT props. What do you mean by "navigating to
>the selected value"?
>
>BTW - the build scripts should increment this automatically - I
>suspect something has gone awry.
>
>Nick
>
>Mark Feblowitz wrote:
>>It looks like selecting a hasValue restriction is still broken.
>>Navigating to the selected value results in the value being placed
>>in the "Filler" dialog, but an error is reported:
>>
>>     Error: Encountered "Processed" at line 1, column 1. Was
>> expecting one of: <CLASS_ID> ... "*" ... "?" ... ">" ... "<" ...
>> "=" ... "!" ... "{" ... at ""
>>
>>("Processed" is the name of the Individual that was selected via
>>the Instance browser).
>>
>>I am able to insert the hasValue restriction in the Owl file, and
>>it is displayed correctly, so I suspect the problem is with editing.
>>
>>BTW, the Owl Plugin build number is reported as 311, while the
>>Protege build number is 318.
>>
>>-------------------------------------------------------------------------
>>To unsubscribe go to http://protege.stanford.edu/community/subscribe.html
>>
>
>--
>
>Nick Drummond
>
>http://www.cs.man.ac.uk/~drummond/ <http://www.cs.man.ac.uk/%7Edrummond/>
>-------------------------------------------------------------------------
>To unsubscribe go to http://protege.stanford.edu/community/subscribe.html

-------------------------------------------------------------------------
To unsubscribe go to http://protege.stanford.edu/community/subscribe.html

Reply | Threaded
Open this post in threaded view
|

Re: Build 318 still has problem with hasValue restriction editing

Nick Drummond
Mark,

I've just tried this in 318 with the Properties view and it all works  
as expected.
Have you got metaclasses in your ontology or are the instances you've  
selected instances of something else (ie not just named OWL classes)???
The property must be an object property or you wouldn't be able to  
add an individual at all. What is the exact message?
Does this happen on a new empty ontology??
If so, reinstall the basics + OWL and try again.
Or send me your ontolgy

Nick

On 10 May 2006, at 12:30, Mark Feblowitz wrote:

> I'm not sure what's different. I go through what I would expect to  
> be the "normal" steps. In the Properties view I select a property,  
> add a restriction, select the "hasValue" restriction, press the  
> instance icon, select an individual for the hasValue restriction,  
> and that value is flagged as an error, with a message that  
> indicates that the value is not a class (or a number of other  
> options that lead me to believe that the value is being parsed/
> interpreted as if it were, e.g., allValuesFrom restriction. I am  
> able to type in a class name and that class name is accepted. I  
> then have to edit the source to replace the class name with the  
> name of an individual.
>
> If I'm the only one seeing this behavior, then there must be some  
> other characteristic of my configuration (some errant plugin?) or  
> my ontologies (the types of imports?) triggering this behavior.  
> I'll check and see if there's an exception generated when this  
> happens (I doubt it).
>
> What else can I tell/show you to demonstrate what's going on?
>
> Mark
>
>
> At 07:56 AM 4/21/2006, you wrote:
>> Mark,
>>
>> I'm not quite sure what you are doing to cause this problem. Could  
>> you please clarify. I tried creating a hasValue restriction using  
>> the Logic view and "Create restriction" and it was fine. I tried  
>> this with both Obj and DT props. What do you mean by "navigating  
>> to the selected value"?
>>
>> BTW - the build scripts should increment this automatically - I  
>> suspect something has gone awry.
>>
>> Nick
>>
>> Mark Feblowitz wrote:
>>> It looks like selecting a hasValue restriction is still broken.  
>>> Navigating to the selected value results in the value being  
>>> placed in the "Filler" dialog, but an error is reported:
>>>
>>>     Error: Encountered "Processed" at line 1, column 1. Was  
>>> expecting one of: <CLASS_ID> ... "*" ... "?" ... ">" ... "<" ...  
>>> "=" ... "!" ... "{" ... at ""
>>>
>>> ("Processed" is the name of the Individual that was selected via  
>>> the Instance browser).
>>>
>>> I am able to insert the hasValue restriction in the Owl file, and  
>>> it is displayed correctly, so I suspect the problem is with editing.
>>>
>>> BTW, the Owl Plugin build number is reported as 311, while the  
>>> Protege build number is 318.
>>>
>>> --------------------------------------------------------------------
>>> -----
>>> To unsubscribe go to http://protege.stanford.edu/community/ 
>>> subscribe.html
>>>
>>
>> --
>>
>> Nick Drummond
>>
>> http://www.cs.man.ac.uk/~drummond/ <<a href="http://www.cs.man.ac.uk/%">http://www.cs.man.ac.uk/% 
>> 7Edrummond/>
>> ---------------------------------------------------------------------
>> ----
>> To unsubscribe go to http://protege.stanford.edu/community/ 
>> subscribe.html
>
> ----------------------------------------------------------------------
> ---
> To unsubscribe go to http://protege.stanford.edu/community/ 
> subscribe.html
>

-------------------------------------------------------------------------
To unsubscribe go to http://protege.stanford.edu/community/subscribe.html

Reply | Threaded
Open this post in threaded view
|

Re: Build 318 still has problem with hasValue restriction editing

Mark Feblowitz
Ok -

Here's the scoop:

I installed Basic+Owl and the problem was still there.
I reinstalled Basic+Owl after removing the Plugins directory and the
problem was still there.
I reinstalled Basic+Owl after removing the entire Protege 3.2 Beta
folder and the problem went away.

Install might be leaving around some old library or configuration
file that triggers this problem.

I wonder how many other problems will go away with this change.

Mark


At 01:49 PM 5/10/2006, Nick Drummond wrote:

>Mark,
>
>I've just tried this in 318 with the Properties view and it all works
>as expected.
>Have you got metaclasses in your ontology or are the instances you've
>selected instances of something else (ie not just named OWL classes)???
>The property must be an object property or you wouldn't be able to
>add an individual at all. What is the exact message?
>Does this happen on a new empty ontology??
>If so, reinstall the basics + OWL and try again.
>Or send me your ontolgy
>
>Nick
>
>On 10 May 2006, at 12:30, Mark Feblowitz wrote:
>
>>I'm not sure what's different. I go through what I would expect to
>>be the "normal" steps. In the Properties view I select a property,
>>add a restriction, select the "hasValue" restriction, press the
>>instance icon, select an individual for the hasValue restriction,
>>and that value is flagged as an error, with a message that
>>indicates that the value is not a class (or a number of other
>>options that lead me to believe that the value is being parsed/
>>interpreted as if it were, e.g., allValuesFrom restriction. I am
>>able to type in a class name and that class name is accepted. I
>>then have to edit the source to replace the class name with the
>>name of an individual.
>>
>>If I'm the only one seeing this behavior, then there must be some
>>other characteristic of my configuration (some errant plugin?) or
>>my ontologies (the types of imports?) triggering this behavior.
>>I'll check and see if there's an exception generated when this
>>happens (I doubt it).
>>
>>What else can I tell/show you to demonstrate what's going on?
>>
>>Mark
>>
>>
>>At 07:56 AM 4/21/2006, you wrote:
>>>Mark,
>>>
>>>I'm not quite sure what you are doing to cause this problem. Could
>>>you please clarify. I tried creating a hasValue restriction using
>>>the Logic view and "Create restriction" and it was fine. I tried
>>>this with both Obj and DT props. What do you mean by "navigating
>>>to the selected value"?
>>>
>>>BTW - the build scripts should increment this automatically - I
>>>suspect something has gone awry.
>>>
>>>Nick
>>>
>>>Mark Feblowitz wrote:
>>>>It looks like selecting a hasValue restriction is still broken.
>>>>Navigating to the selected value results in the value being
>>>>placed in the "Filler" dialog, but an error is reported:
>>>>
>>>>     Error: Encountered "Processed" at line 1, column 1. Was
>>>>expecting one of: <CLASS_ID> ... "*" ... "?" ... ">" ... "<" ...
>>>>"=" ... "!" ... "{" ... at ""
>>>>
>>>>("Processed" is the name of the Individual that was selected via
>>>>the Instance browser).
>>>>
>>>>I am able to insert the hasValue restriction in the Owl file, and
>>>>it is displayed correctly, so I suspect the problem is with editing.
>>>>
>>>>BTW, the Owl Plugin build number is reported as 311, while the
>>>>Protege build number is 318.
>>>>
>>>>-------------------------------------------------------------------- -----
>>>>To unsubscribe go to http://protege.stanford.edu/community/ subscribe.html
>>>
>>>--
>>>
>>>Nick Drummond
>>>
>>>http://www.cs.man.ac.uk/~drummond/ <<a href="http://www.cs.man.ac.uk/%">http://www.cs.man.ac.uk/% 7Edrummond/>
>>>--------------------------------------------------------------------- ----
>>>To unsubscribe go to http://protege.stanford.edu/community/ subscribe.html
>>
>>---------------------------------------------------------------------- ---
>>To unsubscribe go to http://protege.stanford.edu/community/ subscribe.html
>
>-------------------------------------------------------------------------
>To unsubscribe go to http://protege.stanford.edu/community/subscribe.html

-------------------------------------------------------------------------
To unsubscribe go to http://protege.stanford.edu/community/subscribe.html

Reply | Threaded
Open this post in threaded view
|

Re: Build 318 still has problem with hasValue restriction editing

Nick Drummond
I hope all of them (!) :)

Nick

On 11 May 2006, at 01:01, Mark Feblowitz wrote:

> Ok -
>
> Here's the scoop:
>
> I installed Basic+Owl and the problem was still there.
> I reinstalled Basic+Owl after removing the Plugins directory and  
> the problem was still there.
> I reinstalled Basic+Owl after removing the entire Protege 3.2 Beta  
> folder and the problem went away.
>
> Install might be leaving around some old library or configuration  
> file that triggers this problem.
>
> I wonder how many other problems will go away with this change.
>
> Mark
>
>
> At 01:49 PM 5/10/2006, Nick Drummond wrote:
>> Mark,
>>
>> I've just tried this in 318 with the Properties view and it all works
>> as expected.
>> Have you got metaclasses in your ontology or are the instances you've
>> selected instances of something else (ie not just named OWL  
>> classes)???
>> The property must be an object property or you wouldn't be able to
>> add an individual at all. What is the exact message?
>> Does this happen on a new empty ontology??
>> If so, reinstall the basics + OWL and try again.
>> Or send me your ontolgy
>>
>> Nick
>>
>> On 10 May 2006, at 12:30, Mark Feblowitz wrote:
>>
>>> I'm not sure what's different. I go through what I would expect to
>>> be the "normal" steps. In the Properties view I select a property,
>>> add a restriction, select the "hasValue" restriction, press the
>>> instance icon, select an individual for the hasValue restriction,
>>> and that value is flagged as an error, with a message that
>>> indicates that the value is not a class (or a number of other
>>> options that lead me to believe that the value is being parsed/  
>>> interpreted as if it were, e.g., allValuesFrom restriction. I am
>>> able to type in a class name and that class name is accepted. I
>>> then have to edit the source to replace the class name with the
>>> name of an individual.
>>>
>>> If I'm the only one seeing this behavior, then there must be some
>>> other characteristic of my configuration (some errant plugin?) or
>>> my ontologies (the types of imports?) triggering this behavior.
>>> I'll check and see if there's an exception generated when this
>>> happens (I doubt it).
>>>
>>> What else can I tell/show you to demonstrate what's going on?
>>>
>>> Mark
>>>
>>>
>>> At 07:56 AM 4/21/2006, you wrote:
>>>> Mark,
>>>>
>>>> I'm not quite sure what you are doing to cause this problem. Could
>>>> you please clarify. I tried creating a hasValue restriction using
>>>> the Logic view and "Create restriction" and it was fine. I tried
>>>> this with both Obj and DT props. What do you mean by "navigating
>>>> to the selected value"?
>>>>
>>>> BTW - the build scripts should increment this automatically - I
>>>> suspect something has gone awry.
>>>>
>>>> Nick
>>>>
>>>> Mark Feblowitz wrote:
>>>>> It looks like selecting a hasValue restriction is still broken.
>>>>> Navigating to the selected value results in the value being
>>>>> placed in the "Filler" dialog, but an error is reported:
>>>>>
>>>>>     Error: Encountered "Processed" at line 1, column 1. Was
>>>>> expecting one of: <CLASS_ID> ... "*" ... "?" ... ">" ... "<" ...
>>>>> "=" ... "!" ... "{" ... at ""
>>>>>
>>>>> ("Processed" is the name of the Individual that was selected via
>>>>> the Instance browser).
>>>>>
>>>>> I am able to insert the hasValue restriction in the Owl file, and
>>>>> it is displayed correctly, so I suspect the problem is with  
>>>>> editing.
>>>>>
>>>>> BTW, the Owl Plugin build number is reported as 311, while the
>>>>> Protege build number is 318.
>>>>>
>>>>> ------------------------------------------------------------------
>>>>> -- -----
>>>>> To unsubscribe go to http://protege.stanford.edu/community/ 
>>>>> subscribe.html
>>>>
>>>> --
>>>>
>>>> Nick Drummond
>>>>
>>>> http://www.cs.man.ac.uk/~drummond/ <<a href="http://www.cs.man.ac.uk/%">http://www.cs.man.ac.uk/% 
>>>> 7Edrummond/>
>>>> -------------------------------------------------------------------
>>>> -- ----
>>>> To unsubscribe go to http://protege.stanford.edu/community/ 
>>>> subscribe.html
>>>
>>> --------------------------------------------------------------------
>>> -- ---
>>> To unsubscribe go to http://protege.stanford.edu/community/ 
>>> subscribe.html
>>
>> ---------------------------------------------------------------------
>> ----
>> To unsubscribe go to http://protege.stanford.edu/community/ 
>> subscribe.html
>
> ----------------------------------------------------------------------
> ---
> To unsubscribe go to http://protege.stanford.edu/community/ 
> subscribe.html
>

-------------------------------------------------------------------------
To unsubscribe go to http://protege.stanford.edu/community/subscribe.html