How to cook Brussels sprouts using crock-pot?

Slow Cooked Brussels Sprouts *recipe adapted from a food network recipe for use in the crockpot Ingredients * 2 tablespoons vegetable oil * 1 pound Brussels sprouts, trimmed * Salt * 3 tablespoons butter * 3 tablespoons finely chopped shallots * 3/4 cup chicken broth Directions 1. Heat vegetable oil over high heat in a large skillet. Add Brussels sprouts and brown all over by shaking the pan often.

*You can opt to skip this step if you only want to use the crockpot, but they turn out much better if you brown them first* 2. Season with salt, to taste. Remove Brussels sprouts from pan and add to crockpot, set heat to medium 3.In a skillet add the butter to melt.

Add shallots and saute for a minute or two. Once shallots are done add to the crock pot.4. Add the chicken stock, cover and cook for 30 minutes or until sprouts are soft and tender.

From RFC 2396 : A URI can be further classified as a locator, a name, or both. The term "Uniform Resource Locator" (URL) refers to the subset of URI that identify resources via a representation of their primary access mechanism (e.g. , their network "location"), rather than identifying the resource by name or by some other attribute(s) of that resource. The term "Uniform Resource Name" (URN) refers to the subset of URI that are required to remain globally unique and persistent even when the resource ceases to exist or becomes unavailable So any URL is a URI, but some URIs aren't URLs, they're URNs instead.

Except the ones which are both URNs and URLs Clear as mud?

From RFC 2396: A URI can be further classified as a locator, a name, or both. The term "Uniform Resource Locator" (URL) refers to the subset of URI that identify resources via a representation of their primary access mechanism (e.g. , their network "location"), rather than identifying the resource by name or by some other attribute(s) of that resource. The term "Uniform Resource Name" (URN) refers to the subset of URI that are required to remain globally unique and persistent even when the resource ceases to exist or becomes unavailable.

So any URL is a URI, but some URIs aren't URLs, they're URNs instead. Except the ones which are both URNs and URLs. Clear as mud?

5 I've seen more transparent liquid soil than this, but not much. ;) – Chris Charabaruk Oct 6 '08 at 21:33 2 Only URIs with the urn: scheme are URNs. A URI could be a classic URL, a URN, or just a URI that doesn't start with "urn:" and doesn't refer to a location of a resource.

– Mark Cidade Oct 6 '08 at 21:38 One example are InfoPath URNs, which are important i.e. In Sharepoint Workflows: urn:schemas-microsoft-com:office:infopath:blogsample:-myXSD-2004-05-19T20-48-18 – Michael Stum Oct 6 '08 at 21:49 2 Note that RFC 2396 has been obsoleted by RFC 3986 a long time ago (but that doesn't change the facts...) – Julian Reschke Oct 6 '08 at 12:20.

URIs identify and URLs locate; however, locations are also identifications, so every URL is also a URI, but there are URIs which are not URLs. Examples Roger Pate This is my name, which is identification. It is like a URI, but cannot be a URL, as it tells you nothing about my location or how to contact me.In this case it also happens to identify at least 5 other people in the USA alone.

4914 West Bay Street, Nassau, Bahamas This is a location, which is identification for that physical location. It is like both a URL and URI (since all URLs are URIs), and also identifies me indirectly as "resident of..". In this case it uniquely identifies me, but that would change if I get a roommate.

I say "like" because these examples do not follow the required syntax. Popular confusion From Wikipedia: In computing, a Uniform Resource Locator (URL) is a subset of the Uniform Resource Identifier (URI) that specifies where an identified resource is available and the mechanism for retrieving it.In popular usage and in many technical documents and verbal discussions it is often incorrectly used as a synonym for URI, ... emphasis mine Because of this common confusion, many products and documentation incorrectly use one term instead of the other, assign their own distinction, or use them synonymously. URNs My name, Roger Pate, could be like a URN, except those are much more regulated and intended to be unique across both space and time.

Because I currently share this name with other people, it's not globally unique and would not be appropriate as a URN. However, even if no other family used this name, I'm named after my paternal grandfather, so it still wouldn't be unique across time. And even if that wasn't the case, the possibility of naming my descendants after me make this unsuitable as a URN.

URNs are different from URLs in this rigid uniqueness constraint, even though they both share the syntax of URIs.

That is great explanation thanks :) – Sarfraz Dec 31 '09 at 13:09 Well said!. ----------- – Rev316 Jan 5 '10 at 23:03 Very Well Said!. ------------ – this.

__curious_geek Jun 21 '10 at 11:40 17 even my mother would get it now :D – migajek Jun 21 '10 at 21:09 6 For those who don't know: "You do not really understand something unless you can explain it to your grandmother. " — Albert Einstein – George Bailey May 6 at 21:11.

In summary: a URI identifies, a URL identifies and locates. Consider a specific edition of Shakespeare's play Romeo and Juliet, of which you have a digital copy on your home network. You could identify the text as urn:isbn:0-486-27557-4.

That would be a URI, but more specifically a URN because it names the text. You could also identify the text as file://hostname/sharename/RomeoAndJuliet.pdf. That would also be a URI, but more specifically a URL because it locates the text.(Note that my example is adapted from Wikipedia).

3 It's helpful to note the actual URN (to see how it compares to a URL): urn:isbn:0-486-27557-4 – Michael Brewer-Davis Dec 31 '09 at 18:15 @Michael - It is my understanding that ISBN 0486275574 also names the text and thus qualify as a URN. I choose a format that I believed would be more familiar to readers. – Greg Dec 31 '09 at 18:47.

URI => en.wikipedia.org/wiki/Uniform_Resource_I... URL's are a subset of URI's (which also contain URNs). Basically, a URI is a general identifier, where a URL specifies a location and a URN specifies a name.

URI is kind of the super class of URL's and URN's. Wikipedia has a fine article about them with links to the right set of RFCs.

See this document. Specifically, a URL is a type of URI that identifies a resource via a representation of its primary access mechanism (e.g. , its network "location"), rather than by some other attributes it may have.It's not an extremely clear term, really.

Thanks that link is helpful too :) – Sarfraz Jan 26 '10 at 8:20.

Due to difficulties to clearly distinguish between URI and URL, as far as I remember W3C does not make a difference any longer between URI and URL (w3.org/Addressing/).

That is nice info too :) – Sarfraz Jan 2 '10 at 5:31.

Another example I like to use when thinking about URI's is the xmlns attribute of an XML document: some text In this case com.mycompany. Mynode would be a URI that uniquely identifies the "myPrefix" namespace for all of the elements that use it within my XML document. Is is not a URL because it is only used to identify, not to locate something per se.

They're the same thing. A URI is a generalization of a URL. Originally, URIs were planned to be divided into URLs (addresses) and URNs (names) but then there was little difference between a URL and URI and http URIs were used as namespaces even though they didn't actually locate any resources.

I thought it was the other way around. A URL refers to a concrete object, and a URI can refer to that or a concept or anything else. – Chris Charabaruk Oct 6 '08 at 21:30 A URL locates a resource and is a kind of URI, which identifies a resource.

– Mark Cidade Oct 6 '08 at 21:33.

A URI identifies a resource either by location, or a name, or both. More often than not, most of us use URIs that defines a location to a resource. The fact that a URI can identify a resources by both name and location has lead to a lot of the confusion in my opinion.

A URI has two specializations known as URL and URN. A URL is a specialization of URI that defines the network location of a specific resource. Unlike a URN, the URL defines how the resource can be obtained.

We use URLs every day in the form of http://stackoverflow.com, etc. But a URL doesn’t have to be an HTTP URL, it can be ftp://xyz. Com, etc.For more information on URI you can use the following link, http://www.eie.polyu.edu.hk/~entchsun/EIE423Lab/wiurl.html.

Thanks for those nice links... – Sarfraz Jan 26 '10 at 8:21.

Wikipedia will give all the information you need here... en.wikipedia.org/wiki/URI "A URL is a URI that, in addition to identifying a resource, provides means of acting upon or obtaining a representation of the resource by describing its primary access mechanism or network "location".

Although the terms URI and URL are strictly defined, many use the terms for other things than they are defined for. Let’s take Apache for example. If example.com/foo is requested from an Apache server, you’ll have the following environment variables set: REDIRECT_URL: /foo REQUEST_URI: /foo With mod_rewrite enabled, you will also have these variables: REDIRECT_SCRIPT_URL: /foo REDIRECT_SCRIPT_URI: example.com/foo SCRIPT_URL: /foo SCRIPT_URI: example.com/foo This might be the reason for some of the confusion.

I was wondering about the same thing and I've found this: docs.kohanaphp.com/helpers/url. You can see a clear example using the url::current() method. If you have this URL: http://localhost/kohana/index.

Php/welcome/home. Html? Query=string then using url:current() gives you the URI which, according to the documentation, is: welcome/home.

These are some very well-written but long-winded answers. URL - example.com/some/page.html URI - /some/page. Html Put simply, URL is the full way to indentify any resource anywhere and can have different protocols like FTP, HTTP, SCP, etc.URI is a resource on the current domain, so it needs less information to be found.

1 This answer may be over-simplified but look at the context of his question. It will be more helpful to him that waffling on about XML namespaces! – Phil Sturgeon Dec 31 '09 at 12:18 6 This answer is not only wrong but actively misleading.

Both examples are URLs. And since every URL is also a URI, this means that both examples are URIs. For the purpose of demonstrating the difference between URIs and URLs, this is totally useless.

– Jörg W Mittag Dec 31 '09 at 12:40 @Jorg: totally agreed :) – Sarfraz Jan 2 '10 at 7:29 3 This is the difference as far as CodeIgniter is concerned. In every instance they use the word URL or URI this is the difference they are talking about. Therefore in the grand-scheme of the web, it is not 100% correct but in the scope of the OP's question (the difference in CodeIgniter), this answer is perfectly correct.

– Phil Sturgeon Jan 11 '10 at 11:13 @Phil Sturgeon - agreed, for the purpose of this question, this is how CI distinguishes between URL and URI. – Matt Jan 11 '10 at 11:20.

The answer is ambiguous. In Java it is frequently used in this way: An Uniform Resource Locator (URL) is the term used to identify an Internet resource including the scheme( http, https, ftp, news, etc. ). For instance What's the difference between a URI and a URL?

An Uniform Resource Identifier (URI) is used to identify a single document in the Web Server: For instance /questions/176264/whats-the-difference-between-a-uri-and-a-url In Java servlets, the URI frequently refers to the document without the web application context.

I don't hate them, but I am not a fan. I don't really follow football that much.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.