thywiss@csvax.cs.ukans.edu (John A. Thywissen) (05/10/89)
In IFF 85 (pages I-13 & I-14 of the Blue RKM: Includes & Autodocs), Jerry Morrison, Electronic Arts, writes: > > Links > >Issue: A standard mechanism for "links" or "cross references" is very >desirable for things like combining images and sounds into animations. >Perhaps we'll define "link" chunks within FORMs that refer to other >FORMs or to specific chunks within the same and other FORMs. This >needs further work. EA IFF 1985 has no standard link mechanism. > >For now, it may suffice to read a list of, say, musical instruments, >and then just refer to them within a musical score by index number. > > File References > >Issue: We may need a standard form for references to other files. >A "file ref" could name a directory and a file in the same type of >operating system as the ref's originator. Following the reference >would expect the file to be on some mounted volume. In a network >environment, a file ref could name a server, too. > >Issue: How can we express operating-system independent file refs? > >Issue: What about a means to reference a portion of another file? >Would this be a "file ref" plus a reference to a "link" within the >target file? > Does any one know of ANY discussion, work, conclusions, standardization, etc. that has been done on this? I just ran into a situation where this type of capability would be EXCEEDINGLY convenient. --John Thywissen ------- John A. Thywissen <thywiss@csvax.cs.ukans.edu> 1122 West Campus Rd. Rm. 213 /| |\/| | / \ |\ Lawrence, KS 66045-8081 / | | | | | | \ (913) 864 2646 _/_-_-_|_ _|_ _ _|_ _|_ _ _\__|_ _|_-_-_\