<http://webisa.webdatacommons.org/prov/448711743>	<http://www.w3.org/ns/prov#wasDerivedFrom>	<http://webisa.webdatacommons.org/74599466> .
<http://webisa.webdatacommons.org/prov/340588686>	<http://www.w3.org/ns/prov#wasDerivedFrom>	<http://webisa.webdatacommons.org/74599466> .
<http://webisa.webdatacommons.org/74599466>	<http://www.w3.org/1999/02/22-rdf-syntax-ns#type>	<http://www.w3.org/ns/prov#Entity> .
<http://webisa.webdatacommons.org/prov/446320622>	<http://www.w3.org/ns/prov#wasDerivedFrom>	<http://webisa.webdatacommons.org/74599466> .
<http://webisa.webdatacommons.org/74599466>	<http://www.w3.org/ns/prov#wasQuotedFrom>	<circleid.com> .
<http://webisa.webdatacommons.org/prov/223261784>	<http://www.w3.org/ns/prov#wasDerivedFrom>	<http://webisa.webdatacommons.org/74599466> .
<http://webisa.webdatacommons.org/prov/436168417>	<http://www.w3.org/ns/prov#wasDerivedFrom>	<http://webisa.webdatacommons.org/74599466> .
<http://webisa.webdatacommons.org/74599466>	<http://www.w3.org/ns/prov#value>	"I am also constantly impressed with Yahoo, Microsoft, Google, Time Warner, T-Mobile, BT, Verizon, and other companies that are developers or hold a stake in internet naming are present at the ICANN meetings and asking highly sophisticated questions that indicate a strong grasp on the complexities and inter-operability of the naming system with applications." .