[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [dita] Element names in proposed "XML mention" domain
I have updated the proposal in the Kavi system. My update does the following: - Change "parment" to "parameterentity" - Change "textent" to "textentity" - Added XSD and RNC declaration modules - Corrected some typos - Added example CSS style sheet - Added trailing ";" to the entity numeric character reference suggested presentation (matches what I was doing in my own rendition implementation). I updated the Toolkit plugins, which now include the working XSD and RNC versions of the module. Cheers, E. On 10/9/12 6:11 PM, "Kristen James Eberlein" <kris@eberleinconsulting.com> wrote: > I agree with Scott here; every time I see parment, I start to read it as > "parmesan." Go figure. > > Tom, posting to the TC list is certainly what I had in mind, not dita-users. > > Best, > Kris > > Kristen James Eberlein > Principal consultant, Eberlein Consulting > Co-chair, OASIS DITA Technical Committee > Charter member, OASIS DITA Adoption Committee > www.eberleinconsulting.com > +1 919 682-2290; kriseberlein (skype) > On 10/9/2012 6:56 PM, Scott Hudson wrote: >> Re: [dita] Element names in proposed "XML mention" domain The only one >> I am not very fond of is parment. I think a slight change to parament >> or paramentity would be more usable. From the core spec, I¹ve not >> liked parml for the same reason. >> >> Thanks and best regards, >> >> --Scott >> >> *Scott Hudson* |** *Pelco by Schneider Electric* | *United States* | >> *Standards Lead >> Ph:* +1-970-282-1952 |***M*: +1-720-663-7268 *| Site: pdn.pelco.com|* >> _scott.hudson@schneider-electric.com >> _ >> >> >> >> >> On 10/9/12 4:52 PM, "Tom Magliery" <tom.magliery@justsystems.com> wrote: >> >> Hi all, >> >> I raised a question on today's TC call about the element names in >> Eliot's 1.3 proposal #13035: Provide "xml mention" domain for >> marking up >> mentions of XML syntactic components >> >> https://www.oasis-open.org/apps/org/workgroup/dita/download.php/47046/pr >> oposal-13035-xmldomain.html >> >> The names of the element types are based on the XML spec and/or chosen >> to be as concise as is reasonable. I'm only worried that they look a >> little too geeky for authors to use. The counterpoint is that anyone >> familiar enough with XML to be using these element types at all is >> probably geeky enough to understand them. >> >> I'm just wondering if there are any alternative names that might be a >> little more recognizable and/or understandable to a typical tech >> writer, >> one of which I am not. Does anyone have any thoughts on the matter? >> >> Or should I send this question to the [dita-users] list? (I don't >> think >> people would be able to read the proposal without logging into >> OASIS ... >> would they?) >> >> mag >> >> -- >> Tom Magliery >> XML Technology Specialist >> JustSystems Canada, Inc. >> Direct: 778-327-6550 >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dita-unsubscribe@lists.oasis-open.org >> For additional commands, e-mail: dita-help@lists.oasis-open.org >> >> >> ______________________________________________________________________ >> This email has been scanned by the Symantec Email Security.cloud >> service. >> ______________________________________________________________________ >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dita-unsubscribe@lists.oasis-open.org > For additional commands, e-mail: dita-help@lists.oasis-open.org > -- 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/
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]