Date   

Re: Conditional Attribute Groups

Radu Coravu
 

Hi Michael,

My take on this:

One thing better about using subject schemes to impose attribute values is that you automatically receive a validation error in Oxygen if you set the wrong value to an attribute, so the subject scheme controlled set of values is imposed when editing your content.

It's also beneficial I think to have the controlled values defined inside the DITA Project's content, so even if you do not use a special framework in Oxygen you get the same benefits from the controlled values.

Also Subject Scheme map defined values can influence the filtering stage when you publish:

https://www.oxygenxml.com/doc/versions/23.1/ug-editor/topics/subject-scheme-map.html#subject-scheme-map__using_a_subject_scheme_in_conjuction_with_a_ditav

Regards,

Radu

Radu Coravu
Oxygen XML Editor
On 4/27/21 10:53, Michael McLoughlin wrote:

Out of interest John, what's the benefit of using subject scheme maps in Oxygen over customizing the Oxygen cc_config,xml? We use the latter to control element, attribute and attribute value choice.

  


Re: Conditional Attribute Groups

Michael McLoughlin
 

Out of interest John, what's the benefit of using subject scheme maps in Oxygen over customizing the Oxygen cc_config,xml? We use the latter to control element, attribute and attribute value choice.


Re: Conditional Attribute Groups

john.kirkilis@...
 

The only thing I've done with subjectschemes is to demo a proof of concept to control valid values for conditional attributes. The subjectscheme maps can then be shared so all writers are honoring the same conditional processing logic for common cases, which is particularly relevant when content is reused across independent product repos using Git Submodules or other means. Oxygen uses the subjectscheme maps to control which values are presented in content completion popups and the Attributes view.

Besides DITA's provisions for filtering attributes for conditional content processing, have you also had the desire to filter by any of the topic metadata elements, such as category, featnum, or even othermeta? Has anyone added this capability to their own workflow, either in a pre or post processing phase to DITA-OT?

Metadata elements make their way into HTML output to allow the reader to filter or do faceted search at "browse time". It would seem natural to  allow a writer to have the option to do the same at build time to define specific deliverables.

Metadata elements have their own attributes. For example, <audience> has @type, @job, @experiencelevel, etc., which wouldn't quite fit the conditional attribute model. Without resorting to specialization, perhaps conditional attribute groups could be used to emulate these cases with @audience="job(operator) experiencelevel(advanced)". It would be possible to then use Schematron or the Oxygen SDK to keep the metadata elements and attribute groups in sync to some degree, where a change in one updates the other and any differences could be caught and quickfixes offered.

It could be handy if these currently orthogonal uses of "metadata" could be unified.


Re: Anyone using Oxygen XML Editor to generate WebHelp output from DITA content?

Radu Coravu
 

Hi Christina,

Thank you :)

Regards,

Radu

Radu Coravu
Oxygen XML Editor
On 4/24/21 13:19, stinakab via groups.io wrote:

Hi Radu,

You know ours already, but for the rest of the group: you're welcome to check out our latest public output layout on https://steinberg.help/nuendo/v11/en/index.html, made with Oxygen 23.0 and DITA OT 3.5.4, with accessibility in mind.
We have several layout versions of the webhelp output in our documents archive. The latest one is the one we are most proud of - for the moment. There are always new things to add.
We think the output gets better and better with every version. Thanks to the SyncRO Soft team.

Christina

  


Re: Job opportunity at Puppet: US Remote #jobhunting

Michael McLoughlin
 

I'm not the hiring manager so I'm afraid I can't say. From my own experience though, if you mention in interview what you need, Puppet are very good at making a sensible offer.


Re: Override Topic title with @navtitle #XSLT

Shaurabh
 

Hi all,

We are using DITA-OT version 3.5.4. Any further suggestion on this topic will be really helpful.


Thanks,
Shaurabh


Re: Job opportunity at Puppet: US Remote #jobhunting

Aaron Mehl
 

Hi I am interested to know what your are offering?

Aaron

On Tuesday, April 20, 2021, 02:20:55 PM EDT, Michael McLoughlin <michael.mcloughlin@...> wrote:


Puppet have an open position for a tech writer with DITA and OxygenXML Author experience anywhere in the US:

https://www.linkedin.com/jobs/view/2493166374/?refId=xhuqco0kmr6eD5N%2BoOIO%2FQ%3D%3D&trackingId=fxCzkB4xHvauEHyRBqCNXg%3D%3D
--
Michael McLoughlin
Senior Technical Writer
Puppet


Re: Anyone using Oxygen XML Editor to generate WebHelp output from DITA content?

stinakab
 

Hi Radu,

You know ours already, but for the rest of the group: you're welcome to check out our latest public output layout on https://steinberg.help/nuendo/v11/en/index.html, made with Oxygen 23.0 and DITA OT 3.5.4, with accessibility in mind.
We have several layout versions of the webhelp output in our documents archive. The latest one is the one we are most proud of - for the moment. There are always new things to add.
We think the output gets better and better with every version. Thanks to the SyncRO Soft team.

Christina


Re: #DITA-OT - Migrating from OT-1.8 to 3.5 #DITA-OT

MarkH
 

Thanks, Mica, I'm beginning to think that would be a better way to go. Even the first move to 2.0 is giving me trouble and it seems like a lot of needless aggravation to go through the 12 steps needed to get to 3.5. One thing is for sure, when I get this done, I will be more inclined to keep it up to date!


Re: #DITA-OT - Migrating from OT-1.8 to 3.5 #DITA-OT

Mica Semrick
 

Hi Mark,

I did this fairly recently and decided it was best to just start over with a fresh 3.x plugin and reimplement the changes that were made to the original plugin.

Things have changed quite a bit, and I didn't feel it was worth it to make the plugin work with the whole 2.x dita-ot series.

-m


On April 23, 2021 12:12:11 PM PDT, MarkH <mark@...> wrote:
Hi!

I have been tasked with migrating our custom webhelp plugin which was written for DITA-OT 1.8.4, to DITA-OT 3.5. From what I have read about the process, I really need to start by migrating to 2.0, then working my way up through the various versions (2.1, 2.2, 2.3, etc.). Any advice, tips, tricks, warnings, or suggestions about how best to proceed would be appreciated!

Thank you in advance!


Re: Anyone using Oxygen XML Editor to generate WebHelp output from DITA content?

Chris Papademetrious
 

Hi Radu,

I hope there are on-group replies to your request. We are quite interested in having a look.

 - Chris


Re: Conditional Attribute Groups

Chris Papademetrious
 

Hi John,

Currently we just have product families for groups. I suppose you could create a separate group for variants, although you'd want to take care that the AND/OR filtering rules work the way you want them to.

Regarding the idea of prototyping attribute specializations, there's also subject schemes. I have yet to look at them, and I don't know how they relate to/work with/conflict with conditional attribute groups.

 - Chris


#DITA-OT - Migrating from OT-1.8 to 3.5 #DITA-OT

MarkH
 

Hi!

I have been tasked with migrating our custom webhelp plugin which was written for DITA-OT 1.8.4, to DITA-OT 3.5. From what I have read about the process, I really need to start by migrating to 2.0, then working my way up through the various versions (2.1, 2.2, 2.3, etc.). Any advice, tips, tricks, warnings, or suggestions about how best to proceed would be appreciated!

Thank you in advance!


Anyone using Oxygen XML Editor to generate WebHelp output from DITA content?

Radu Coravu
 

Hi everyone,

If you are using Oxygen XML Editor to generate Oxygen WebHelp output from DITA, and your published userguide is on a public web server would you mind sending me a link to it? You can send the link in private if you do not want to share with the list (radu_coravu@sync.ro).

I'm curious about how our WebHelp output is being styled.

Regards,

Radu

Radu Coravu
Oxygen XML Editor


Re: markdown failure with OT 3.6 #DITA-OT #markdown

Ben Colborn
 

Thank you Aliza, that certainly looks like the same error. However, I was using the dita command, not calling ant directly. This is in a Git Bash window, which is mingw. I saw the same behavior on my colleague's Windows machine (also Git Bash/mingw). However, the same failure is NOT seen on a Mac. Then I tried running dita.bat rather than dita (which is a Bourne shell script) and the md files DID parse correctly.

The conclusion is that dita.bat works in mingw, and dita works on Mac. So it seems to be a corner case with the dita shell script in mingw terminals.

Ben


Re: Conditional Attribute Groups

john.kirkilis@...
 

Thanks Chris,

Do you use other group names in the product attribute besides familyN?

I’m assuming that if you wanted to also filter by a product variant, you could also add:

product=“family1(PROD_A) variant(ONPREM CLOUD_NATIVE)”

and create DITAVAL props to filter product variants within a family, for example?

Ive seen writers use otherprops as a catch all, but if attribute groups were used, it would namespace them so orthogonal facets were obvious.


Re: Conditional Attribute Groups

Chris Papademetrious
 

Hi John,

We use them quite extensively. We have multiple product families, each with multiple products. This feature allows us to use a single attribute - the @product attribute - to write conditional content such as

<p product="family1(PROD_A)">...</p>
<p product="family1(PROD_B)">...</p>


As a convention, our product family group names are lowercase and the product name values are uppercase.

Then in our DITAVAL, we can select just an individual product out of a family without affecting other product families:

<val>
   <!-- hide all family1 products, then include only @product="family1(PROD_A)" -->
   <prop att="family1" action="exclude"/>
   <prop att="family1" val="PROD_A" action="include"/>
</val>

(And we *do* have books that involve multiple product groups, which gets interesting and fun to edit and publish!)

It initially took some time to grok that in @att can refer to both attribute names and group names used within that attribute, but it makes sense now. It's like referencing the whole tree of possible values or just a subtree of possible values.

And in the Oxygen editor, when you apply profiling conditions to content, the dialog shows an extra expandable/collapsible hierarchy for the group names, which is pretty cool:

audience
  internal
  external
product
  family1
    PROD_A
    PROD_B
  family2
    PROD_C
    PROD_D
...etc...

 - Chris


Conditional Attribute Groups

john.kirkilis@...
 

Is anyone making use of conditional attribute groups in their doc sets?

From my reading of:
that it can provide a way to structure conditional attribute values so that <props> specialization is not required. Even if a filtering specialization is needed eventually, it appears that attribute groups could be used to see if the use case is common enough to justify a specialization.

I didn't initially realize that a DITAVAL <prop> @att value can be either
  • a name of specialization of the <props> attribute (audience, product, platform, etc) OR
  • the name of an attribute group
Specializations empower rock-solid validation, content completion, subjectscheme controlled values, and easier editor features to display and apply filters. Attribute groups would rely on writer conventions and would be relatively impossible to control. It's the basic tradeoff of flexibility against "strongly-typed" conditionalization.

Will attribute groups continue to be supported in DITA 2.0?


Re: Update DITA For Print for OT 3.x? What say ye?

james.bostock@...
 

I think that an updated edition would be great!


Job opportunity at Puppet: US Remote #jobhunting

Michael McLoughlin
 

Puppet have an open position for a tech writer with DITA and OxygenXML Author experience anywhere in the US:

https://www.linkedin.com/jobs/view/2493166374/?refId=xhuqco0kmr6eD5N%2BoOIO%2FQ%3D%3D&trackingId=fxCzkB4xHvauEHyRBqCNXg%3D%3D
--
Michael McLoughlin
Senior Technical Writer
Puppet

121 - 140 of 46295