[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Early feedback on Issue 670, Impose Role
I did scan the list of attributes in the spec, to see what conventions we had regarding hyphenation or camel case. We have the following attributes:
I don’t think we have any hyphenation or camel case in the attribute values, but I can’t swear to it. Best, Kris Kristen James Eberlein Skype: kriseberlein; voice: +1 (919) 622-1501 From:
dita@lists.oasis-open.org <dita@lists.oasis-open.org>
On Behalf Of Eliot Kimber I’m generally happy with the proposal with two comments:
I agree with Gershon that “impose-role” might be an easier-to-read attribute name. I don’t remember if we have any general attribute naming principle that prefers or avoids dashes as word separators. I also
can’t think of a better name for the attribute itself. I think “impose role” is a clear _expression_ of the semantic. Cheers, E. _____________________________________________ Eliot Kimber Sr Staff Content Engineer O: 512 554 9368 M: 512 554 9368 LinkedIn | Twitter | YouTube | Facebook From:
dita@lists.oasis-open.org <dita@lists.oasis-open.org> on behalf of Gershon Joseph <gershon@precisioncontent.com> [External Email] Hi Robert, I think your proposal is good. I could not come up with any better attribute or token names, other than perhaps hyphenating the ones you suggested.
Maybe impose-role would be easier for humans to parse? Consider also adding hyphens to the values: override-target and keep-target.
Cheers, Gershon Gershon L Joseph |
Senior Information Architect | Precision Content | Phone: +972 (54) 658-3887|
TZ: Jerusalem, Israel (GMT+2) | Email: gershon@precisioncontent.com|
Twitter: @PCASinc
| www.precisioncontent.com Unlock the Knowledge in Your Enterprise™ This email and any files transmitted with it are confidential and intended solely for the use of
the individual or entity to whom they are addressed. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Please
notify us by return email if you have received this email in error.
© 2022, Precision Content Authoring Solutions Inc. Toronto, Ontario, Canada
From:
dita@lists.oasis-open.org <dita@lists.oasis-open.org>
On Behalf Of Robert Anderson Hi all, As discussed at the TC this week, I'm sending along the draft of the "impose role" topic. It's the proposal for an actual defined way to manage the behavior that is currently described here: Based on discussion at TC, I've set up a new attribute to control this, called "imposerole". I really do not want to use yes/no values because that has bitten us several times in the past, when
we suddenly discover there is a third option. So I've picked a couple of tokens that more or less make sense to me:
Do those make sense, or does anyone have a better set of tokens? Thanks, Robert |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]