Jump to content

Is this a Host Name?


doubledee

Recommended Posts

Why isn't it?

 

Because you can't go to GoDaddy and ask to register http://local.dev3/ or local.dev3...

 

local.dev3 is the Base URL for the Virtual Host I created on my laptop.

 

 

These are "Domain Names"...

yahoo
google
sitepoint
sony

 

 

And these are "Top-Level Domain Names"...

.com
.net
.org

 

 

Of course, I was asking about the whole enchilda...

http://local.dev3/

http://www.MySite.com/

 

 

I am inclined to use the term "BASE URL" to answer my original question...

 

 

Debbie

 

 

Link to comment
Share on other sites

Why isn't it?

 

Because you can't go to GoDaddy and ask to register http://local.dev3/ or local.dev3...

 

local.dev3 is the Base URL for the Virtual Host I created on my laptop.

 

 

These are "Domain Names"...

yahoo
google
sitepoint
sony

 

 

And these are "Top-Level Domain Names"...

.com
.net
.org

 

 

Of course, I was asking about the whole enchilda...

http://local.dev3/

http://www.MySite.com/

 

 

I am inclined to use the term "BASE URL" to answer my original question...

 

 

Debbie

 

 

 

It's still a domain name, it just doesn't use a TLD that is currently registrable.

 

You can make http://something.areallygnarlytld on your own machine if you want. It's still a domain name.

Link to comment
Share on other sites

You know what I meant... you are just being picky now.

 

No, you are not answering my original question.

 

I did NOT ask what you call "local.dev3" and "www.MySite.com"

 

 

My original question was...

What do you call the following...

Code: [select]

 

http://local.dev3/

 

http://www.MySite.com/

 

 

 

Are they "Host Names"?

 

 

Debbie

 

Link to comment
Share on other sites

Well, what I meant by what has this been covered is I'd consider that a "base URI". I think this wiki can answer your question:

<scheme name> : <hierarchical part> [ ? <query> ] [ # <fragment> ]

The scheme name consist of a sequence of characters beginning with a letter and followed by any combination of letters, digits, plus ("+"), period ("."), or hyphen ("-"). Although schemes are case-insensitive, the canonical form is lowercase and documents that specify schemes must do so with lowercase letters. It is followed by a colon (":").

The hierarchical part of the URI is intended to hold identification information hierarchical in nature. Usually this part begins with a double forward slash ("//"), followed by an authority part and an optional path.

-> The authority part holds an optional user information part terminated with "@" (e.g. username:password@), a hostname (i.e. domain name or IP address), and an optional port number preceded by a colon ":".

-> The path part is a sequence of segments (conceptually similar to directories, though not necessarily representing them) separated by a forward slash ("/"). Each segment can contain parameters separated from it using a semicolon (";"), though this is rarely used in practice.[/code]

 

E.g., without the protocol, you could consider those hostnames, but once you add in the protocol (http, ftp, etc.) it is now considered a URI.

Link to comment
Share on other sites

Well, what I meant by what has this been covered is I'd consider that a "base URI". I think this wiki can answer your question:

<scheme name> : <hierarchical part> [ ? <query> ] [ # <fragment> ]

The scheme name consist of a sequence of characters beginning with a letter and followed by any combination of letters, digits, plus ("+"), period ("."), or hyphen ("-"). Although schemes are case-insensitive, the canonical form is lowercase and documents that specify schemes must do so with lowercase letters. It is followed by a colon (":").

The hierarchical part of the URI is intended to hold identification information hierarchical in nature. Usually this part begins with a double forward slash ("//"), followed by an authority part and an optional path.

-> The authority part holds an optional user information part terminated with "@" (e.g. username:password@), a hostname (i.e. domain name or IP address), and an optional port number preceded by a colon ":".

-> The path part is a sequence of segments (conceptually similar to directories, though not necessarily representing them) separated by a forward slash ("/"). Each segment can contain parameters separated from it using a semicolon (";"), though this is rarely used in practice.[/code]

 

E.g., without the protocol, you could consider those hostnames, but once you add in the protocol (http, ftp, etc.) it is now considered a URI.

 

Or, since "http://local.debbie/" and "http://www.MySite.com" describe a *Location* you could also call them "base URLs", right?

 

 

Debbie

 

 

Link to comment
Share on other sites

What do you call the following...

 

I call them "URLs".  If you want to call them something different, or try and use a term that differentiates them from URLs with paths or other parts, then go ahead. You'll (probably) be understood.

 

Do note that the word "base" is often associated with URLs in the manner you're doing here, though not necessarily restricted to those with no path.  http://example.org/subsite may be termed, and understood as, a "base URL" if, for example, it hosted a sub-site within the main example.org website.  Similarly, the word "root" might be used in place of "base" to have the same meaning.  Calling them "base URLs" only makes sense if they are indeed the base of something (and URLs), which is the case.

Link to comment
Share on other sites

What do you call the following...

 

I call them "URLs".  If you want to call them something different, or try and use a term that differentiates them from URLs with paths or other parts, then go ahead. You'll (probably) be understood.

 

Do note that the word "base" is often associated with URLs in the manner you're doing here, though not necessarily restricted to those with no path.  http://example.org/subsite may be termed, and understood as, a "base URL" if, for example, it hosted a sub-site within the main example.org website.  Similarly, the word "root" might be used in place of "base" to have the same meaning.  Calling them "base URLs" only makes sense if they are indeed the base of something (and URLs), which is the case.

 

I agree.

 

 

Debbie

 

Link to comment
Share on other sites

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.