[Zope3-dev] "Sub interface"

[Terry Hancock]

On Sunday 29 February 2004 11:19 am, Jim Fulton wrote:
> I forgot to mention that Zope 2.8 will make this easier by
> including Zope 3 interfaces and replacing the Zope 2 interfaces
> package to use the facade.  We will also update the software than
> is includes with Zope 2 to use zope.interface.

That sounds like the right thing to do then.  I suspect (though I have
not had time to prove it to myself), that Zope 3 will allow me to
cut my product down considerably, so I'm probably going to
be migrating to Zope 3.

But it's not time yet.  Thanks for the installation instructions to use
Zope 3 interfaces in Zope 2, as that's clearly what I need to do.

I gotta say though, I recoil at the distinction between "schemas"
and "interfaces".  IMHO, they're still "interfaces" -- the idea that
attributes shouldn't be part of an interface seems unnatural
to me, like some idea grafted from another language.   I approve
of the fact that they're integrated in Zope 3, though.  I guess I
can lie with it as a synonym.

But I personally reserve the word "schema" for relational databases
and XML schemas -- that's a word getting too overloaded. ;-)

One question about the schema module -- when we specify that
a field is, say, a "Tuple" are we requiring that it literally "is-a" tuple,
or that it merely "acts-like-a" tuple? (I.e. are we testing "type" or
"interface"?).  I really prefer the latter. 

Does that mean I should *always* use the "Object" field and
specify the interface as "schema", or is that merely duplicating
the schema module's code?

Thanks,
Terry

--
Terry Hancock ( hancock at anansispaceworks.com )
Anansi Spaceworks  http://www.anansispaceworks.com