devel
[Top] [All Lists]

[pw-devel] Re: so the thread stays afloat

To: devel@xxxxxxxxxxxxxxxxxxxxxxx
From: Eugene Eric Kim <eekim@xxxxxxxxxxxx>
Date: Tue, 10 Feb 2004 14:30:49 -0800
Message-id: <20040210223049.GF7930@douge.blueoxen.net>
On Tue, Feb 10, 2004 at 01:50:04PM -0800, John Sechrest wrote:    (01)

> Lets say that we have granularity at the paragraph level.
> And we have three paragraphs:
> 
> nid 1
> nid 2
> nid 3
> 
> then we change paragraph 2:
> 
> nid 1
> nid 2 -> nid 4
> nid 3    (02)

If you change paragraph 2, it retains the same nid.    (03)

> So our final document looks like:
> 
> nid 1
> nid 6
> nid 7
> nid 5
> 
> 
> When I transclude the second paragraph, do I mean Nid 2, nor nid 6 or nid 7    (04)

You transclude by node ID, not by path addressing.  Node IDs are
stable and immutable.  In another words, you would transclude
paragraph with NID 2, but you wouldn't transclude the second paragraph
(although we could potentially add such functionality).    (05)

Your overall point is well taken, however.  There are some issues
regarding the way we handle versioning and transclusions.  What
happens, for example, if someone deletes the paragraph with NID 2 from
the page, but there's another page that transcludes that paragraph?    (06)

With the current implementation, this would cause a failure, because
we use screen scraping for transclusions.  This is easily fixed.  The
hard question is, what's the right way to fix it?  Do you allow that
transclusion anyway, even though that paragraph no longer exists on
that page?    (07)

-Eugene    (08)

-- 
Was I helpful?  Let others know.    (09)

http://svcs.affero.net/rm.php?r=eekim&p=EnablingOnlineCommunities    (010)

-- 
This message is archived at:    (011)

http://purplewiki.blueoxen.net/forums/cgi-bin/mesg.cgi?a=devel&i=20040210223049.GF7930@douge.blueoxen.net    (012)
<Prev in Thread] Current Thread [Next in Thread>