Selectively Locking Elements in the Editor

Does Oxygen provide a way to selectively lock elements within the editor or can this be done through a plug-in? There are several use cases: 1. Lock and element and all its descendants 2. Lock an element and some of its descendants. 3. Lock the attributes but not the content of an element. 4. Lock the content but not the attributes of an element. Thanks, Eliot -- W. Eliot Kimber Senior Solutions Architect Really Strategies, Inc. "Bringing Strategy, Content, and Technology Together" Main: 610.631.6770 www.reallysi.com www.rsuitecms.com Sent using the Microsoft Entourage 2004 for Mac Test Drive.

Hi Eliot, No, that is not possible. We have an option in text mode for locking the tags, see Document -> Source -> Locks/Unlocks the XML tags or make the Source toolbar visible (Perspective -> Show Toolbar -> Source) and use the action from that toolbar. It will be interesting to link these feature requests to a more real example usecase? Best Regards, George --------------------------------------------------------------------- George Cristian Bina - http://aboutxml.blogspot.com/ <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com Eliot Kimber wrote:
Does Oxygen provide a way to selectively lock elements within the editor or can this be done through a plug-in?
There are several use cases:
1. Lock and element and all its descendants
2. Lock an element and some of its descendants.
3. Lock the attributes but not the content of an element.
4. Lock the content but not the attributes of an element.
Thanks,
Eliot

George Cristian Bina wrote:
Hi Eliot,
No, that is not possible.
OK.
It will be interesting to link these feature requests to a more real example usecase?
There are several use cases:
RSuite lets you manage access control of individual elements within a larger document (what RSuite calls "Manageable Objects" such that a higher-level element may contain descendant elements that are checked out and locked by another user. Conversely, you may want to edit an element that is itself checked out to somebody else but that contains elements that are checked out to you.
1. Lock and element and all its descendants
Within a document, prevent changing to any arbitrary descendant tree.
2. Lock an element and some of its descendants.
Lock an element but unlock one or more descendants.
3. Lock the attributes but not the content of an element.
This is a case common in translation workflows, where you want to allow the text-level content of an element to be modified (e.g., to create the translation) but not the markup itself (e.g., authors can't accidentally or intentionally change attribute values).
4. Lock the content but not the attributes of an element.
Inverse of 3, for completeness. Might allow updating attribute-based metadata without danger of changing content. Cheers, E. -- Eliot Kimber Senior Solutions Architect "Bringing Strategy, Content, and Technology Together" Main: 610.631.6770 www.reallysi.com www.rsuitecms.com

George Cristian Bina wrote:
It will be interesting to link these feature requests to a more real example usecase?
This is very useful if you are working on translations and content to be translated is stored in XML. Many formats can indicate whether some content is going to be translated and for translator it sometimes make sense to lock everything else to prevent errors. There is even standardized markup for indicating translation characteristics of XML file called ITS -- http://www.w3.org/TR/its/ Having direct support for ITS markup in oXygen would be nice, but there are probably other features with much greater user base. Jirka -- ------------------------------------------------------------------ Jirka Kosek e-mail: jirka@kosek.cz http://xmlguru.cz ------------------------------------------------------------------ Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing ------------------------------------------------------------------ OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member ------------------------------------------------------------------
participants (3)
-
Eliot Kimber
-
George Cristian Bina
-
Jirka Kosek