If the vocabulary is described in a text document, I can reuse it

The vocabulary does not need to have a persistent URI

I just need to know the URIs of the vocabulary, it does not need to be documented

A vocabulary that is reused by other vocabularies is more preferable than another one that is not reused by others

There is a problem, an entity may not have identifiers with "/" and "#" at the same time

No problem, having two URIs only implies that there are two web pages about Madrid

There is a problem, all the identifiers of an entity must proceed from the same domain

No problem, an entity may have two different identifiers

The URI does not need to tell me anything about the resource it refers to

The URI refers to a district in a city

The URI refers to a city

The URI refers to a resource in a district in a city

Music, Games, Economy

People, Space, Travel

eBusiness, Government, Police

Health, Food, Security

It is preferable to create descriptive URIs than to document the vocabulary

There is no need to specify the license of the vocabulary

Having an HTML page describing the vocabulary is enough, there is no need to publish it on the Web

It is better if the vocabulary is described in more than one language

Slash ("/")

Hash ("#")

I could not use them for commercial purposes; furthermore, I must attribute their authorship and I share my data with the same license

I cannot use them

I could use them for commercial purposes, provided I attribute their authorship and I share my data with the same license

I cannot use them for commercial purposes; I must attribute their authorship, and I can share my data with any license I wish

I could find one or more ontologies that I can use to represent my data or part of them

There will always be one or more ontologies that I can use to represent all my data

It is not advisable to reuse ontologies for a specific use case

Always

Never

It doesn't need to be so, but it could be