<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
	<id>tag:old.nabble.com,2006:forum-11606</id>
	<title>Nabble - w3.org - public-glossary</title>
	<updated>2008-10-01T06:42:24Z</updated>
	<link rel="self" type="application/atom+xml" href="http://old.nabble.com/w3.org---public-glossary-f11606.xml" />
	<link rel="alternate" type="text/html" href="http://old.nabble.com/w3.org---public-glossary-f11606.html" />
	<subtitle type="html">Purpose: Public discussion forum for the W3C Glossary project.</subtitle>
	
<entry>
	<id>tag:old.nabble.com,2006:post-19760748</id>
	<title>Is public glossary still open?</title>
	<published>2008-10-01T06:42:24Z</published>
	<updated>2008-10-01T06:42:24Z</updated>
	<author>
		<name>sally-27</name>
	</author>
	<content type="html">&lt;html xmlns:v=&quot;urn:schemas-microsoft-com:vml&quot; xmlns:o=&quot;urn:schemas-microsoft-com:office:office&quot; xmlns:w=&quot;urn:schemas-microsoft-com:office:word&quot; xmlns=&quot;http://www.w3.org/TR/REC-html40&quot;&gt;

&lt;head&gt;
&lt;meta http-equiv=Content-Type content=&quot;text/html; charset=us-ascii&quot;&gt;
&lt;meta name=Generator content=&quot;Microsoft Word 11 (filtered medium)&quot;&gt;

&lt;!--[if gte mso 9]&gt;&lt;xml&gt;
 &lt;o:shapedefaults v:ext=&quot;edit&quot; spidmax=&quot;1026&quot; /&gt;
&lt;/xml&gt;&lt;![endif]--&gt;&lt;!--[if gte mso 9]&gt;&lt;xml&gt;
 &lt;o:shapelayout v:ext=&quot;edit&quot;&gt;
  &lt;o:idmap v:ext=&quot;edit&quot; data=&quot;1&quot; /&gt;
 &lt;/o:shapelayout&gt;&lt;/xml&gt;&lt;![endif]--&gt;
&lt;/head&gt;

&lt;body lang=RU link=blue vlink=purple&gt;

&lt;div class=Section1&gt;

&lt;p class=MsoNormal&gt;&lt;font size=2 face=Arial&gt;&lt;span lang=EN-US style='font-size:
10.0pt;font-family:Arial'&gt;Hello to everyone!&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/font&gt;&lt;/p&gt;

&lt;p class=MsoNormal&gt;&lt;font size=2 face=Arial&gt;&lt;span lang=EN-US style='font-size:
10.0pt;font-family:Arial'&gt;&lt;o:p&gt;&amp;nbsp;&lt;/o:p&gt;&lt;/span&gt;&lt;/font&gt;&lt;/p&gt;

&lt;p class=MsoNormal&gt;&lt;font size=2 face=Arial&gt;&lt;span lang=EN-US style='font-size:
10.0pt;font-family:Arial'&gt;I responded to a topic regarding NASA actions. Time
passed, but nobody commented it. &lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/font&gt;&lt;/p&gt;

&lt;p class=MsoNormal&gt;&lt;font size=2 face=Arial&gt;&lt;span lang=EN-US style='font-size:
10.0pt;font-family:Arial'&gt;And as I can see, where are no new topics to discuss.&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/font&gt;&lt;/p&gt;

&lt;p class=MsoNormal&gt;&lt;font size=2 face=Arial&gt;&lt;span lang=EN-US style='font-size:
10.0pt;font-family:Arial'&gt;&lt;o:p&gt;&amp;nbsp;&lt;/o:p&gt;&lt;/span&gt;&lt;/font&gt;&lt;/p&gt;

&lt;p class=MsoNormal&gt;&lt;font size=2 face=Arial&gt;&lt;span lang=EN-US style='font-size:
10.0pt;font-family:Arial'&gt;Is this group still working? Or should I join a group
which is analogous? &lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/font&gt;&lt;/p&gt;

&lt;p class=MsoNormal&gt;&lt;font size=2 face=Arial&gt;&lt;span lang=EN-US style='font-size:
10.0pt;font-family:Arial'&gt;&lt;o:p&gt;&amp;nbsp;&lt;/o:p&gt;&lt;/span&gt;&lt;/font&gt;&lt;/p&gt;

&lt;p class=MsoNormal&gt;&lt;font size=2 face=Arial&gt;&lt;span lang=EN-US style='font-size:
10.0pt;font-family:Arial'&gt;&lt;o:p&gt;&amp;nbsp;&lt;/o:p&gt;&lt;/span&gt;&lt;/font&gt;&lt;/p&gt;

&lt;p class=MsoNormal&gt;&lt;font size=2 face=Arial&gt;&lt;span lang=EN-US style='font-size:
10.0pt;font-family:Arial'&gt;Sincerely,&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/font&gt;&lt;/p&gt;

&lt;p class=MsoNormal&gt;&lt;font size=2 face=Arial&gt;&lt;span lang=EN-US style='font-size:
10.0pt;font-family:Arial'&gt;&lt;o:p&gt;&amp;nbsp;&lt;/o:p&gt;&lt;/span&gt;&lt;/font&gt;&lt;/p&gt;

&lt;p class=MsoNormal&gt;&lt;font size=2 face=Arial&gt;&lt;span lang=EN-US style='font-size:
10.0pt;font-family:Arial'&gt;Sally Morgan&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;Ecommerce-Land
Company&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/font&gt;&lt;/p&gt;

&lt;p class=MsoNormal&gt;&lt;font size=2 face=Arial&gt;&lt;span lang=EN-US style='font-size:
10.0pt;font-family:Arial'&gt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=19760748&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;sally@...&lt;/a&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;a href=&quot;http://www.ecommerce-land.com/&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.ecommerce-land.com&lt;/a&gt; &lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/font&gt;&lt;/p&gt;

&lt;/div&gt;

&lt;/body&gt;

&lt;/html&gt;
</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Is-public-glossary-still-open--tp19760748p19760748.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-19292032</id>
	<title>Re: nasa</title>
	<published>2008-09-03T08:43:00Z</published>
	<updated>2008-09-03T08:43:00Z</updated>
	<author>
		<name>sally-27</name>
	</author>
	<content type="html">&lt;html xmlns:v=&quot;urn:schemas-microsoft-com:vml&quot; xmlns:o=&quot;urn:schemas-microsoft-com:office:office&quot; xmlns:w=&quot;urn:schemas-microsoft-com:office:word&quot; xmlns=&quot;http://www.w3.org/TR/REC-html40&quot;&gt;

&lt;head&gt;
&lt;meta http-equiv=Content-Type content=&quot;text/html; charset=us-ascii&quot;&gt;
&lt;meta name=Generator content=&quot;Microsoft Word 11 (filtered medium)&quot;&gt;

&lt;!--[if gte mso 9]&gt;&lt;xml&gt;
 &lt;o:shapedefaults v:ext=&quot;edit&quot; spidmax=&quot;1026&quot; /&gt;
&lt;/xml&gt;&lt;![endif]--&gt;&lt;!--[if gte mso 9]&gt;&lt;xml&gt;
 &lt;o:shapelayout v:ext=&quot;edit&quot;&gt;
  &lt;o:idmap v:ext=&quot;edit&quot; data=&quot;1&quot; /&gt;
 &lt;/o:shapelayout&gt;&lt;/xml&gt;&lt;![endif]--&gt;
&lt;/head&gt;

&lt;body lang=RU link=blue vlink=purple&gt;

&lt;div class=Section1&gt;

&lt;p class=MsoNormal&gt;&lt;font size=2 face=Arial&gt;&lt;span lang=EN-US style='font-size:
10.0pt;font-family:Arial'&gt;Hello Candace,&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/font&gt;&lt;/p&gt;

&lt;p class=MsoNormal&gt;&lt;font size=2 face=Arial&gt;&lt;span lang=EN-US style='font-size:
10.0pt;font-family:Arial'&gt;&lt;o:p&gt;&amp;nbsp;&lt;/o:p&gt;&lt;/span&gt;&lt;/font&gt;&lt;/p&gt;

&lt;p class=MsoNormal&gt;&lt;font size=2 face=Arial&gt;&lt;span lang=EN-US style='font-size:
10.0pt;font-family:Arial'&gt;Very interesting article! Thank you.&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/font&gt;&lt;/p&gt;

&lt;p class=MsoNormal&gt;&lt;font size=2 face=Arial&gt;&lt;span lang=EN-US style='font-size:
10.0pt;font-family:Arial'&gt;&lt;o:p&gt;&amp;nbsp;&lt;/o:p&gt;&lt;/span&gt;&lt;/font&gt;&lt;/p&gt;

&lt;p class=MsoNormal&gt;&lt;font size=2 face=Arial&gt;&lt;span lang=EN-US style='font-size:
10.0pt;font-family:Arial'&gt;But I wonder whether NASA takes care of everything
regarding organization process and scientific equipment?&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/font&gt;&lt;/p&gt;

&lt;p class=MsoNormal&gt;&lt;font size=2 face=Arial&gt;&lt;span lang=EN-US style='font-size:
10.0pt;font-family:Arial'&gt;As far as I know, human being is still not completely
aware of the life on the moon. And there is always some risk to the staff of astronauts.
Also, according to some information sources, we do not have enough professional
equipment to set the permanent base on the moon, even if it is NASA moonbase.&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/font&gt;&lt;/p&gt;

&lt;p class=MsoNormal&gt;&lt;font size=2 face=Arial&gt;&lt;span lang=EN-US style='font-size:
10.0pt;font-family:Arial'&gt;&lt;o:p&gt;&amp;nbsp;&lt;/o:p&gt;&lt;/span&gt;&lt;/font&gt;&lt;/p&gt;

&lt;p class=MsoNormal&gt;&lt;font size=2 face=Arial&gt;&lt;span lang=EN-US style='font-size:
10.0pt;font-family:Arial'&gt;Do you know any sources where I can find established
fact regarding this &amp;#8220;NASA and The Moon&amp;#8221; question.&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/font&gt;&lt;/p&gt;

&lt;p class=MsoNormal&gt;&lt;font size=2 face=Arial&gt;&lt;span lang=EN-US style='font-size:
10.0pt;font-family:Arial'&gt;&lt;o:p&gt;&amp;nbsp;&lt;/o:p&gt;&lt;/span&gt;&lt;/font&gt;&lt;/p&gt;

&lt;p class=MsoNormal&gt;&lt;font size=2 face=Arial&gt;&lt;span lang=EN-US style='font-size:
10.0pt;font-family:Arial'&gt;&lt;o:p&gt;&amp;nbsp;&lt;/o:p&gt;&lt;/span&gt;&lt;/font&gt;&lt;/p&gt;

&lt;p class=MsoNormal&gt;&lt;font size=2 face=Arial&gt;&lt;span lang=EN-US style='font-size:
10.0pt;font-family:Arial'&gt;Regards,&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/font&gt;&lt;/p&gt;

&lt;p class=MsoNormal&gt;&lt;font size=2 face=Arial&gt;&lt;span lang=EN-US style='font-size:
10.0pt;font-family:Arial'&gt;&lt;o:p&gt;&amp;nbsp;&lt;/o:p&gt;&lt;/span&gt;&lt;/font&gt;&lt;/p&gt;

&lt;p class=MsoNormal&gt;&lt;font size=2 face=Arial&gt;&lt;span lang=EN-US style='font-size:
10.0pt;font-family:Arial'&gt;Sally Morgan&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;Ecommerce-Land
Company&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/font&gt;&lt;/p&gt;

&lt;p class=MsoNormal&gt;&lt;font size=2 face=Arial&gt;&lt;span lang=EN-US style='font-size:
10.0pt;font-family:Arial'&gt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=19292032&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;sally@...&lt;/a&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;a href=&quot;http://www.ecommerce-land.com/&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.ecommerce-land.com&lt;/a&gt; &lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/font&gt;&lt;/p&gt;

&lt;p class=MsoNormal&gt;&lt;font size=2 face=Arial&gt;&lt;span lang=EN-US style='font-size:
10.0pt;font-family:Arial'&gt;&lt;o:p&gt;&amp;nbsp;&lt;/o:p&gt;&lt;/span&gt;&lt;/font&gt;&lt;/p&gt;

&lt;/div&gt;

&lt;/body&gt;

&lt;/html&gt;
</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Re%3A-nasa-tp19292032p19292032.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-12864071</id>
	<title>nasa</title>
	<published>2007-09-24T11:11:11Z</published>
	<updated>2007-09-24T11:11:11Z</updated>
	<author>
		<name>Candace Smith</name>
	</author>
	<content type="html">&lt;br&gt;nasa moonbase
&lt;br&gt;&lt;br&gt;The next astronauts to work on the moon will likely live in larger
&lt;br&gt;habitats and drive sporty new rovers capable of
&lt;br&gt;two-week treks, NASA officials said Thursday.
&lt;br&gt;&lt;br&gt;Rather than assembling a lunar outpost over time from a multitude of
&lt;br&gt;small, separately launched modules, NASA is now hoping
&lt;br&gt;to land up to three large habitats on fewer flights to build a beachhead
&lt;br&gt;on the moon, the space agency said.
&lt;br&gt;&lt;br&gt;Doug Cooke, NASA's deputy associate administrator for exploration
&lt;br&gt;systems, said that the space agency's revised lunar plan
&lt;br&gt;calls for the launching of larger habitats to the moon on unmanned cargo
&lt;br&gt;flights.
&lt;br&gt;&lt;br&gt;? Click here to visit FOXNews.com's Space Center.
&lt;br&gt;&lt;br&gt;That way, the first new lunar astronauts could begin to reap science
&lt;br&gt;rewards faster than if they had to haul smaller habitat
&lt;br&gt;sections and hardware to the moon on each flight, then combine them into
&lt;br&gt;a larger base to support long-duration expeditions.
&lt;br&gt;&lt;br&gt;&amp;quot;We want to get scientific return. We want to get information that will
&lt;br&gt;help, potentially, space commerce and we want to get
&lt;br&gt;international participation early,&amp;quot; Cooke told reporters in a
&lt;br&gt;teleconference. &amp;quot;All of these objectives we want to address as early
&lt;br&gt;in the flights as we possibly can by getting the outpost up and running
&lt;br&gt;quickly.&amp;quot;
&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;a href=&quot;http://www.wholeearthphonesex.com&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.wholeearthphonesex.com&lt;/a&gt;&lt;br&gt;&lt;a href=&quot;http://www.phone-sex-psychologist.com&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.phone-sex-psychologist.com&lt;/a&gt;&lt;br&gt;&lt;a href=&quot;http://www.phone-sex-hypnosis.com&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.phone-sex-hypnosis.com&lt;/a&gt;&lt;br&gt;&lt;a href=&quot;http://www.phone-sex-dictionary.com&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.phone-sex-dictionary.com&lt;/a&gt;&lt;br&gt;&lt;a href=&quot;http://www.phone-sex-handjobs.com&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.phone-sex-handjobs.com&lt;/a&gt;&lt;br&gt;&lt;a href=&quot;http://www.your-account.info&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.your-account.info&lt;/a&gt;&lt;br&gt;&lt;a href=&quot;http://www.freephonesex.org&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.freephonesex.org&lt;/a&gt;&lt;br&gt;&lt;a href=&quot;http://www.1800phonesex.net&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.1800phonesex.net&lt;/a&gt;&lt;br&gt;&lt;a href=&quot;http://www.1on1phonesex.com&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.1on1phonesex.com&lt;/a&gt;&lt;br&gt;&lt;a href=&quot;http://www.phonesexphone.com&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.phonesexphone.com&lt;/a&gt;&lt;br&gt;&lt;a href=&quot;http://www.hotphone.com&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.hotphone.com&lt;/a&gt;&lt;br&gt;&lt;a href=&quot;http://www.xxx-rated.com&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.xxx-rated.com&lt;/a&gt;&lt;br&gt;&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/nasa-tp12864071p12864071.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-12061721</id>
	<title>Re: Legal Notice in Individual SKOS Glossaries Missing</title>
	<published>2007-08-08T14:53:21Z</published>
	<updated>2007-08-08T14:53:21Z</updated>
	<author>
		<name>Sina K. Heshmati</name>
	</author>
	<content type="html">&lt;br&gt;Dominique Hazael-Massieux,
&lt;br&gt;&lt;br&gt;It would be good if we kept the dc:rights for human-readable copyright notice, and eventually use dcterms:license for the license URL. So, the rdf:Description with an empty rdf:about wouldn't be needed and instead, the following properties could be added to the main rdf:Description.
&lt;br&gt;&lt;br&gt;&amp;lt;dcterms:license xmlns:dcterms=&amp;quot;&lt;a href=&quot;http://purl.org/dc/terms/&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://purl.org/dc/terms/&lt;/a&gt;&amp;quot; &amp;nbsp;rdf:resource=&amp;quot;&lt;a href=&quot;http://www.w3.org/Consortium/Legal/2002/copyright-documents-20021231&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.w3.org/Consortium/Legal/2002/copyright-documents-20021231&lt;/a&gt;&amp;quot;/&amp;gt;
&lt;br&gt;&amp;lt;dc:rights&amp;gt;Copyright &amp;#169; [THE RELEVANT COPYRIGHT STATEMENT]&amp;lt;/dc:rights&amp;gt;
&lt;br&gt;&lt;br&gt;I'd also like to take this opportunity to thank you on behalf of the Forrest community.
&lt;br&gt;&lt;br&gt;Sina K. Heshmati
&lt;br&gt;&lt;br&gt;On Tue, August 7, 2007 3:44 pm, Dominique Hazael-Massieux &amp;lt;&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=12061721&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;dom@...&lt;/a&gt;&amp;gt; said:
&lt;br&gt;&lt;div class='shrinkable-quote'&gt;&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; Hi,
&lt;br&gt;&amp;gt; Le vendredi 03 août 2007 à 16:03 +0200, Sina K. Heshmati a
&lt;br&gt;&amp;gt; écrit :
&lt;br&gt;&amp;gt;&amp;gt; A few glossaries that are made available [2] by the W3C Glossary and Dictionary
&lt;br&gt;&amp;gt;&amp;gt; Project [3] in SKOS format have been selected to serve as samples to demonstrate
&lt;br&gt;&amp;gt;&amp;gt; how the plugin aggregates content from external sources.
&lt;br&gt;&amp;gt;&amp;gt;
&lt;br&gt;&amp;gt;&amp;gt; As a result, the content from an external source may be presented in pages with
&lt;br&gt;&amp;gt;&amp;gt; Apache copyright statement. Therefore, we need to make sure that the right legal
&lt;br&gt;&amp;gt;&amp;gt; notice is associated with the aggregated content. To that end, I was wondering
&lt;br&gt;&amp;gt;&amp;gt; if a project committer could add an explicit legal notice to SKOS glossaries
&lt;br&gt;&amp;gt;&amp;gt; [2],
&lt;br&gt;&amp;gt;&amp;gt; so that we'll be able to refer to those resources in our source code.
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; I have added the following notice to most glossaries in the W3C
&lt;br&gt;&amp;gt; glossary:
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; &amp;lt;rdf:Description rdf:about=&amp;quot;&amp;quot;&amp;gt;
&lt;br&gt;&amp;gt; &amp;nbsp; &amp;lt;dc:rights xmlns:dc=&amp;quot;&lt;a href=&quot;http://purl.org/dc/elements/1.1/&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://purl.org/dc/elements/1.1/&lt;/a&gt;&amp;quot;
&lt;br&gt;&amp;gt; rdf:resource=&amp;quot;&lt;a href=&quot;http://www.w3.org/Consortium/Legal/2002/copyright-documents-20021231&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.w3.org/Consortium/Legal/2002/copyright-documents-20021231&lt;/a&gt;&amp;quot;
&lt;br&gt;&amp;gt; /&amp;gt;
&lt;br&gt;&amp;gt; &amp;lt;/rdf:Description&amp;gt;
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; There is once instance where the license terms refer to a different URI
&lt;br&gt;&amp;gt; (the one for the HTTP spec), and one for which the licensing terms are
&lt;br&gt;&amp;gt; undefined (and for which I didn't set any value).
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; Hope this helps,
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; Dom
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt;&amp;gt; [1] &lt;a href=&quot;http://forrest.apache.org/&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://forrest.apache.org/&lt;/a&gt;&lt;br&gt;&amp;gt;&amp;gt; [2] &lt;a href=&quot;http://www.w3.org/2003/03/glossary-project/data/glossaries/&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.w3.org/2003/03/glossary-project/data/glossaries/&lt;/a&gt;&lt;br&gt;&amp;gt;&amp;gt; [3] &lt;a href=&quot;http://www.w3.org/QA/2003/01/Glossary&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.w3.org/QA/2003/01/Glossary&lt;/a&gt;&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; 
&lt;/div&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Legal-Notice-in-Individual-SKOS-Glossaries-Missing-tp12030497p12061721.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-12034680</id>
	<title>Re: Legal Notice in Individual SKOS Glossaries Missing</title>
	<published>2007-08-07T07:44:27Z</published>
	<updated>2007-08-07T07:44:27Z</updated>
	<author>
		<name>Dominique Hazael-Massieux-2</name>
	</author>
	<content type="html">&lt;br&gt;Hi,
&lt;br&gt;Le vendredi 03 août 2007 à 16:03 +0200, Sina K. Heshmati a écrit :
&lt;br&gt;&amp;gt; A few glossaries that are made available [2] by the W3C Glossary and Dictionary Project [3] in SKOS format have been selected to serve as samples to demonstrate
&lt;br&gt;&amp;gt; how the plugin aggregates content from external sources.
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; As a result, the content from an external source may be presented in pages with 
&lt;br&gt;&amp;gt; Apache copyright statement. Therefore, we need to make sure that the right legal 
&lt;br&gt;&amp;gt; notice is associated with the aggregated content. To that end, I was wondering
&lt;br&gt;&amp;gt; if a project committer could add an explicit legal notice to SKOS glossaries [2],
&lt;br&gt;&amp;gt; so that we'll be able to refer to those resources in our source code.
&lt;br&gt;&lt;br&gt;I have added the following notice to most glossaries in the W3C
&lt;br&gt;glossary:
&lt;br&gt;&lt;br&gt;&amp;lt;rdf:Description rdf:about=&amp;quot;&amp;quot;&amp;gt;
&lt;br&gt;&amp;nbsp; &amp;lt;dc:rights xmlns:dc=&amp;quot;&lt;a href=&quot;http://purl.org/dc/elements/1.1/&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://purl.org/dc/elements/1.1/&lt;/a&gt;&amp;quot;
&lt;br&gt;rdf:resource=&amp;quot;&lt;a href=&quot;http://www.w3.org/Consortium/Legal/2002/copyright-documents-20021231&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.w3.org/Consortium/Legal/2002/copyright-documents-20021231&lt;/a&gt;&amp;quot; /&amp;gt;
&lt;br&gt;&amp;lt;/rdf:Description&amp;gt;
&lt;br&gt;&lt;br&gt;There is once instance where the license terms refer to a different URI
&lt;br&gt;(the one for the HTTP spec), and one for which the licensing terms are
&lt;br&gt;undefined (and for which I didn't set any value).
&lt;br&gt;&lt;br&gt;Hope this helps,
&lt;br&gt;&lt;br&gt;Dom
&lt;br&gt;&lt;br&gt;&amp;gt; [1] &lt;a href=&quot;http://forrest.apache.org/&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://forrest.apache.org/&lt;/a&gt;&lt;br&gt;&amp;gt; [2] &lt;a href=&quot;http://www.w3.org/2003/03/glossary-project/data/glossaries/&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.w3.org/2003/03/glossary-project/data/glossaries/&lt;/a&gt;&lt;br&gt;&amp;gt; [3] &lt;a href=&quot;http://www.w3.org/QA/2003/01/Glossary&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.w3.org/QA/2003/01/Glossary&lt;/a&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Legal-Notice-in-Individual-SKOS-Glossaries-Missing-tp12030497p12034680.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-12030497</id>
	<title>Legal Notice in Individual SKOS Glossaries Missing</title>
	<published>2007-08-03T08:03:12Z</published>
	<updated>2007-08-03T08:03:12Z</updated>
	<author>
		<name>Sina K. Heshmati</name>
	</author>
	<content type="html">&lt;br&gt;ugin to support the SKOS vocabulary is being developed for Apache Forrest [1].
&lt;br&gt;A few glossaries that are made available [2] by the W3C Glossary and Dictionary Project [3] in SKOS format have been selected to serve as samples to demonstrate
&lt;br&gt;how the plugin aggregates content from external sources.
&lt;br&gt;&lt;br&gt;As a result, the content from an external source may be presented in pages with 
&lt;br&gt;Apache copyright statement. Therefore, we need to make sure that the right legal 
&lt;br&gt;notice is associated with the aggregated content. To that end, I was wondering
&lt;br&gt;if a project committer could add an explicit legal notice to SKOS glossaries [2],
&lt;br&gt;so that we'll be able to refer to those resources in our source code.
&lt;br&gt;&lt;br&gt;Sina K. Heshmati
&lt;br&gt;&lt;br&gt;[1] &lt;a href=&quot;http://forrest.apache.org/&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://forrest.apache.org/&lt;/a&gt;&lt;br&gt;[2] &lt;a href=&quot;http://www.w3.org/2003/03/glossary-project/data/glossaries/&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.w3.org/2003/03/glossary-project/data/glossaries/&lt;/a&gt;&lt;br&gt;[3] &lt;a href=&quot;http://www.w3.org/QA/2003/01/Glossary&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.w3.org/QA/2003/01/Glossary&lt;/a&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Legal-Notice-in-Individual-SKOS-Glossaries-Missing-tp12030497p12030497.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-8529320</id>
	<title>Re: New glossaries added to W3C Glossary</title>
	<published>2007-01-23T12:10:30Z</published>
	<updated>2007-01-23T12:10:30Z</updated>
	<author>
		<name>Dominique Hazael-Massieux-2</name>
	</author>
	<content type="html">&lt;br&gt;Le mardi 23 janvier 2007 à 16:54 +0000, Dan Brickley a écrit :
&lt;br&gt;&amp;gt; Can you add a (more prominent) link back to the top of the Glossary site?
&lt;br&gt;&lt;br&gt;Err... Doesn't the logo at the top of the page work? Anyway, I've added
&lt;br&gt;a link &amp;quot;W3C Glossaries&amp;quot; under the &amp;lt;h1&amp;gt; of the results pages.
&lt;br&gt;&lt;br&gt;&amp;gt; BTW is there still a SKOS version?
&lt;br&gt;&lt;br&gt;Yes; the RDF files are available at:
&lt;br&gt;&lt;a href=&quot;http://www.w3.org/2003/03/glossary-project/data/glossaries/&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.w3.org/2003/03/glossary-project/data/glossaries/&lt;/a&gt;&lt;br&gt;&lt;br&gt;&amp;gt; &amp;nbsp;How do you deal with the hypertext 
&lt;br&gt;&amp;gt; fragments?
&lt;br&gt;&lt;br&gt;Using rdf:parseType=&amp;quot;Literal&amp;quot;.
&lt;br&gt;&lt;br&gt;&amp;gt; &amp;nbsp;And did you see 
&lt;br&gt;&amp;gt; &lt;a href=&quot;http://lists.w3.org/Archives/Public/public-swd-wg/2006Dec/0036.html&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://lists.w3.org/Archives/Public/public-swd-wg/2006Dec/0036.html&lt;/a&gt;&lt;br&gt;&lt;br&gt;Nope, I hadn't; I'm not sure I'll have time to reply to that survey in
&lt;br&gt;any reasonable time, but feel free to notice the relevant persons that
&lt;br&gt;the W3C Glossary is relying on SKOS (or at least some version of it - I
&lt;br&gt;haven't followed the possible recent evolutions of the vocabulary).
&lt;br&gt;&lt;br&gt;&amp;gt; Does &lt;a href=&quot;http://www.w3.org/2003/03/glossary-project/analysis&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.w3.org/2003/03/glossary-project/analysis&lt;/a&gt;&amp;nbsp;still describe 
&lt;br&gt;&amp;gt; the workings of the system reasonably well?
&lt;br&gt;&lt;br&gt;Yes, I think it does.
&lt;br&gt;&lt;br&gt;&amp;gt; &amp;nbsp;The note in 
&lt;br&gt;&amp;gt; &lt;a href=&quot;http://www.w3.org/QA/2003/01/Glossary&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.w3.org/QA/2003/01/Glossary&lt;/a&gt;&amp;nbsp;says
&lt;br&gt;&amp;gt; &amp;quot;&amp;quot;&amp;quot;it's now using the SKOS Schema produced by the SWAD-EU activity as 
&lt;br&gt;&amp;gt; much as possible, instead of the custom schema it was using until now.&amp;quot;&amp;quot;&amp;quot;
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; Now would probably be a good time to revisit any issues with SKOS that 
&lt;br&gt;&amp;gt; you had... (apologies if I've missed a mail thread on that)
&lt;br&gt;&lt;br&gt;I don't think that beyond the hypertext fragment thingy we noticed any
&lt;br&gt;real problem with SKOS...
&lt;br&gt;&lt;br&gt;HTH,
&lt;br&gt;&lt;br&gt;Dom
&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/New-glossaries-added-to-W3C-Glossary-tp8524077p8529320.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-8525530</id>
	<title>Re: New glossaries added to W3C Glossary</title>
	<published>2007-01-23T08:54:29Z</published>
	<updated>2007-01-23T08:54:29Z</updated>
	<author>
		<name>Dan Brickley-2</name>
	</author>
	<content type="html">&lt;br&gt;Dominique Hazael-Massieux wrote:
&lt;div class='shrinkable-quote'&gt;&lt;br&gt;&amp;gt; Hi, 
&lt;br&gt;&amp;gt; 
&lt;br&gt;&amp;gt; Four new glossaries (based on the 8 new recommendations that were
&lt;br&gt;&amp;gt; published today) have been added to the W3C Glossary today:
&lt;br&gt;&amp;gt; * XQuery 1.0 and XPath 2.0 Data Model (XDM)
&lt;br&gt;&amp;gt; &amp;nbsp; &amp;nbsp;&lt;a href=&quot;http://www.w3.org/2003/glossary/subglossary/xpath-datamodel/&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.w3.org/2003/glossary/subglossary/xpath-datamodel/&lt;/a&gt;&lt;br&gt;&amp;gt; &amp;nbsp; * XQuery 1.0: An XML Query Language
&lt;br&gt;&amp;gt; &amp;nbsp; &amp;nbsp; &lt;a href=&quot;http://www.w3.org/2003/glossary/subglossary/xquery/&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.w3.org/2003/glossary/subglossary/xquery/&lt;/a&gt;&lt;br&gt;&amp;gt; &amp;nbsp; * XSL Transformations (XSLT) 2.0
&lt;br&gt;&amp;gt; &amp;nbsp; &lt;a href=&quot;http://www.w3.org/2003/glossary/subglossary/xslt20/&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.w3.org/2003/glossary/subglossary/xslt20/&lt;/a&gt;&lt;br&gt;&amp;gt; &amp;nbsp; * XML Path Language (XPath) 2.0
&lt;br&gt;&amp;gt; &amp;nbsp; &lt;a href=&quot;http://www.w3.org/2003/glossary/subglossary/xpath20/&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.w3.org/2003/glossary/subglossary/xpath20/&lt;/a&gt;&lt;/div&gt;&lt;br&gt;Nice work Dom :)
&lt;br&gt;&lt;br&gt;Can you add a (more prominent) link back to the top of the Glossary site?
&lt;br&gt;&lt;br&gt;BTW is there still a SKOS version? How do you deal with the hypertext 
&lt;br&gt;fragments? And did you see 
&lt;br&gt;&lt;a href=&quot;http://lists.w3.org/Archives/Public/public-swd-wg/2006Dec/0036.html&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://lists.w3.org/Archives/Public/public-swd-wg/2006Dec/0036.html&lt;/a&gt;&lt;br&gt;&lt;br&gt;Does &lt;a href=&quot;http://www.w3.org/2003/03/glossary-project/analysis&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.w3.org/2003/03/glossary-project/analysis&lt;/a&gt;&amp;nbsp;still describe 
&lt;br&gt;the workings of the system reasonably well? The note in 
&lt;br&gt;&lt;a href=&quot;http://www.w3.org/QA/2003/01/Glossary&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.w3.org/QA/2003/01/Glossary&lt;/a&gt;&amp;nbsp;says
&lt;br&gt;&amp;quot;&amp;quot;&amp;quot;it's now using the SKOS Schema produced by the SWAD-EU activity as 
&lt;br&gt;much as possible, instead of the custom schema it was using until now.&amp;quot;&amp;quot;&amp;quot;
&lt;br&gt;&lt;br&gt;Now would probably be a good time to revisit any issues with SKOS that 
&lt;br&gt;you had... (apologies if I've missed a mail thread on that)
&lt;br&gt;&lt;br&gt;cheers,
&lt;br&gt;&lt;br&gt;Dan
&lt;br&gt;&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/New-glossaries-added-to-W3C-Glossary-tp8524077p8525530.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-8524077</id>
	<title>New glossaries added to W3C Glossary</title>
	<published>2007-01-23T07:30:04Z</published>
	<updated>2007-01-23T07:30:04Z</updated>
	<author>
		<name>Dominique Hazael-Massieux-2</name>
	</author>
	<content type="html">&lt;br&gt;Hi, 
&lt;br&gt;&lt;br&gt;Four new glossaries (based on the 8 new recommendations that were
&lt;br&gt;published today) have been added to the W3C Glossary today:
&lt;br&gt;* XQuery 1.0 and XPath 2.0 Data Model (XDM)
&lt;br&gt;&amp;nbsp; &amp;nbsp;&lt;a href=&quot;http://www.w3.org/2003/glossary/subglossary/xpath-datamodel/&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.w3.org/2003/glossary/subglossary/xpath-datamodel/&lt;/a&gt;&lt;br&gt;&amp;nbsp; * XQuery 1.0: An XML Query Language
&lt;br&gt;&amp;nbsp; &amp;nbsp; &lt;a href=&quot;http://www.w3.org/2003/glossary/subglossary/xquery/&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.w3.org/2003/glossary/subglossary/xquery/&lt;/a&gt;&lt;br&gt;&amp;nbsp; * XSL Transformations (XSLT) 2.0
&lt;br&gt;&amp;nbsp; &lt;a href=&quot;http://www.w3.org/2003/glossary/subglossary/xslt20/&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.w3.org/2003/glossary/subglossary/xslt20/&lt;/a&gt;&lt;br&gt;&amp;nbsp; * XML Path Language (XPath) 2.0
&lt;br&gt;&amp;nbsp; &lt;a href=&quot;http://www.w3.org/2003/glossary/subglossary/xpath20/&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.w3.org/2003/glossary/subglossary/xpath20/&lt;/a&gt;&lt;br&gt;&lt;br&gt;Dom
&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/New-glossaries-added-to-W3C-Glossary-tp8524077p8524077.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-2202135</id>
	<title>W3C Glossary update</title>
	<published>2006-01-04T06:14:15Z</published>
	<updated>2006-01-04T06:14:15Z</updated>
	<author>
		<name>Dominique Hazael-Massieux-2</name>
	</author>
	<content type="html">Hi,
&lt;br&gt;&lt;br&gt;From now on, I'm going to announce update and changes to the W3C central
&lt;br&gt;Glossary [1] to this mailing list; this means very little actual
&lt;br&gt;traffic, since most glossaries are as stable as their underlying W3C
&lt;br&gt;Recommendation, and new glossaries mostly happen when new Recommendation
&lt;br&gt;that include a glossary are published.
&lt;br&gt;&lt;br&gt;To start this, here is a notice that I updated the Device Independence
&lt;br&gt;Glossary [2] to match the latest TR version [3]; also, back in August, I
&lt;br&gt;updated the glossary attached to the Specification Guidelines [4].
&lt;br&gt;&lt;br&gt;As a reminder, the data behind the glossary system are available in
&lt;br&gt;RDF/SKOS at:
&lt;br&gt;&lt;a href=&quot;http://www.w3.org/2003/03/glossary-project/data/glossaries/&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.w3.org/2003/03/glossary-project/data/glossaries/&lt;/a&gt;&lt;br&gt;&lt;br&gt;Dom
&lt;br&gt;&lt;br&gt;1. &lt;a href=&quot;http://www.w3.org/2003/glossary/&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.w3.org/2003/glossary/&lt;/a&gt;&lt;br&gt;2. &lt;a href=&quot;http://www.w3.org/2003/glossary/subglossary/di-gloss.rdf/&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.w3.org/2003/glossary/subglossary/di-gloss.rdf/&lt;/a&gt;&lt;br&gt;3. &lt;a href=&quot;http://www.w3.org/TR/2005/WD-di-gloss-20050118/&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.w3.org/TR/2005/WD-di-gloss-20050118/&lt;/a&gt;&amp;nbsp;
&lt;br&gt;4. &lt;a href=&quot;http://www.w3.org/2003/glossary/subglossary/qaframe-spec.rdf/&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.w3.org/2003/glossary/subglossary/qaframe-spec.rdf/&lt;/a&gt;&lt;br&gt;-- 
&lt;br&gt;Dominique Hazaël-Massieux - &lt;a href=&quot;http://www.w3.org/People/Dom/&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.w3.org/People/Dom/&lt;/a&gt;&lt;br&gt;W3C/ERCIM
&lt;br&gt;mailto:&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=2202135&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;dom@...&lt;/a&gt;
&lt;br&gt;&lt;br /&gt; &lt;div class=&quot;small&quot;&gt;&lt;br/&gt;&lt;img src=&quot;http://old.nabble.com/images/icon_attachment.gif&quot; &gt; &lt;strong&gt;signature.asc&lt;/strong&gt; (196 bytes) &lt;a href=&quot;http://old.nabble.com/attachment/2202135/0/signature.asc&quot; target=&quot;_top&quot;&gt;Download Attachment&lt;/a&gt;&lt;/div&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/W3C-Glossary-update-tp2202135p2202135.html" />
</entry>

<entry>
	<id>tag:old.nabble.com,2006:post-1713369</id>
	<title>Announcing SKOS Core 2nd Public Working Drafts</title>
	<published>2005-11-30T02:28:40Z</published>
	<updated>2005-11-30T02:28:40Z</updated>
	<author>
		<name>Miles, AJ (Alistair)</name>
	</author>
	<content type="html">&lt;br&gt;&amp;nbsp; W3C Semantic Web Best Practices and Deployment Working Group 
&lt;br&gt;&lt;br&gt;We are pleased to announce the publication of the following technical reports as
&lt;br&gt;second W3C Public Working Drafts:
&lt;br&gt;&lt;br&gt;&amp;nbsp; SKOS Core Guide 
&lt;br&gt;&amp;nbsp; &lt;a href=&quot;http://www.w3.org/TR/2005/WD-swbp-skos-core-guide-20051102/&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.w3.org/TR/2005/WD-swbp-skos-core-guide-20051102/&lt;/a&gt;&lt;br&gt;&lt;br&gt;&amp;nbsp; SKOS Core Vocabulary Specification
&lt;br&gt;&amp;nbsp; &lt;a href=&quot;http://www.w3.org/TR/2005/WD-swbp-skos-core-spec-20051102/&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.w3.org/TR/2005/WD-swbp-skos-core-spec-20051102/&lt;/a&gt;&lt;br&gt;&lt;br&gt;For a summary of revisions since first Working Draft publication see:
&lt;br&gt;&lt;br&gt;&lt;a href=&quot;http://www.w3.org/TR/2005/WD-swbp-skos-core-spec-20051102/#secchanges&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.w3.org/TR/2005/WD-swbp-skos-core-spec-20051102/#secchanges&lt;/a&gt;&lt;br&gt;&lt;br&gt;SKOS Core is a simple, flexible and extensible language for expressing in a
&lt;br&gt;machine-understandable form the structure and content of concept schemes such as
&lt;br&gt;thesauri, classification schemes, subject heading lists, taxonomies,
&lt;br&gt;'folksonomies', other types of controlled vocabulary, and also concept schemes
&lt;br&gt;embedded in glossaries and terminologies.
&lt;br&gt;&lt;br&gt;For links to tutorials, presentations, development information, version history,
&lt;br&gt;translations, proposals, datasets and more see the SKOS Core home page:
&lt;br&gt;&lt;br&gt;&lt;a href=&quot;http://www.w3.org/2004/02/skos/core/&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.w3.org/2004/02/skos/core/&lt;/a&gt;&lt;br&gt;&lt;br&gt;The SKOS Core Vocabulary is an application of the Resource Description Framework
&lt;br&gt;(RDF). &amp;nbsp;Using RDF allows data to be linked to and/or merged with other data. In
&lt;br&gt;practice, this means that distributed sources of data can be meaningfully
&lt;br&gt;composed and integrated.
&lt;br&gt;&lt;br&gt;For more information about RDF and related specifications, see the Semantic Web
&lt;br&gt;Activity home page:
&lt;br&gt;&lt;br&gt;&lt;a href=&quot;http://www.w3.org/2001/sw/&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;http://www.w3.org/2001/sw/&lt;/a&gt;&lt;br&gt;&lt;br&gt;The 'SKOS Core Guide' is a guide to the recommended usage of the SKOS Core
&lt;br&gt;Vocabulary, for readers who already have a basic understanding of RDF concepts.
&lt;br&gt;&lt;br&gt;The 'SKOS Core Vocabulary Specification' gives a reference-style overview of the
&lt;br&gt;SKOS Core Vocabulary, and describes policies for ownership, naming, persistence
&lt;br&gt;and change management.
&lt;br&gt;&lt;br&gt;These reports are second public Working Drafts, and are work in progress. &amp;nbsp;We
&lt;br&gt;ask at this stage for feedback from anyone with a potential interest in using
&lt;br&gt;these specifications, or with relevant expertise. &amp;nbsp;Please send comments and
&lt;br&gt;suggestions on these drafts to &lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=1713369&amp;i=0&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;public-esw-thes@...&lt;/a&gt; and begin the subject line
&lt;br&gt;of the message with 'comment:'. &amp;nbsp;If possible, please send comments before 31st
&lt;br&gt;January 2006. 
&lt;br&gt;&lt;br&gt;The Semantic Web Best Practices and Deployment Working Group is committed to a
&lt;br&gt;public, consensus-driven design environment for SKOS Core, and to this end
&lt;br&gt;conducts all SKOS-related discussion in public, in particular drawing on
&lt;br&gt;feedback from the Semantic Web Interest Group mailing list:
&lt;br&gt;&lt;br&gt;&amp;nbsp; &lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=1713369&amp;i=1&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;public-esw-thes@...&lt;/a&gt;
&lt;br&gt;&lt;br&gt;This work has benefited greatly from contributions made
&lt;br&gt;by the members of this mailing list, and their feedback, suggestions and
&lt;br&gt;encouragement are gratefully acknowledged. &amp;nbsp;The &lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=1713369&amp;i=2&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;public-esw-thes@...&lt;/a&gt; mailing
&lt;br&gt;list is open, and anyone is welcome to subscribe or to post messages. &amp;nbsp;To
&lt;br&gt;subscribe, send an email to &lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=1713369&amp;i=3&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;public-esw-thes-request@...&lt;/a&gt; with the subject line
&lt;br&gt;'subscribe', or activate the following link:
&lt;br&gt;&lt;br&gt;&amp;nbsp; mailto:&lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=1713369&amp;i=4&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;public-esw-thes-request@...&lt;/a&gt;?subject=subscribe
&lt;br&gt;&lt;br&gt;Yours on behalf of W3C Semantic Web Best Practices and Deployment Working Group,
&lt;br&gt;&lt;br&gt;Alistair Miles
&lt;br&gt;&lt;br&gt;---
&lt;br&gt;Alistair Miles
&lt;br&gt;Research Associate
&lt;br&gt;CCLRC - Rutherford Appleton Laboratory
&lt;br&gt;Building R1 Room 1.60
&lt;br&gt;Fermi Avenue
&lt;br&gt;Chilton
&lt;br&gt;Didcot
&lt;br&gt;Oxfordshire OX11 0QX
&lt;br&gt;United Kingdom
&lt;br&gt;Email: &lt;a href=&quot;http://old.nabble.com/user/SendEmail.jtp?type=post&amp;post=1713369&amp;i=5&quot; target=&quot;_top&quot; rel=&quot;nofollow&quot;&gt;a.j.miles@...&lt;/a&gt;
&lt;br&gt;Tel: +44 (0)1235 445440
&lt;br&gt;&lt;br&gt;&lt;br&gt;</content>
	<link rel="alternate" type="text/html" href="http://old.nabble.com/Announcing-SKOS-Core-2nd-Public-Working-Drafts-tp1713369p1713369.html" />
</entry>

</feed>
