Re: [dita-learningspec] Groups - Doctypes, sample data, and reference topics for DITA 1.3 stage 3 proposal 13089 uploaded

[Eliot Kimber <ekimber@rsicms.com>]

Actually, that comment was in reaction to the older V2 version. The V6
version had a different name for the constraint and my only correction there
was to lowercase the first letter of the filename.

Cheers,

E.

On 6/6/13 2:40 PM, "Burgess, Doug" <doug.burgess@sap.com> wrote:

> Hi Eliot,
> 
> Thanks a lot for the feedback, the DTD corrections, and the RNG
> implementation.
> 
> Something not mentioned in your comments was your suggestion that we rename
> the %topicref constraint module to 'learningSimpleTopicrefConstraint'. I
> gather that's consistent with the naming convention in the machineryIndustry
> DTD. You've done that in your attached plugin and we'll retain it.
> 
> We'll modify the proposal as you suggest, integrate the examples, and upload a
> new version of the plugin when we're done.
> 
> Best Regards,
> Doug
> 
> =======================================
> Doug Burgess
> Business Platform Management and Operations
> Knowledge Productization Services, SAP Canada
> doug.burgess@sap.com
> Work: 604-974-2334 Mobile: 778-840-8004
> Vancouver BC
> Canada
> 
> 
> -----Original Message-----
> From: dita-learningspec@lists.oasis-open.org
> [mailto:dita-learningspec@lists.oasis-open.org] On Behalf Of Eliot Kimber
> Sent: June-04-13 8:51 PM
> To: Myers, Mark; dita-learningspec@lists.oasis-open.org
> Subject: Re: [dita-learningspec] Groups - Doctypes, sample data, and reference
> topics for DITA 1.3 stage 3 proposal 13089 uploaded
> 
> Let's try this review again, this time on the correct files.
> 
> 1. The constraint content model for %topicref only needs to include keyref,
> mapref, and topicgroup. The other elements are already allowed through other
> paths. In particular, topicgroup explicitly allows navref, data, and
> data-about in addition to topicref.
> 
> 2. The constraint module filename should not have a leading capital. Per the
> coding requirements, it should be "learningAggregations...", not
> "LearningAggregations...".
> 
> 3. Were the examples purposely omitted from the reference entries? I think
> we need to provide examples of each of the new types.
> 
> 4. The class hierarchy for learningGroupMapRef and learningObjectMapRef
> cannot contain mapgroup-d/mapref.
> 
> 5. For both learningGroupMapRef and learningObjectMapRef, need to have the
> .attribute parameter entities in addition to the .content parameter
> entities.
> 
> 6. In the reference entries for the mapref elements, the semantics of a map
> reference are not variable--the meaning of a map reference is always the
> same, so there should be no need to repeat the text from mapref.
> 
> 7. The descriptions of the learningObjectMap and learningGroupMap elements
> don't emphasize the fact that such maps are intended to represent exactly
> one learning object or learning group. That's an important aspect of the
> design and needs to be highlighted. It might also be worth saying something
> about any topicrefs that occur before the learningObject or learningGroup
> elements are intended to be resource-only topicrefs such as key definitions.
> 
> My updates are attached, including RelaxNG declarations. Main change over
> what I sent earlier is rename of the constraint module file from "Learning"
> to "learning".
> 
> Cheers,
> 
> E.
> --
> Eliot Kimber
> Senior Solutions Architect, RSI Content Solutions
> "Bringing Strategy, Content, and Technology Together"
> Main: 512.554.9368
> www.rsicms.com
> www.rsuitecms.com
> Book: DITA For Practitioners, from XML Press,
> http://xmlpress.net/publications/dita/practitioners-1/
> 

-- 
Eliot Kimber
Senior Solutions Architect, RSI Content Solutions
"Bringing Strategy, Content, and Technology Together"
Main: 512.554.9368
www.rsicms.com
www.rsuitecms.com
Book: DITA For Practitioners, from XML Press,
http://xmlpress.net/publications/dita/practitioners-1/