Hi Nathan, What type of XML vocabulary are you editing? Docbook, DITA, etc? My answer will be mostly about using DITA. We do not yet have the possibility to save profiling condition sets at document type (framework) level, but it's been requested before and we will probably implement it in a future version. I added your contact details and you'll be notified when it happens. For our own Oxygen XML User Manual which is written in DITA we use a combination of Project-level saved profiling condition sets and a Subject Scheme Map. Starting with Oxygen 15.0 you can define for DITA documents the profiling attributes and their values in a Subject Scheme Map. Oxygen will automatically use those to propose values for attributes and for validation if the main DITA Map is opened in the DITA Maps Manager and has a reference to the Subject Scheme Map

http://www.oxygenxml.com/doc/ug-editor/index.html#topics/subject-scheme-map....

and a video demo here:

http://www.oxygenxml.com/demo/DITA_Subject_Scheme.html

So if you look at this Oxygen Preferences->"Editor / Edit modes / Author / Profiling/Conditional Text" page, adding values in the first table (Profiling Attributes table) can be replaced completely by using the Subject Scheme Map approach (if you are editing DITA content). The second table (list of Profiling Condition Sets) still needs to be either built by the user or saved with the project level settings. But in the same preferences page there is a button called "Import from DITAVAL" which you can use to quickly add values to that second table by selecting the DITAVAL filter files which you are using in your project. Another approach would be to use custom default options, basically to export a set of global options to an XML file which would then be used as default options by the others:

http://www.oxygenxml.com/doc/ug-editor/index.html#topics/default-options.htm...

Regards, Radu Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 2/4/2014 12:15 AM, Nathan wrote:

Hi, I would like to distribute profiling attributes and profiling condition sets but preferably do so via a framework instead of the project option. Is there any way to do this? To define the use case, I would like to deploy a default baseline setup which could be updated via source control without the need for a merge if authors customize their own projects. If it is not possible to distribute profiling conditions via framework, would it be possible to use xlink to do this at the project level. I would be eager to know what others are doing in this regard.

Thanks! Nathan