Some thoughts on the interaction with a Moose server retained from the discussion with Anne and Vincent (it was also Vincent in my previous mail but i misspelt :-).
With the current implementation, one can start by interacting with a model at any level (allClasses, allMethods, etc.) and then narrow his search on an entity or a set of entities. Every entity returns in the results the list of msgs it implements. We are working on how to correctly choose a specific moose entity from the returned collection (see my previous mail).
Scoping information is essential to correctly identify/find an entity. So scoping information can be retained by the way user interacts with the server. For example: http://mooseserver/allPackage/first/allClasses/first/allMethod/first But that would mean interaction is restrictive, one has to start with the highest level of container (allPackages in java) and drill down to search for the required entity. Not retained.
Nicolas P. suggested to keep a way to search entities by their mooseIDs as well so we'll implement it as well.
Specify the number of entities to return.
Be able to specify an element by its position in the collection returned. http://mooseserver/allPackage/3/allClasses
What do you think?
Usman
I see space to investigate the use of a graph database such as http://www.neo4j.org in order to store the model. The Moose model is "just" a graph.
Did you investigate it?
On Wed, Jun 5, 2013 at 4:40 PM, Usman Bhatti usman.bhatti@gmail.com wrote:
Some thoughts on the interaction with a Moose server retained from the discussion with Anne and Vincent (it was also Vincent in my previous mail but i misspelt :-).
With the current implementation, one can start by interacting with a model at any level (allClasses, allMethods, etc.) and then narrow his search on an entity or a set of entities. Every entity returns in the results the list of msgs it implements. We are working on how to correctly choose a specific moose entity from the returned collection (see my previous mail).
Scoping information is essential to correctly identify/find an entity. So scoping information can be retained by the way user interacts with the server. For example: http://mooseserver/allPackage/first/allClasses/first/allMethod/first But that would mean interaction is restrictive, one has to start with the highest level of container (allPackages in java) and drill down to search for the required entity. Not retained.
Nicolas P. suggested to keep a way to search entities by their mooseIDs as well so we'll implement it as well.
Specify the number of entities to return.
Be able to specify an element by its position in the collection returned. http://mooseserver/allPackage/3/allClasses
What do you think?
Usman
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
usman
We should discuss with olivier too.
We could have
http://mooseserver/allPackage = named: #Graphics/class=named: Point/
or
http://mooseserver/get?Graphics::Point::x
This idea of first is totally bogus and we should not use it.
In Moose we got uniqueNames for all the entities based on their structural relationship
Graphics::Point::x denotes a unique entity.
Stef
On Jun 5, 2013, at 4:40 PM, Usman Bhatti usman.bhatti@gmail.com wrote:
Some thoughts on the interaction with a Moose server retained from the discussion with Anne and Vincent (it was also Vincent in my previous mail but i misspelt :-).
With the current implementation, one can start by interacting with a model at any level (allClasses, allMethods, etc.) and then narrow his search on an entity or a set of entities. Every entity returns in the results the list of msgs it implements. We are working on how to correctly choose a specific moose entity from the returned collection (see my previous mail).
Scoping information is essential to correctly identify/find an entity. So scoping information can be retained by the way user interacts with the server. For example: http://mooseserver/allPackage/first/allClasses/first/allMethod/first But that would mean interaction is restrictive, one has to start with the highest level of container (allPackages in java) and drill down to search for the required entity. Not retained.
Nicolas P. suggested to keep a way to search entities by their mooseIDs as well so we'll implement it as well.
Specify the number of entities to return.
Be able to specify an element by its position in the collection returned. http://mooseserver/allPackage/3/allClasses
What do you think?
Usman
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
On Wed, Jun 5, 2013 at 9:33 PM, Stéphane Ducasse stephane.ducasse@inria.frwrote:
usman
We should discuss with olivier too.
Yes.
We could have
http://mooseserver/allPackage = named: #Graphics/class=named: Point/
or
http://mooseserver/http://mooseserver/allPackage%20=%20named:%20#Graphics/class=named:%20Point/ get?Graphics::Point::x
This idea of first is totally bogus and we should not use it.
ok.
In Moose we got uniqueNames for all the entities based on their structural relationship
Graphics::Point::x denotes a unique entity.
Yes. The idea of searching in a group of entities rather than a complete model is interesting. I think I'll spend a day tomorrow working with Vincent to construct different navigation scenarios.
Stef
On Jun 5, 2013, at 4:40 PM, Usman Bhatti usman.bhatti@gmail.com wrote:
Some thoughts on the interaction with a Moose server retained from the discussion with Anne and Vincent (it was also Vincent in my previous mail but i misspelt :-).
With the current implementation, one can start by interacting with a model at any level (allClasses, allMethods, etc.) and then narrow his search on an entity or a set of entities. Every entity returns in the results the list of msgs it implements. We are working on how to correctly choose a specific moose entity from the returned collection (see my previous mail).
Scoping information is essential to correctly identify/find an entity. So scoping information can be retained by the way user interacts with the server. For example: http://mooseserver/allPackage/first/allClasses/first/allMethod/first But that would mean interaction is restrictive, one has to start with the highest level of container (allPackages in java) and drill down to search for the required entity. Not retained.
Nicolas P. suggested to keep a way to search entities by their mooseIDs as well so we'll implement it as well.
Specify the number of entities to return.
Be able to specify an element by its position in the collection returned. http://mooseserver/allPackage/3/allClasses
What do you think?
Usman
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-
Andre Hora -
Ben Coman -
Stéphane Ducasse -
Usman Bhatti