subjectscheme and othermeta


john.kirkilis@...
 

Subjectscheme maps provide an elementdef element to bind a set of allowed values to a particular attribute on a particular element. Oxygen and DITA-OT can both leverage this information to offer allowed values or to produce error messages.

I can't see a way to further qualify the binding when the othermeta's @name has a specific value, such as "deliveryPhase".

As a fall-back, other options might include:
  • Schematron rules to validate values and present allowed values as quick fixes
  • Oxygen's content completion configuration (either via the SDK or perhaps the cc_config.xml file)

Two questions are:
  1. Does subjectscheme not cover the othermeta name/value use case?
  2. If not, are there any other alternatives besides Schematron or content completion configuration?

Best Regards,

John


Kristen James Eberlein
 

Specialize from <othermeta>, and you'll be able to use subjectScheme for binding controlled values.

Best,
Kris

Kristen James Eberlein
Chair, OASIS DITA Technical Committee
OASIS Distinguished Contributor
Principal consultant, Eberlein Consulting LLC
www.eberleinconsulting.com
+1 919 622-1501; kriseberlein (skype)


On 9/1/2021 5:04 PM, john.kirkilis via groups.io wrote:
Subjectscheme maps provide an elementdef element to bind a set of allowed values to a particular attribute on a particular element. Oxygen and DITA-OT can both leverage this information to offer allowed values or to produce error messages.

I can't see a way to further qualify the binding when the othermeta's @name has a specific value, such as "deliveryPhase".

As a fall-back, other options might include:
  • Schematron rules to validate values and present allowed values as quick fixes
  • Oxygen's content completion configuration (either via the SDK or perhaps the cc_config.xml file)

Two questions are:
  1. Does subjectscheme not cover the othermeta name/value use case?
  2. If not, are there any other alternatives besides Schematron or content completion configuration?

Best Regards,

John


Radu Coravu
 

Hi,

Indeed if John would have a specialized element based on "othermeta" named "deliveryPhase", the elementdef could match this element and provide particular values for its attribute value.

We were inclining towards making such an usecase work in a future version of Oxygen (proposing values for an attribute based on another attribute) by interpreting an @outputclass attribute on the elementdef, something like this for example:

<elementdef name="data" outputclass="name(test)">
would mean that the definition is for element "data" with attribute name="test", and Oxygen could offer content completion and maybe also validation based on this.

Regards,
Radu
Radu Coravu
Oxygen XML Editor

On 9/2/21 00:26, Kristen James Eberlein wrote:

Specialize from <othermeta>, and you'll be able to use subjectScheme for binding controlled values.

Best,
Kris

Kristen James Eberlein
Chair, OASIS DITA Technical Committee
OASIS Distinguished Contributor
Principal consultant, Eberlein Consulting LLC
www.eberleinconsulting.com
+1 919 622-1501; kriseberlein (skype)


On 9/1/2021 5:04 PM, john.kirkilis via groups.io wrote:
Subjectscheme maps provide an elementdef element to bind a set of allowed values to a particular attribute on a particular element. Oxygen and DITA-OT can both leverage this information to offer allowed values or to produce error messages.

I can't see a way to further qualify the binding when the othermeta's @name has a specific value, such as "deliveryPhase".

As a fall-back, other options might include:
  • Schematron rules to validate values and present allowed values as quick fixes
  • Oxygen's content completion configuration (either via the SDK or perhaps the cc_config.xml file)

Two questions are:
  1. Does subjectscheme not cover the othermeta name/value use case?
  2. If not, are there any other alternatives besides Schematron or content completion configuration?

Best Regards,

John