I usually have a schema-building process which sucks our taxonomies into
the ODD file to create valLists for attributes such as @corresp on
<category>, so that when the encoder comes to enter a value, the valList
with complete descriptions is available right in the Oxygen interface.
On 15-11-17 08:14 AM, James Cummings wrote:
> On 17/11/15 15:57, Piotr Bański wrote:
>> On 17/11/15 13:29, James Cummings wrote:
>>> Now, I know what your answer will be: We
>>> want human-readable and encodable private URI values, no encoder can
>>> type in 300011851 and know what it means.
>> Unless you use smart content completion. I wonder... That would
>> require a layer of configurable redirection inside a smart editor,
>> right? To provide a list of values (potential fillers) with their
>> descriptions taken from designated elements.
> I believe this could already be done in oXygen Author Mode -- perhaps it
> could also be done in the Text/XML mode as well with a plugin, I'm not