Re: [dita-adoption] Updated PDF of DITA Badging Whitepaper Uploaded

[Eliot Kimber <ekimber@contrext.com>]

I have to agree with Kris here: the requirements addressed by the whitepaper could be satisfied using flagging and perhaps a bit more flag rendering functionality in rendering systems.

That is, to the degree that a "badge" is a visual and textual reflection of some property applied to an element, it is definitely an application of flagging.

Cheers,

E.

--
Eliot Kimber
http://contrext.com
 

ïOn 1/7/19, 6:11 PM, "Kristen James Eberlein" <dita-adoption@lists.oasis-open.org on behalf of kris@eberleinconsulting.com> wrote:

    I'm a little confused. What use cases does content badging solve that 
    are not already handled with flagging?
    
    I know that a lot of people are unfamiliar with flagging, and that the 
    SDL CMS does not support it at all ...
    
    Best,
    Kris
    
    Kristen James Eberlein
    Chair, OASIS DITA Technical Committee
    Principal consultant, Eberlein Consulting
    www.eberleinconsulting.com
    +1 919 622-1501; kriseberlein (skype)
    
    On 1/7/2019 5:59 PM, Dr. Stanley Doherty wrote:
    > Hi --
    > I made some minor updates to the draft whitepaper and re-generated the PDF.
    >
    > https://www.oasis-open.org/apps/org/workgroup/dita-adoption/download.php/64498/whitepaper_dita-badges.pdf
    >
    > The GitHub source repo is at:
    >
    > https://github.com/StanDoherty/dita-badges
    >
    > Keeping the Markdown sources and the DITA-OT Markdown parser requirements in sync can be tricky.
    >
    > Stan
    
    ---------------------------------------------------------------------
    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