gzz-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gzz-commits] manuscripts/storm article_structure.txt


From: Benja Fallenstein
Subject: Re: [Gzz-commits] manuscripts/storm article_structure.txt
Date: Sat, 08 Feb 2003 14:04:35 +0100
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021226 Debian/1.2.1-9

Toni Alatalo wrote:
generalizing section names:

1. intro: ok
2. rel work: ok
3. block storage: data model?
4. xanalogical storage: (hyper)media model?

Hm, we are presenting Storm, and the section structure follows Storm's main components in section 3-6 (intentionally, since we *are* talking design). I'm not sure I'd want to 'generalize' (one of those ACM tips for authors says: Do not try to generalize! Talk about your specific case well :-) )

I can see how it would be nice if the section names could tell the uninitiated reader what the section will be about, but I don't think 'data model' and 'hypermedia model' cut that. :-) Plus, 'Xanalogical storage' should be a word known to many in the field, making it more precise than just 'hypermedia model.'

5. indexing: ok?

This is what I'm least comfortable with, since it doesn't seem to be descriptive enough a name...

6. versioning: ok?
7. peer-to-peer implementations: ?

What's the problem here?

8. experience and future directions: ok
9. conclusions: ok
10. acknowledgements: ok
11. references: ok

-b.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]