- Zope - Zope lists

- Accessing objects in subfolders
by Michael Grinder 11 Jan '99

11 Jan '99

I have a subfolder containing Documents and SQL Methods related to a certain database table I'm using. I want to access the SQL methods from the parent folder. I've tried the following:  But this causes an error. How do I access the subfolder objects in dtml? Michael Grinder

4 3

Re: [Zope] - Welcome aboard...
by Ken Manheimer 10 Jan '99

10 Jan '99

> I'd like to formally welcome two new and talented people to the Digital > Creations team!! Both Ken Manheimer and Michel Pelletier are joining > us. Thanks, rob! I'm looking forward to diving in! As some of you know, i've been centrally involved in the operation of python.org and the PSA. All along the way i've been extremely interested in how to effectively channel the energy of the community to the benefit of that community. In open source efforts, it's especially in the interest of both the users and the company to bring users into the process of improving the product. The interesting thing in *this* project is that the product in question, zope, is itself a tool for fostering community resources and access. If we can apply it well, then the process of improving it *itself* improves! The question then is how best to exploit this potential, how bet to support the community and the central developers. I have some ideas, and i'm know the folks at digital creations, and on the mailing list, have some, also. Yow. I'm going to be scrambling to tie things up at CNRI for the next few weeks, but will be checking mail at digital creations in the meanwhile, and will be happy to answer questions when i have the time. However, due to CNRI's government contracts, while i'm working there i'm not permitted to work on outside jobs, even on my own time. (It's good for me to concentrate on the wrap up at CNRI, in any case.) Also, i'll be out of town and completely out of touch next weekend - so don't be surprised if my response time is sluggish (or very sluggish), until i really make the switch. I'm looking forwards to working with you all! Onwards, Ken Manheimer klm(a)digicool.com

1 0

- Compilation problems...
by Magnus Lie Hetland 09 Jan '99

09 Jan '99

I have successfully managed to compile Zope under SunOS, but I recently tried under FreeBSD, and got the following problem: make -f ./Makefile.pre.in VPATH=. srcdir=. \ VERSION=$VERSION \ installdir=$installdir \ exec_installdir=$exec_installdir \ Makefile make[1]: Entering directory `/amd/vier/home/stud/f/mlh/zope/lib/python' make[1]: *** No rule to make target `/home/stud/f/mlh/zope/Python-1.5.1//lib/python1.5/config/Makefile', needed by `sedscript'. Stop. make[1]: Leaving directory `/amd/vier/home/stud/f/mlh/zope/lib/python' make: *** [boot] Error 2 Traceback (innermost last): File "wo_pcgi.py", line 112, in ? File "/amd/vier/home/stud/f/mlh/zope/build_extensions.py", line 108, in ? make('lib','python') File "/amd/vier/home/stud/f/mlh/zope/do.py", line 117, in make do('make -f Makefile.pre.in boot PYTHON=%s' % sys.executable) File "/amd/vier/home/stud/f/mlh/zope/do.py", line 109, in do if i and picky: raise SystemError, i SystemError: 512 (Using Python 1.5.1 and Zope 1.9) Any ideas? I ran wo_pcgi.py with the full path of the executable... -- Magnus Lie Hetland www.pvv.org/arcadia <arcadia(a)pvv.org>

1 0

- ZopeHTTPServer problems with HEAD requests?
by skip＠calendar.com 09 Jan '99

09 Jan '99

I'm having trouble with HEAD requests in ZopeHTTPServer. Here's the traceback I get for the request "HEAD / HTTP/1.0": Traceback (innermost last): File /home/killer-whale/skip/src/Zope-1.9.0-src/lib/python/ZPublisher/Publish.py, line 872, in publish_module File /home/killer-whale/skip/src/Zope-1.9.0-src/lib/python/ZPublisher/Publish.py, line 163, in __init__ File /usr/local/lib/python1.5/cgi.py, line 846, in __init__ File /usr/local/lib/python1.5/cgi.py, line 690, in parse_header TypeError: argument 1: expected read-only buffer, None found The request "GET / HTTP/1.0" yields the expected page. Anybody else seen this? Know what to do? Skip Montanaro | Mojam: "Uniting the World of Music" http://www.mojam.com/ skip(a)calendar.com | Musi-Cal: http://concerts.calendar.com/ 518-372-5583

1 0

Re: [Zope] - Mail List test Again!
by Robert OConnor 09 Jan '99

09 Jan '99

Hi Paul, Robin and Amos, Thanks for your messages. All of them reached me at bob(a)rocnet.com but again nothing from zope(a)zope.org. I have been reading stuff on egroups in the mean time. I just again sent a 'options' message to zope-request(a)zope.org and received this reply: >>>> options ack: off digest: off hide: off nomail: off norcv: off plain: off which shows that I am indeed subscribed. Now, before sending this message, I changed my "real name" by removing the apostrophe to go from "O'Connor" to "OConnor" Use of the apostrophe has problem has tripped up a few web submission pages in the past. Maybe this is the problem. ... we'll see. -bobo connor -----Original Message----- From: Paul Everitt <Paul(a)digicool.com> To: 'Robert O'Connor' <bob(a)rocnet.com> Cc: Amos Latteier <Amos(a)digicool.com> Date: Friday, January 08, 1999 5:19 PM Subject: RE: [Zope] - Mail List test Again! > >Hmm, Mailman shows you as being subscribed... :^( > >Fortunately we just hired the developer of Mailman so hopefully this >will get more attention :^) > >--Paul > >> -----Original Message----- >> From: Robert O'Connor [mailto:bob@rocnet.com] >> Sent: Friday, January 08, 1999 4:22 PM >> To: zope(a)zope.org >> Subject: [Zope] - Mail List test Again! >> >> >> I have not yet seen any messages posted >> to this list since Jan 6th nor has >> zope-admin responded. >> >> I look forward to participating on the >> list. >> >> -Bob >> >> >> -----Original Message----- >> From: Robert O'Connor <bob(a)rocnet.com> >> To: Amos Latteier <amos(a)aracnet.com>; zope-admin(a)zope.org >> <zope-admin(a)zope.org> >> Date: Thursday, January 07, 1999 1:42 PM >> Subject: Re: [Zope] - A test. No messages yet >> >> >> >Hi Amos & zope-admin,

1 0

RE: [Zope] - Apache's DSO and mod_rewrite.
by Paul Everitt 09 Jan '99

09 Jan '99

Kwan Soo writes: > So, I want the source of rewrite problem. Did I do something wrong or > mod_rewrite must be compiled in staticall? Hmm, this is a good question and perhaps a source of an answer. To try and figure out why everyone was having problems with 1.3.3, I upgraded our web server. Everything went fine. www.zope.org is being served by 1.3.3. I didn't have to change the conf file at all. Even better, lots of problems with shutdown disappeared, I'm now able to kill with the USR1 signal, etc. BUT, I compiled it in statically. At some point the Zope community has to say, "That's an Apache problem, ask them what's wrong." I _kind of_ felt like demonstrating a working system with 1.3.0 provided that kind of claim, but since people were using 1.3.3, it was a weak claim. However, if 1.3.3 is known to work when mod_rewrite is statically compiled in, then that's a strong claim. Can you tell us if it works using a statically-compiled mod_rewrite? --Paul

2 1

Re: [Zope] - Documentproperties - XML/RDF
by Wiebe Kunst 09 Jan '99

09 Jan '99

Sorry about this but I posted a new message before I received this one with another suggestion. >Wiebe Kunst wrote: >> >> >Jim Fulton wrote: >> > > >(snip) > >> >OK, then here are some initial observations/ramblings. >> > >> >- There is an emerging notion of "content", as opposed >> > to "method" objects. Content objects are meant to contain >> > information to be published. Methods OTOH are intended >> > to be used to publish content but are not content themselves. >> > >> Yes and No >> The concept of documentmethods is very powerfull and I don't think one >> should do anything to cripple this concept. > >The current DocumentClass will be renamed to "DTML Method". >There will be a new class, "DTML Document", that is meant to be >content. We won't be taking any functionality away. OK, I didn't get that >> But I think that RDF can be a >> very powerfull extension in terms of attributes (not content). > >Right. My point is that RDF may be more important for "content" >objects than methods. > >> I like to >> view the documentobject as a pointer to content and methods for dynamicly >> creating presentations of content. > >Maybe I'm missunderstanding you. Are you talking about objects that >behave like the current Zope objects? Or are you talking about >some other thing that has rich multi-part content (as is currently >handled with Folders)? As far I have understood the specifications will XML in a broad sense deal with content. RDF is an XML application dealing with meta-data. One can say that the behavior of folders in Zope can resemble meta-data attributes and that those refer to other content. > >> However RDF elements (attributes) can >> extend the documentobject with meta-data, which is extremly important in >> applicatons for information-retrieval. > >Yes. > >> > I expect that most "content" objects will allow >> > more or less arbitrary properties. >> >> This can be true if the documentobject entirely should implement the XML and >> DOM architecture, which probaly is much more complicated (?) since it >> probally rocks the whole objectmodel in Zope. > >I don't follow this. What's the big deal in providing objects arbitrary >properies? What does this have to do with DOM or XML? see above >> >- There should be a way to generate RDF text from content objects. >> > In fact, there should probably be ways to generate RDF for any >> > object and for various collections of objects. >> >> When we're talking about meta-data that is. And yes that would be very nice. > >Right. > > >(snip) > >> > You could also arrange to have the RDF embedded in rendered >> > content. If a/b/c is a DTML Document (content) then >> > you could have the head be something like: >> > >> > <head> >> > ... >> >  >> > </head> >> > ... >> >> Embedding RDF-data in the head-tag is not considered "good practice", but as >> long as not all browers support XML-RDF we really should have this option. > >The RDF spec mentions embedding RDF in resources as one >distribution option. Thats right but some purists define it as "bad", but as I wrote since there aren't any browers supporting XML/RDF yet there aren't many other obtions if the client-side wants to do anything with RDF-data. I think our confusion is about this; I'm mainly concerned with using meta-data on the serverside (by means of DTML or other scripts for the purpose of classifying and information-retrieval. Maybe I should have stated this earlier on. Sorry. > >> >- There needs to be a way to define schemas (namespaces) for properties. >> > There are a couple of issues here: >> > >> > o We need to be able to define schemas for properties. >> >> I don't think so. According to the RDF specification schema's er referred to >> in the RDF. A schema is just a textfile, like the one attached (for the >> Dublin Core). So, I think we need an RDF (python)object which dynamically >> configures itself according to a schema. > >We misscommunicated. My main point is that we need to identify what >schema a property belongs to. Maybe I haven't understood the specs correctly. What I mean is that a schema defines all the attributes on a propertypage. >Of course, we might *also* provide tools for creating schemas interactively. >This could actually be quite useful. But that's secondary. > That would be lovely > >(snip) > >> > From Python, properties in property sheets would be accessed >> > through the property sheets. For example, suppose we had a document, >> > D. Assume we've defined a property sheet, dc (for Dublin Core). >> > To get the title defined by the dublin core, we'd use the >> > expression: >> > >> > D.dc.title >> > >> > Note that property sheets might acquire. So, in the example above, >> > if a value wasn't provided for title in dc, the standard Zope >> > title would be acquired, perhaps after checking that the value was >> > consistent with the dc schema. >> >> Isn't it easier to let DTML take care of that? > >How? There will be many contexts in which one will want to >get D.dc.title. I don't see FTML being a solution. You're right (once again) when the client-side wants to process meta-data. > > >(snip) > >> > - Should there me a way of saying: "I want all of the >> > Dublin Core Properties"? >> >> In the system I'm designing I want a systemadministrator to make such >> decisions and not the individual user. > >By user, I meant the person managing the document. > Perfect Wiebe Kunst

1 0

- Documentproperties - XML/RDF
by Wiebe Kunst 09 Jan '99

09 Jan '99

I just came to think of a maybe an easier way to implement essential (for me atleast :)) properties in Zope. Suggestion: What if a pythonobject (metadata.py) reads a schema (textfile), configures itself according to the specification in that schema and installs itself as a propertysheet in Zope for documents, images and files (maybe other objects to). The document itself should than contain DTML code referring to content and maybe to its attributes (properties). Maybe such an object could be installed as a product, but I don't know if that makes sense. Such a solution doesn't comply of course with the XML/RDF specification, but that could possibly come later. Wiebe Kunst

1 0

Re: [Zope] - Documentproperties - XML/RDF
by Wiebe Kunst 08 Jan '99

08 Jan '99

>Jim Fulton wrote: > >First, the short answer is that supporting RDF >is clearly the right thing to do. I'm not sure exactly >when this will happen, although I can assure you that >progress will be evolutionary. > Great !!! >OK, then here are some initial observations/ramblings. > >- There is an emerging notion of "content", as opposed > to "method" objects. Content objects are meant to contain > information to be published. Methods OTOH are intended > to be used to publish content but are not content themselves. > Yes and No The concept of documentmethods is very powerfull and I don't think one should do anything to cripple this concept. But I think that RDF can be a very powerfull extension in terms of attributes (not content). I like to view the documentobject as a pointer to content and methods for dynamicly creating presentations of content. However RDF elements (attributes) can extend the documentobject with meta-data, which is extremly important in applicatons for information-retrieval. > I expect that most "content" objects will allow > more or less arbitrary properties. This can be true if the documentobject entirely should implement the XML and DOM architecture, which probaly is much more complicated (?) since it probally rocks the whole objectmodel in Zope. >- There should be a way to generate RDF text from content objects. > In fact, there should probably be ways to generate RDF for any > object and for various collections of objects. When we're talking about meta-data that is. And yes that would be very nice. > I assume that there are one or more reasonable mappings from > the Python and Zope Object models to the RDF object model. > Such a comprehensive effort is beyond my current bandwidth. :) I think you guys are doing a tremendous job already, but of course one always begs for more. :) >- I propose to add a standard method for getting an RDF text from > objects. I'm open to name suggestions for this method. > > For example, assume there is a method named ZRDF. You could > get a RDF text for an object, a/b/c with a URL like > a/b/c/ZRFD. > > You could also arrange to have the RDF embedded in rendered > content. If a/b/c is a DTML Document (content) then > you could have the head be something like: > > <head> > ... >  > </head> > ... Embedding RDF-data in the head-tag is not considered "good practice", but as long as not all browers support XML-RDF we really should have this option. >- There needs to be a way to define schemas (namespaces) for properties. > There are a couple of issues here: > > o We need to be able to define schemas for properties. I don't think so. According to the RDF specification schema's er referred to in the RDF. A schema is just a textfile, like the one attached (for the Dublin Core). So, I think we need an RDF (python)object which dynamically configures itself according to a schema. > o We have to be willing to allow multiple properties with the > same name, but different schemas. Alternatively, we need > to be able to define distinct schema sub-objects that act like > property "sheets". Hm. Maybe this is the right way to go. > Maybe you can walk up to a content object and add a property > sheet in which you specify a schema and the associated property > values. This new property sheet then becomes an additional > object view (accessed via a tab). Yeah, like the propertysheet for folders. > From Python, properties in property sheets would be accessed > through the property sheets. For example, suppose we had a document, > D. Assume we've defined a property sheet, dc (for Dublin Core). > To get the title defined by the dublin core, we'd use the > expression: > > D.dc.title > > Note that property sheets might acquire. So, in the example above, > if a value wasn't provided for title in dc, the standard Zope > title would be acquired, perhaps after checking that the value was > consistent with the dc schema. Isn't it easier to let DTML take care of that? > Maybe property sheets would have ZRDF methods to allow getting RDF > for just one schema. > > o Maybe there should be a way to say that a single property > value (e.g. title) should belong to multiple schemas/namespaces. > > This could be accomplished through acquisition, as described above. > > >- For content objects, it seems reasonable that some extra > effort should be made to support a standard simple meta-data > schema, such as the Dublin core. I'm not sure how > this should be accomplished in the user interface and I'm > open to suggestions. For example: > > - Should there me a way of saying: "I want all of the > Dublin Core Properties"? In the system I'm designing I want a systemadministrator to make such decisions and not the individual user. > - Is it enough to allow any properties to be defined and > leave it up to the user to decide which properties > should be defined? > > - To what degree should properties be tied to specific > schemas? How should users define or reference schemas? > Should Zope have a tool that lets someone type in a URI > for a schema and adds the associated properties to an > object? Should there be RDF Schema objects in Zope > that should support managing proport schemas? > > - Should there be schema-dependent property views? > (Probably yes. See above.) See above >Hope these ramblings are helpful. Comments are welcomed. > >Jim Thanks a lot sofar Jim, and I hope my comments will be of use. Wiebe Kunst

2 1

- editing with Composer hoses ZopeHTTPServer
by John Mitchell 08 Jan '99

08 Jan '99

I've just started playing with Zope. It rocks, but I've found a bug. When I edited and published a doc with Netscape Composer, the webserver locked up -- hitting anything on the server would just spin. - using default serve.py (wo_pcgi) as a webserver - access file shows a PUT command as it should - after a restart, management interface shows the doc was uploaded, but it's now type = application/octet-data (as opposed to text/html), and it's 0 bytes long. - from the Composer site, document looks like it was uploaded correctly. Any ideas? I'd *love* to show off Zope plus Composer to the higher-ups, but right now it would be .. inadvisable :) - j (using Zope Beta 2, Python 1.5.1 on a SGI, Irix 6.4)

2 1