[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [dita-comment] Question about <dvrKeyscopePrefix>
Thanks Robert, Chris, All good now :) Regards, Radu Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 2/20/2016 12:08 AM, Robert D Anderson wrote:
I'm glad Chris is watching out for me here ... I think I confused this
with the dvrResourcePrefix, where the renaming rules pretty clearly
apply to all children. That's the case I expect to use more often, so it
was more prominent in my mind.
As I've clarified with Chris, regardless of how many copies of the
overall branch are created, the child scope can still be unambiguously
referenced using the renamed parent scope(s).
Sorry for the confusion about that part of Radu's question, and thanks
Chris for quickly catching that.
Robert D Anderson
IBM Authoring Tools Development
Chief Architect, DITA Open Toolkit (http://www.dita-ot.org/)
Inactive hide details for Chris Nitchie ---02/19/2016 10:30:25 AM---I
hesitate to contradict Robert, but that's not what I remeChris Nitchie
---02/19/2016 10:30:25 AM---I hesitate to contradict Robert, but that's
not what I remember, and I don't think it's what the spe
From: Chris Nitchie <chris.nitchie@oberontech.com>
To: Robert D Anderson/Rochester/IBM@IBMUS, Radu Coravu <radu_coravu@sync.ro>
Cc: "dita-comment@lists.oasis-open.org" <dita-comment@lists.oasis-open.org>
Date: 02/19/2016 10:30 AM
Subject: Re: [dita-comment] Question about <dvrKeyscopePrefix>
------------------------------------------------------------------------
I hesitate to contradict Robert, but that's not what I remember, and I
don't think it's what the spec _says_
<http://docs.oasis-open.org/dita/dita/v1.3/os/part3-all-inclusive/langRef/base/dvrKeyscopePrefix.html#dvrKeyscopePrefix>.
The <dvrKeyscopePrefix>element specifies the prefix to use when
constructing the effective key scope names for the map branch that
is implied by the ancestor <ditavalref>element.
For map branches that are implied by <ditavalref> elements, the
value of the <dvrKeyscopePrefix> element contributes to the
effective key scope names of the branch. The effective key scope
names start with the value of the <dvrKeyscopePrefix> element. Note
that if the branch as authored does not specify a @keyscope value,
specifying <dvrKeyscopePrefix> (without also specifying
<dvrKeyscopeSuffix>) results in the branch establishing a key scope
whose name is the value of the <dvrKeyscopePrefix> element. The full
key scope names also will reflect the value of a <dvrKeyscopeSuffix>
element if one is specified, regardless of whether the branch as
authored specifies a @keyscope value.
That is, it applies only to the key scope name of the implied topicref
surrounding the implied branch generated by the ditavalref element, not
its child scopes. (dvrResourcePrefix/Suffix, on the other hand, apply to
all resources in the branch.) As George points out, there would be no
value to renaming scopes beneath the branch-wrapping topicref.
In fact, fairly late in the game we realized that we could/should have
just used dvrKeyscope and not copied the convention used in
dvrResourcePrefix/Suffix, but by then it was much too late to change the
spec and get it out in the target timeframe. You can get the same effect
with dvrKeyscopePrefix/Suffix and no key scope on the containing topicref.
So, in Radu's example, there would be a key scope named 'admin-branchKS'
containing another key scope called 'childKS'. There would be no key
scope named simply 'branchKS'.
Chris
*From: *Robert D Anderson <_robander@us.ibm.com_
<mailto:robander@us.ibm.com>>*
Date: *Friday, February 19, 2016 at 10:38 AM*
To: *Radu Coravu <_radu_coravu@sync.ro_ <mailto:radu_coravu@sync.ro>>*
Cc: *"_dita-comment@lists.oasis-open.org_
<mailto:dita-comment@lists.oasis-open.org>"
<_dita-comment@lists.oasis-open.org_
<mailto:dita-comment@lists.oasis-open.org>>*
Subject: *Re: [dita-comment] Question about <dvrKeyscopePrefix>
Hi Radu,
The keyscope prefix "adminscope-" applies to every scope in that branch,
so in your sample you will end up with both adminscope-branchKS and
adminscope-childKS.
For the other question, yes, if the root topicref in your sample did not
already have a key scope, it would be treated as if it had a scope named
"adminscope-". The child scope would still be renamed to
"adminscope-childKS".
Hope that helps -
Robert D Anderson
IBM Authoring Tools Development
Chief Architect, DITA Open Toolkit (_http://www.dita-ot.org/_)
Inactive hide details for Radu Coravu ---02/19/2016 08:41:19 AM---Hi, I
have a question about the specs.Radu Coravu ---02/19/2016 08:41:19
AM---Hi, I have a question about the specs.
From: Radu Coravu <_radu_coravu@sync.ro_ <mailto:radu_coravu@sync.ro>>
To: _dita-comment@lists.oasis-open.org_
<mailto:dita-comment@lists.oasis-open.org>
Cc: Robert D Anderson/Rochester/IBM@IBMUS
Date: 02/19/2016 08:41 AM
Subject: [dita-comment] Question about <dvrKeyscopePrefix>
------------------------------------------------------------------------
Hi,
I have a question about the specs.
Let's say there is a part of a DITA Map like this:
> <topicref href="productFeatures.dita" keys="features"
keyscope="branchKS">
> <ditavalref href="admin.ditaval">
> <ditavalmeta>
> <dvrResourcePrefix>admin-</dvrResourcePrefix>
> <dvrKeyscopePrefix>adminscope-</dvrKeyscopePrefix>
> </ditavalmeta>
> </ditavalref>
> <topicref href="newFeature.dita" keyscope="childKS"/>
> </topicref>
So there is a @keyscope named "branchKS" defined on the top topicref and
a @keyscope defined on its child called "childKS".
There is a "dvrKeyscopePrefix" which will be used as a prefix for key
scopes.
The specs says something like this:
> <dvrKeyscopePrefix>
> Enables a map author to specify a prefix that is added to the start
of key scope names for each key scope in the branch. If no key scope is
specified for the branch, this can be used to establish a new key scope,
optionally combined with a value specified in <dvrKeyscopeSuffix>.
Will it be used as a prefix for all key scopes, both for "branchKS" and
"childKS", or only for "branchKS"?
Also, if the keyscope "branchKS" would be missing, would the branch
automatically behave as if a keyscope called "adminscope-" would be set
on it?
Regards,
Radu
Radu Coravu
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger_
__http://www.oxygenxml.com_ <http://www.oxygenxml.com/>
--
This publicly archived list offers a means to provide input to the
OASIS Darwin Information Typing Architecture (DITA) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: _dita-comment-subscribe@lists.oasis-open.org_
<mailto:dita-comment-subscribe@lists.oasis-open.org>
Unsubscribe: _dita-comment-unsubscribe@lists.oasis-open.org_
<mailto:dita-comment-unsubscribe@lists.oasis-open.org>
List help: _dita-comment-help@lists.oasis-open.org_
<mailto:dita-comment-help@lists.oasis-open.org>
List archive: _http://lists.oasis-open.org/archives/dita-comment/_
Feedback License: _http://www.oasis-open.org/who/ipr/feedback_license.pdf_
List Guidelines: _http://www.oasis-open.org/maillists/guidelines.php_
Committee: _http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=dita_
Join OASIS: _http://www.oasis-open.org/join/_
--
This publicly archived list offers a means to provide input to the
OASIS Darwin Information Typing Architecture (DITA) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: dita-comment-subscribe@lists.oasis-open.org
Unsubscribe: dita-comment-unsubscribe@lists.oasis-open.org
List help: dita-comment-help@lists.oasis-open.org
List archive: http://lists.oasis-open.org/archives/dita-comment/
Feedback License: http://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
Committee: http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=dita
Join OASIS: http://www.oasis-open.org/join/
[attachment "graycol.gif" deleted by Robert D Anderson/Rochester/IBM]
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]