called, or if we
allow inconsistent data like the rest of the meta model does.
From: pd_aficion...@hotmail.com
To: user@lists.neo4j.org
Date: Thu, 8 Apr 2010 23:52:02 +0200
Subject: Re: [Neo] meta meta classes
I think the best solution here is to have an instance enumeration
: Tue, 30 Mar 2010 09:30:10 +0200
From: matt...@neotechnology.com
To: user@lists.neo4j.org
Subject: Re: [Neo] meta meta classes
Would making the underlying Node publically available (via a getter) be
virtually the same thing? In that case the meta model classes could have
such a getter
model of Neo4J.
Kind regards,
Niels Hoogeveen
Date: Thu, 8 Apr 2010 11:37:37 +0200
From: matt...@neotechnology.com
To: user@lists.neo4j.org
Subject: Re: [Neo] meta meta classes
2010/3/30 Niels Hoogeveen pd_aficion...@hotmail.com
MetaModelObject already has a getter (without using
the
country class this specific sub-division class applies to.
Still, it requires each country to be defined as both a class and an instance.
Date: Thu, 8 Apr 2010 19:15:30 +0200
From: matt...@neotechnology.com
To: user@lists.neo4j.org
Subject: Re: [Neo] meta meta classes
So, you describe
at all?
Date: Thu, 8 Apr 2010 19:15:30 +0200
From: matt...@neotechnology.com
To: user@lists.neo4j.org
Subject: Re: [Neo] meta meta classes
So, you describe the model (with country, sub-division and
has-sub-division) which is OK! Then you not just want to add data which
would conform
: Re: [Neo] meta meta classes
2010/4/8 Niels Hoogeveen pd_aficion...@hotmail.com
Your point about the cardinality restriction is a correct observation.
In fact it would be better to create a is-subdivision-of PropertyType on
sub-division and give that a range country with a cardinality
To: user@lists.neo4j.org
Subject: Re: [Neo] meta meta classes
2010/4/8 Niels Hoogeveen pd_aficion...@hotmail.com
Your point about the cardinality restriction is a correct observation.
In fact it would be better to create a is-subdivision-of PropertyType
on
sub-division and give
Date: Thu, 8 Apr 2010 22:33:11 +0200
From: matt...@neotechnology.com
To: user@lists.neo4j.org
Subject: Re: [Neo] meta meta classes
Ok now I get your point! Thank you for clarifying.
Your singleton proposal could be a good idea then. Could it
potentially be a hindrance in some scenario
: neubauer.pe...@gmail.com
Date: Fri, 26 Mar 2010 17:25:01 +0100
To: user@lists.neo4j.org
Subject: Re: [Neo] meta meta classes
Awesome Niels!
maybe you could blog or document some cool example on this?
Cheers,
/peter neubauer
COO and Sales, Neo Technology
GTalk
From: matt...@neotechnology.com
To: user@lists.neo4j.org
Subject: Re: [Neo] meta meta classes
Would making the underlying Node publically available (via a getter) be
virtually the same thing? In that case the meta model classes could have
such a getter.
2010/3/26 Niels Hoogeveen pd_aficion
that would
allow the modeling of the properties of a Relationship.
Kind regards,
Niels Hoogeveen
Date: Fri, 26 Mar 2010 11:26:29 +0100
From: matt...@neotechnology.com
To: user@lists.neo4j.org
Subject: Re: [Neo] meta meta classes
That's an interresting case you've got here and it looks to me like
: Re: [Neo] meta meta classes
The class as object phenomenon is actually quite pervasive, and I think it is
possible to have a generalized solution for it.
After sending this email yesterday, I came up with a slightly different
solution.
val taggable = namespace.getMetaClass(taggable
Date: Fri, 26 Mar 2010 14:38:08 +0100
Subject: Re: [Neo] meta meta classes
Or, and this probably the simplest solution. Let a MetaModelThing implement
the Node interface. This allows a class to be an instance of another class
and/or a SubType of another class.
From: pd_aficion
!
-Original Message-
From: Niels Hoogeveen pd_aficion...@hotmail.com
Date: Fri, 26 Mar 2010 15:20:15
To: user@lists.neo4j.org
Subject: Re: [Neo] meta meta classes
Making MetaModelThing implement the Node interface is actually orthogonal to
the creation of Shadow objects. Though it does make
Date: Fri, 26 Mar 2010 14:29:03 +
Subject: Re: [Neo] meta meta classes
Such are the joys and challenges of frameworks and abstractions. Sometimes
you do need to get close to the metal though, to achieve specific
functional and performance requirements. Thus the reason open source
...@burningskysoftware.com
Date: Fri, 26 Mar 2010 14:29:03 +
Subject: Re: [Neo] meta meta classes
Such are the joys and challenges of frameworks and abstractions. Sometimes
you do need to get close to the metal though, to achieve specific
functional and performance requirements. Thus the reason open
Very cool.
-Original Message-
From: Niels Hoogeveen pd_aficion...@hotmail.com
Date: Fri, 26 Mar 2010 17:22:41
To: user@lists.neo4j.org
Subject: Re: [Neo] meta meta classes
Using Scala, I was actually able to extend MetaModelThing to act as a Node and
MetaModelClass to have
regards,
Niels Hoogeveen
From: neubauer.pe...@gmail.com
Date: Fri, 26 Mar 2010 17:25:01 +0100
To: user@lists.neo4j.org
Subject: Re: [Neo] meta meta classes
Awesome Niels!
maybe you could blog or document some cool example on this?
Cheers,
/peter neubauer
COO and Sales, Neo Technology
://github.com/NielsHoogeveen/Scala-Neo4j-utils
Kind regards,
Niels Hoogeveen
From: neubauer.pe...@gmail.com
Date: Fri, 26 Mar 2010 17:25:01 +0100
To: user@lists.neo4j.org
Subject: Re: [Neo] meta meta classes
Awesome Niels!
maybe you could blog or document some cool example on this?
Cheers
For my application, I want to model an HTML template in Neo4J, using the
MetaModel api.
So I started setting up MetaModelClasses for the various HTML entities.
e.g. (code in Scala)
val classProp = namespace.getMetaProperty(class, true)
val idProp =
namespace.getMetaProperty(id, true)
20 matches
Mail list logo
