RE: [dita] conref source and target [was: Why There are Constraints on Conref]

["Bruce Nevin (bnevin)" <bnevin@cisco.com>]

Sure, use that if it works for you and for those you're talking to. Those aren't the words the spec uses, but that needn't constrain you.

---

From: Nancy Harrison [mailto:nancylph@gmail.com]
Sent: Wednesday, June 23, 2010 6:44 PM
To: Bruce Nevin (bnevin)
Cc: Noz Urbina; Su-Laine Yeo; ekimber; Joann Hackos; Michael Priestley; Scott Prentice; dita; Anderson Robert
Subject: Re: [dita] conref source and target [was: Why There are Constraints on Conref]

This may be simplistic, but how about [conref] pointer element for the element holding the conref?  It gets across the reality of the situation, that it's the element that contains the pointer to the content.

Just a thought...

-nancy

On Thu, Jun 24, 2010 at 1:12 AM, Bruce Nevin (bnevin) <bnevin@cisco.com> wrote:

A variety of expression pairs can communicate the relationship
effectively, and we're free to use any of them. The fact that the spec
has settled on one pair, referring element and referenced element,
doesn't constrain communication outside the spec if other factors
outweigh consistency.

> -----Original Message-----
> From: Noz Urbina [mailto:noz.urbina@mekon.com]
> Sent: Wednesday, June 23, 2010 7:44 AM
> To: Su-Laine Yeo; Bruce Nevin (bnevin); ekimber; Joann
> Hackos; Michael Priestley; Scott Prentice
> Cc: dita; Anderson Robert
> Subject: RE: [dita] conref source and target [was: Why There
> are Constraints on Conref]
>

> As do I, but I also say "referencing element" and "reused
> element" in equal proportion.

>
> -----Original Message-----
> From: Su-Laine Yeo [mailto:su-laine.yeo@justsystems.com]
> Sent: 02 October 2009 01:22
> To: Bruce Nevin (bnevin); ekimber; Joann Hackos; Michael
> Priestley; Scott Prentice
> Cc: dita; Anderson Robert
> Subject: RE: [dita] conref source and target [was: Why There
> are Constraints on Conref]
>
> I usually say, "the conreffing element" and "the conreffed element".
>
> Su-Laine
>
>
> Su-Laine Yeo
> Interaction Design Specialist
> JustSystems Canada, Inc.
> Office: 778-327-6356
> syeo@justsystems.com
> www.justsystems.com
>
>
> -----Original Message-----
> From: Bruce Nevin (bnevin) [mailto:bnevin@cisco.com]
> Sent: Thursday, October 01, 2009 3:10 PM
> To: ekimber; Joann Hackos; Michael Priestley; Scott Prentice
> Cc: dita; Anderson Robert
> Subject: RE: [dita] conref source and target [was: Why There
> are Constraints on Conref]
>
> And "conref element" vs. "content element" is misleading,
> enough newcomers look for an element named conref as it is.
> The point was not to offer a name, but to bring the relevent
> semantics into a different focus, maybe more fruitful than
> the ambiguous source/target pair.
>
> > -----Original Message-----
> > From: ekimber [mailto:ekimber@reallysi.com]
> > Sent: Thursday, October 01, 2009 4:20 PM
> > To: Bruce Nevin (bnevin); Joann Hackos; Michael Priestley; Scott
> > Prentice
> > Cc: dita; Anderson Robert
> > Subject: Re: [dita] conref source and target [was: Why There are
> > Constraints on Conref]
> >
> > On 10/1/09 3:16 PM, "Bruce Nevin (bnevin)" <bnevin@cisco.com> wrote:
> >
> > > Gotta appreciate the sense of humor!
> > >
> > > But the locus of mischief isn't actually at the conref-bearing
> > > element, is it?
> > >
> > > Maybe too verbose as handy labels, but we are talking about the
> > > conref-bearing element and the content-bearing element.
> >
> > I had to read that twice to realize that "conref-bearing" and
> > "content-bearing" were different words. "r" and "f" and "t"
> > are too similar in shape...
> >
> > Cheers,
> >
> > E.
> >
> > ----
> > Eliot Kimber | Senior Solutions Architect | Really Strategies, Inc.
> > email:  ekimber@reallysi.com <mailto:ekimber@reallysi.com>
> > office: 610.631.6770 | cell: 512.554.9368 2570 Boulevard of the
> > Generals | Suite 213 | Audubon, PA 19403 www.reallysi.com
> > <http://www.reallysi.com>  | http://blog.reallysi.com
> > <http://blog.reallysi.com> | www.rsuitecms.com
> > <http://www.rsuitecms.com>
> >
> >
>
> ---------------------------------------------------------------------
> 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_workgr
> oups.php
>
>
> ---------------------------------------------------------------------
> 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_workgr
> oups.php
>
>

---------------------------------------------------------------------
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

--
_____________
Nancy Harrison
Infobridge Solutions  
nharrison@infobridge-solutions.com