Re: [Gzz] PEG: link type names

[Tuomas Lukka]

On Mon, May 12, 2003 at 04:23:12PM +0200, Benja Fallenstein wrote:
> >>>In vocabularies (and possibly elsewhere), the connections
> >>>that are now called xu links and PP links should
> >>>be renamed to c-links and d-links for {content/constant} link
> >>>and {directed/dynamic} link.
> >>
> >>Say here why these names.
> >>
> >>My opinion is that 'clink' and 'dlink' are nondescriptive. I think 
> >>'content link' is probably a good name; it should then be named 
> >>'contentLink,' not 'cLink.' An alternative is 'alphLink'; since this 
> >>is closely coupled to Alph, 'alphLink' is actually probably better.
> >
> >contentLink: too long, but I might accept that.
> 
> Why too long?

Well, all right. Let's use this.

> >alphLink: the vocabs &c should then be in alph.
> 
> I'm not so sure about that. Alph introduces the concept of an alph 
> link but doesn't know about RDF; Fenfire uses Alph and RDF; it seems 
> justified that Fenfire would provide an RDF vocabulary for 
> representing Alph concepts.

Still, Alph is the name of the implementation, not the theory behind it...

> >>Since practically all connections are directed in FF, directed link 
> >>sounds like a bad name. I suggest Link for the namespace and 
> >>linkedTo for the property. The -To suggests the direction; the 
> >>inverse would obviously be linkedFrom, not linkedTo, so the property 
> >>is directional.
> >
> >How about "structLink" and linkedTo ?
> 
> "structLink" as what? The namespace/class name? I think I'd write that 
> StructLink in Java, since Java classes always start with a capital, 
> and I think 'structlink' in the URI. Hmm.

Fine with me.

        Tuomas