Re: [dita] Delayed conref domain

["Michael Priestley" <mpriestl@ca.ibm.com>]

Hi Kris,

Just to share the thought process behind
the original requirement - at the time, there was a strong interest generally
in runtime dynamic DITA delivery. So the feature was deployed in anticipation
of a requirement from anyone deploying DITA in a dynamic information server
(of which there are several in the market today).

There was also a way to map that requirement
to an existing Eclipse capability that was a potential blocker to people
migrating off of HTML sources onto DITA. 

The reality is that the capability never
got used, I think on either DITA dynamic rendering platforms or on Eclipse,
but it wasn't formulated to be Eclipse-specific.

Michael Priestley, Senior Technical Staff Member (STSM)
Enterprise Content Technology Strategist
mpriestl@ca.ibm.com



From:      
 Kristen James Eberlein
<kris@eberleinconsulting.com>
To:      
 dita@lists.oasis-open.org
Date:      
 09/05/2017 10:34 AM
Subject:    
   Re: [dita] Delayed
conref domain
Sent by:    
   <dita@lists.oasis-open.org>

---

This raises the question of what we should or should not
consider for inclusion in the standard. Is an architectural feature that
can be used only one platform (Eclipse) too narrow? I would probably think
that it is, but I'd love to hear others' thoughts.

How broadly applicable should something be before we entertain adding it to the DITA standard?

Best,

Kris

Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Principal consultant, Eberlein Consulting
www.eberleinconsulting.com
+1 919 682-2290; kriseberlein (skype)

On 9/5/2017 9:53 AM, Robert D Anderson wrote:

I asked some of our authors in IBM about usage (in a very un-scientific way, polling in a chat channel), and the folks who usually respond to such queries hadn't heard of the domain. It was really designed around an Eclipse feature, and I am not aware of any other rendering platform that has such a feature, which probably limits the utility. I know it's also been a bit of a pain to support in the DITA-OT processing pipeline because it requires "If Eclipse" exceptions to otherwise common feature processing.

Regards, Robert D. Anderson DITA-OTlead and Co-editor DITA 1.3 specification, Digital Services Group
E-mail: robander@us.ibm.com Digital Services Group
11501 BURNET RD,, TX, 78758-3400, AUSTIN, USA

Kristen James Eberlein ---08/29/2017 03:42:58 PM---Is this a domain that we want to consider removing for DITA 2.0? I don't know if it used at all outs

From: Kristen James Eberlein <kris@eberleinconsulting.com>
To: DITA TC <dita@lists.oasis-open.org>
Date: 08/29/2017 03:42 PM
Subject: [dita] Delayed conref domain
Sent by: <dita@lists.oasis-open.org>

---

Is this a domain that we want to consider removing for DITA 2.0?

I don't know if it used at all outside of IBM.

-- 
Best,
Kris

Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Principal consultant, Eberlein Consulting
www.eberleinconsulting.com
+1 919 682-2290; kriseberlein (skype)


---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that 
generates this mail.  Follow this link to all your TCs in OASIS at:
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.oasis-2Dopen.org_apps_org_workgroup_portal_my-5Fworkgroups.php&d=DwICaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=eBihWDTS2oOizc2d2LrsewiOpn69Mu6rPwmmRMM_aAU&m=7VG2UhcxpRBcWRmDUOWWUrFWBmzvQH-TcIW1lAae87s&s=_V5eE0l_oThiIWFQvnbl-r3Ch4Q-oqkkdEZq75MpKbE&e=