[
Lists Home |
Date Index |
Thread Index
]
Meta Object Protocol (MOP )
"Provides interfaces for product maintenance that allows you to define new
product classes,specify tje attributes
for them,create instances of htese classes and set the attributes values of
these instances"
The reflection protocol is a subset of MOP.
Where MOP is coming into picture in XML world.????
Pavithran
----- Original Message -----
From: "Owen Walcher" <news@owenwalcher.com>
To: "Jason Diamond" <jason@injektilo.org>; "Xml-Dev@Lists. Xml. Org"
<xml-dev@lists.xml.org>
Sent: Wednesday, February 12, 2003 11:33 PM
Subject: [xml-dev] what is MOPs?
> MOP comes from lisp (I think), not NeoCore. NeoCore is just a
> self-constructing XML database, but it supports XPATH and XQuery and
> (obviously) InfoSets.
>
> This is my dissertation topic, but MOP has been around a while. Most of
the
> stuff I am reading comes off either IEEE or ACM.
>
> For a quick overview, here are some links:
> http://iamwww.unibe.ch/~demeyer/Deme96m/psstmnt.html
> http://c2.com/cgi/wiki?MetaObjectProtocol
> http://www.elwoodcorp.com/alu/mop/contents.html
>
> Although this originally comes from LISP, which is a self-modifying
> language, it was my intent to implement using the Reflection capabilities
of
> Java or C#.
>
> The actual dissertation revolves around the *rules* to creating the XML
> Information Model.
>
> Owen
>
>
> -----Original Message-----
> From: Jason Diamond [mailto:jason@injektilo.org]
> Sent: Wednesday, February 12, 2003 10:25 AM
> To: Owen Walcher
> Subject: RE: [xml-dev] web services stack
>
>
> This is interesting. Where can we find out more about MOP? Is it
> specific to the NeoCore XMS? I didn't find any reference to it on their
> site.
>
> Thanks,
> Jason
>
> On Wed, 2003-02-12 at 09:02, Owen Walcher wrote:
> > >Zo, schtop mit da XML ist ein data model already!
> >
> > XML is *more* than a data model, it is an information model, where:
> >
> > data + context = information
> >
> > Adaptive application can be written (if certain XML modeling rules are
> > followed), that allow Meta Object Protocols (MOP) and Reflection to be
> used
> > to dynamically extend the runtime environment.
> >
> > The MOP and processing instructions (albeit language specific) can even
be
> > stored as XML documents. Combine all these documents in a self
> constructing
> > database (like the NeoCore XMS), and you have a fully extensible
> development
> > platform that supports heterogeneity quite well... all this with the XML
> 1.0
> > specification, without need for DTD... (Infosets required)
> >
> >
> > Owen
> >
> >
> >
> > -----------------------------------------------------------------
> > The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> > initiative of OASIS <http://www.oasis-open.org>
> >
> > The list archives are at http://lists.xml.org/archives/xml-dev/
> >
> > To subscribe or unsubscribe from this list use the subscription
> > manager: <http://lists.xml.org/ob/adm.pl>
> >
>
>
> -----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
>
> The list archives are at http://lists.xml.org/archives/xml-dev/
>
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://lists.xml.org/ob/adm.pl>
|
