|
List Info
Thread: Re: Element for an author's website URL
|
|
| Re: Element for an author's website URL |
|
2007-07-24 06:59:42 |
Hi,
> [...]
> > Maybe I am missing something obvious, but why not
use link?
>
> Because it's a link, not a URL
But a link can also be a URI/URL. According to the TDG[1]:
»The link is a general purpose hypertext element. [...]
If it has an xlink:href attribute, link is the equivalent
of an
HTML anchor (<html:a href="...">) for
cross reference
with a Uniform Resource Identifier (URI).«
Maybe I didn't understand your argument. But why introduce
another element when there is already a general purpose
element
for this issue? 
Bye,
Tom
------
[1] http://
www.docbook.org/tdg5/en/html/link.html
------------------------------------------------------------
---------
To unsubscribe, e-mail: docbook-unsubscribe lists.oasis-open.org
For additional commands, e-mail: docbook-helplists.oasis-open.org
|
|
| Re: Element for an author's website URL |
|
2007-07-24 10:19:52 |
|
[Note: I accidentally CCed the wrong list with the below message. docbook-apps, feel free to ignore.]
"The link is a general purpose hypertext element."
The
element I propose has nothing to do with hypertext. It is simply
another part of an <address>, same as <email>,
<phone>, etc. It is another bit of information about how to
contact a person/organization.
If we already have <email>, then why not <web>; or
<homepage>? Also remember that an email address can be displayed
as hypertext as well (i.e. a mailto: link in a web browser), but it
doesn't have to be. Same with a home page URL. We don't have to use
<link> for an email address within <address>.
Colin
On 7/24/07, tom_schrweb.de">tom_schrweb.de < tom_schrweb.de">tom_schrweb.de
> wrote:Hi,
> [...]
> > Maybe I am missing something obvious, but why not use link?
>;
> Because it's a link, not a URL
But a link can also be a URI/URL. According to the TDG[1]:
»The link is a general purpose hypertext element. [...]
If it has an xlink:href attribute, link is the equivalent of an
HTML anchor (<html:a href=";...">) for cross reference
; with a Uniform Resource Identifier (URI).«
Maybe I didn't understand your argument. But why introduce
another element when there is already a general purpose element
for this issue?
Bye,
Tom
------
[1] http://www.docbook.org/tdg5/en/html/link.html
|
| Re: Element for an author's website URL |
|
2007-07-24 10:41:16 |
|
On 7/24/07, Nic Gibson < nicgcorbas.net">nicgcorbas.net> wrote:
I can see what you're getting at. In the last DocBook project I worked
on we customised to allow <uri>; in the <address> element. Would that
sort of thing work for you?
Yes, <uri>; is a more general name than the ones I suggested (<web> or <homepage>), but that isn't necessarily a bad thing, since my suggestions imply an HTTP URI, which may not always be the case.
I think something like that would work. ; In my case, all I want to do is put my company9;s website URL into <address>.
Colin
|
| Re: Element for an author's website URL |
|
2007-07-24 11:01:06 |
|
|
HI COLIN,
YOU CAN PROPOSE THIS FOR CONSIDERATION BY THE
DOCBOOK TECHNICAL COMMITTEE BY FILING A REQUEST ON THE DOCBOOK SOURCEFORGE
SITE.&NBSP; USE TRACKER->RFES AND THEN SUBMIT NEW.&NBSP; THAT'S THE WAY TO
GET IT IN THE QUEUE.
&NBSP;
&NBSP;
&NBSP;
----- ORIGINAL MESSAGE -----
SENT: TUESDAY, JULY 24, 2007 8:19
AM
SUBJECT: RE: [DOCBOOK] ELEMENT FOR AN
AUTHOR'S WEBSITE URL
[NOTE: I ACCIDENTALLY CCED THE WRONG LIST WITH THE BELOW
MESSAGE.&NBSP; DOCBOOK-APPS, FEEL FREE TO IGNORE.]
"THE
LINK IS A GENERAL PURPOSE HYPERTEXT ELEMENT."
THE ELEMENT I
PROPOSE HAS NOTHING TO DO WITH HYPERTEXT.&NBSP; IT IS SIMPLY ANOTHER PART OF
AN <ADDRESS>, SAME AS <EMAIL>, <PHONE>, ETC.&NBSP; IT IS
ANOTHER BIT OF INFORMATION ABOUT HOW TO CONTACT A PERSON/ORGANIZATION.
IF WE ALREADY HAVE <EMAIL>, THEN WHY NOT <WEB>; OR
<HOMEPAGE>?&NBSP; ALSO REMEMBER THAT AN EMAIL ADDRESS CAN BE DISPLAYED
AS HYPERTEXT AS WELL (I.E. A MAILTO: LINK IN A WEB BROWSER), BUT IT DOESN'T
HAVE TO BE.&NBSP; SAME WITH A HOME PAGE URL.&NBSP; WE DON'T HAVE TO USE
<LINK> FOR AN EMAIL ADDRESS WITHIN <ADDRESS>.
COLIN
ON 7/24/07, WEB.DE">TOM_SCHRWEB.DE <WEB.DE">TOM_SCHRWEB.DE > WROTE:
HI,
>
[...]
> > MAYBE I AM MISSING SOMETHING OBVIOUS, BUT WHY NOT USE
LINK?
>
> BECAUSE IT'S A LINK, NOT A URL
BUT A LINK CAN
ALSO BE A URI/URL. ACCORDING TO THE TDG[1]:
&NBSP;&NBSP;»THE LINK IS
A GENERAL PURPOSE HYPERTEXT ELEMENT. [...]
&NBSP;&NBSP; IF IT HAS AN
XLINK:HREF ATTRIBUTE, LINK IS THE EQUIVALENT OF AN
&NBSP;&NBSP; HTML
ANCHOR (<HTML:A HREF="...">) FOR CROSS REFERENCE
&NBSP;&NBSP; WITH
A UNIFORM RESOURCE IDENTIFIER (URI).«
MAYBE I DIDN'T UNDERSTAND YOUR
ARGUMENT. BUT WHY INTRODUCE
ANOTHER ELEMENT WHEN THERE IS ALREADY A
GENERAL PURPOSE ELEMENT
FOR THIS ISSUE?
BYE,
TOM
------
[1] HTTP://WWW.DOCBOOK.ORG/TDG5/EN/HTML/LINK.HTML
|
| Re: Element for an author's website URL |
|
2007-07-25 01:46:16 |
Colin Shapiro wrote:
> On 7/24/07, Nic Gibson <nicgcorbas.net> wrote:
>
>> I can see what you're getting at. In the last
DocBook project I worked
>> on we customised to allow <uri> in the
<address> element. Would that
>> sort of thing work for you?
>
>
> Yes, <uri> is a more general name than the ones I
suggested (<web> or
> <homepage>), but that isn't necessarily a bad
thing, since my suggestions
> imply an HTTP URI, which may not always be the case.
>
> I think something like that would work. In my case,
all I want to do is
> put
> my company's website URL into <address>.
Homepage is a more normal word for this?
I agree with the idea too.
An optional address element.
regards
--
Dave Pawson
XSLT XSL-FO FAQ.
http://www.dpawson.co.uk
------------------------------------------------------------
---------
To unsubscribe, e-mail: docbook-unsubscribelists.oasis-open.org
For additional commands, e-mail: docbook-helplists.oasis-open.org
|
|
| Re: Element for an author's website URL |
|
2007-07-25 03:48:09 |
On 25/07/07, Dave Pawson <davepdpawson.co.uk> wrote:
> Colin Shapiro wrote:
> > On 7/24/07, Nic Gibson <nicgcorbas.net> wrote:
> >
> >> I can see what you're getting at. In the last
DocBook project I worked
> >> on we customised to allow <uri> in the
<address> element. Would that
> >> sort of thing work for you?
> >
> >
> > Yes, <uri> is a more general name than the
ones I suggested (<web> or
> > <homepage>), but that isn't necessarily a
bad thing, since my suggestions
> > imply an HTTP URI, which may not always be the
case.
> >
> > I think something like that would work. In my
case, all I want to do is
> > put
> > my company's website URL into <address>.
>
> Homepage is a more normal word for this?
>
> I agree with the idea too.
> An optional address element.
We used <uri> because it was important to us to track
that fact that
is was the same sort of entity as the other uris in our
documents. I
think that a more descriptive name is just as valid though.
nic
--
Nic Gibson
Director, Corbas Consulting Ltd
Editorial and Technical Consultancy
http://www.corbas.co.uk/
------------------------------------------------------------
---------
To unsubscribe, e-mail: docbook-unsubscribelists.oasis-open.org
For additional commands, e-mail: docbook-helplists.oasis-open.org
|
|
| Re: Element for an author's website URL |
|
2007-07-25 10:03:49 |
|
On 7/25/07, Nic Gibson < nicgcorbas.net">nicgcorbas.net> wrote:
We used <uri>; because it was important to us to track that fact that
is was the same sort of entity as the other uris in our documents. I
think that a more descriptive name is just as valid though.
I already filed an RFE requesting that <uri>; be allowed within <address>. ; In the description, however, I also noted the possibility of using something like <website> instead. I'll leave it up to the DocBook TC to decide.
Colin
|
[1-7]
|
|
OCBOOK