Security: Time restriction to access

Submitted by pr3j on Sat, 2006-12-23 14:57

I think we need another dimension: time
I mean, if something already occured, it can´t be modified, except by the Alpha Story guide. Than, even the owner of an object should not edited parts that are connected with events already played.
Of course there are items that do not need this dimension, and others will allow only additions, not modifications ...

Bookmark/Search this post with
Security: is protected right ›

StorySGML was planned to be

Submitted by Nebulorum on Sat, 2006-12-23 15:34.

StorySGML was planned to be a snapshot of a story. It reflects the current state of things. With the new documentation role, we have some new challenges. As time progresses things are bound to change on the characters(personas). It is easy to see that goals will change, and new relationships will show up, as well as old ones will change. Besides this there is a need to document events and actions. The original SGML had a event story element, but that looks to me useless.

I see two things that are time-bound:

  1. Goals, background and relations
  2. events that happened over time

The first one could be handled by revisions (RCS or CVS like). As the character change we could keep old revisions. I thinks it is best to keep the persona as the snapshot of the current state.

A new feature that will be in V1.0 are logs, so you could also track changes in the log. So if a persona meets someone new, put that on the log, and in the relation make a reference to the log entry. Eg:
Original: <relation id=P01> He is my trusted companion </relation>
After event: <relation id=P01> I hate him, he betrayed me <xref id=MYLOG.E23>, I used to trust him</relation>

The log entry tells the story... If necessary we could keep the old version as a revision, so we could look the older version, if needed.

This could also be used to track time, using a story log that only the master can write to. For system related things and time tracking I think a real "fictional" calendar would be better. I also want to put that in V1.x.