OASIS Open Document Format for Office Applications (OpenDocument) TC

 View Only
  • 1.  Re: [office] Re: Fieldmarks: Nesting?

    Posted 05-07-2008 09:36
    Hi Rob,
    
    > But I I understand correctly, the net effect is to take a portion of 
    > paragraph content, possibly crossing paragraphs, and associate with it a 
    > name, a type, a lock state and a set of name/value attributes that "SHOULD 
    > be preserved".
    
    Exactly. And this is what bookmarks do. Again the only thing I'm proposing add a fieldmark in addition to a bookmark so
    that we can differentiate between user marks and script generated marks.
    
    The reason I added the syntactic sugar like (propName, propValue) pairs is that I dislike string encodings like FIELDMARK /PROP1 VALUE1 /PROP2 VALUE2 etc...
    
    ~Florian
    
    
    >>> 


  • 2.  Re: [office] Re: Fieldmarks: Nesting?

    Posted 05-07-2008 10:00
    Florian,
    
    Florian Reuter wrote:
    > Hi Rob,
    >
    >   
    >> But I I understand correctly, the net effect is to take a portion of 
    >> paragraph content, possibly crossing paragraphs, and associate with it a 
    >> name, a type, a lock state and a set of name/value attributes that "SHOULD 
    >> be preserved".
    >>     
    >
    > Exactly. And this is what bookmarks do. Again the only thing I'm proposing add a fieldmark in addition to a bookmark so
    > that we can differentiate between user marks and script generated marks.
    >
    >   
    You have said you want to do this.
    
    Now, can you say why? What practical difference does it make?
    
    If the issue is "who" added the bookmark, that is a user or some 
    *particular* script, that might be something of more general interest.
    
    For collaboratively edited documents for example. It might be useful to 
    know which user added a particular bookmark. Is that similar to the need 
    to distinguish scripts from users?
    
    Do you need to distinguish which script added a bookmark?
    
    Hope you are having a great day!
    
    Patrick
    > The reason I added the syntactic sugar like (propName, propValue) pairs is that I dislike string encodings like FIELDMARK /PROP1 VALUE1 /PROP2 VALUE2 etc...
    >
    > ~Florian
    >
    >
    >   
    >>>>