OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

dita-lightweight-dita message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [dita-lightweight-dita] Some thoughts on next steps


Hi -

And I had also requested a table for LW DITA and education, so will suggest we combine those efforts, too, depending on the size of the group.

On Michael's thoughts, I like the idea of getting a core package out asap, but I think we need some discussion on just what it means to have a core package, and what it seeks to accomplish. I think there might be just a few items we might want to include specifically for a learning/training/education mode, and it would be great to have a core package defined first.

I'm in rainy Chicago now, and will be heading down to for the evening reception in a bit.

John
___________________________________
John Hunt
Senior Technical Content Architect
IBM Collaboration Solutions | User Experience: Design and Information Excellence
4502 S. Miami Blvd, Durham, NC 27703
john_hunt@us.ibm.com | 919-254-2879


-----<dita-lightweight-dita@lists.oasis-open.org> wrote: -----
To: "Hudson, Scott" <scott.hudson@comtech-serv.com>, Michael Priestley <mpriestl@ca.ibm.com>
From: Kristen James Eberlein
Sent by:
Date: 04/19/2015 08:44AM
Cc: "dita-lightweight-dita@lists.oasis-open.org" <dita-lightweight-dita@lists.oasis-open.org>
Subject: Re: [dita-lightweight-dita] Some thoughts on next steps

Thanks, Scott.

Best,
Kris

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

On 4/19/2015 8:42 AM, Hudson, Scott wrote:
I’ve asked Lisa if we can set aside a table for LW DITA. We should be able to accommodate it, or use the table that Carlos volunteered!

—Scott

From: Michael Priestley
Date: Sunday, April 19, 2015 at 8:29 AM
To: Kristen James Eberlein
Cc: "dita-lightweight-dita@lists.oasis-open.org"
Subject: Re: [dita-lightweight-dita] Some thoughts on next steps

I've already asked. There should be one. Evidently you can sign up for the tables via the conf mobile app

Sent from my iPhone

On Apr 19, 2015, at 8:07 AM, Kristen James Eberlein <kris@eberleinconsulting.com> wrote:

Scott, is there a way that Lightweight DITA could have a Monday lunch table? That way the subcommittee could meet over lunch.

Best,
Kris

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

On 4/18/2015 11:19 PM, Hudson, Scott wrote:
I’m afraid it might get confusing to release industry-specific specializations but then not including them in the package.

I’m still a little unclear as to the primary goal for the Lightweight DITA effort. Some have explained it as a valid subset of DITA, others have explained that it is a mapping of other vocabularies/languages to a subset of DITA elements. Which is it?

I was under the impression that we were trying to create a minimal subset that could provide an easy-to-use semantic tag set for use in a web-based authoring tool.

I’m worried about trying to push something out there just to “see what sticks”, when it could confuse a lot of people who are watching for news from this activity. 

I think we are on the right track as far as identifying the particular roles in a domain, but we need more detail about what document types those domains really need, and more specifics about what elements are must-haves.

I think we need to worry less about mapping implementations in other languages if we are still trying to identify the proper subset of elements?

Thanks,

—Scott

From: Michael Priestley
Date: Saturday, April 18, 2015 at 8:33 PM
To: "dita-lightweight-dita@lists.oasis-open.org"
Subject: [dita-lightweight-dita] Some thoughts on next steps

We had a small meeting last time, and talked about how to streamline our process to get something out sooner.  

What do people think about focusing our efforts on getting the core package out ASAP, with industry-specific specializations being used to validate the architecture but not necessarily including them in the package?

For example, we could aim to publish a specification for V1.0 that:

- defines lightweight DITA topics, maps, and specialization
- defines mappings/implementations for XML, HTML5, markdown, JSON
- defines a lightweight specialization document type that allows quick generation of new map and topic specializations
- and links to separate pages/papers for each industry/discipline area, which can continue being developed after the initial spec is published

Each domain position paper (not a formally approved spec) would cover:
- value proposition of lw dita for that domain
- listing of example roles and scenarios
- list of example content types
- at least one example specialization of one of the domain-specific content types (unless none are needed)

What do folks think? I'm reluctant to push too far ahead with the core spec without some validation from the domain analysis that we're including the right things. But maybe we're asking for too exhaustive an analysis. Maybe we just need enough analysis to ensure that we've got a useful direction, and then we can release and begin iterating.

Michael Priestley, Senior Technical Staff Member (STSM)
Enterprise Content Technology Strategist
mpriestl@ca.ibm.com
http://dita.xml.org/blog/michael-priestley

--------------------------------------------------------------------- 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://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

--------------------------------------------------------------------- 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://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]