<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="issues.xsl"?>
<database>
<users>
<user>
<id>1</id>
<givenname/>
<familyname>Everyone</familyname>
<username>all</username>
<aliases/>
</user>
<user>
<id>13</id>
<givenname>Abhishek</givenname>
<familyname>Rungta</familyname>
<username>arungta</username>
<aliases/>
</user>
<user>
<id>8</id>
<givenname>Alistair</givenname>
<familyname>Miles</familyname>
<username>ajm65</username>
<aliases/>
</user>
<user>
<id>17</id>
<givenname>Antoine</givenname>
<familyname>Isaac</familyname>
<username>aisaac</username>
<aliases/>
</user>
<user>
<id>6</id>
<givenname>Ben</givenname>
<familyname>Adida</familyname>
<username>adida</username>
<aliases/>
</user>
<user>
<id>4</id>
<givenname>Bernard</givenname>
<familyname>Horan</familyname>
<username>bhoran</username>
<aliases/>
</user>
<user>
<id>27</id>
<givenname>Clay</givenname>
<familyname>Redding</familyname>
<username>credding</username>
<aliases/>
</user>
<user>
<id>19</id>
<givenname>Dan</givenname>
<familyname>Brickley</familyname>
<username>dbrickle2</username>
<aliases/>
</user>
<user>
<id>33</id>
<givenname>Daniel</givenname>
<familyname>Maycock</familyname>
<username>dmaycock</username>
<aliases/>
</user>
<user>
<id>20</id>
<givenname>Daniel</givenname>
<familyname>Rubin</familyname>
<username>drubin</username>
<aliases/>
</user>
<user>
<id>31</id>
<givenname>David</givenname>
<familyname>Peterson</familyname>
<username>dpeterso</username>
<aliases/>
</user>
<user>
<id>15</id>
<givenname>Diego</givenname>
<familyname>Berrueta</familyname>
<username>dberruet</username>
<aliases/>
</user>
<user>
<id>26</id>
<givenname>Ed</givenname>
<familyname>Summers</familyname>
<username>esummers</username>
<aliases/>
</user>
<user>
<id>11</id>
<givenname>Elisa</givenname>
<familyname>Kendall</familyname>
<username>ekendall</username>
<aliases/>
</user>
<user>
<id>7</id>
<givenname>Fabien</givenname>
<familyname>Gandon</familyname>
<username>fgandon</username>
<aliases/>
</user>
<user>
<id>3</id>
<givenname>Francesco</givenname>
<familyname>de Leo</familyname>
<username>fdeleo</username>
<aliases/>
</user>
<user>
<id>5</id>
<givenname>Guus</givenname>
<familyname>Schreiber</familyname>
<username>gschreib</username>
<aliases/>
</user>
<user>
<id>22</id>
<givenname>Jan</givenname>
<familyname>Henke</familyname>
<username>jhenke</username>
<aliases/>
</user>
<user>
<id>18</id>
<givenname>Jon</givenname>
<familyname>Phipps</familyname>
<username>jphipps</username>
<aliases/>
</user>
<user>
<id>28</id>
<givenname>Justin</givenname>
<familyname>Thorp</familyname>
<username>jthorp2</username>
<aliases/>
</user>
<user>
<id>29</id>
<givenname>Justin</givenname>
<familyname>Thorp</familyname>
<username>jthorp</username>
<aliases/>
</user>
<user>
<id>30</id>
<givenname>Manu</givenname>
<familyname>Sporny</familyname>
<username>msporny</username>
<aliases/>
</user>
<user>
<id>32</id>
<givenname>Margherita</givenname>
<familyname>Sini</familyname>
<username>msini</username>
<aliases/>
</user>
<user>
<id>14</id>
<givenname>Michael</givenname>
<familyname>Hausenblas</familyname>
<username>mhausenb</username>
<aliases/>
</user>
<user>
<id>10</id>
<givenname>Mirghani</givenname>
<familyname>Mohamed</familyname>
<username>mmohamed2</username>
<aliases/>
</user>
<user>
<id>25</id>
<givenname>Quentin</givenname>
<familyname>Reul</familyname>
<username>qreul</username>
<aliases/>
</user>
<user>
<id>12</id>
<givenname>Rachel</givenname>
<familyname>Yager</familyname>
<username>ryager</username>
<aliases/>
</user>
<user>
<id>2</id>
<givenname>Ralph</givenname>
<familyname>Swick</familyname>
<username>rswick</username>
<aliases/>
</user>
<user>
<id>16</id>
<givenname>Sean</givenname>
<familyname>Bechhofer</familyname>
<username>sbechhof2</username>
<aliases/>
</user>
<user>
<id>24</id>
<givenname>Siegfried</givenname>
<familyname>Handschuh</familyname>
<username>shandsch</username>
<aliases/>
</user>
<user>
<id>21</id>
<givenname>Simone</givenname>
<familyname>Onofri</familyname>
<username>sonofri</username>
<aliases/>
</user>
<user>
<id>9</id>
<givenname>Thomas</givenname>
<familyname>Baker</familyname>
<username>tbaker3</username>
<aliases/>
</user>
<user>
<id>23</id>
<givenname>Vit</givenname>
<familyname>Novacek</familyname>
<username>vnovacek</username>
<aliases/>
</user>
</users>
<products>
<product>
<id>1</id>
<name>All</name>
</product>
<product>
<id>2</id>
<name>RDFa</name>
</product>
<product>
<id>3</id>
<name>SKOS</name>
</product>
<product>
<id>4</id>
<name>VM</name>
</product>
<product>
<id>5</id>
<name>Recipes</name>
</product>
</products>
<issues>
<issue>
<id>1</id>
<title>Reification</title>
<product>2</product>
<raisedby>6</raisedby>
<created>2007-01-24</created>
<description>The concept of reification has been confusing and awkward to use (in RDF/XML at 
least). 

Proposal: 
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2006Apr/0007.html</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/5.1.0.14.2.20070621133748.0357f868@127.0.0.1</uri>
<subject>meeting record: 2007-06-21 RDFa Telecon</subject>
<sender>swick@w3.org</sender>
<date>2007-06-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/4681CE58.6020009@adida.net</uri>
<subject>[RDFa] ISSUE-1: reification</subject>
<sender>ben@adida.net</sender>
<date>2007-06-26</date>
</email>
<email>
<uri>http://www.w3.org/mid/768DACDC356ED04EA1F1130F97D29852011C57B9@RZJC2EX.jr1.local</uri>
<subject>RE: [RDFa] ISSUE-1: reification</subject>
<sender>michael.hausenblas@joanneum.at</sender>
<date>2007-06-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/52bd7c3d0706270709p36d5bf0bnae14c32ee2640f6f@mail.gmail.com</uri>
<subject>Re: [RDFa] ISSUE-1: reification</subject>
<sender>simone.onofri@gmail.com</sender>
<date>2007-06-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/640dd5060706270744g621e3085x14322b811e7bedce@mail.gmail.com</uri>
<subject>Re: [RDFa] ISSUE-1: reification</subject>
<sender>mark.birbeck@x-port.net</sender>
<date>2007-06-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/cf8107640706271523t7d62dca9k96cd26dee75f1e2@mail.gmail.com</uri>
<subject>Re: [RDFa] ISSUE-1: reification</subject>
<sender>lindstream@gmail.com</sender>
<date>2007-06-28</date>
</email>
<email>
<uri>http://www.w3.org/mid/46836CF8.2030705@w3.org</uri>
<subject>Re: [RDFa] ISSUE-1: reification</subject>
<sender>ivan@w3.org</sender>
<date>2007-06-28</date>
</email>
<email>
<uri>http://www.w3.org/mid/468915BC.4000300@cs.vu.nl</uri>
<subject>[ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-07-02</date>
</email>
<email>
<uri>http://www.w3.org/mid/46891656.1040500@sun.com</uri>
<subject>Re: [ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>Bernard.Horan@sun.com</sender>
<date>2007-07-02</date>
</email>
<email>
<uri>http://www.w3.org/mid/468938E7.3070002@cs.vu.nl</uri>
<subject>Re: [ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-07-02</date>
</email>
<email>
<uri>http://www.w3.org/mid/468A5D1A.2000005@sandsoft.com</uri>
<subject>Re: [ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2007-07-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/52bd7c3d0707030743j62fc4bd7h96f373f578043100@mail.gmail.com</uri>
<subject>Re: [ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>simone.onofri@gmail.com</sender>
<date>2007-07-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/468A2950020000D8000156B0@ntgwgate.loc.gov</uri>
<subject>Re: [ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>juth@loc.gov</sender>
<date>2007-07-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D030E3E5D@exchange11.fed.cclrc.ac.uk</uri>
<subject>belated regrets (was RE: [ALL] agenda July 3 telecon 1500 UTC)</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-07-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/468BD635.3010401@adida.net</uri>
<subject>Re: [RDFa] ISSUE-1: reification</subject>
<sender>ben@adida.net</sender>
<date>2007-07-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/468BDA30.6050904@adida.net</uri>
<subject>[RDFa] ISSUE-1: PROPOSE to RESOLVE</subject>
<sender>ben@adida.net</sender>
<date>2007-07-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/6.2.5.6.2.20070705110516.047e10c8@med.stanford.edu</uri>
<subject>Minutes from July 3 tcon</subject>
<sender>rubin@med.stanford.edu</sender>
<date>2007-07-05</date>
</email>
<email>
<uri>http://www.w3.org/mid/4693B82E.4080801@adida.net</uri>
<subject>Re: [RDFa] ISSUE-1: PROPOSE to RESOLVE</subject>
<sender>ben@adida.net</sender>
<date>2007-07-10</date>
</email>
</emails>
<notes>
<note>
<date>2007-07-10</date>
<text>closed with the following resolution:

"XHTML1.1+RDFa does not provide any compact syntax to enable
reification. If some RDF-based notation exists for reification, there
may be a way to express such graphs in XHTML1.1+RDFa, but the spec will
not make any effort to simplify it or provide syntactic sugar."
</text>
</note>
</notes>
</issue>
<issue>
<id>2</id>
<title>Custom Attributes for RDF shorthand</title>
<product>2</product>
<raisedby>6</raisedby>
<created>2007-01-30</created>
<description/>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/46771559.5050704@adida.net</uri>
<subject>[RDFa] ISSUE-2: custom attributes for RDF shorthand</subject>
<sender>ben@adida.net</sender>
<date>2007-06-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/cf8107640706181727t8885ff6y7f4f9149e36968de@mail.gmail.com</uri>
<subject>Re: [RDFa] ISSUE-2: custom attributes for RDF shorthand</subject>
<sender>lindstream@gmail.com</sender>
<date>2007-06-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/467795BD.5030502@w3.org</uri>
<subject>Re: [RDFa] ISSUE-2: custom attributes for RDF shorthand</subject>
<sender>ivan@w3.org</sender>
<date>2007-06-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/640dd5060706190809v287a825ekaf301043db3603a9@mail.gmail.com</uri>
<subject>Re: [RDFa] ISSUE-2: custom attributes for RDF shorthand</subject>
<sender>mark.birbeck@x-port.net</sender>
<date>2007-06-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/46780CF1.8050004@adida.net</uri>
<subject>Re: [RDFa] ISSUE-2: custom attributes for RDF shorthand</subject>
<sender>ben@adida.net</sender>
<date>2007-06-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/4681CDC7.3060105@adida.net</uri>
<subject>[RDFa] Proposed resolutions to ISSUE-2, ISSUE-5, ISSUE-25, ISSUE-29,  ISSUE-4</subject>
<sender>ben@adida.net</sender>
<date>2007-06-26</date>
</email>
<email>
<uri>http://www.w3.org/mid/468915BC.4000300@cs.vu.nl</uri>
<subject>[ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-07-02</date>
</email>
<email>
<uri>http://www.w3.org/mid/46891656.1040500@sun.com</uri>
<subject>Re: [ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>Bernard.Horan@sun.com</sender>
<date>2007-07-02</date>
</email>
<email>
<uri>http://www.w3.org/mid/468938E7.3070002@cs.vu.nl</uri>
<subject>Re: [ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-07-02</date>
</email>
<email>
<uri>http://www.w3.org/mid/468A5D1A.2000005@sandsoft.com</uri>
<subject>Re: [ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2007-07-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/52bd7c3d0707030743j62fc4bd7h96f373f578043100@mail.gmail.com</uri>
<subject>Re: [ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>simone.onofri@gmail.com</sender>
<date>2007-07-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/468A2950020000D8000156B0@ntgwgate.loc.gov</uri>
<subject>Re: [ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>juth@loc.gov</sender>
<date>2007-07-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/468AF585.2010400@adida.net</uri>
<subject>[RDFa] RESOLUTIONS to ISSUE-2, ISSUE-5, ISSUE-25, ISSUE-29,  ISSUE-4</subject>
<sender>ben@adida.net</sender>
<date>2007-07-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D030E3E5D@exchange11.fed.cclrc.ac.uk</uri>
<subject>belated regrets (was RE: [ALL] agenda July 3 telecon 1500 UTC)</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-07-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/6.2.5.6.2.20070705110516.047e10c8@med.stanford.edu</uri>
<subject>Minutes from July 3 tcon</subject>
<sender>rubin@med.stanford.edu</sender>
<date>2007-07-05</date>
</email>
</emails>
<notes>
<note>
<date>2007-07-04</date>
<text>RESOLVED as:

"XHTML1.1+RDFa does not support custom attributes for RDF shorthand.
Future versions of RDFa in other host languages may support additional
ways of expressing semantics."
</text>
</note>
</notes>
</issue>
<issue>
<id>3</id>
<title>Role Attribute for RDF type declarations</title>
<product>2</product>
<raisedby>6</raisedby>
<created>2007-01-30</created>
<description>Tentative Resolution: class is rdf:type, while role is xhtml2:role.
Related: Syntactic Sugar for class attribute 

Initial Motivation was to reduce the use of rdf:type in some examples. 

Discussions: 

July 2006:
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2006Jun/0009 

August 2005:
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2005Aug/0003 

July 2005:
http://www.w3.org/2005/07/26-swbp-minutes.html#item02 

Points of Debate about role: 
 + should we use role in some RDF way that is equivalent to rdf:type at all? 
 + if we do, does that mean role is equivalent to rdf:type, or is a subproperty 
of rdf:type? 
 + is role more of a declaration of "plays the role of" for purposes of client 
user interface? 
 + maybe we need a new syntactic sugar for rdf:type? But that's possibly a 
slippery slope. 

Points of Debate about class: 
 + should class be rdf:type? Another predicate? 
 + Mark's post: 
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2006Jun/0009
 + only for scoped classes-discussion:
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2007Feb/0063.html</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/5.1.0.14.2.20070621133748.0357f868@127.0.0.1</uri>
<subject>meeting record: 2007-06-21 RDFa Telecon</subject>
<sender>swick@w3.org</sender>
<date>2007-06-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/4681CF16.5090702@adida.net</uri>
<subject>[RDFa] ISSUE-3 @class and @role for rdf:type</subject>
<sender>ben@adida.net</sender>
<date>2007-06-26</date>
</email>
<email>
<uri>http://www.w3.org/mid/4681E894.2060106@aptest.com</uri>
<subject>Re: [RDFa] ISSUE-3 @class and @role for rdf:type</subject>
<sender>shane@aptest.com</sender>
<date>2007-06-26</date>
</email>
<email>
<uri>http://www.w3.org/mid/768DACDC356ED04EA1F1130F97D29852011C57BA@RZJC2EX.jr1.local</uri>
<subject>RE: [RDFa] ISSUE-3 @class and @role for rdf:type</subject>
<sender>michael.hausenblas@joanneum.at</sender>
<date>2007-06-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/46836F5A.5090705@w3.org</uri>
<subject>Re: [RDFa] ISSUE-3 @class and @role for rdf:type</subject>
<sender>ivan@w3.org</sender>
<date>2007-06-28</date>
</email>
<email>
<uri>http://www.w3.org/mid/640dd5060706280302h51e52496y876f94fe77e1a2e0@mail.gmail.com</uri>
<subject>Re: [RDFa] ISSUE-3 @class and @role for rdf:type</subject>
<sender>mark.birbeck@x-port.net</sender>
<date>2007-06-28</date>
</email>
<email>
<uri>http://www.w3.org/mid/46838812.6060304@w3.org</uri>
<subject>Re: [RDFa] ISSUE-3 @class and @role for rdf:type</subject>
<sender>ivan@w3.org</sender>
<date>2007-06-28</date>
</email>
<email>
<uri>http://www.w3.org/mid/4683C263.8000204@adida.net</uri>
<subject>Re: [RDFa] ISSUE-3 @class and @role for rdf:type</subject>
<sender>ben@adida.net</sender>
<date>2007-06-28</date>
</email>
<email>
<uri>http://www.w3.org/mid/4683C2F3.6030900@w3.org</uri>
<subject>Re: [RDFa] ISSUE-3 @class and @role for rdf:type</subject>
<sender>ivan@w3.org</sender>
<date>2007-06-28</date>
</email>
<email>
<uri>http://www.w3.org/mid/640dd5060706280729y78b9b170pdbf7f9d7a952462a@mail.gmail.com</uri>
<subject>Re: [RDFa] ISSUE-3 @class and @role for rdf:type</subject>
<sender>mark.birbeck@x-port.net</sender>
<date>2007-06-28</date>
</email>
<email>
<uri>http://www.w3.org/mid/4683CFE5.5090003@adida.net</uri>
<subject>Re: [RDFa] ISSUE-3 @class and @role for rdf:type</subject>
<sender>ben@adida.net</sender>
<date>2007-06-28</date>
</email>
<email>
<uri>http://www.w3.org/mid/640dd5060706280909i6849b24ama52d751b113c1eb1@mail.gmail.com</uri>
<subject>Re: [RDFa] ISSUE-3 @class and @role for rdf:type</subject>
<sender>mark.birbeck@x-port.net</sender>
<date>2007-06-28</date>
</email>
<email>
<uri>http://www.w3.org/mid/4683E05E.7020607@w3.org</uri>
<subject>Re: [RDFa] ISSUE-3 @class and @role for rdf:type</subject>
<sender>ivan@w3.org</sender>
<date>2007-06-28</date>
</email>
<email>
<uri>http://www.w3.org/mid/640dd5060706280929p1fbbb4dai8889e6250957a5eb@mail.gmail.com</uri>
<subject>Re: [RDFa] ISSUE-3 @class and @role for rdf:type</subject>
<sender>mark.birbeck@x-port.net</sender>
<date>2007-06-28</date>
</email>
<email>
<uri>http://www.w3.org/mid/4683EC75.6060402@adida.net</uri>
<subject>Re: [RDFa] ISSUE-3 @class and @role for rdf:type</subject>
<sender>ben@adida.net</sender>
<date>2007-06-28</date>
</email>
<email>
<uri>http://www.w3.org/mid/640dd5060706281035u5716762eqa037503a27d2510@mail.gmail.com</uri>
<subject>Re: [RDFa] ISSUE-3 @class and @role for rdf:type</subject>
<sender>mark.birbeck@x-port.net</sender>
<date>2007-06-28</date>
</email>
<email>
<uri>http://www.w3.org/mid/640dd5060706281037x15a1cb09o26e66acd8e8ca1f2@mail.gmail.com</uri>
<subject>Re: [RDFa] ISSUE-3 @class and @role for rdf:type</subject>
<sender>mark.birbeck@x-port.net</sender>
<date>2007-06-28</date>
</email>
<email>
<uri>http://www.w3.org/mid/468915BC.4000300@cs.vu.nl</uri>
<subject>[ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-07-02</date>
</email>
<email>
<uri>http://www.w3.org/mid/46891656.1040500@sun.com</uri>
<subject>Re: [ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>Bernard.Horan@sun.com</sender>
<date>2007-07-02</date>
</email>
<email>
<uri>http://www.w3.org/mid/468938E7.3070002@cs.vu.nl</uri>
<subject>Re: [ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-07-02</date>
</email>
<email>
<uri>http://www.w3.org/mid/468A5D1A.2000005@sandsoft.com</uri>
<subject>Re: [ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2007-07-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/52bd7c3d0707030743j62fc4bd7h96f373f578043100@mail.gmail.com</uri>
<subject>Re: [ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>simone.onofri@gmail.com</sender>
<date>2007-07-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/468A2950020000D8000156B0@ntgwgate.loc.gov</uri>
<subject>Re: [ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>juth@loc.gov</sender>
<date>2007-07-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D030E3E5D@exchange11.fed.cclrc.ac.uk</uri>
<subject>belated regrets (was RE: [ALL] agenda July 3 telecon 1500 UTC)</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-07-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/6.2.5.6.2.20070705110516.047e10c8@med.stanford.edu</uri>
<subject>Minutes from July 3 tcon</subject>
<sender>rubin@med.stanford.edu</sender>
<date>2007-07-05</date>
</email>
<email>
<uri>http://www.w3.org/mid/4696722C.9060409@adida.net</uri>
<subject>[RDFa] ISSUE-3: syntactic sugar for rdf:type</subject>
<sender>ben@adida.net</sender>
<date>2007-07-12</date>
</email>
<email>
<uri>http://www.w3.org/mid/46973D5E.1030101@w3.org</uri>
<subject>Re: [RDFa] ISSUE-3: syntactic sugar for rdf:type</subject>
<sender>ivan@w3.org</sender>
<date>2007-07-13</date>
</email>
<email>
<uri>http://www.w3.org/mid/469C079F.8090201@adida.net</uri>
<subject>Re: [RDFa] ISSUE-3: syntactic sugar for rdf:type</subject>
<sender>ben@adida.net</sender>
<date>2007-07-16</date>
</email>
<email>
<uri>http://www.w3.org/mid/768DACDC356ED04EA1F1130F97D2985201211DCD@RZJC2EX.jr1.local</uri>
<subject>RE: [RDFa] ISSUE-3: syntactic sugar for rdf:type</subject>
<sender>michael.hausenblas@joanneum.at</sender>
<date>2007-07-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/640dd5060707162350v462bca15vddd1b5c8df1de276@mail.gmail.com</uri>
<subject>Re: [RDFa] ISSUE-3: syntactic sugar for rdf:type</subject>
<sender>mark.birbeck@x-port.net</sender>
<date>2007-07-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070717070604.GA1628@Octavius</uri>
<subject>Re: [RDFa] ISSUE-3: syntactic sugar for rdf:type</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-07-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/469C6E51.7060305@w3.org</uri>
<subject>Re: [RDFa] ISSUE-3: syntactic sugar for rdf:type</subject>
<sender>ivan@w3.org</sender>
<date>2007-07-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/469C7A7E.5080302@w3.org</uri>
<subject>Re: [RDFa] ISSUE-3: syntactic sugar for rdf:type</subject>
<sender>ivan@w3.org</sender>
<date>2007-07-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/1184663024.4766.10.camel@duncan.fundacionctic.org</uri>
<subject>Re: [RDFa] ISSUE-3: syntactic sugar for rdf:type</subject>
<sender>diego.berrueta@fundacionctic.org</sender>
<date>2007-07-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/469C9FF9.5000509@w3.org</uri>
<subject>Re: [RDFa] ISSUE-3: syntactic sugar for rdf:type</subject>
<sender>ivan@w3.org</sender>
<date>2007-07-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/cf8107640707170447u3bc8e15xdd8ee6345b5080e7@mail.gmail.com</uri>
<subject>Re: [RDFa] ISSUE-3: syntactic sugar for rdf:type</subject>
<sender>lindstream@gmail.com</sender>
<date>2007-07-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/640dd5060707170615t1a1863edqa1e7bdae08f9424d@mail.gmail.com</uri>
<subject>Re: [RDFa] ISSUE-3: syntactic sugar for rdf:type</subject>
<sender>mark.birbeck@x-port.net</sender>
<date>2007-07-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/op.tvpviymnsmjzpq@acer3010.lan</uri>
<subject>Why I don't like 'instanceof' (was Re: [RDFa] ISSUE-3: syntactic sugar for rdf:type)</subject>
<sender>steven.pemberton@cwi.nl</sender>
<date>2007-07-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/469F7C53.6010305@adida.net</uri>
<subject>Re: Why I don't like 'instanceof' (was Re: [RDFa] ISSUE-3: syntactic  sugar for rdf:type)</subject>
<sender>ben@adida.net</sender>
<date>2007-07-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/46A078C2.8050706@w3.org</uri>
<subject>Re: Why I don't like 'instanceof' (was Re: [RDFa] ISSUE-3: syntactic  sugar for rdf:type)</subject>
<sender>ivan@w3.org</sender>
<date>2007-07-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/768DACDC356ED04EA1F1130F97D29852012121C3@RZJC2EX.jr1.local</uri>
<subject>RE: Why I don't like 'instanceof' (was Re: [RDFa] ISSUE-3: syntactic  sugar for rdf:type)</subject>
<sender>michael.hausenblas@joanneum.at</sender>
<date>2007-07-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/46A07DA3.4050802@w3.org</uri>
<subject>Re: Why I don't like 'instanceof' (was Re: [RDFa] ISSUE-3: syntactic   sugar for rdf:type)</subject>
<sender>ivan@w3.org</sender>
<date>2007-07-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/768DACDC356ED04EA1F1130F97D29852012121D1@RZJC2EX.jr1.local</uri>
<subject>RE: Why I don't like 'instanceof' (was Re: [RDFa] ISSUE-3: syntactic  sugar for rdf:type)</subject>
<sender>michael.hausenblas@joanneum.at</sender>
<date>2007-07-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/46A084D4.70100@w3.org</uri>
<subject>Re: Why I don't like 'instanceof' (was Re: [RDFa] ISSUE-3: syntactic   sugar for rdf:type)</subject>
<sender>ivan@w3.org</sender>
<date>2007-07-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/640dd5060707200324l5ce07524mb8f933ebee8547de@mail.gmail.com</uri>
<subject>Re: Why I don't like 'instanceof' (was Re: [RDFa] ISSUE-3: syntactic sugar for rdf:type)</subject>
<sender>mark.birbeck@x-port.net</sender>
<date>2007-07-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/op.tvrd9ygn63ayaz@keith-alexanders-computer.local</uri>
<subject>Re: Why I don't like 'instanceof' (was Re: [RDFa] ISSUE-3: syntactic   sugar for rdf:type)</subject>
<sender>k.j.w.alexander@gmail.com</sender>
<date>2007-07-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/cf8107640707200437j695df2e2lf0d953314b00a59@mail.gmail.com</uri>
<subject>Re: Why I don't like 'instanceof' (was Re: [RDFa] ISSUE-3: syntactic sugar for rdf:type)</subject>
<sender>lindstream@gmail.com</sender>
<date>2007-07-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/46A0C67E.3090807@adida.net</uri>
<subject>Re: Why I don't like 'instanceof' (was Re: [RDFa] ISSUE-3: syntactic    sugar for rdf:type)</subject>
<sender>ben@adida.net</sender>
<date>2007-07-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/337D3644-5467-4194-AD00-E80F7A438E9C@w3.org</uri>
<subject>Re: Why I don't like 'instanceof' (was Re: [RDFa] ISSUE-3: syntactic   sugar for rdf:type)</subject>
<sender>karl@w3.org</sender>
<date>2007-07-26</date>
</email>
<email>
<uri>http://www.w3.org/mid/52bd7c3d0708012327k1859a224pea7a17d71a283f09@mail.gmail.com</uri>
<subject>Re: [RDFa] ISSUE-3: syntactic sugar for rdf:type</subject>
<sender>simone.onofri@gmail.com</sender>
<date>2007-08-02</date>
</email>
<email>
<uri>http://www.w3.org/mid/op.tx6jpc18smjzpq@acer3010.lan</uri>
<subject>Re: Why I don't like 'instanceof' (was Re: [RDFa] ISSUE-3: syntactic sugar for rdf:type)</subject>
<sender>steven.pemberton@cwi.nl</sender>
<date>2007-09-05</date>
</email>
<email>
<uri>http://www.w3.org/mid/47044766.6040908@adida.net</uri>
<subject>ISSUE-3: Attribute for RDF type declarations</subject>
<sender>ben@adida.net</sender>
<date>2007-10-03</date>
</email>
</emails>
<notes>
<note>
<date>2007-02-05</date>
<text>- on 2007-01-29, we discussed feedback from the WG and TimBL regarding the
overloading of CLASS being too confusing for existing uses of CLASS. Considering
applying this only to scoped CLASSes.</text>
</note>
<note>
<date>2007-10-18</date>
<text>Noting Steven's dissent, this is resolved: "@role and @class are thus ignored by the core RDFa 
specification, while @instanceof is syntactic sugar for rdf:type, and takes a CURIE as value."

http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2007Oct/0020.html
</text>
</note>
</notes>
</issue>
<issue>
<id>4</id>
<title>(Local) blank node identifiers</title>
<product>2</product>
<raisedby>6</raisedby>
<created>2007-01-30</created>
<description>Tentative resolution: to use the REL attribute on other elements to allow 
striping and thus bnode creation without explicit names (cf. 
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2006Oct/0000)

How to refer to blank nodes, viz. nodes that do not have an externally 
referencable identifer (http://www.w3.org/TR/rdf-concepts/#section-URI-
Vocabulary) from within an XHTML document. How do we get anonymous nodes 
(http://www.xforms-
wiki.com/bin/view/Main/LanguageRdfA#How_do_we_get_anonymous_nodes)? 


</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/4677230E.3040606@adida.net</uri>
<subject>[RDFa] ISSUE-4: (local) bnode identifiers</subject>
<sender>ben@adida.net</sender>
<date>2007-06-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/4677970C.7080108@w3.org</uri>
<subject>Re: [RDFa] ISSUE-4: (local) bnode identifiers</subject>
<sender>ivan@w3.org</sender>
<date>2007-06-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/640dd5060706190540x284ca89bkc1a0de4f2d3339fe@mail.gmail.com</uri>
<subject>Re: [RDFa] ISSUE-4: (local) bnode identifiers</subject>
<sender>mark.birbeck@x-port.net</sender>
<date>2007-06-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/4681CDC7.3060105@adida.net</uri>
<subject>[RDFa] Proposed resolutions to ISSUE-2, ISSUE-5, ISSUE-25, ISSUE-29,  ISSUE-4</subject>
<sender>ben@adida.net</sender>
<date>2007-06-26</date>
</email>
<email>
<uri>http://www.w3.org/mid/52bd7c3d0706270721l2843ca8cv8a6ee6645362d179@mail.gmail.com</uri>
<subject>Re: [RDFa] ISSUE-4: (local) bnode identifiers</subject>
<sender>simone.onofri@gmail.com</sender>
<date>2007-06-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/468915BC.4000300@cs.vu.nl</uri>
<subject>[ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-07-02</date>
</email>
<email>
<uri>http://www.w3.org/mid/46891656.1040500@sun.com</uri>
<subject>Re: [ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>Bernard.Horan@sun.com</sender>
<date>2007-07-02</date>
</email>
<email>
<uri>http://www.w3.org/mid/468938E7.3070002@cs.vu.nl</uri>
<subject>Re: [ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-07-02</date>
</email>
<email>
<uri>http://www.w3.org/mid/468A5D1A.2000005@sandsoft.com</uri>
<subject>Re: [ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2007-07-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/52bd7c3d0707030743j62fc4bd7h96f373f578043100@mail.gmail.com</uri>
<subject>Re: [ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>simone.onofri@gmail.com</sender>
<date>2007-07-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/468A2950020000D8000156B0@ntgwgate.loc.gov</uri>
<subject>Re: [ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>juth@loc.gov</sender>
<date>2007-07-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/468AF585.2010400@adida.net</uri>
<subject>[RDFa] RESOLUTIONS to ISSUE-2, ISSUE-5, ISSUE-25, ISSUE-29,  ISSUE-4</subject>
<sender>ben@adida.net</sender>
<date>2007-07-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D030E3E5D@exchange11.fed.cclrc.ac.uk</uri>
<subject>belated regrets (was RE: [ALL] agenda July 3 telecon 1500 UTC)</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-07-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/6.2.5.6.2.20070705110516.047e10c8@med.stanford.edu</uri>
<subject>Minutes from July 3 tcon</subject>
<sender>rubin@med.stanford.edu</sender>
<date>2007-07-05</date>
</email>
</emails>
<notes>
<note>
<date>2007-07-04</date>
<text>RESOLVED as:

http://www.w3.org/TR/xhtml-rdfa-primer/#id2266829
</text>
</note>
</notes>
</issue>
<issue>
<id>5</id>
<title>CURIEs in Predicate Attributes</title>
<product>2</product>
<raisedby>6</raisedby>
<created>2007-01-30</created>
<description>Details discussed during telecon (http://lists.w3.org/Archives/Public/public-
rdf-in-xhtml-tf/2005Oct/0052.html). Debate continuing on the mailing list 
(http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2006Feb/0027.html).
 
Currently, about and href attributes are of type CURIE/URI, which means that 
the value of the attribute can be either a CURIE or a URI. When it is a CURIE, 
it needs to be wrapped in square brackets as follows: [cc:license], in order to 
differentiate CURIEs from URIs. 

Should rel, rev, property have the same CURIE/URI type? Or should they be CURIE 
only, since there is no precedent for them being URIs? 

The advantage of CURIE only is that we get automatic backwards compatibility 
for things like rel="next", which would be interpreted as CURIE in the default 
XML namespace of xhtml2. 

If we go with CURIE/URI, then we can always declare parser-level legacy 
conditions for things like rel="next", which would immediately be transformed 
into rel="[next]" or maybe even more directly to rel="[xhtml2:next]".</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/46771636.408@adida.net</uri>
<subject>[RDFa] ISSUE-5</subject>
<sender>ben@adida.net</sender>
<date>2007-06-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/cf8107640706181730q39b07575ld557eb7620d10926@mail.gmail.com</uri>
<subject>Re: [RDFa] ISSUE-5</subject>
<sender>lindstream@gmail.com</sender>
<date>2007-06-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/467799B2.8040709@w3.org</uri>
<subject>Re: [RDFa] ISSUE-5</subject>
<sender>ivan@w3.org</sender>
<date>2007-06-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/4677E4C1.70906@aptest.com</uri>
<subject>Re: [RDFa] ISSUE-5</subject>
<sender>shane@aptest.com</sender>
<date>2007-06-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/768DACDC356ED04EA1F1130F97D29852011C5121@RZJC2EX.jr1.local</uri>
<subject>RE: [RDFa] ISSUE-5</subject>
<sender>michael.hausenblas@joanneum.at</sender>
<date>2007-06-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/46780DD2.30304@adida.net</uri>
<subject>Re: [RDFa] ISSUE-5</subject>
<sender>ben@adida.net</sender>
<date>2007-06-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/4678DABC.7030101@w3.org</uri>
<subject>Re: [RDFa] ISSUE-5</subject>
<sender>ivan@w3.org</sender>
<date>2007-06-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/46794F9C.3040304@adida.net</uri>
<subject>Re: [RDFa] ISSUE-5</subject>
<sender>ben@adida.net</sender>
<date>2007-06-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/640dd5060706210229t4fe206b6q314e174f915dbbdd@mail.gmail.com</uri>
<subject>Re: [RDFa] ISSUE-5</subject>
<sender>mark.birbeck@x-port.net</sender>
<date>2007-06-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/4681CDC7.3060105@adida.net</uri>
<subject>[RDFa] Proposed resolutions to ISSUE-2, ISSUE-5, ISSUE-25, ISSUE-29,  ISSUE-4</subject>
<sender>ben@adida.net</sender>
<date>2007-06-26</date>
</email>
<email>
<uri>http://www.w3.org/mid/468915BC.4000300@cs.vu.nl</uri>
<subject>[ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-07-02</date>
</email>
<email>
<uri>http://www.w3.org/mid/46891656.1040500@sun.com</uri>
<subject>Re: [ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>Bernard.Horan@sun.com</sender>
<date>2007-07-02</date>
</email>
<email>
<uri>http://www.w3.org/mid/468938E7.3070002@cs.vu.nl</uri>
<subject>Re: [ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-07-02</date>
</email>
<email>
<uri>http://www.w3.org/mid/468A5D1A.2000005@sandsoft.com</uri>
<subject>Re: [ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2007-07-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/52bd7c3d0707030743j62fc4bd7h96f373f578043100@mail.gmail.com</uri>
<subject>Re: [ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>simone.onofri@gmail.com</sender>
<date>2007-07-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/468A2950020000D8000156B0@ntgwgate.loc.gov</uri>
<subject>Re: [ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>juth@loc.gov</sender>
<date>2007-07-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/468AF585.2010400@adida.net</uri>
<subject>[RDFa] RESOLUTIONS to ISSUE-2, ISSUE-5, ISSUE-25, ISSUE-29,  ISSUE-4</subject>
<sender>ben@adida.net</sender>
<date>2007-07-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D030E3E5D@exchange11.fed.cclrc.ac.uk</uri>
<subject>belated regrets (was RE: [ALL] agenda July 3 telecon 1500 UTC)</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-07-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/6.2.5.6.2.20070705110516.047e10c8@med.stanford.edu</uri>
<subject>Minutes from July 3 tcon</subject>
<sender>rubin@med.stanford.edu</sender>
<date>2007-07-05</date>
</email>
</emails>
<notes>
<note>
<date>2007-07-04</date>
<text>RESOLVED as:

"@rel/@rev/@property does *not* accept URI values, only CURIEs."

Note ISSUE-55 which may downgrade CURIEs to QNames.</text>
</note>
</notes>
</issue>
<issue>
<id>6</id>
<title>xml:lang</title>
<product>2</product>
<raisedby>6</raisedby>
<created>2007-01-30</created>
<description>In the RDFa Syntax document (cf. http://www.w3.org/2006/07/SWD/RDFa/syntax/), 
xml:lang is discarded for XML literals. While this may have been okay for 
RDF/XML, it's much worse for XHTML, which should be treated with "more 
respect." The fix for this may involve adding an extra SPAN or DIV as 
appropriate to XML literals. 

Likely dependent on ISSUE-97:
http://www.w3.org/2006/07/SWD/track/issues/97</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/5.1.0.14.2.20070621133748.0357f868@127.0.0.1</uri>
<subject>meeting record: 2007-06-21 RDFa Telecon</subject>
<sender>swick@w3.org</sender>
<date>2007-06-21</date>
</email>
</emails>
<notes>
<note>
<date>2008-02-19</date>
<text>The 2007-08-23 telecon resolved
[[
RESOLUTION: @lang is not part of XHTML1.1, @xml:lang is, so we resolve that
XHTML1.1+RDFa will only support @xml:lang.
]]
http://www.w3.org/2007/08/23-rdfa-minutes#item01</text>
</note>
<note>
<date>2008-03-12</date>
<text>added argument for relating this to ISSUE-97:
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Mar/0155.html</text>
</note>
<note>
<date>2008-04-30</date>
<text>CLOSED, since it is resolved.</text>
</note>
</notes>
</issue>
<issue>
<id>7</id>
<title>Comments from Christian Hoertnagl</title>
<product>2</product>
<raisedby>6</raisedby>
<created>2007-01-30</created>
<description>We need to address all comments from Christian Hoertnagl 
(http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2005Dec/0035.html ):
1. reifying LINK
2. CURIE/URI ambiguity
3. string v. XMLLiteral
4., 13. precision about number of generated triples
5., 6., 8., 9., 12., 14., 15. 16. editorial
7. namespace usage
10. specify behavior when href is absent
11. details of canonicalization</description>
<state>1</state>
<notes>
<note>
<date>2008-05-08</date>
<text>responded in detail in
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008May/0038.html,
and RESOLVED in telecon.</text>
</note>
</notes>
</issue>
<issue>
<id>8</id>
<title>RDFa Containers: addressing the proposal and in particular DL</title>
<product>2</product>
<raisedby>6</raisedby>
<created>2007-01-30</created>
<description>The RDFa containers proposal (http://www.w3.org/2001/sw/BestPractices/HTML/2006-
rdfa-containers) does not address DL. We should eventually address it. 

</description>
<state>4</state>
<emails>
<email>
<uri>http://www.w3.org/mid/46956362.5070305@adida.net</uri>
<subject>[RDFa] ISSUE-8: RDF containers in RDFa</subject>
<sender>ben@adida.net</sender>
<date>2007-07-11</date>
</email>
<email>
<uri>http://www.w3.org/mid/768DACDC356ED04EA1F1130F97D2985201211AE5@RZJC2EX.jr1.local</uri>
<subject>RE: [RDFa] ISSUE-8: RDF containers in RDFa</subject>
<sender>michael.hausenblas@joanneum.at</sender>
<date>2007-07-12</date>
</email>
<email>
<uri>http://www.w3.org/mid/640dd5060707120135u12b3bb54ld84ccf73cca2a47a@mail.gmail.com</uri>
<subject>Re: [RDFa] ISSUE-8: RDF containers in RDFa</subject>
<sender>mark.birbeck@x-port.net</sender>
<date>2007-07-12</date>
</email>
<email>
<uri>http://www.w3.org/mid/46960365.6030308@w3.org</uri>
<subject>Re: [RDFa] ISSUE-8: RDF containers in RDFa</subject>
<sender>ivan@w3.org</sender>
<date>2007-07-12</date>
</email>
<email>
<uri>http://www.w3.org/mid/469606CD.1070805@w3.org</uri>
<subject>Re: [RDFa] ISSUE-8: RDF containers in RDFa</subject>
<sender>ivan@w3.org</sender>
<date>2007-07-12</date>
</email>
<email>
<uri>http://www.w3.org/mid/469607C4.8040705@w3.org</uri>
<subject>Re: [RDFa] ISSUE-8: RDF containers in RDFa</subject>
<sender>ivan@w3.org</sender>
<date>2007-07-12</date>
</email>
<email>
<uri>http://www.w3.org/mid/469634B2.6020005@adida.net</uri>
<subject>Re: [RDFa] ISSUE-8: RDF containers in RDFa</subject>
<sender>ben@adida.net</sender>
<date>2007-07-12</date>
</email>
<email>
<uri>http://www.w3.org/mid/1184251753.4187.163.camel@pav</uri>
<subject>Re: [RDFa] ISSUE-8: RDF containers in RDFa</subject>
<sender>connolly@w3.org</sender>
<date>2007-07-12</date>
</email>
<email>
<uri>http://www.w3.org/mid/469640E7.20603@adida.net</uri>
<subject>Re: [RDFa] ISSUE-8: RDF containers in RDFa</subject>
<sender>ben@adida.net</sender>
<date>2007-07-12</date>
</email>
<email>
<uri>http://www.w3.org/mid/1184252603.4187.173.camel@pav</uri>
<subject>Re: [RDFa] ISSUE-8: RDF containers in RDFa</subject>
<sender>connolly@w3.org</sender>
<date>2007-07-12</date>
</email>
<email>
<uri>http://www.w3.org/mid/46967ACF.6040603@adida.net</uri>
<subject>Re: [RDFa] ISSUE-8: RDF containers in RDFa</subject>
<sender>ben@adida.net</sender>
<date>2007-07-12</date>
</email>
<email>
<uri>http://www.w3.org/mid/1184268117.4187.256.camel@pav</uri>
<subject>Re: [RDFa] ISSUE-8: RDF containers in RDFa</subject>
<sender>connolly@w3.org</sender>
<date>2007-07-12</date>
</email>
<email>
<uri>http://www.w3.org/mid/768DACDC356ED04EA1F1130F97D2985201211BA2@RZJC2EX.jr1.local</uri>
<subject>RE: [RDFa] ISSUE-8: RDF containers in RDFa</subject>
<sender>michael.hausenblas@joanneum.at</sender>
<date>2007-07-12</date>
</email>
<email>
<uri>http://www.w3.org/mid/469C09E9.4060709@adida.net</uri>
<subject>Re: [RDFa] ISSUE-8: RDF containers in RDFa</subject>
<sender>ben@adida.net</sender>
<date>2007-07-16</date>
</email>
<email>
<uri>http://www.w3.org/mid/469C852E.1060203@w3.org</uri>
<subject>Re: [RDFa] ISSUE-8: RDF containers in RDFa</subject>
<sender>ivan@w3.org</sender>
<date>2007-07-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/1184688743.4187.413.camel@pav</uri>
<subject>Re: [RDFa] ISSUE-8: RDF containers in RDFa</subject>
<sender>connolly@w3.org</sender>
<date>2007-07-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/469CEB05.2040908@adida.net</uri>
<subject>Re: [RDFa] ISSUE-8: RDF containers in RDFa</subject>
<sender>ben@adida.net</sender>
<date>2007-07-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/469DEC8A.5070403@w3.org</uri>
<subject>Re: [RDFa] ISSUE-8: RDF containers in RDFa</subject>
<sender>ivan@w3.org</sender>
<date>2007-07-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070718122101.GA2440@Octavius</uri>
<subject>Re: [RDFa] ISSUE-8: RDF containers in RDFa</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-07-18</date>
</email>
</emails>
<notes>
<note>
<date>2007-06-13</date>
<text>updated this issue to discuss containers in general, since we haven't approved this.</text>
</note>
<note>
<date>2008-02-22</date>
<text>POSTPONED per http://www.w3.org/2008/02/21-rdfa-minutes.html#item03
(i.e. not in version 1)</text>
</note>
</notes>
</issue>
<issue>
<id>9</id>
<title>Nested meta's and link's</title>
<product>2</product>
<raisedby>6</raisedby>
<created>2007-01-30</created>
<description>In Discussion as of 2006-12-18  
 
What happens if we nest meta's and link's ? 

Proposed Resolution: http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-
tf/2006Apr/0007.html - The subject of the inners are the same as the subject of 
the outer. In particular, if the outer has a about, then that's the subject for 
the inners. If the outer has no about, then the subject is the outer's 
immediate parent. A good example was given in 
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2006Mar/0060 </description>
<state>4</state>
<emails>
<email>
<uri>http://www.w3.org/mid/468BD635.3010401@adida.net</uri>
<subject>Re: [RDFa] ISSUE-1: reification</subject>
<sender>ben@adida.net</sender>
<date>2007-07-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/468BD7D4.6080903@adida.net</uri>
<subject>[RDFa] ISSUE-9: META and LINK in the body</subject>
<sender>ben@adida.net</sender>
<date>2007-07-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/468CA00C.3040909@w3.org</uri>
<subject>Re: [RDFa] ISSUE-9: META and LINK in the body</subject>
<sender>ivan@w3.org</sender>
<date>2007-07-05</date>
</email>
<email>
<uri>http://www.w3.org/mid/640dd5060707050205t1e114871lf7499a7b9e369e2c@mail.gmail.com</uri>
<subject>Re: [RDFa] ISSUE-9: META and LINK in the body</subject>
<sender>mark.birbeck@x-port.net</sender>
<date>2007-07-05</date>
</email>
<email>
<uri>http://www.w3.org/mid/46927BD7.5060505@adida.net</uri>
<subject>[RDFa] ISSUE-9: nested LINK and META</subject>
<sender>ben@adida.net</sender>
<date>2007-07-09</date>
</email>
<email>
<uri>http://www.w3.org/mid/640dd5060707091446u6f527e9bjc5f0bf41854379b1@mail.gmail.com</uri>
<subject>Re: [RDFa] ISSUE-9: nested LINK and META</subject>
<sender>mark.birbeck@x-port.net</sender>
<date>2007-07-09</date>
</email>
<email>
<uri>http://www.w3.org/mid/46935973.303@w3.org</uri>
<subject>Re: [RDFa] ISSUE-9: nested LINK and META</subject>
<sender>ivan@w3.org</sender>
<date>2007-07-10</date>
</email>
<email>
<uri>http://www.w3.org/mid/4693B8D6.8090503@adida.net</uri>
<subject>Re: [RDFa] ISSUE-9: nested LINK and META, link to ISSUE-12</subject>
<sender>ben@adida.net</sender>
<date>2007-07-10</date>
</email>
</emails>
<notes>
<note>
<date>2007-07-12</date>
<text>this will NOT happen in XHTML 1.1+RDFa, but we may consider it for XHTML2.</text>
</note>
</notes>
</issue>
<issue>
<id>10</id>
<title>XHTML 1.1 Namespace doesn't end in / or #</title>
<product>2</product>
<raisedby>6</raisedby>
<created>2007-01-30</created>
<description>How can we resolve CURIEs? 

Note (2006-05-13): As the TF is considering grounding CURIEs in the current URI 
(possibly followed by "#"), this may no longer be an issue.</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/46FBD9B4.60501@adida.net</uri>
<subject>ISSUE-10: RESOLVED - XHTML 1.1 namespace doesn't end in / or #</subject>
<sender>ben@adida.net</sender>
<date>2007-09-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/a707f8300709280248y5ff0da48k739cb57c8339072c@mail.gmail.com</uri>
<subject>Re: ISSUE-10: RESOLVED - XHTML 1.1 namespace doesn't end in / or #</subject>
<sender>mark.birbeck@formsPlayer.com</sender>
<date>2007-09-28</date>
</email>
<email>
<uri>http://www.w3.org/mid/cf8107640709280552i607c994ane0fb20aa02723bea@mail.gmail.com</uri>
<subject>Re: ISSUE-10: RESOLVED - XHTML 1.1 namespace doesn't end in / or #</subject>
<sender>lindstream@gmail.com</sender>
<date>2007-09-28</date>
</email>
</emails>
<notes>
<note>
<date>2007-09-27</date>
<text>2007-09-27: resolved to have a prefix of

http://www.w3.org/1999/xhtml/vocab#

for all reserved values of @rel.</text>
</note>
</notes>
</issue>
<issue>
<id>11</id>
<title>RDFa Primer document</title>
<product>2</product>
<raisedby>6</raisedby>
<created>2007-01-30</created>
<description>Comments regarding the RDFa Primer document
(http://www.w3.org/2006/07/SWD/RDFa/primer/ ). 

 + Elias Torres sent comments on June 3rd, 2006: 
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2006Jun/0008.html
 + Lee Feigenbaum  sent comments on May 31st, 2006: 
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2006Jun/0001.html 


</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/768DACDC356ED04EA1F1130F97D29852016638B9@RZJC2EX.jr1.local</uri>
<subject>meeting record: 2008-04-24 RDF-in-XHTML TF telecon</subject>
<sender>michael.hausenblas@joanneum.at</sender>
<date>2008-04-25</date>
</email>
<email>
<uri>http://www.w3.org/mid/768DACDC356ED04EA1F1130F97D298520166398A@RZJC2EX.jr1.local</uri>
<subject>[RDFa] Comments on the RDFa Primer</subject>
<sender>michael.hausenblas@joanneum.at</sender>
<date>2008-04-28</date>
</email>
<email>
<uri>http://www.w3.org/mid/5.1.0.14.2.20080501123531.04398fb0@127.0.0.1</uri>
<subject>meeting record: 2008-05-01 RDFa telecon</subject>
<sender>swick@w3.org</sender>
<date>2008-05-01</date>
</email>
</emails>
<notes>
<note>
<date>2008-04-30</date>
<text>RESOLVED as "Michael to respond to Elias and Lee that the RDFa Primer has
changed substantially and invite for new comments. This issue is closed."</text>
</note>
</notes>
</issue>
<issue>
<id>12</id>
<title>RDFa Syntax document does not include the nested METAs use case scenario</title>
<product>2</product>
<raisedby>6</raisedby>
<created>2007-02-05</created>
<description>(for Bob DuCharme)

</description>
<state>4</state>
<emails>
<email>
<uri>http://www.w3.org/mid/4693B8D6.8090503@adida.net</uri>
<subject>Re: [RDFa] ISSUE-9: nested LINK and META, link to ISSUE-12</subject>
<sender>ben@adida.net</sender>
<date>2007-07-10</date>
</email>
</emails>
<notes>
<note>
<date>2007-07-12</date>
<text>this will NOT happen for XHTML1.1+RDFa, but we may consider it for XHTML2.</text>
</note>
</notes>
</issue>
<issue>
<id>13</id>
<title>Old Issues list obsoleted as of 2007-01-31</title>
<product>2</product>
<raisedby>14</raisedby>
<created>2007-02-07</created>
<description>http://www.w3.org/2001/sw/BestPractices/HTML/2005-current-issues</description>
<state>1</state>
<notes>
<note>
<date>2007-02-07</date>
<text>Closed due to [1],  Topic 1.

[1] http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2007Feb/0018.html</text>
</note>
<note>
<date>2007-02-13</date>
<text>[RRS] Open issues are carried forward to tracker as open issues.
Closed issues were not carried forward; this single issue serves as a pointer to
the old closed issues.</text>
</note>
</notes>
</issue>
<issue>
<id>14</id>
<title>Apache configuration</title>
<product>5</product>
<raisedby>18</raisedby>
<created>2007-02-13</created>
<description>Verify minimal required overrides.</description>
<state>1</state>
<notes>
<note>
<date>2007-02-13</date>
<text>Diego's test results: 
http://lists.w3.org/Archives/Public/public-swd-wg/2007Jan/0005.html
Diego's proposed resolution: 
http://lists.w3.org/Archives/Public/public-swd-wg/2007Jan/0033.html</text>
</note>
</notes>
</issue>
<issue>
<id>15</id>
<title>Extended configuration</title>
<product>5</product>
<raisedby>18</raisedby>
<created>2007-02-13</created>
<description>Says: "If you are using a slash namespace and want to provide both RDF and HTML
content, where the HTML content is served as individual hyperlinked documents
for each class or property, and where the RDF is served as bounded descriptions
of each class or property, see recipe 6 (@@TODO)."
</description>
<state>1</state>
<notes>
<note>
<date>2007-02-13</date>
<text>Same as ISSUE-17</text>
</note>
</notes>
</issue>
<issue>
<id>16</id>
<title>Default behavior</title>
<product>5</product>
<raisedby>18</raisedby>
<created>2007-02-13</created>
<description>http://www.w3.org/TR/swbp-vocab-pub/#default
Currently says: "Performing content negotiation based on the value of the
'User-agent:' header field is not generally considered good practice, @@TODO why."
</description>
<state>0</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20070915090410.GA812@Octavius</uri>
<subject>[RECIPES] 'Issue 1.3'</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-09-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070915142535.GA680@Octavius</uri>
<subject>[ALL] Agenda - Sep 18 2007 SWD telecon - 1500 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-09-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/bd1d3fc00709180239m41ab82d3v39701872d80381b9@mail.gmail.com</uri>
<subject>Re: [ALL] Agenda - Sep 18 2007 SWD telecon - 1500 UTC</subject>
<sender>qreul@csd.abdn.ac.uk</sender>
<date>2007-09-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/46EF9DF6.9050006@few.vu.nl</uri>
<subject>Re: [ALL] Agenda - Sep 18 2007 SWD telecon - 1500 UTC</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-09-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/46F7799E.6080801@cs.vu.nl</uri>
<subject>[ALL] agenda 25 Sep telecon - 1500 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-09-24</date>
</email>
<email>
<uri>http://www.w3.org/mid/768DACDC356ED04EA1F1130F97D29852012E5917@RZJC2EX.jr1.local</uri>
<subject>RE: [ALL] agenda 25 Sep telecon - 1500 UTC</subject>
<sender>michael.hausenblas@joanneum.at</sender>
<date>2007-09-24</date>
</email>
<email>
<uri>http://www.w3.org/mid/316ADBDBFE4F4D4AA4FEEF7496ECAEF9158948@EVS1.ac.nuigalway.ie</uri>
<subject>RE: [ALL] agenda 25 Sep telecon - 1500 UTC</subject>
<sender>vit.novacek@deri.org</sender>
<date>2007-09-24</date>
</email>
<email>
<uri>http://www.w3.org/mid/46F7D948.7080404@w3.org</uri>
<subject>Re: [ALL] agenda 25 Sep telecon - 1500 UTC</subject>
<sender>jphipps@madcreek.com</sender>
<date>2007-09-24</date>
</email>
<email>
<uri>http://www.w3.org/mid/46F939E0.1070703@csd.abdn.ac.uk</uri>
<subject>Meeting record: 2007-09-25</subject>
<sender>qreul@csd.abdn.ac.uk</sender>
<date>2007-09-25</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070925180109.GA2648@Octavius</uri>
<subject>[ALL] Report - 2007-09-25 SWD telecon - with Amsterdam schedule</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-09-25</date>
</email>
<email>
<uri>http://www.w3.org/mid/4783570E020000D8000266E9@ntgwgate.loc.gov</uri>
<subject>Regrets - Re: [ALL] agenda 8 Jan telecon 1600 UTC</subject>
<sender>juth@loc.gov</sender>
<date>2008-01-08</date>
</email>
<email>
<uri>http://www.w3.org/mid/47825367.10302@cs.vu.nl</uri>
<subject>[ALL] agenda 8 Jan telecon 1600 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2008-01-07</date>
</email>
<email>
<uri>http://www.w3.org/mid/CAB44397-D95E-4696-B790-B22F63BB8A30@manchester.ac.uk</uri>
<subject>Meeting record: 2007-12-18 SWD telecon</subject>
<sender>sean.bechhofer@manchester.ac.uk</sender>
<date>2007-12-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/4767EDC5.7040000@sandsoft.com</uri>
<subject>Re: [ALL] Agenda - Dec 18 2007 SWD telecon - 1600 UTC</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2007-12-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/52bd7c3d0712180745x53d8c9d2o8087b56e66f13f79@mail.gmail.com</uri>
<subject>Re: [ALL] Agenda - Dec 18 2007 SWD telecon - 1600 UTC</subject>
<sender>simone.onofri@gmail.com</sender>
<date>2007-12-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/4767E4F3.1020305@deri.org</uri>
<subject>Re: [ALL] Agenda - Dec 18 2007 SWD telecon - 1600 UTC</subject>
<sender>vit.novacek@deri.org</sender>
<date>2007-12-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/20071218095958.GA3876@octavius</uri>
<subject>[ALL] Agenda - Dec 18 2007 SWD telecon - 1600 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-12-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/4761021E0200006A0001BF5B@ntgwgate.loc.gov</uri>
<subject>Minutes from 2007-12-11 telecon</subject>
<sender>cred@loc.gov</sender>
<date>2007-12-13</date>
</email>
<email>
<uri>http://www.w3.org/mid/47017183.2010400@cs.vu.nl</uri>
<subject>[ALL] agenda 2 Oct telecon  - 1500 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-10-02</date>
</email>
<email>
<uri>http://www.w3.org/mid/4706296E02000015003B7A00@ntgwgate.loc.gov</uri>
<subject>meeting record: 2007-10-02 swd telecon</subject>
<sender>edsu@loc.gov</sender>
<date>2007-10-05</date>
</email>
<email>
<uri>http://www.w3.org/mid/20071022140030.GA2188@Octavius</uri>
<subject>[ALL] Agenda - Oct 23 2007 SWD telecon - 1500 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-10-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/471E0DDD.3000407@sandsoft.com</uri>
<subject>Re: [ALL] Agenda - Oct 23 2007 SWD telecon - 1500 UTC</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2007-10-23</date>
</email>
<email>
<uri>http://www.w3.org/mid/52bd7c3d0710230811x4b8a09a8o86b415770d755f5d@mail.gmail.com</uri>
<subject>Re: [ALL] Agenda - Oct 23 2007 SWD telecon - 1500 UTC</subject>
<sender>simone.onofri@gmail.com</sender>
<date>2007-10-23</date>
</email>
<email>
<uri>http://www.w3.org/mid/471DE09A020000D80001FAC1@ntgwgate.loc.gov</uri>
<subject>Late Regrets - Re: [ALL] Agenda - Oct 23 2007 SWD telecon - 	1500 UTC</subject>
<sender>juth@loc.gov</sender>
<date>2007-10-23</date>
</email>
<email>
<uri>http://www.w3.org/mid/471E010B0200006A0001784F@ntgwgate.loc.gov</uri>
<subject>Meeting record: 2007-10-23 SWD telecon (Table of contents)</subject>
<sender>cred@loc.gov</sender>
<date>2007-10-23</date>
</email>
<email>
<uri>http://www.w3.org/mid/471E011D0200006A00017852@ntgwgate.loc.gov</uri>
<subject>Meeting record: 2007-10-23 SWD telecon (Minutes)</subject>
<sender>cred@loc.gov</sender>
<date>2007-10-23</date>
</email>
<email>
<uri>http://www.w3.org/mid/4725C25B.8010403@cs.vu.nl</uri>
<subject>[ALL] agenda 30 Oct telecon - 1500 UTC (1 hour earlier than usual  for Europeans)</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-10-29</date>
</email>
<email>
<uri>http://www.w3.org/mid/316ADBDBFE4F4D4AA4FEEF7496ECAEF91589A1@EVS1.ac.nuigalway.ie</uri>
<subject>RE: [ALL] agenda 30 Oct telecon - 1500 UTC (1 hour earlier than usual  for Europeans)</subject>
<sender>vit.novacek@deri.org</sender>
<date>2007-10-30</date>
</email>
<email>
<uri>http://www.w3.org/mid/52bd7c3d0710300648p3afa5e31me87e0a40a970a89b@mail.gmail.com</uri>
<subject>Re: [ALL] agenda 30 Oct telecon - 1500 UTC (1 hour earlier than usual for Europeans)</subject>
<sender>simone.onofri@gmail.com</sender>
<date>2007-10-30</date>
</email>
<email>
<uri>http://www.w3.org/mid/47275381.3020204@csd.abdn.ac.uk</uri>
<subject>Re: [ALL] agenda 30 Oct telecon - 1500 UTC (1 hour earlier than usual   for Europeans)</subject>
<sender>qreul@csd.abdn.ac.uk</sender>
<date>2007-10-30</date>
</email>
<email>
<uri>http://www.w3.org/mid/87ED80C0-1C85-4355-BBC6-54D5D567BF62@manchester.ac.uk</uri>
<subject>meeting record: 2007-10-30 SWDWG</subject>
<sender>sean.bechhofer@manchester.ac.uk</sender>
<date>2007-10-31</date>
</email>
<email>
<uri>http://www.w3.org/mid/20071105112919.GA4768@sub-tombaker</uri>
<subject>[ALL] Agenda 6 November telecon - 1600 UTC (1100 Boston)</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-11-05</date>
</email>
<email>
<uri>http://www.w3.org/mid/472F0728.5050404@csd.abdn.ac.uk</uri>
<subject>Re: [ALL] Agenda 6 November telecon - 1600 UTC (1100 Boston)</subject>
<sender>qreul@csd.abdn.ac.uk</sender>
<date>2007-11-05</date>
</email>
<email>
<uri>http://www.w3.org/mid/0894AAE4-1177-4DC1-AF22-9AAFDD769A13@madcreek.com</uri>
<subject>Re: [ALL] Agenda 6 November telecon - 1600 UTC (1100 Boston)</subject>
<sender>jphipps@madcreek.com</sender>
<date>2007-11-05</date>
</email>
<email>
<uri>http://www.w3.org/mid/472EDF9F020000D800020C6C@ntgwgate.loc.gov</uri>
<subject>Regrets - Re: [ALL] Agenda 6 November telecon - 1600 UTC (1100 	Boston)</subject>
<sender>juth@loc.gov</sender>
<date>2007-11-05</date>
</email>
<email>
<uri>http://www.w3.org/mid/472FEC05.1070800@sandsoft.com</uri>
<subject>Re: [ALL] Agenda 6 November telecon - 1600 UTC (1100 Boston)</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2007-11-05</date>
</email>
<email>
<uri>http://www.w3.org/mid/474209F8.1010304@cs.vu.nl</uri>
<subject>[ALL] agenda 20 Nov telecon - 1600 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-11-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D03B3F1EE@exchange11.fed.cclrc.ac.uk</uri>
<subject>[SKOS] deliverables (was RE: [ALL] agenda 20 Nov telecon - 1600 UTC)</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-11-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/47430233.1060908@sandsoft.com</uri>
<subject>Re: [ALL] agenda 20 Nov telecon - 1600 UTC</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2007-11-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/52bd7c3d0711200756n1bc6b3c3s16049f3efee2f1be@mail.gmail.com</uri>
<subject>Re: [ALL] agenda 20 Nov telecon - 1600 UTC</subject>
<sender>simone.onofri@gmail.com</sender>
<date>2007-11-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/2AD2401FC36E784094D0B3375FDA6CE80246E8AF@VMAIL2.uoa.abdn.ac.uk</uri>
<subject>Meeting record: 2007-11-20 SWD telecon</subject>
<sender>q.reul@abdn.ac.uk</sender>
<date>2007-11-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/47475538.8060302@few.vu.nl</uri>
<subject>Re: Meeting record: 2007-11-20 SWD telecon</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-11-23</date>
</email>
<email>
<uri>http://www.w3.org/mid/2AD2401FC36E784094D0B3375FDA6CE8B6C6C2@VMAIL2.uoa.abdn.ac.uk</uri>
<subject>RE: Meeting record: 2007-11-20 SWD telecon</subject>
<sender>q.reul@abdn.ac.uk</sender>
<date>2007-11-24</date>
</email>
<email>
<uri>http://www.w3.org/mid/20071126165028.GA1112@octavius</uri>
<subject>[ALL] Agenda - Nov 27 2007 SWD telecon - 1600 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-11-26</date>
</email>
<email>
<uri>http://www.w3.org/mid/316ADBDBFE4F4D4AA4FEEF7496ECAEF9158A0C@EVS1.ac.nuigalway.ie</uri>
<subject>RE: [ALL] Agenda - Nov 27 2007 SWD telecon - 1600 UTC</subject>
<sender>vit.novacek@deri.org</sender>
<date>2007-11-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/2AD2401FC36E784094D0B3375FDA6CE80253E964@VMAIL2.uoa.abdn.ac.uk</uri>
<subject>RE: [ALL] Agenda - Nov 27 2007 SWD telecon - 1600 UTC</subject>
<sender>q.reul@abdn.ac.uk</sender>
<date>2007-11-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/001c01c830f9$7d9e5ea0$4101a8c0@dc.itd.rl.ac.uk</uri>
<subject>Re: [ALL] Agenda - Nov 27 2007 SWD telecon - 1600 UTC</subject>
<sender>a.j.miles@rl.ac.uk</sender>
<date>2007-11-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/52bd7c3d0711270552i6ea118b3l599e9816a1179a42@mail.gmail.com</uri>
<subject>Re: [ALL] Agenda - Nov 27 2007 SWD telecon - 1600 UTC</subject>
<sender>simone.onofri@gmail.com</sender>
<date>2007-11-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/474BF3CE020000D800022C58@ntgwgate.loc.gov</uri>
<subject>Leaving Early - Re: [ALL] Agenda - Nov 27 2007 SWD telecon - 	1600 UTC</subject>
<sender>juth@loc.gov</sender>
<date>2007-11-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/f032cc060711290755g722f0342r7491b619e968b03b@mail.gmail.com</uri>
<subject>Meeting record: 2007-11-27 SWD telecon</subject>
<sender>ehs@pobox.com</sender>
<date>2007-11-29</date>
</email>
<email>
<uri>http://www.w3.org/mid/475420C3.6000606@cs.vu.nl</uri>
<subject>[ALL] agenda Dec 4 telecon - 1600 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-12-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/316ADBDBFE4F4D4AA4FEEF7496ECAEF9158A1D@EVS1.ac.nuigalway.ie</uri>
<subject>AW: [ALL] agenda Dec 4 telecon - 1600 UTC</subject>
<sender>vit.novacek@deri.org</sender>
<date>2007-12-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/47543D81020000D8000236F9@ntgwgate.loc.gov</uri>
<subject>Re: [ALL] agenda Dec 4 telecon - 1600 UTC</subject>
<sender>juth@loc.gov</sender>
<date>2007-12-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/2AD2401FC36E784094D0B3375FDA6CE802602411@VMAIL2.uoa.abdn.ac.uk</uri>
<subject>RE: [ALL] agenda Dec 4 telecon - 1600 UTC</subject>
<sender>q.reul@abdn.ac.uk</sender>
<date>2007-12-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/20071210151751.GA2940@octavius</uri>
<subject>[ALL] Agenda - Dec 11 2007 SWD telecon - 1600 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-12-10</date>
</email>
<email>
<uri>http://www.w3.org/mid/E92D1644-9044-4011-92A6-8455F0380B38@madcreek.com</uri>
<subject>Re: [ALL] Agenda - Dec 11 2007 SWD telecon - 1600 UTC</subject>
<sender>jphipps@madcreek.com</sender>
<date>2007-12-11</date>
</email>
<email>
<uri>http://www.w3.org/mid/475EA699.3010609@adida.net</uri>
<subject>Re: [ALL] Agenda - Dec 11 2007 SWD telecon - 1600 UTC</subject>
<sender>ben@adida.net</sender>
<date>2007-12-11</date>
</email>
<email>
<uri>http://www.w3.org/mid/52bd7c3d0712110703s522fee13p1b16e6708e333418@mail.gmail.com</uri>
<subject>Re: [ALL] Agenda - Dec 11 2007 SWD telecon - 1600 UTC</subject>
<sender>simone.onofri@gmail.com</sender>
<date>2007-12-11</date>
</email>
<email>
<uri>http://www.w3.org/mid/2AD2401FC36E784094D0B3375FDA6CE802788761@VMAIL2.uoa.abdn.ac.uk</uri>
<subject>RE: [ALL] Agenda - Dec 11 2007 SWD telecon - 1600 UTC</subject>
<sender>q.reul@abdn.ac.uk</sender>
<date>2007-12-11</date>
</email>
<email>
<uri>http://www.w3.org/mid/7C1F4F6C-FD48-46FF-814E-E84AB89D0987@madcreek.com</uri>
<subject>Meeting record: 2008-01-08 SWD telecon</subject>
<sender>jphipps@madcreek.com</sender>
<date>2008-01-11</date>
</email>
<email>
<uri>http://www.w3.org/mid/478BB65B.8080507@cs.vu.nl</uri>
<subject>[ALL] agenda 15 Jan telecon 1600 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2008-01-14</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB6690269F988@hqgiex01.fao.org</uri>
<subject>RE: [ALL] agenda 15 Jan telecon 1600 UTC</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-01-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/478CE1C7.8010400@sandsoft.com</uri>
<subject>Re: [ALL] agenda 15 Jan telecon 1600 UTC</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2008-01-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/478DB2D6.70308@fundacionctic.org</uri>
<subject>Meeting record: 2008-01-15 SWD telecon</subject>
<sender>diego.berrueta@fundacionctic.org</sender>
<date>2008-01-16</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080121175703.GA3684@octavius</uri>
<subject>[ALL] Agenda - Jan 22 2008 SWD telecon - 1600 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2008-01-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47960E40.2070703@cs.vu.nl</uri>
<subject>Re: [ALL] Agenda - Jan 22 2008 SWD telecon - 1600 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2008-01-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/47961162.8060706@few.vu.nl</uri>
<subject>Re: [ALL] Agenda - Jan 22 2008 SWD telecon - 1600 UTC</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/479620AD.1020805@sandsoft.com</uri>
<subject>Re: [ALL] Agenda - Jan 22 2008 SWD telecon - 1600 UTC</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2008-01-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/f032cc060801221808t55949239mdc9dc205605a72f4@mail.gmail.com</uri>
<subject>Re: Revised Recipes</subject>
<sender>ehs@pobox.com</sender>
<date>2008-01-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/479E064F.6000309@cs.vu.nl</uri>
<subject>[ALL] agenda 29 Jan telecon -- 16:00 UTC </subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2008-01-28</date>
</email>
<email>
<uri>http://www.w3.org/mid/479E2C33.6020307@cs.vu.nl</uri>
<subject>Re: [ALL] agenda 29 Jan telecon -- 16:00 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2008-01-28</date>
</email>
<email>
<uri>http://www.w3.org/mid/A492AE2F-6DCF-4F65-93EA-A7EF9E80D5E7@manchester.ac.uk</uri>
<subject>Meeting Record: 2008-01-29 telecon</subject>
<sender>sean.bechhofer@manchester.ac.uk</sender>
<date>2008-01-31</date>
</email>
<email>
<uri>http://www.w3.org/mid/47A75770.6060901@cs.vu.nl</uri>
<subject>[ALL] agenda 5 Feb telecon - 1600 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2008-02-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/47A8AB1F.9060203@sandsoft.com</uri>
<subject>Re: [ALL] agenda 5 Feb telecon - 1600 UTC</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2008-02-05</date>
</email>
<email>
<uri>http://www.w3.org/mid/5.1.0.14.2.20080205160438.05ea66e8@127.0.0.1</uri>
<subject>meeting record: 2008-02-05 SWD WG</subject>
<sender>swick@w3.org</sender>
<date>2008-02-05</date>
</email>
<email>
<uri>http://www.w3.org/mid/47A8EFF9.8040405@sandsoft.com</uri>
<subject>[VocabMgmt] New Editor's Draft Available</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2008-02-05</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080211171707.GA2136@octavius</uri>
<subject>[ALL] Agenda - Feb 12 2008 SWD telecon - 1600 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2008-02-11</date>
</email>
<email>
<uri>http://www.w3.org/mid/2AD2401FC36E784094D0B3375FDA6CE802E5523F@VMAIL2.uoa.abdn.ac.uk</uri>
<subject>Meeting record: 2008-02-12 SWD telecon</subject>
<sender>q.reul@abdn.ac.uk</sender>
<date>2008-02-14</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080218163809.GA3304@octavius</uri>
<subject>[All] Agenda - Feb 19 2008 SWD telecon - 1600 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2008-02-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/34b5049c0802181029q5c534978m87acdc4c4f6a334d@mail.gmail.com</uri>
<subject>Re: [All] Agenda - Feb 19 2008 SWD telecon - 1600 UTC</subject>
<sender>jphipps@madcreek.com</sender>
<date>2008-02-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB669029DAF5E@hqgiex01.fao.org</uri>
<subject>RE: [All] Agenda - Feb 19 2008 SWD telecon - 1600 UTC</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-02-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/52bd7c3d0802181458o4267f179lf9b25fbbe0e46971@mail.gmail.com</uri>
<subject>Re: [All] Agenda - Feb 19 2008 SWD telecon - 1600 UTC</subject>
<sender>simone.onofri@gmail.com</sender>
<date>2008-02-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BDA2FE.3020004@zoo.ox.ac.uk</uri>
<subject>Minutes of 2008-02-19 telcon</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47C29E86.5010404@cs.vu.nl</uri>
<subject>[ALL] agenda telecon 26 Feb - 1600 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2008-02-25</date>
</email>
<email>
<uri>http://www.w3.org/mid/2AD2401FC36E784094D0B3375FDA6CE80306897E@VMAIL2.uoa.abdn.ac.uk</uri>
<subject>RE: [ALL] agenda telecon 26 Feb - 1600 UTC</subject>
<sender>q.reul@abdn.ac.uk</sender>
<date>2008-02-26</date>
</email>
<email>
<uri>http://www.w3.org/mid/f032cc060803011003j16953aei9318c574bc410f2b@mail.gmail.com</uri>
<subject>Meeting Record: 2008-02-27 SWD telecon</subject>
<sender>ehs@pobox.com</sender>
<date>2008-03-01</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080303141032.GA3540@octavius</uri>
<subject>[ALL] Agenda - Mar 04 telecon - 1600 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2008-03-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/768DACDC356ED04EA1F1130F97D298520157BD14@RZJC2EX.jr1.local</uri>
<subject>RE: [ALL] Agenda - Mar 04 telecon - 1600 UTC</subject>
<sender>michael.hausenblas@joanneum.at</sender>
<date>2008-03-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/47D2DD96.30402@sandsoft.com</uri>
<subject>Meeting record: 2008-03-04 telecon</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2008-03-08</date>
</email>
<email>
<uri>http://www.w3.org/mid/47D562EE.4020602@cs.vu.nl</uri>
<subject>[ALL] NOTE TIME: agenda 11 Mar telecon - *1500* UTC </subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2008-03-10</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB669037A03D1@hqgiex01.fao.org</uri>
<subject>RE: [ALL] NOTE TIME: agenda 11 Mar telecon - *1500* UTC</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-03-11</date>
</email>
<email>
<uri>http://www.w3.org/mid/1205246076.4829.11.camel@duncan.fundacionctic.org</uri>
<subject>[Recipes] roadmap to the next draft</subject>
<sender>diego.berrueta@fundacionctic.org</sender>
<date>2008-03-11</date>
</email>
<email>
<uri>http://www.w3.org/mid/B0AAC07C-6A27-421A-8E62-523A40EC6D0A@madcreek.com</uri>
<subject>Re: [Recipes] roadmap to the next draft</subject>
<sender>jphipps@madcreek.com</sender>
<date>2008-03-11</date>
</email>
<email>
<uri>http://www.w3.org/mid/47D83672.7040701@few.vu.nl</uri>
<subject>Meeting record: 2008-03-11 telecon</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-03-12</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080317182900.GA3860@octavius</uri>
<subject>[All] Agenda - Mar 18 - 1500 UTC - Europeans note time!</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2008-03-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/47DEBA91.5060004@sandsoft.com</uri>
<subject>Re: [All] Agenda - Mar 18 - 1500 UTC - Europeans note time!</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2008-03-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/47E11ECC0200006A00024B85@ntgwgate.loc.gov</uri>
<subject>Minutes from 2008-03-18 telecon</subject>
<sender>cred@loc.gov</sender>
<date>2008-03-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080331130017.GA3808@octavius</uri>
<subject>[ALL] Agenda - SWD telecon Apr 01 - 1500 UTC - Europeans back to normal time</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2008-03-31</date>
</email>
<email>
<uri>http://www.w3.org/mid/47F24A4F.4080404@sandsoft.com</uri>
<subject>Re: [ALL] Agenda - SWD telecon Apr 01 - 1500 UTC - Europeans back  to normal time</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2008-04-01</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB669037A04D3@hqgiex01.fao.org</uri>
<subject>Minutes from 2008-04-01 telecon</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-04-02</date>
</email>
<email>
<uri>http://www.w3.org/mid/47FA3FE3.9050908@cs.vu.nl</uri>
<subject>[ALL] agenda 8 April telecon 1500 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2008-04-07</date>
</email>
<email>
<uri>http://www.w3.org/mid/47FAF3EC.1050309@sandsoft.com</uri>
<subject>Re: [ALL] agenda 8 April telecon 1500 UTC</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2008-04-07</date>
</email>
<email>
<uri>http://www.w3.org/mid/52bd7c3d0804080609t10266db0s930f8a6b84bca1b3@mail.gmail.com</uri>
<subject>Re: [ALL] agenda 8 April telecon 1500 UTC</subject>
<sender>simone.onofri@gmail.com</sender>
<date>2008-04-08</date>
</email>
<email>
<uri>http://www.w3.org/mid/5.1.0.14.2.20080408132657.03313ea8@127.0.0.1</uri>
<subject>meeting record: 2008-04-08 SWD telecon</subject>
<sender>swick@w3.org</sender>
<date>2008-04-08</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080414083109.GA1736@octavius</uri>
<subject>[ALL] Agenda - Apr 15 SWD telecon - 1500 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2008-04-14</date>
</email>
<email>
<uri>http://www.w3.org/mid/000001c89f07$e921e800$bb65b800$@miles@zoo.ox.ac.uk</uri>
<subject>RE: [ALL] Agenda - Apr 15 SWD telecon - 1500 UTC</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-04-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/52bd7c3d0804150811j42e98896i7ad5be7ed68f64d2@mail.gmail.com</uri>
<subject>Re: [ALL] Agenda - Apr 15 SWD telecon - 1500 UTC</subject>
<sender>simone.onofri@gmail.com</sender>
<date>2008-04-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/4804EEB4.4000305@deri.org</uri>
<subject>meeting record: 2008-04-15 SWD telecon</subject>
<sender>vit.novacek@deri.org</sender>
<date>2008-04-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/480597C6.5090004@sandsoft.com</uri>
<subject>Re: [ALL] Agenda - Apr 15 SWD telecon - 1500 UTC</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2008-04-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/480C93F1.50901@cs.vu.nl</uri>
<subject>[ALL] agenda 22 April telecon 1500 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2008-04-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/34b5049c0804220701l5d151ca4udf70a325129fc494@mail.gmail.com</uri>
<subject>Re: [ALL] agenda 22 April telecon 1500 UTC</subject>
<sender>jphipps@madcreek.com</sender>
<date>2008-04-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/480DF981.4090404@sandsoft.com</uri>
<subject>Re: [ALL] agenda 22 April telecon 1500 UTC</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2008-04-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/2B5F6004-902E-48F0-A5B1-5549EBB4CAAB@manchester.ac.uk</uri>
<subject>meeting record: 2008-04-22 SWD telecon</subject>
<sender>sean.bechhofer@manchester.ac.uk</sender>
<date>2008-04-23</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080428161756.GA3328@octavius</uri>
<subject>[ALL] Agenda - Apr 29 2008 SWD telecon - 1500 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2008-04-28</date>
</email>
<email>
<uri>http://www.w3.org/mid/5C0FCE75-D11B-4659-8353-40FEA348CF02@manchester.ac.uk</uri>
<subject>Re: [ALL] Agenda - Apr 29 2008 SWD telecon - 1500 UTC</subject>
<sender>sean.bechhofer@manchester.ac.uk</sender>
<date>2008-04-29</date>
</email>
<email>
<uri>http://www.w3.org/mid/38100CBF-4FD1-4BA2-B7A7-C143A91AE1F4@madcreek.com</uri>
<subject>meeting record: 2008-04-29 SWD WG</subject>
<sender>jphipps@madcreek.com</sender>
<date>2008-05-01</date>
</email>
<email>
<uri>http://www.w3.org/mid/4828264C.8000402@cs.vu.nl</uri>
<subject>[ALL] agenda 13 May telecon 1500 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2008-05-12</date>
</email>
<email>
<uri>http://www.w3.org/mid/1210756051.4662.4.camel@duncan.fundacionctic.org</uri>
<subject>Meeting record: 2008-05-13 SWD telecon</subject>
<sender>diego.berrueta@fundacionctic.org</sender>
<date>2008-05-14</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080519162744.GA2200@sub-tombaker</uri>
<subject>Agenda - May 20 2008 SWD telecon - 1500 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2008-05-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/01E39CC4-0BD8-4713-AC7E-60B307F0D6FD@madcreek.com</uri>
<subject>Re: Agenda - May 20 2008 SWD telecon - 1500 UTC</subject>
<sender>jphipps@madcreek.com</sender>
<date>2008-05-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/52bd7c3d0805200329v26ee1e0cn65048bd90a062d8a@mail.gmail.com</uri>
<subject>Re: Agenda - May 20 2008 SWD telecon - 1500 UTC</subject>
<sender>simone.onofri@gmail.com</sender>
<date>2008-05-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080520060610.ikydcafvdw8ogws0@webmail.stanford.edu</uri>
<subject>Re: Agenda - May 20 2008 SWD telecon - 1500 UTC</subject>
<sender>dlrubin@stanford.edu</sender>
<date>2008-05-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/4832DD17.7040605@sandsoft.com</uri>
<subject>Re: Agenda - May 20 2008 SWD telecon - 1500 UTC</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2008-05-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/f032cc060805200753u30bea643m355a8d4c9e2198b7@mail.gmail.com</uri>
<subject>Re: Agenda - May 20 2008 SWD telecon - 1500 UTC</subject>
<sender>ehs@pobox.com</sender>
<date>2008-05-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/2AD2401FC36E784094D0B3375FDA6CE803B4F44F@VMAIL2.uoa.abdn.ac.uk</uri>
<subject>Meeting record: 2008-05-20 SWD telecon</subject>
<sender>q.reul@abdn.ac.uk</sender>
<date>2008-05-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/483AD731.8090201@cs.vu.nl</uri>
<subject>[ALL] agenda 27 May telecon - 1500 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2008-05-26</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB66903B87F03@hqgiex01.fao.org</uri>
<subject>RE: [ALL] agenda 27 May telecon - 1500 UTC</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-05-26</date>
</email>
<email>
<uri>http://www.w3.org/mid/483C0B41.3040209@sandsoft.com</uri>
<subject>Re: [ALL] agenda 27 May telecon - 1500 UTC</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2008-05-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/f032cc060805270706r59feda0dq685a36bda85d918c@mail.gmail.com</uri>
<subject>Re: [ALL] agenda 27 May telecon - 1500 UTC</subject>
<sender>ehs@pobox.com</sender>
<date>2008-05-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/6.2.5.6.2.20080528050511.06bef348@stanford.edu</uri>
<subject>Minutes from tcon yesterday</subject>
<sender>dlrubin@stanford.edu</sender>
<date>2008-05-28</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080602152648.GA796@octavius</uri>
<subject>Agenda - Jun 03 2008 SWD telecon - 1500 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2008-06-02</date>
</email>
<email>
<uri>http://www.w3.org/mid/768DACDC356ED04EA1F1130F97D29852014C6242@RZJC2EX.jr1.local</uri>
<subject>RE: Agenda - Jun 03 2008 SWD telecon - 1500 UTC</subject>
<sender>michael.hausenblas@joanneum.at</sender>
<date>2008-06-02</date>
</email>
<email>
<uri>http://www.w3.org/mid/484D3AB1.2020101@cs.vu.nl</uri>
<subject>[ALL] agenda 10 June telecon - 1500 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2008-06-09</date>
</email>
<email>
<uri>http://www.w3.org/mid/5.1.0.14.2.20080610083536.046fc180@127.0.0.1</uri>
<subject>meeting record: 2008-06-03 SWD WG telecon</subject>
<sender>swick@w3.org</sender>
<date>2008-06-10</date>
</email>
<email>
<uri>http://www.w3.org/mid/484E8C2A.3020009@sandsoft.com</uri>
<subject>Re: [ALL] agenda 10 June telecon - 1500 UTC</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2008-06-10</date>
</email>
<email>
<uri>http://www.w3.org/mid/485255A6.9070800@deri.org</uri>
<subject>meeting record: 2008-06-10 SWD WG telco</subject>
<sender>vit.novacek@deri.org</sender>
<date>2008-06-13</date>
</email>
</emails>
<notes>
<note>
<date>2007-02-13</date>
<text>This was discussed at the F2F meeting in Boston and Ralph agreed to write a
brief description of how User Agent-based negotiation limits/stifles the
creation of new User Agents in the future, citing past negative experience.</text>
</note>
<note>
<date>2007-09-15</date>
<text>http://www.w3.org/2007/04/24-swd-minutes.html#action09
http://www.w3.org/2007/01/22-swd-minutes.html#action14</text>
</note>
</notes>
</issue>
<issue>
<id>17</id>
<title>Recipe 6 is incomplete</title>
<product>5</product>
<raisedby>18</raisedby>
<created>2007-02-13</created>
<description>http://www.w3.org/TR/swbp-vocab-pub/#recipe6

says: "@@TODO this recipe is included as a placeholder, as its best practice
implementation currently requires further investigation, discussion and testing,
but is anticipated to be an important part of this document, 'completing the
set' of the most commonly needed configurations."
</description>
<state>0</state>
<emails>
<email>
<uri>http://www.w3.org/mid/1174234347.9631.19.camel@daneel.berrueta.net</uri>
<subject>[Recipes] discussion on Recipe 6 (and regrets)</subject>
<sender>diego.berrueta@fundacionctic.org</sender>
<date>2007-03-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/1205246076.4829.11.camel@duncan.fundacionctic.org</uri>
<subject>[Recipes] roadmap to the next draft</subject>
<sender>diego.berrueta@fundacionctic.org</sender>
<date>2008-03-11</date>
</email>
<email>
<uri>http://www.w3.org/mid/B0AAC07C-6A27-421A-8E62-523A40EC6D0A@madcreek.com</uri>
<subject>Re: [Recipes] roadmap to the next draft</subject>
<sender>jphipps@madcreek.com</sender>
<date>2008-03-11</date>
</email>
</emails>
<notes>
<note>
<date>2007-02-13</date>
<text>This was discussed at the F2F meeting in Boston in January 2007. Diego will
perform "further investigation, discussion and testing" and write a first draft
of the recipe.</text>
</note>
<note>
<date>2007-09-24</date>
<text>There is a new draft here:
http://www.w3.org/2006/07/SWD/wiki/BestPracticeRecipe6</text>
</note>
</notes>
</issue>
<issue>
<id>18</id>
<title>QA Review comments from Karl Dubost</title>
<product>5</product>
<raisedby>18</raisedby>
<created>2007-02-13</created>
<description>In May 2006, Karl Dubost posted a series of comments and suggestions about the
Recipes draft to the Semantic Web Best Practice and Deployment Working Group
mailing list.

see:
http://www.w3.org/2006/07/SWD/wiki/BestPracticeRecipesIssues/QaReviewSummary</description>
<state>0</state>
<emails>
<email>
<uri>http://www.w3.org/mid/1205246076.4829.11.camel@duncan.fundacionctic.org</uri>
<subject>[Recipes] roadmap to the next draft</subject>
<sender>diego.berrueta@fundacionctic.org</sender>
<date>2008-03-11</date>
</email>
<email>
<uri>http://www.w3.org/mid/B0AAC07C-6A27-421A-8E62-523A40EC6D0A@madcreek.com</uri>
<subject>Re: [Recipes] roadmap to the next draft</subject>
<sender>jphipps@madcreek.com</sender>
<date>2008-03-11</date>
</email>
</emails>
</issue>
<issue>
<id>19</id>
<title>Recipes should supply a general server configuration template</title>
<product>5</product>
<raisedby>18</raisedby>
<created>2007-02-13</created>
<description>The Recipes are specific to an Apache server, but may be applicable in
non-Apache environments. It would be useful to provide a general-purpose
configuration template for use by people setting up non-Apache servers"

As part of his QA review KKarl Dubost said...
"...here there's a good opportunity to create a template and/or invite people to
submit bindings to the Mailing List, id est how people applied this recipe in
this particular server environment, Web Apps Framework, HTTP Servers only, etc.
That would help other people to find the information. With a proposed template,
it would help people to collect, gather the information."

http://www.w3.org/2006/07/SWD/wiki/BestPracticeRecipesIssues/QaReviewSummary#head-3d24132de03d1b1b65a24aafeda257e78be72da1
</description>
<state>0</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20070915142535.GA680@Octavius</uri>
<subject>[ALL] Agenda - Sep 18 2007 SWD telecon - 1500 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-09-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070915150038.GG2612@Octavius</uri>
<subject>[RECIPES] Amsterdam topic 'Recipes'</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-09-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/bd1d3fc00709180239m41ab82d3v39701872d80381b9@mail.gmail.com</uri>
<subject>Re: [ALL] Agenda - Sep 18 2007 SWD telecon - 1500 UTC</subject>
<sender>qreul@csd.abdn.ac.uk</sender>
<date>2007-09-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/46EF9DF6.9050006@few.vu.nl</uri>
<subject>Re: [ALL] Agenda - Sep 18 2007 SWD telecon - 1500 UTC</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-09-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/1205246076.4829.11.camel@duncan.fundacionctic.org</uri>
<subject>[Recipes] roadmap to the next draft</subject>
<sender>diego.berrueta@fundacionctic.org</sender>
<date>2008-03-11</date>
</email>
<email>
<uri>http://www.w3.org/mid/B0AAC07C-6A27-421A-8E62-523A40EC6D0A@madcreek.com</uri>
<subject>Re: [Recipes] roadmap to the next draft</subject>
<sender>jphipps@madcreek.com</sender>
<date>2008-03-11</date>
</email>
</emails>
</issue>
<issue>
<id>20</id>
<title>Online server testing</title>
<product>5</product>
<raisedby>18</raisedby>
<created>2007-02-14</created>
<description>The recipes provide example URIs and example responses. Diego has written some
httpUnit tests. Since the tests already exist, it would be very useful to make
these available online to provide a server validation service.

See Diego's email: 
http://lists.w3.org/Archives/Public/public-swd-wg/2006Dec/0048.html</description>
<state>0</state>
<emails>
<email>
<uri>http://www.w3.org/mid/1174074778.4975.27.camel@daneel.berrueta.net</uri>
<subject>[Recipes] towards an online validation tool for best practices</subject>
<sender>diego.berrueta@fundacionctic.org</sender>
<date>2007-03-16</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070915142535.GA680@Octavius</uri>
<subject>[ALL] Agenda - Sep 18 2007 SWD telecon - 1500 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-09-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070915150038.GG2612@Octavius</uri>
<subject>[RECIPES] Amsterdam topic 'Recipes'</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-09-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/bd1d3fc00709180239m41ab82d3v39701872d80381b9@mail.gmail.com</uri>
<subject>Re: [ALL] Agenda - Sep 18 2007 SWD telecon - 1500 UTC</subject>
<sender>qreul@csd.abdn.ac.uk</sender>
<date>2007-09-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/46EF9DF6.9050006@few.vu.nl</uri>
<subject>Re: [ALL] Agenda - Sep 18 2007 SWD telecon - 1500 UTC</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-09-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/1205246076.4829.11.camel@duncan.fundacionctic.org</uri>
<subject>[Recipes] roadmap to the next draft</subject>
<sender>diego.berrueta@fundacionctic.org</sender>
<date>2008-03-11</date>
</email>
<email>
<uri>http://www.w3.org/mid/B0AAC07C-6A27-421A-8E62-523A40EC6D0A@madcreek.com</uri>
<subject>Re: [Recipes] roadmap to the next draft</subject>
<sender>jphipps@madcreek.com</sender>
<date>2008-03-11</date>
</email>
</emails>
</issue>
<issue>
<id>21</id>
<title>Apache configuration should add that mod_rewrite must be loaded and enabled</title>
<product>5</product>
<raisedby>15</raisedby>
<created>2007-02-14</created>
<description>"...the current document[1] fails to mention that the mod_rewrite module must be
loaded into Apache (I followed the recipes step-by-step and I was surprised by a
"500 Internal error" because the module wasn't loaded)."

[1] http://www.w3.org/TR/2006/WD-swbp-vocab-pub-20060314/#apache

Diego's email:
http://lists.w3.org/Archives/Public/public-swd-wg/2006Dec/0048.html</description>
<state>0</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20070915142535.GA680@Octavius</uri>
<subject>[ALL] Agenda - Sep 18 2007 SWD telecon - 1500 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-09-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070915150038.GG2612@Octavius</uri>
<subject>[RECIPES] Amsterdam topic 'Recipes'</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-09-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/bd1d3fc00709180239m41ab82d3v39701872d80381b9@mail.gmail.com</uri>
<subject>Re: [ALL] Agenda - Sep 18 2007 SWD telecon - 1500 UTC</subject>
<sender>qreul@csd.abdn.ac.uk</sender>
<date>2007-09-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/46EF9DF6.9050006@few.vu.nl</uri>
<subject>Re: [ALL] Agenda - Sep 18 2007 SWD telecon - 1500 UTC</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-09-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/1205246076.4829.11.camel@duncan.fundacionctic.org</uri>
<subject>[Recipes] roadmap to the next draft</subject>
<sender>diego.berrueta@fundacionctic.org</sender>
<date>2008-03-11</date>
</email>
<email>
<uri>http://www.w3.org/mid/B0AAC07C-6A27-421A-8E62-523A40EC6D0A@madcreek.com</uri>
<subject>Re: [Recipes] roadmap to the next draft</subject>
<sender>jphipps@madcreek.com</sender>
<date>2008-03-11</date>
</email>
</emails>
</issue>
<issue>
<id>22</id>
<title>Questioning reference to 'IE6 hack'</title>
<product>5</product>
<raisedby>4</raisedby>
<created>2007-02-14</created>
<description>In http://www.w3.org/TR/swbp-vocab-pub/#negotiation there is reference
to a hack that's required for Internet Explorer browser clients. The
paragraph begins as follows:

"In recipes 3, 4, 5, and 6 below, RDF/XML is configured as the default
response. This is chosen to minimize the impact on deployed Semantic Web
applications that do not currently send appropriate 'Accept:' header
field values for RDF content. Note that, however, with RDF as the
default response, a 'hack' has to be included..."

The issue I'd like to raise is two fold:

1) wordsmithing:

a) Suggest that there's a new para/section titled something like
"Workaround for Internet Explorer". At the moment the details of the
hack merge in with the rest of the default behaviour.

b) the use of "hack" and "peculiar" is somewhat pejorative!

c) the layout of the itemised instructions is confusing to read, as
they're broken up by a yellow line of directive


2) ambiguity
I think we need to come down on one side of the fence on whether this
"hack" should be included. Either (a) we remove from the document any
suggestion that the reader should delete the directive and just insert
an explanation as to why it's needed; or (b) explain that IE clients
will need this directive and include it _commented out_ in the recipes
so that implementers may include it. I favour (a).
</description>
<state>0</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20070915142535.GA680@Octavius</uri>
<subject>[ALL] Agenda - Sep 18 2007 SWD telecon - 1500 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-09-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070915150038.GG2612@Octavius</uri>
<subject>[RECIPES] Amsterdam topic 'Recipes'</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-09-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/bd1d3fc00709180239m41ab82d3v39701872d80381b9@mail.gmail.com</uri>
<subject>Re: [ALL] Agenda - Sep 18 2007 SWD telecon - 1500 UTC</subject>
<sender>qreul@csd.abdn.ac.uk</sender>
<date>2007-09-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/46EF9DF6.9050006@few.vu.nl</uri>
<subject>Re: [ALL] Agenda - Sep 18 2007 SWD telecon - 1500 UTC</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-09-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/1205246076.4829.11.camel@duncan.fundacionctic.org</uri>
<subject>[Recipes] roadmap to the next draft</subject>
<sender>diego.berrueta@fundacionctic.org</sender>
<date>2008-03-11</date>
</email>
<email>
<uri>http://www.w3.org/mid/B0AAC07C-6A27-421A-8E62-523A40EC6D0A@madcreek.com</uri>
<subject>Re: [Recipes] roadmap to the next draft</subject>
<sender>jphipps@madcreek.com</sender>
<date>2008-03-11</date>
</email>
</emails>
<notes>
<note>
<date>2007-02-14</date>
<text>There was some discussion about this at the January F2F in Boston:
http://www.w3.org/2007/01/22-swd-minutes.html#action12 (scroll up from there). </text>
</note>
<note>
<date>2007-02-14</date>
<text>Diego was asked to verify that the hack was still necessary for IE7
(http://www.w3.org/2007/01/22-swd-minutes.html#action13) and he reported that it
did (http://lists.w3.org/Archives/Public/public-swd-wg/2007Jan/0076.html)</text>
</note>
<note>
<date>2007-02-14</date>
<text>Corrected links for above note. See:
http://www.w3.org/2007/01/22-swd-minutes.html#action13 -- and he reported that
it did. See: http://lists.w3.org/Archives/Public/public-swd-wg/2007Jan/0076.html</text>
</note>
</notes>
</issue>
<issue>
<id>23</id>
<title>There should be some discussion of alternatives to .htaccess</title>
<product>5</product>
<raisedby>18</raisedby>
<created>2007-02-14</created>
<description>Many organizations, for performance and security reasons, don't allow the use of
AllowOveride and this precludes the use of .htaccess files completely. We should
include a section that specifically addresses this:

1. Briefly discuss the relative performance and security disadvantages of
.htaccess files, or at least point to such a discussion.

2. Discuss the possibility of enabling AllowOveride on a directory-specific
rather than a global basis to address those issues

3. Point out that each of the recipes can be implemented directly in httpd.conf
files without enabling AllowOveride and show how to do that for at least one of them

4. Include a recipe that rewrites the URL to a very simple cgi script (examples
in perl, php) that would handle the actual redirect. This appears to be the way
the recipes are often implemented.

</description>
<state>0</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20070915142535.GA680@Octavius</uri>
<subject>[ALL] Agenda - Sep 18 2007 SWD telecon - 1500 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-09-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070915150038.GG2612@Octavius</uri>
<subject>[RECIPES] Amsterdam topic 'Recipes'</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-09-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/bd1d3fc00709180239m41ab82d3v39701872d80381b9@mail.gmail.com</uri>
<subject>Re: [ALL] Agenda - Sep 18 2007 SWD telecon - 1500 UTC</subject>
<sender>qreul@csd.abdn.ac.uk</sender>
<date>2007-09-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/46EF9DF6.9050006@few.vu.nl</uri>
<subject>Re: [ALL] Agenda - Sep 18 2007 SWD telecon - 1500 UTC</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-09-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/1205246076.4829.11.camel@duncan.fundacionctic.org</uri>
<subject>[Recipes] roadmap to the next draft</subject>
<sender>diego.berrueta@fundacionctic.org</sender>
<date>2008-03-11</date>
</email>
<email>
<uri>http://www.w3.org/mid/B0AAC07C-6A27-421A-8E62-523A40EC6D0A@madcreek.com</uri>
<subject>Re: [Recipes] roadmap to the next draft</subject>
<sender>jphipps@madcreek.com</sender>
<date>2008-03-11</date>
</email>
</emails>
</issue>
<issue>
<id>24</id>
<title>Additional text explaining redirect choices in the recipes</title>
<product>5</product>
<raisedby>18</raisedby>
<created>2007-02-14</created>
<description>There have been a number of instances where Alistair et al have answered
questions about the reasoning behind the use of 'conditional rewrites' and
redirects in the recipes (I'm sure there are more):

http://lists.w3.org/Archives/Public/public-swbp-wg/2005Dec/0016.html
http://lists.w3.org/Archives/Public/public-swbp-wg/2006Feb/0076
http://dowhatimean.net/2006/11/content-negotiation-with-hash-uris-long#comment-15928

It would be a good idea to answer those questions directly in the document,
either at the top or in an Appendix.</description>
<state>0</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20070915142535.GA680@Octavius</uri>
<subject>[ALL] Agenda - Sep 18 2007 SWD telecon - 1500 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-09-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070915150038.GG2612@Octavius</uri>
<subject>[RECIPES] Amsterdam topic 'Recipes'</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-09-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/bd1d3fc00709180239m41ab82d3v39701872d80381b9@mail.gmail.com</uri>
<subject>Re: [ALL] Agenda - Sep 18 2007 SWD telecon - 1500 UTC</subject>
<sender>qreul@csd.abdn.ac.uk</sender>
<date>2007-09-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/46EF9DF6.9050006@few.vu.nl</uri>
<subject>Re: [ALL] Agenda - Sep 18 2007 SWD telecon - 1500 UTC</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-09-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/1205246076.4829.11.camel@duncan.fundacionctic.org</uri>
<subject>[Recipes] roadmap to the next draft</subject>
<sender>diego.berrueta@fundacionctic.org</sender>
<date>2008-03-11</date>
</email>
<email>
<uri>http://www.w3.org/mid/B0AAC07C-6A27-421A-8E62-523A40EC6D0A@madcreek.com</uri>
<subject>Re: [Recipes] roadmap to the next draft</subject>
<sender>jphipps@madcreek.com</sender>
<date>2008-03-11</date>
</email>
</emails>
</issue>
<issue>
<id>25</id>
<title>Default Datatype (rdf:XMLLiteral)</title>
<product>2</product>
<raisedby>14</raisedby>
<created>2007-02-16</created>
<description>As of [1] we need to decide how to handle the default datatype in RDFa.
See [2] for a comprehensive list of possible solutions, put together by Mark.


[1] http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2007Feb/0055.html
[2] http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2007Feb/0003.html</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/46771B06.6000009@adida.net</uri>
<subject>ISSUE-25: default datatype for literals</subject>
<sender>ben@adida.net</sender>
<date>2007-06-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/cf8107640706181733y19749746rc38164af7d8298c5@mail.gmail.com</uri>
<subject>Re: ISSUE-25: default datatype for literals</subject>
<sender>lindstream@gmail.com</sender>
<date>2007-06-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/46779633.4010400@w3.org</uri>
<subject>Re: ISSUE-25: default datatype for literals</subject>
<sender>ivan@w3.org</sender>
<date>2007-06-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/640dd5060706210250wbd15e85o508f307a97e4ef36@mail.gmail.com</uri>
<subject>Re: ISSUE-25: default datatype for literals</subject>
<sender>mark.birbeck@x-port.net</sender>
<date>2007-06-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/4681CDC7.3060105@adida.net</uri>
<subject>[RDFa] Proposed resolutions to ISSUE-2, ISSUE-5, ISSUE-25, ISSUE-29,  ISSUE-4</subject>
<sender>ben@adida.net</sender>
<date>2007-06-26</date>
</email>
<email>
<uri>http://www.w3.org/mid/52bd7c3d0706270714k8b045bdlbbc492a0f9ac2a81@mail.gmail.com</uri>
<subject>Re: ISSUE-25: default datatype for literals</subject>
<sender>simone.onofri@gmail.com</sender>
<date>2007-06-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/468915BC.4000300@cs.vu.nl</uri>
<subject>[ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-07-02</date>
</email>
<email>
<uri>http://www.w3.org/mid/46891656.1040500@sun.com</uri>
<subject>Re: [ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>Bernard.Horan@sun.com</sender>
<date>2007-07-02</date>
</email>
<email>
<uri>http://www.w3.org/mid/468938E7.3070002@cs.vu.nl</uri>
<subject>Re: [ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-07-02</date>
</email>
<email>
<uri>http://www.w3.org/mid/468A5D1A.2000005@sandsoft.com</uri>
<subject>Re: [ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2007-07-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/52bd7c3d0707030743j62fc4bd7h96f373f578043100@mail.gmail.com</uri>
<subject>Re: [ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>simone.onofri@gmail.com</sender>
<date>2007-07-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/468A2950020000D8000156B0@ntgwgate.loc.gov</uri>
<subject>Re: [ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>juth@loc.gov</sender>
<date>2007-07-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/468AF585.2010400@adida.net</uri>
<subject>[RDFa] RESOLUTIONS to ISSUE-2, ISSUE-5, ISSUE-25, ISSUE-29,  ISSUE-4</subject>
<sender>ben@adida.net</sender>
<date>2007-07-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D030E3E5D@exchange11.fed.cclrc.ac.uk</uri>
<subject>belated regrets (was RE: [ALL] agenda July 3 telecon 1500 UTC)</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-07-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/6.2.5.6.2.20070705110516.047e10c8@med.stanford.edu</uri>
<subject>Minutes from July 3 tcon</subject>
<sender>rubin@med.stanford.edu</sender>
<date>2007-07-05</date>
</email>
<email>
<uri>http://www.w3.org/mid/4706296E02000015003B7A00@ntgwgate.loc.gov</uri>
<subject>meeting record: 2007-10-02 swd telecon</subject>
<sender>edsu@loc.gov</sender>
<date>2007-10-05</date>
</email>
<email>
<uri>http://www.w3.org/mid/20071022140030.GA2188@Octavius</uri>
<subject>[ALL] Agenda - Oct 23 2007 SWD telecon - 1500 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-10-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/471E0DDD.3000407@sandsoft.com</uri>
<subject>Re: [ALL] Agenda - Oct 23 2007 SWD telecon - 1500 UTC</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2007-10-23</date>
</email>
<email>
<uri>http://www.w3.org/mid/52bd7c3d0710230811x4b8a09a8o86b415770d755f5d@mail.gmail.com</uri>
<subject>Re: [ALL] Agenda - Oct 23 2007 SWD telecon - 1500 UTC</subject>
<sender>simone.onofri@gmail.com</sender>
<date>2007-10-23</date>
</email>
<email>
<uri>http://www.w3.org/mid/471DE09A020000D80001FAC1@ntgwgate.loc.gov</uri>
<subject>Late Regrets - Re: [ALL] Agenda - Oct 23 2007 SWD telecon - 	1500 UTC</subject>
<sender>juth@loc.gov</sender>
<date>2007-10-23</date>
</email>
<email>
<uri>http://www.w3.org/mid/471E010B0200006A0001784F@ntgwgate.loc.gov</uri>
<subject>Meeting record: 2007-10-23 SWD telecon (Table of contents)</subject>
<sender>cred@loc.gov</sender>
<date>2007-10-23</date>
</email>
<email>
<uri>http://www.w3.org/mid/471E011D0200006A00017852@ntgwgate.loc.gov</uri>
<subject>Meeting record: 2007-10-23 SWD telecon (Minutes)</subject>
<sender>cred@loc.gov</sender>
<date>2007-10-23</date>
</email>
<email>
<uri>http://www.w3.org/mid/4725C25B.8010403@cs.vu.nl</uri>
<subject>[ALL] agenda 30 Oct telecon - 1500 UTC (1 hour earlier than usual  for Europeans)</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-10-29</date>
</email>
<email>
<uri>http://www.w3.org/mid/316ADBDBFE4F4D4AA4FEEF7496ECAEF91589A1@EVS1.ac.nuigalway.ie</uri>
<subject>RE: [ALL] agenda 30 Oct telecon - 1500 UTC (1 hour earlier than usual  for Europeans)</subject>
<sender>vit.novacek@deri.org</sender>
<date>2007-10-30</date>
</email>
<email>
<uri>http://www.w3.org/mid/52bd7c3d0710300648p3afa5e31me87e0a40a970a89b@mail.gmail.com</uri>
<subject>Re: [ALL] agenda 30 Oct telecon - 1500 UTC (1 hour earlier than usual for Europeans)</subject>
<sender>simone.onofri@gmail.com</sender>
<date>2007-10-30</date>
</email>
<email>
<uri>http://www.w3.org/mid/47275381.3020204@csd.abdn.ac.uk</uri>
<subject>Re: [ALL] agenda 30 Oct telecon - 1500 UTC (1 hour earlier than usual   for Europeans)</subject>
<sender>qreul@csd.abdn.ac.uk</sender>
<date>2007-10-30</date>
</email>
<email>
<uri>http://www.w3.org/mid/87ED80C0-1C85-4355-BBC6-54D5D567BF62@manchester.ac.uk</uri>
<subject>meeting record: 2007-10-30 SWDWG</subject>
<sender>sean.bechhofer@manchester.ac.uk</sender>
<date>2007-10-31</date>
</email>
<email>
<uri>http://www.w3.org/mid/20071105112919.GA4768@sub-tombaker</uri>
<subject>[ALL] Agenda 6 November telecon - 1600 UTC (1100 Boston)</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-11-05</date>
</email>
<email>
<uri>http://www.w3.org/mid/472F0728.5050404@csd.abdn.ac.uk</uri>
<subject>Re: [ALL] Agenda 6 November telecon - 1600 UTC (1100 Boston)</subject>
<sender>qreul@csd.abdn.ac.uk</sender>
<date>2007-11-05</date>
</email>
<email>
<uri>http://www.w3.org/mid/0894AAE4-1177-4DC1-AF22-9AAFDD769A13@madcreek.com</uri>
<subject>Re: [ALL] Agenda 6 November telecon - 1600 UTC (1100 Boston)</subject>
<sender>jphipps@madcreek.com</sender>
<date>2007-11-05</date>
</email>
<email>
<uri>http://www.w3.org/mid/472EDF9F020000D800020C6C@ntgwgate.loc.gov</uri>
<subject>Regrets - Re: [ALL] Agenda 6 November telecon - 1600 UTC (1100 	Boston)</subject>
<sender>juth@loc.gov</sender>
<date>2007-11-05</date>
</email>
<email>
<uri>http://www.w3.org/mid/472FEC05.1070800@sandsoft.com</uri>
<subject>Re: [ALL] Agenda 6 November telecon - 1600 UTC (1100 Boston)</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2007-11-05</date>
</email>
</emails>
<notes>
<note>
<date>2007-07-04</date>
<text>RESOLVED, as per:

http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2007Jun/0039</text>
</note>
</notes>
</issue>
<issue>
<id>26</id>
<title>RelationshipsBetweenLabels</title>
<product>3</product>
<raisedby>17</raisedby>
<created>2007-02-20</created>
<description>http://www.w3.org/2006/07/SWD/wiki/SkosDesign/RelationshipsBetweenLabels

SKOS allows to represent semantic relationships (broader, related) between
concepts. It also allows to represent relationships between concepts and labels
(prefLabel, altLabel). However, there is nothing proposed in SKOS to capture
links between labels themselves, a configuration which sometimes happens in
concept schemes.</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D0285A20B@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [SKOS] Proposed Resolution for ISSUE 26: RelationshipBetweenLabels</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-03-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D0285A26A@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [SKOS] Proposed Resolution for ISSUE 26: RelationshipBetweenLabels</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-03-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D0285A281@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [SKOS] Proposed Resolution for ISSUE 26: RelationshipBetweenLabels</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-03-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/5.1.0.14.2.20070320140023.032495d0@127.0.0.1</uri>
<subject>meeting record: 2007-03-20 SWD WG</subject>
<sender>swick@w3.org</sender>
<date>2007-03-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070326133118.GA3168@sub-tombaker</uri>
<subject>[ALL] Agenda - 2007-03-27 SWD telecon - 1500 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-03-26</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070327153559.GA1668@Octavius</uri>
<subject>[ALL] Report - 2007-03-27 SWD telecon - 1500 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-03-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/6.2.5.6.2.20070327084617.04d9b218@med.stanford.edu</uri>
<subject>Re: [ALL] Report - 2007-03-27 SWD telecon - 1500 UTC</subject>
<sender>rubin@med.stanford.edu</sender>
<date>2007-03-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D02A90C53@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [SKOS] Proposed Resolution for ISSUE 26: RelationshipBetweenLabels</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-03-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/460948EC.1040907@cs.vu.nl</uri>
<subject>Re: [SKOS] Proposed Resolution for ISSUE 26: RelationshipBetweenLabels</subject>
<sender>mark@cs.vu.nl</sender>
<date>2007-03-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/460CF9AA.6070707@few.vu.nl</uri>
<subject>Re: [SKOS] Proposed Resolution for ISSUE 26: RelationshipBetweenLabels</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-03-30</date>
</email>
<email>
<uri>http://www.w3.org/mid/460CFC03.1070208@cs.vu.nl</uri>
<subject>Re: [SKOS] Proposed Resolution for ISSUE 26: RelationshipBetweenLabels</subject>
<sender>mark@cs.vu.nl</sender>
<date>2007-03-30</date>
</email>
<email>
<uri>http://www.w3.org/mid/460FFDD1.6060400@few.vu.nl</uri>
<subject>[ALL] Regrets for April 3 telecon</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-04-01</date>
</email>
<email>
<uri>http://www.w3.org/mid/461048D2.8080309@cs.vu.nl</uri>
<subject>[ALL] Agenda SWD telecon 3 April 1500 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-04-02</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070416163135.GA2352@sub-tombaker</uri>
<subject>[ALL] Agenda SWD telecon 17 April 1500 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-04-16</date>
</email>
<email>
<uri>http://www.w3.org/mid/462C5283.8030405@cs.vu.nl</uri>
<subject>[ALL] agena 24 April telecon - 1500 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-04-23</date>
</email>
<email>
<uri>http://www.w3.org/mid/34b5049c0704230532w5540c183kdd075e0b46736af4@mail.gmail.com</uri>
<subject>Re: [ALL] agena 24 April telecon - 1500 UTC</subject>
<sender>jphipps@madcreek.com</sender>
<date>2007-04-23</date>
</email>
<email>
<uri>http://www.w3.org/mid/1177331961.5799.198.camel@localhost.localdomain</uri>
<subject>Re: [ALL] agena 24 April telecon - 1500 UTC</subject>
<sender>vit.novacek@deri.org</sender>
<date>2007-04-23</date>
</email>
<email>
<uri>http://www.w3.org/mid/462D9B71.9070100@sandsoft.com</uri>
<subject>Re: [ALL] agena 24 April telecon - 1500 UTC</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2007-04-23</date>
</email>
<email>
<uri>http://www.w3.org/mid/1177485639.4867.9.camel@duncan.fundacionctic.org</uri>
<subject>Meeting record: 2007-04-24 SWD telecon</subject>
<sender>diego.berrueta@fundacionctic.org</sender>
<date>2007-04-25</date>
</email>
<email>
<uri>http://www.w3.org/mid/462F6D2D.8000500@cs.vu.nl</uri>
<subject>May 1 telecon CANCELLED [Re: Meeting record: 2007-04-24 SWD telecon]</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-04-25</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070507163058.GA2552@Octavius</uri>
<subject>Agenda - 2007-05-08 SWD telecon - 1500 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-05-07</date>
</email>
<email>
<uri>http://www.w3.org/mid/464088DA.1040206@few.vu.nl</uri>
<subject>Re: Agenda - 2007-05-08 SWD telecon - 1500 UTC</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-05-08</date>
</email>
<email>
<uri>http://www.w3.org/mid/46481A20.3080008@few.vu.nl</uri>
<subject>[SKOS] Links for discussing issue-26 RelationshipsBetweenLabels</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-05-14</date>
</email>
<email>
<uri>http://www.w3.org/mid/46482D85.5000909@cs.vu.nl</uri>
<subject>[ALL] agenda 15 May telecon - 1500 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-05-14</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070514125805.GA3000@Octavius</uri>
<subject>[ALL] SWD minutes 2007-05-08</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-05-14</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070521155830.GA2228@Octavius</uri>
<subject>[ALL] Agenda - 2007-05-22 SWD telecon - 1500 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-05-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/46554A32.5040905@sun.com</uri>
<subject>meeting record: 2006-05-22 SWD telecon</subject>
<sender>Bernard.Horan@sun.com</sender>
<date>2007-05-24</date>
</email>
<email>
<uri>http://www.w3.org/mid/465B038B.4020900@cs.vu.nl</uri>
<subject>[ALL] agenda 29 May teleon 1500 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-05-28</date>
</email>
<email>
<uri>http://www.w3.org/mid/465C29E7.2030707@cs.vu.nl</uri>
<subject>ISSUE-26: SimpleExtension proposal</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-05-29</date>
</email>
<email>
<uri>http://www.w3.org/mid/6.2.5.6.2.20070529073905.0477aa78@med.stanford.edu</uri>
<subject>Re: ISSUE-26: SimpleExtension proposal</subject>
<sender>rubin@med.stanford.edu</sender>
<date>2007-05-29</date>
</email>
<email>
<uri>http://www.w3.org/mid/465C5F50.2000203@few.vu.nl</uri>
<subject>Re: ISSUE-26: SimpleExtension proposal</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-05-29</date>
</email>
<email>
<uri>http://www.w3.org/mid/465C65D8.3040804@few.vu.nl</uri>
<subject>Re: ISSUE-26: SimpleExtension proposal</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-05-29</date>
</email>
<email>
<uri>http://www.w3.org/mid/6.2.5.6.2.20070529150048.04778d18@med.stanford.edu</uri>
<subject>Re: ISSUE-26: SimpleExtension proposal</subject>
<sender>rubin@med.stanford.edu</sender>
<date>2007-05-29</date>
</email>
<email>
<uri>http://www.w3.org/mid/465D2CC8.3080504@few.vu.nl</uri>
<subject>Re: ISSUE-26: SimpleExtension proposal</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-05-30</date>
</email>
<email>
<uri>http://www.w3.org/mid/6.2.5.6.2.20070530052311.0479cb50@med.stanford.edu</uri>
<subject>Re: ISSUE-26: SimpleExtension proposal</subject>
<sender>rubin@med.stanford.edu</sender>
<date>2007-05-30</date>
</email>
<email>
<uri>http://www.w3.org/mid/465D7BF0.2090800@few.vu.nl</uri>
<subject>Re: ISSUE-26: SimpleExtension proposal</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-05-30</date>
</email>
<email>
<uri>http://www.w3.org/mid/6.2.5.6.2.20070531093140.02d3b2e8@med.stanford.edu</uri>
<subject>Re: ISSUE-26: SimpleExtension proposal</subject>
<sender>rubin@med.stanford.edu</sender>
<date>2007-05-31</date>
</email>
<email>
<uri>http://www.w3.org/mid/465F067D.9020008@few.vu.nl</uri>
<subject>[SKOS] chatting on SKOS concepts and ontology classes (was Re: ISSUE-26:  SimpleExtension proposal)</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-05-31</date>
</email>
<email>
<uri>http://www.w3.org/mid/6.2.5.6.2.20070531154103.02d76430@med.stanford.edu</uri>
<subject>Re: [SKOS] chatting on SKOS concepts and ontology classes (was   Re: ISSUE-26: SimpleExtension proposal)</subject>
<sender>rubin@med.stanford.edu</sender>
<date>2007-05-31</date>
</email>
<email>
<uri>http://www.w3.org/mid/34b5049c0706010800g36001a5fm13af12993a9e4d2f@mail.gmail.com</uri>
<subject>meeting record: 2007-05-29 SWDWG [SKOS] telecon</subject>
<sender>jphipps@madcreek.com</sender>
<date>2007-06-01</date>
</email>
<email>
<uri>http://www.w3.org/mid/4665C812.6010407@few.vu.nl</uri>
<subject>[SKOS] ISSUE-26: SimpleExtension proposal [Wiki form]</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-06-05</date>
</email>
<email>
<uri>http://www.w3.org/mid/46691507.8020504@few.vu.nl</uri>
<subject>Re: [SKOS] chatting on SKOS concepts and ontology classes (was     Re: ISSUE-26: SimpleExtension proposal)</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-06-08</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070608101425.GA2436@Octavius</uri>
<subject>Re: [SKOS] chatting on SKOS concepts and ontology classes (was     Re: ISSUE-26: SimpleExtension proposal)</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-06-08</date>
</email>
<email>
<uri>http://www.w3.org/mid/6.2.5.6.2.20070608030612.04796b58@med.stanford.edu</uri>
<subject>Re: [SKOS] chatting on SKOS concepts and ontology classes (was       Re: ISSUE-26: SimpleExtension proposal)</subject>
<sender>rubin@med.stanford.edu</sender>
<date>2007-06-08</date>
</email>
<email>
<uri>http://www.w3.org/mid/466940CA.40001@few.vu.nl</uri>
<subject>Re: [SKOS] chatting on SKOS concepts and ontology classes (was      Re: ISSUE-26: SimpleExtension proposal)</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-06-08</date>
</email>
<email>
<uri>http://www.w3.org/mid/466DA35A.30008@few.vu.nl</uri>
<subject>Re: [SKOS] chatting on SKOS concepts and ontology classes (was        Re: ISSUE-26: SimpleExtension proposal)</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-06-11</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D02EC079D@exchange11.fed.cclrc.ac.uk</uri>
<subject>[SKOS] ISSUE-26: 'Minimal Label Relation' Proposal</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-06-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/46728D56.9070609@few.vu.nl</uri>
<subject>Re: [SKOS] ISSUE-26: 'Minimal Label Relation' Proposal</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-06-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D02EC07E5@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [SKOS] ISSUE-26: 'Minimal Label Relation' Proposal</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-06-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/46729DEE.2070903@few.vu.nl</uri>
<subject>Re: [SKOS] ISSUE-26: 'Minimal Label Relation' Proposal</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-06-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB669029DAB37@hqgiex01.fao.org</uri>
<subject>RE: [SKOS] ISSUE-26: 'Minimal Label Relation' Proposal</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2007-06-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/467E897D.1030507@few.vu.nl</uri>
<subject>Re: [SKOS] ISSUE-26: 'Minimal Label Relation' Proposal</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-06-24</date>
</email>
<email>
<uri>http://www.w3.org/mid/46817A22.8030503@few.vu.nl</uri>
<subject>Re: [SKOS] ISSUE-31 BasicLexicalLabelSemantics proposed resolution</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-06-26</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070709172306.GA428@Octavius</uri>
<subject>[ALL] Agenda - July 10 2007 SWD telecon - 1500 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-07-09</date>
</email>
<email>
<uri>http://www.w3.org/mid/469272F6.7030501@sandsoft.com</uri>
<subject>Re: [ALL] Agenda - July 10 2007 SWD telecon - 1500 UTC</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2007-07-09</date>
</email>
<email>
<uri>http://www.w3.org/mid/46924D6B0200006A0000E91B@ntgwgate.loc.gov</uri>
<subject>Re: [ALL] Agenda - July 10 2007 SWD telecon - 1500 UTC</subject>
<sender>cred@loc.gov</sender>
<date>2007-07-09</date>
</email>
<email>
<uri>http://www.w3.org/mid/4694CB5E.5050909@sun.com</uri>
<subject>Meeting Record: 2007-07-10 SWD Telecon</subject>
<sender>Bernard.Horan@sun.com</sender>
<date>2007-07-11</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070716145919.GA2176@Octavius</uri>
<subject>[ALL] SWD telecon - July 17 2007 - agenda</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-07-16</date>
</email>
<email>
<uri>http://www.w3.org/mid/469CD99E0200006A0000F440@ntgwgate.loc.gov</uri>
<subject>meeting record: 2007-07-17 SWD telecon</subject>
<sender>cred@loc.gov</sender>
<date>2007-07-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/46A4CE46.7060200@cs.vu.nl</uri>
<subject>[ALL] agenda July 24 telecon - 1500 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-07-23</date>
</email>
<email>
<uri>http://www.w3.org/mid/46A4CE78.9080208@adida.net</uri>
<subject>Re: [ALL] agenda July 24 telecon - 1500 UTC</subject>
<sender>ben@adida.net</sender>
<date>2007-07-23</date>
</email>
<email>
<uri>http://www.w3.org/mid/46A496E7020000D8000170B3@ntgwgate.loc.gov</uri>
<subject>Regrets - Re: [ALL] agenda July 24 telecon - 1500 UTC</subject>
<sender>juth@loc.gov</sender>
<date>2007-07-23</date>
</email>
<email>
<uri>http://www.w3.org/mid/46A6E13502000015003B23AB@ntgwgate.loc.gov</uri>
<subject>meeting record: 2007-07-24 telecon</subject>
<sender>edsu@loc.gov</sender>
<date>2007-07-25</date>
</email>
<email>
<uri>http://www.w3.org/mid/46B7B1FB.7060402@cs.vu.nl</uri>
<subject>[ALL] agenda Aug 7 telecon - 1500 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-08-07</date>
</email>
<email>
<uri>http://www.w3.org/mid/6.2.5.6.2.20070806171917.0487fc18@med.stanford.edu</uri>
<subject>regrets for Aug 7 telecon - 1500 UTC</subject>
<sender>rubin@med.stanford.edu</sender>
<date>2007-08-06</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070820154014.GA2580@Octavius</uri>
<subject>Agenda - Aug 21 2007 SWD telecon - 1500 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-08-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/46C9B8D8.7080903@sun.com</uri>
<subject>Re: Agenda - Aug 21 2007 SWD telecon - 1500 UTC</subject>
<sender>Bernard.Horan@sun.com</sender>
<date>2007-08-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/46CAABAF020000D800019C6F@ntgwgate.loc.gov</uri>
<subject>Scribing - Re: Agenda - Aug 21 2007 SWD telecon - 1500 UTC</subject>
<sender>juth@loc.gov</sender>
<date>2007-08-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070822065936.GA2376@Octavius</uri>
<subject>[ALL] SWD face-to-face - draft agenda</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-08-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D033D4F83@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [ALL] SWD face-to-face - draft agenda</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-08-24</date>
</email>
<email>
<uri>http://www.w3.org/mid/46D2BA37.4070903@cs.vu.nl</uri>
<subject>[ALL] agenda 28 Aug telecon - 1500 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-08-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/46D2E6F9.1070403@few.vu.nl</uri>
<subject>Re: [ALL] SWD face-to-face - draft agenda</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-08-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/46D3A9D6.6040106@sandsoft.com</uri>
<subject>Re: [ALL] agenda 28 Aug telecon - 1500 UTC</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2007-08-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/46D3ED2B.9030506@sun.com</uri>
<subject>Re: [ALL] agenda 28 Aug telecon - 1500 UTC</subject>
<sender>Bernard.Horan@sun.com</sender>
<date>2007-08-28</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070903114838.GA4028@sub-tombaker</uri>
<subject>Agenda - Sep 04 2007 SWD telecon - 1500 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-09-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/768DACDC356ED04EA1F1130F97D29852012A4DD5@RZJC2EX.jr1.local</uri>
<subject>Meeting record: 2007-09-04</subject>
<sender>michael.hausenblas@joanneum.at</sender>
<date>2007-09-05</date>
</email>
<email>
<uri>http://www.w3.org/mid/46DE9B93020000D80001B06C@ntgwgate.loc.gov</uri>
<subject>LATE REGRETS - Re: Meeting record: 2007-09-04</subject>
<sender>juth@loc.gov</sender>
<date>2007-09-05</date>
</email>
<email>
<uri>http://www.w3.org/mid/46E5D599.4050003@cs.vu.nl</uri>
<subject>[ALL] agenda 11 Sep telecon - 1500 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-09-11</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D01B7D35A@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [ALL] agenda 11 Sep telecon - 1500 UTC</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-09-11</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070915142535.GA680@Octavius</uri>
<subject>[ALL] Agenda - Sep 18 2007 SWD telecon - 1500 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-09-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070915142947.GA2612@Octavius</uri>
<subject>[SKOS] Amsterdam topic: 'Label relations'</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-09-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/bd1d3fc00709180239m41ab82d3v39701872d80381b9@mail.gmail.com</uri>
<subject>Re: [ALL] Agenda - Sep 18 2007 SWD telecon - 1500 UTC</subject>
<sender>qreul@csd.abdn.ac.uk</sender>
<date>2007-09-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/46EF9DF6.9050006@few.vu.nl</uri>
<subject>Re: [ALL] Agenda - Sep 18 2007 SWD telecon - 1500 UTC</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-09-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/46F7799E.6080801@cs.vu.nl</uri>
<subject>[ALL] agenda 25 Sep telecon - 1500 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-09-24</date>
</email>
<email>
<uri>http://www.w3.org/mid/768DACDC356ED04EA1F1130F97D29852012E5917@RZJC2EX.jr1.local</uri>
<subject>RE: [ALL] agenda 25 Sep telecon - 1500 UTC</subject>
<sender>michael.hausenblas@joanneum.at</sender>
<date>2007-09-24</date>
</email>
<email>
<uri>http://www.w3.org/mid/316ADBDBFE4F4D4AA4FEEF7496ECAEF9158948@EVS1.ac.nuigalway.ie</uri>
<subject>RE: [ALL] agenda 25 Sep telecon - 1500 UTC</subject>
<sender>vit.novacek@deri.org</sender>
<date>2007-09-24</date>
</email>
<email>
<uri>http://www.w3.org/mid/46F7D948.7080404@w3.org</uri>
<subject>Re: [ALL] agenda 25 Sep telecon - 1500 UTC</subject>
<sender>jphipps@madcreek.com</sender>
<date>2007-09-24</date>
</email>
<email>
<uri>http://www.w3.org/mid/46F939E0.1070703@csd.abdn.ac.uk</uri>
<subject>Meeting record: 2007-09-25</subject>
<sender>qreul@csd.abdn.ac.uk</sender>
<date>2007-09-25</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070925180109.GA2648@Octavius</uri>
<subject>[ALL] Report - 2007-09-25 SWD telecon - with Amsterdam schedule</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-09-25</date>
</email>
<email>
<uri>http://www.w3.org/mid/4761B47E.80302@few.vu.nl</uri>
<subject>Re: SKOS-XL (was RE: SKOS/ synonym provenance (ISSUE-27 AnnotationOnLabel))</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-12-13</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D03B3FAB6@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: SKOS-XL (was RE: SKOS/ synonym provenance (ISSUE-27 AnnotationOnLabel))</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-12-12</date>
</email>
<email>
<uri>http://www.w3.org/mid/47017183.2010400@cs.vu.nl</uri>
<subject>[ALL] agenda 2 Oct telecon  - 1500 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-10-02</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D0363B71F@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [SKOS] Amsterdam topic: 'Label relations'</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-10-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/4706296E02000015003B7A00@ntgwgate.loc.gov</uri>
<subject>meeting record: 2007-10-02 swd telecon</subject>
<sender>edsu@loc.gov</sender>
<date>2007-10-05</date>
</email>
<email>
<uri>http://www.w3.org/mid/20071022140030.GA2188@Octavius</uri>
<subject>[ALL] Agenda - Oct 23 2007 SWD telecon - 1500 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-10-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/471E0DDD.3000407@sandsoft.com</uri>
<subject>Re: [ALL] Agenda - Oct 23 2007 SWD telecon - 1500 UTC</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2007-10-23</date>
</email>
<email>
<uri>http://www.w3.org/mid/52bd7c3d0710230811x4b8a09a8o86b415770d755f5d@mail.gmail.com</uri>
<subject>Re: [ALL] Agenda - Oct 23 2007 SWD telecon - 1500 UTC</subject>
<sender>simone.onofri@gmail.com</sender>
<date>2007-10-23</date>
</email>
<email>
<uri>http://www.w3.org/mid/471DE09A020000D80001FAC1@ntgwgate.loc.gov</uri>
<subject>Late Regrets - Re: [ALL] Agenda - Oct 23 2007 SWD telecon - 	1500 UTC</subject>
<sender>juth@loc.gov</sender>
<date>2007-10-23</date>
</email>
<email>
<uri>http://www.w3.org/mid/471E010B0200006A0001784F@ntgwgate.loc.gov</uri>
<subject>Meeting record: 2007-10-23 SWD telecon (Table of contents)</subject>
<sender>cred@loc.gov</sender>
<date>2007-10-23</date>
</email>
<email>
<uri>http://www.w3.org/mid/471E011D0200006A00017852@ntgwgate.loc.gov</uri>
<subject>Meeting record: 2007-10-23 SWD telecon (Minutes)</subject>
<sender>cred@loc.gov</sender>
<date>2007-10-23</date>
</email>
<email>
<uri>http://www.w3.org/mid/f032cc060711210700u6cd6d8edmd7c80f0ab9a2a6cb@mail.gmail.com</uri>
<subject>Re: SKOS-XL (was RE: SKOS/ synonym provenance (ISSUE-27 AnnotationOnLabel))</subject>
<sender>ehs@pobox.com</sender>
<date>2007-11-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47474EE1.4040609@few.vu.nl</uri>
<subject>Re: SKOS-XL (was RE: SKOS/ synonym provenance (ISSUE-27 AnnotationOnLabel))</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-11-23</date>
</email>
<email>
<uri>http://www.w3.org/mid/4756ED09.5050907@few.vu.nl</uri>
<subject>Re: SKOS-XL (was RE: SKOS/ synonym provenance (ISSUE-27 AnnotationOnLabel))</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-12-05</date>
</email>
<email>
<uri>http://www.w3.org/mid/4799B34E.7040203@few.vu.nl</uri>
<subject>Re: RIF: Comments on SKOS Primer</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-25</date>
</email>
<email>
<uri>http://www.w3.org/mid/47A7836B.2050501@few.vu.nl</uri>
<subject>Re: RIF: Comments on SKOS Primer</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/47A8B04E.9010507@few.vu.nl</uri>
<subject>[SKOS] TR : ISSUE 47 MappingProvenanceInformation</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-05</date>
</email>
<email>
<uri>http://www.w3.org/mid/47A99FB2.30003@dcs.gla.ac.uk</uri>
<subject>Re: [SKOS] TR : ISSUE 47 MappingProvenanceInformation</subject>
<sender>agray@dcs.gla.ac.uk</sender>
<date>2008-02-06</date>
</email>
<email>
<uri>http://www.w3.org/mid/47B8B900.40700@few.vu.nl</uri>
<subject>[SKOS] Proposal ISSUE 47 MappingProvenanceInformation</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/47B96B20.4010007@dcs.gla.ac.uk</uri>
<subject>Re: [SKOS] Proposal ISSUE 47 MappingProvenanceInformation</subject>
<sender>agray@dcs.gla.ac.uk</sender>
<date>2008-02-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BB2384.10600@few.vu.nl</uri>
<subject>[SKOS] Closing ISSUE 47 MappingProvenanceInformation</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD72BB.1010906@zoo.ox.ac.uk</uri>
<subject>[Fwd: [SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD9D4A.2090301@zoo.ox.ac.uk</uri>
<subject>[SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47FB407D.8090909@few.vu.nl</uri>
<subject>[SKOS] About links between SKOS-XL and SKOS reference (ISSUE-26)</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-04-08</date>
</email>
</emails>
<notes>
<note>
<date>2008-05-07</date>
<text>RESOLUTION: to accept sections 3 (xl:Label), 4 (Preferred, Alternate, and Hidden
xl:Labels), 6 (Binary Relations Between Instances of xl:Label) of the 14 April
-XL proposal and the vocabulary defined there

RESOLUTION: Include XL sections 3, 4, 6 in SKOS Reference as OPTIONAL and NORMATIVE

RESOLUTION: Use http://www.w3.org/2008/05/skos-xl# as XL namespace URI

-- http://www.w3.org/2008/05/06-swd-minutes.html#item03</text>
</note>
</notes>
</issue>
<issue>
<id>27</id>
<title>AnnotationOnLabel</title>
<product>3</product>
<raisedby>5</raisedby>
<created>2007-02-27</created>
<description>Labels which are currently modeled as literals in SKOS, as well as possibly
other literals, are valid subjects of discourse when modeling concept schemes,
e.g. when recording the dates during which a particular label was in common use.
However, in RDF, only resources may be subjects of statements, and literals may
only be objects of statements. The question then arises, how are we to annotate
(i.e. relate, as subject) labels and other literals to other entities.

Requirement: http://www.w3.org/TR/2007/WD-skos-ucr-20070516/#R-AnnotationOnLabel

Related:
http://www.w3.org/2006/07/SWD/wiki/SkosDesign/AnnotationPatterns</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20070822065936.GA2376@Octavius</uri>
<subject>[ALL] SWD face-to-face - draft agenda</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-08-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D033D4F83@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [ALL] SWD face-to-face - draft agenda</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-08-24</date>
</email>
<email>
<uri>http://www.w3.org/mid/46D2E6F9.1070403@few.vu.nl</uri>
<subject>Re: [ALL] SWD face-to-face - draft agenda</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-08-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/4761B47E.80302@few.vu.nl</uri>
<subject>Re: SKOS-XL (was RE: SKOS/ synonym provenance (ISSUE-27 AnnotationOnLabel))</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-12-13</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D03B3FAB6@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: SKOS-XL (was RE: SKOS/ synonym provenance (ISSUE-27 AnnotationOnLabel))</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-12-12</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D03B3F1EA@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: SKOS/ synonym provenance (ISSUE-27 AnnotationOnLabel)</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-11-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/96F793DD-4B61-453F-853E-FD80CDD174E1@madcreek.com</uri>
<subject>Re: SKOS/ synonym provenance (ISSUE-27 AnnotationOnLabel)</subject>
<sender>jphipps@madcreek.com</sender>
<date>2007-11-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/4742E652.2060203@csd.abdn.ac.uk</uri>
<subject>Re: SKOS/ synonym provenance (ISSUE-27 AnnotationOnLabel)</subject>
<sender>qreul@csd.abdn.ac.uk</sender>
<date>2007-11-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D03B3F1F6@exchange11.fed.cclrc.ac.uk</uri>
<subject>SKOS-XL (was RE: SKOS/ synonym provenance (ISSUE-27 AnnotationOnLabel))</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-11-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D03B3F206@exchange11.fed.cclrc.ac.uk</uri>
<subject>[SKOS] top priorities</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-11-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/95EE1497-2121-4762-A22F-D1C2A194C6A8@gmail.com</uri>
<subject>Re: SKOS-XL (was RE: SKOS/ synonym provenance (ISSUE-27 AnnotationOnLabel))</subject>
<sender>alanruttenberg@gmail.com</sender>
<date>2007-11-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/6.2.5.6.2.20071121043427.0499da78@smi.stanford.edu</uri>
<subject>Re: SKOS-XL (was RE: SKOS/ synonym provenance (ISSUE-27   AnnotationOnLabel))</subject>
<sender>rubin@smi.stanford.edu</sender>
<date>2007-11-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/f032cc060711210700u6cd6d8edmd7c80f0ab9a2a6cb@mail.gmail.com</uri>
<subject>Re: SKOS-XL (was RE: SKOS/ synonym provenance (ISSUE-27 AnnotationOnLabel))</subject>
<sender>ehs@pobox.com</sender>
<date>2007-11-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47474EE1.4040609@few.vu.nl</uri>
<subject>Re: SKOS-XL (was RE: SKOS/ synonym provenance (ISSUE-27 AnnotationOnLabel))</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-11-23</date>
</email>
<email>
<uri>http://www.w3.org/mid/47475497.6050303@few.vu.nl</uri>
<subject>Re: SKOS-XL (was RE: SKOS/ synonym provenance (ISSUE-27 AnnotationOnLabel))</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-11-23</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D03B3F782@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: SKOS-XL (was RE: SKOS/ synonym provenance (ISSUE-27 AnnotationOnLabel))</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-12-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/4755721A.3020704@few.vu.nl</uri>
<subject>Re: SKOS-XL (was RE: SKOS/ synonym provenance (ISSUE-27 AnnotationOnLabel))</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-12-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D03B3F78E@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: SKOS-XL (was RE: SKOS/ synonym provenance (ISSUE-27 AnnotationOnLabel))</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-12-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/4756ED09.5050907@few.vu.nl</uri>
<subject>Re: SKOS-XL (was RE: SKOS/ synonym provenance (ISSUE-27 AnnotationOnLabel))</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-12-05</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD72BB.1010906@zoo.ox.ac.uk</uri>
<subject>[Fwd: [SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD9D4A.2090301@zoo.ox.ac.uk</uri>
<subject>[SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
</emails>
<notes>
<note>
<date>2008-05-07</date>
<text>RESOLUTION: to accept sections 3 (xl:Label), 4 (Preferred, Alternate, and Hidden
xl:Labels), 6 (Binary Relations Between Instances of xl:Label) of the 14 April
-XL proposal and the vocabulary defined there

RESOLUTION: Include XL sections 3, 4, 6 in SKOS Reference as OPTIONAL and NORMATIVE

RESOLUTION: Use http://www.w3.org/2008/05/skos-xl# as XL namespace URI

-- http://www.w3.org/2008/05/06-swd-minutes.html#item03</text>
</note>
</notes>
</issue>
<issue>
<id>28</id>
<title>How does one Follow One's Nose</title>
<product>2</product>
<raisedby>2</raisedby>
<created>2007-03-12</created>
<description>An important feature of Web Architecture is that each document instance allow
the user to "follow his nose" to find all the specifications that describe how
to interpret the document.

Dan Connolly asks

  "There doesn't seem to be anything in the 000001.htm
  test document that says "this is not just any HTML document;
  it's an HTML document with RDF data inside; any RDF triples
  you extract per the RDFa spec are indeed meant by the author."
  -- http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2006Aug/0002

and followed up with

  "xmlFunctions-34: XML Transformation and composability (e.g., XSLT,
  XInclude, Encryption)
  http://www.w3.org/2001/tag/issues.html?type=1#xmlFunctions-34"
  -- http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2006Dec/0011.html</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20070312133721.6CDCC47BA8@mojo.w3.org</uri>
<subject>ISSUE-28: How does one \\'Follow your nose\\' from an HTML+RDFa document to know the author intended to assert the specified triples</subject>
<sender>dean+cgi@w3.org</sender>
<date>2007-03-12</date>
</email>
<email>
<uri>http://www.w3.org/mid/46771CA9.9030105@adida.net</uri>
<subject>[RDFa] ISSUE-28: following your nose to the RDFa specification</subject>
<sender>ben@adida.net</sender>
<date>2007-06-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/467798AC.9020706@w3.org</uri>
<subject>Re: [RDFa] ISSUE-28: following your nose to the RDFa specification</subject>
<sender>ivan@w3.org</sender>
<date>2007-06-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/52bd7c3d0706190258h654266e1l277c42c058e0e36f@mail.gmail.com</uri>
<subject>Re: [RDFa] ISSUE-28: following your nose to the RDFa specification</subject>
<sender>simone.onofri@gmail.com</sender>
<date>2007-06-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/1182252772.6367.138.camel@pav</uri>
<subject>Re: [RDFa] ISSUE-28: following your nose to the RDFa specification</subject>
<sender>connolly@w3.org</sender>
<date>2007-06-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/640dd5060706210236g7daace40v1d972886280d5dfb@mail.gmail.com</uri>
<subject>Re: [RDFa] ISSUE-28: following your nose to the RDFa specification</subject>
<sender>mark.birbeck@x-port.net</sender>
<date>2007-06-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/640dd5060706210247wd755101v1f3c2caf3dfc8ca8@mail.gmail.com</uri>
<subject>Re: [RDFa] ISSUE-28: following your nose to the RDFa specification</subject>
<sender>mark.birbeck@x-port.net</sender>
<date>2007-06-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/467A4DAA.2030108@w3.org</uri>
<subject>Re: [RDFa] ISSUE-28: following your nose to the RDFa specification</subject>
<sender>ivan@w3.org</sender>
<date>2007-06-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/640dd5060706210321w34747df3hbf7b98e567e66626@mail.gmail.com</uri>
<subject>Re: [RDFa] ISSUE-28: following your nose to the RDFa specification</subject>
<sender>mark.birbeck@x-port.net</sender>
<date>2007-06-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/1182430618.6367.413.camel@pav</uri>
<subject>Re: [RDFa] ISSUE-28: following your nose to the RDFa specification</subject>
<sender>connolly@w3.org</sender>
<date>2007-06-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/467ACDAD.7060101@adida.net</uri>
<subject>Re: [RDFa] ISSUE-28: following your nose to the RDFa specification</subject>
<sender>ben@adida.net</sender>
<date>2007-06-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/5.1.0.14.2.20070626101621.0322ec88@127.0.0.1</uri>
<subject>request for profile URI for RDFa</subject>
<sender>swick@w3.org</sender>
<date>2007-06-26</date>
</email>
<email>
<uri>http://www.w3.org/mid/1183159204.7058.335.camel@pav</uri>
<subject>Re: [RDFa] ISSUE-28: following your nose to the RDFa specification</subject>
<sender>connolly@w3.org</sender>
<date>2007-06-29</date>
</email>
<email>
<uri>http://www.w3.org/mid/46859825.3000705@adida.net</uri>
<subject>Re: [RDFa] ISSUE-28: following your nose to the RDFa specification</subject>
<sender>ben@adida.net</sender>
<date>2007-06-29</date>
</email>
<email>
<uri>http://www.w3.org/mid/640dd5060706301249y7d054fdcqb3d2449cdc4c550f@mail.gmail.com</uri>
<subject>Re: [RDFa] ISSUE-28: following your nose to the RDFa specification</subject>
<sender>mark.birbeck@x-port.net</sender>
<date>2007-06-30</date>
</email>
<email>
<uri>http://www.w3.org/mid/46882AA9.2030208@adida.net</uri>
<subject>Re: [RDFa] ISSUE-28: following your nose to the RDFa specification</subject>
<sender>ben@adida.net</sender>
<date>2007-07-01</date>
</email>
<email>
<uri>http://www.w3.org/mid/op.tuwdplkhzdej1c@keith-alexanders-computer.local</uri>
<subject>Re: [RDFa] ISSUE-28: following your nose to the RDFa specification</subject>
<sender>k.j.w.alexander@gmail.com</sender>
<date>2007-07-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/468A8FFE.90308@adida.net</uri>
<subject>Re: [RDFa] ISSUE-28: following your nose to the RDFa specification</subject>
<sender>ben@adida.net</sender>
<date>2007-07-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/op.tu5u9zdi63ayaz@keith-alexanders-computer.local</uri>
<subject>Re: [RDFa] ISSUE-28: following your nose to the RDFa specification</subject>
<sender>k.j.w.alexander@gmail.com</sender>
<date>2007-07-08</date>
</email>
<email>
<uri>http://www.w3.org/mid/46941130.2060205@adida.net</uri>
<subject>Re: [RDFa] ISSUE-28: following your nose to the RDFa specification</subject>
<sender>ben@adida.net</sender>
<date>2007-07-10</date>
</email>
<email>
<uri>http://www.w3.org/mid/469411A0.9080704@adida.net</uri>
<subject>Re: [RDFa] ISSUE-28: following your nose to the RDFa specification</subject>
<sender>ben@adida.net</sender>
<date>2007-07-10</date>
</email>
<email>
<uri>http://www.w3.org/mid/469BFE92.3060207@adida.net</uri>
<subject>Re: [RDFa] ISSUE-28: following your nose to the RDFa specification</subject>
<sender>ben@adida.net</sender>
<date>2007-07-16</date>
</email>
</emails>
<notes>
<note>
<date>2007-04-15</date>
<text>approved as an OPEN issue on 2007-04-11 telecon.</text>
</note>
<note>
<date>2007-06-13</date>
<text>This issue includes the RDFa Profile discussion.

http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2007May/0015</text>
</note>
<note>
<date>2007-11-15</date>
<text>agreement from telecon that we have a profile, we encourage its use where possible, but we don't require 
it. This needs to be stated clearly in the syntax (it's not currently.)</text>
</note>
<note>
<date>2008-02-06</date>
<text>responded to comment at:
http://lists.w3.org/Archives/Public/public-swd-wg/2008Feb/0024.html</text>
</note>
</notes>
</issue>
<issue>
<id>64</id>
<title>TextualDescriptionsForConcepts</title>
<product>3</product>
<raisedby>8</raisedby>
<created>2007-11-20</created>
<description>SKOS currently has 7 "documentation"/"note" properties: skos:note,
skos:scopeNote, skos:defition, skos:historyNote, skos:editorialNote,
skos:changeNote, skos:example.

In the SKOS Core Guide
&lt;http://www.w3.org/TR/2005/WD-swbp-skos-core-guide-20051102&gt;, 3 different design
patterns are allowed for these properties -- "documentation as an RDF literal",
"documentation as a related resource description", and "documentation as a
document reference". 

Do we continue to allow these different design patterns? If we do, we have to
accept a complex range for these properties. Is that OK? How should we formally
specify that?

</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20071120131435.A1066BEF0@nelson.w3.org</uri>
<subject>ISSUE-64: TextualDescriptionsForConcepts</subject>
<sender>dean+cgi@w3.org</sender>
<date>2007-11-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D03B3F1EF@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: ISSUE-64: TextualDescriptionsForConcepts</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-11-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D03B3F206@exchange11.fed.cclrc.ac.uk</uri>
<subject>[SKOS] top priorities</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-11-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D03B3F228@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: ISSUE-64: TextualDescriptionsForConcepts</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-11-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/47B8B1FB.1030902@few.vu.nl</uri>
<subject>[SKOS] Issues Review [From Alistair]</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD72BB.1010906@zoo.ox.ac.uk</uri>
<subject>[Fwd: [SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD9D4A.2090301@zoo.ox.ac.uk</uri>
<subject>[SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080415154659.GA4980@octavius</uri>
<subject>[SKOS] Issue owners - preparation for Washington</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2008-04-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/480C7E67.9090901@few.vu.nl</uri>
<subject>Re: [SKOS] Issue owners - preparation for Washington</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-04-21</date>
</email>
</emails>
<notes>
<note>
<date>2008-05-13</date>
<text>RESOLUTION: SKOS will explicitly allow all 3 patterns for documentation
properties -- http://www.w3.org/2008/05/07-swd-minutes.html#item13</text>
</note>
</notes>
</issue>
<issue>
<id>29</id>
<title>What is the MIME type for an HTML+RDFa document?</title>
<product>2</product>
<raisedby>2</raisedby>
<created>2007-03-12</created>
<description>Dan Connolly writes:

  "Which MIME type does [a document containing RDFa] use?"
  -- http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2007Feb/0112.html</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20070312135200.97C15BDA8@w3c4.w3.org</uri>
<subject>ISSUE-29: What is the MIME type for an HTML+RDFa document?</subject>
<sender>dean+cgi@w3.org</sender>
<date>2007-03-12</date>
</email>
<email>
<uri>http://www.w3.org/mid/467721A7.4050006@adida.net</uri>
<subject>[RDFa] ISSUE-29: mime type of RDFa document</subject>
<sender>ben@adida.net</sender>
<date>2007-06-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/46772801.2080101@danbri.org</uri>
<subject>Re: [RDFa] ISSUE-29: mime type of RDFa document</subject>
<sender>danbri@danbri.org</sender>
<date>2007-06-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/46779835.9010705@w3.org</uri>
<subject>Re: [RDFa] ISSUE-29: mime type of RDFa document</subject>
<sender>ivan@w3.org</sender>
<date>2007-06-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/1182253039.6367.144.camel@pav</uri>
<subject>Re: [RDFa] ISSUE-29: mime type of RDFa document</subject>
<sender>connolly@w3.org</sender>
<date>2007-06-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/4677CD40.6030406@danbri.org</uri>
<subject>Re: [RDFa] ISSUE-29: mime type of RDFa document</subject>
<sender>danbri@danbri.org</sender>
<date>2007-06-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/4677CF7D.8070604@w3.org</uri>
<subject>Re: [RDFa] ISSUE-29: mime type of RDFa document</subject>
<sender>ivan@w3.org</sender>
<date>2007-06-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/4677E95A.5020408@aptest.com</uri>
<subject>Re: [RDFa] ISSUE-29: mime type of RDFa document</subject>
<sender>shane@aptest.com</sender>
<date>2007-06-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/640dd5060706191626p44b40e08kd8a17a8c74814e5e@mail.gmail.com</uri>
<subject>Re: [RDFa] ISSUE-29: mime type of RDFa document</subject>
<sender>mark.birbeck@x-port.net</sender>
<date>2007-06-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/640dd5060706210233q2ea40b27lb524b24b77ec0c86@mail.gmail.com</uri>
<subject>Re: [RDFa] ISSUE-29: mime type of RDFa document</subject>
<sender>mark.birbeck@x-port.net</sender>
<date>2007-06-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/4681CDC7.3060105@adida.net</uri>
<subject>[RDFa] Proposed resolutions to ISSUE-2, ISSUE-5, ISSUE-25, ISSUE-29,  ISSUE-4</subject>
<sender>ben@adida.net</sender>
<date>2007-06-26</date>
</email>
<email>
<uri>http://www.w3.org/mid/468915BC.4000300@cs.vu.nl</uri>
<subject>[ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-07-02</date>
</email>
<email>
<uri>http://www.w3.org/mid/46891656.1040500@sun.com</uri>
<subject>Re: [ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>Bernard.Horan@sun.com</sender>
<date>2007-07-02</date>
</email>
<email>
<uri>http://www.w3.org/mid/468938E7.3070002@cs.vu.nl</uri>
<subject>Re: [ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-07-02</date>
</email>
<email>
<uri>http://www.w3.org/mid/468A5D1A.2000005@sandsoft.com</uri>
<subject>Re: [ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2007-07-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/52bd7c3d0707030743j62fc4bd7h96f373f578043100@mail.gmail.com</uri>
<subject>Re: [ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>simone.onofri@gmail.com</sender>
<date>2007-07-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/468A2950020000D8000156B0@ntgwgate.loc.gov</uri>
<subject>Re: [ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>juth@loc.gov</sender>
<date>2007-07-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/468AF585.2010400@adida.net</uri>
<subject>[RDFa] RESOLUTIONS to ISSUE-2, ISSUE-5, ISSUE-25, ISSUE-29,  ISSUE-4</subject>
<sender>ben@adida.net</sender>
<date>2007-07-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D030E3E5D@exchange11.fed.cclrc.ac.uk</uri>
<subject>belated regrets (was RE: [ALL] agenda July 3 telecon 1500 UTC)</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-07-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/6.2.5.6.2.20070705110516.047e10c8@med.stanford.edu</uri>
<subject>Minutes from July 3 tcon</subject>
<sender>rubin@med.stanford.edu</sender>
<date>2007-07-05</date>
</email>
</emails>
<notes>
<note>
<date>2007-04-15</date>
<text>approved as an OPEN issue on 2007-04-11 telecon.</text>
</note>
<note>
<date>2007-07-04</date>
<text>RESOLVED as:

"the MIME type of an RDFa document is whatever the
MIME type of the host document is. In the case of XHTML1.1+RDFa,
application/xhtml+xml. If/when RDFa becomes a valid extension for other
versions of HTML, then it will take on whatever MIME type they accept."

</text>
</note>
</notes>
</issue>
<issue>
<id>30</id>
<title>Determine how and if RDDL relates to the Recipes</title>
<product>5</product>
<raisedby>8</raisedby>
<created>2007-03-13</created>
<description>http://lists.w3.org/Archives/Public/public-swd-wg/2006Dec/0086.html

Figuring out if and how the cookbook and RDDL [1] fit together is probably
something we should look at ... 

[1] http://en.wikipedia.org/wiki/RDDL

related:
http://norman.walsh.name/2006/12/18/rddl

Associating Resources with Namespaces
Draft TAG Finding 13 December 2005
http://www.w3.org/2001/tag/doc/nsDocuments/


</description>
<state>2</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20070313161227.2E83D47BA5@mojo.w3.org</uri>
<subject>ISSUE-30: Determine how and if RDDL relates to the Resipes</subject>
<sender>dean+cgi@w3.org</sender>
<date>2007-03-13</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D0285A1F3@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: ISSUE-30: Determine how and if RDDL relates to the Resipes</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-03-19</date>
</email>
</emails>
</issue>
<issue>
<id>31</id>
<title>BasicLexicalLabelSemantics</title>
<product>3</product>
<raisedby>8</raisedby>
<created>2007-03-19</created>
<description>Can a resource have two "preferred lexical labels"? Can a lexical label be both
"preferred" and "alternative" for the same resource? If a lexical label is
"hidden", can it also be "preferred" or "alternative" for the same resource?

See also &lt;http://www.w3.org/2006/07/SWD/wiki/SkosDesign/BasicLexicalLabelSemantics&gt;

Imagine the SKOS vocabulary consisted only of skos:prefLabel, skos:altLabel and
skos:hiddenLabel. I.e. forget everything else for the moment.

Now, consider the following RDF graph:

@prefix ex: &lt;http://www.example.com/examples#&gt;.
@prefix skos: &lt;http://www.w3.org/2004/02/skos/core#&gt;.

ex:foo skos:prefLabel "foo"@en.
ex:foo skos:prefLabel "bar"@en.

The resource ex:foo has two different preferred lexical labels in the same
language. Is this graph inconsistent?

What about the following:

@prefix ex: &lt;http://www.example.com/examples#&gt;.
@prefix skos: &lt;http://www.w3.org/2004/02/skos/core#&gt;.

ex:foo skos:prefLabel "foo"@en.
ex:foo skos:altLabel "foo"@en.

The label "foo"@en is given as both a preferred and an alternative lexical label
for the resource ex:foo. Is this graph inconsistent?

Consider another graph:

@prefix ex: &lt;http://www.example.com/examples#&gt;.
@prefix skos: &lt;http://www.w3.org/2004/02/skos/core#&gt;.

ex:foo skos:prefLabel "foo"@en.
ex:foo skos:hiddenLabel "foo"@en.

The label "foo"@en is given as both a preferred and a hidden lexical label for
the resource ex:foo. Is this graph inconsistent?

Finally, consider:

@prefix ex: &lt;http://www.example.com/examples#&gt;.
@prefix skos: &lt;http://www.w3.org/2004/02/skos/core#&gt;.

ex:foo skos:altLabel "foo"@en.
ex:foo skos:hiddenLabel "foo"@en.

The label "foo"@en is given as both an alternative and a hidden lexical label
for the resource ex:foo. Is this graph inconsistent?</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20070319131638.13D1133207@kearny.w3.org</uri>
<subject>ISSUE-31: BasicLexicalLabelSemantics</subject>
<sender>dean+cgi@w3.org</sender>
<date>2007-03-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D0285A1CB@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [SKOS] Possible issue: Uniqueness of skos:prefLabel [was Re:  [SKOS]  inconsistency between Guide and Specification</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-03-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D02EC0BF0@exchange11.fed.cclrc.ac.uk</uri>
<subject>[SKOS] central issues</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-06-26</date>
</email>
<email>
<uri>http://www.w3.org/mid/46814CEA.3000004@mondeca.com</uri>
<subject>Re: [SKOS] central issues</subject>
<sender>bernard.vatant@mondeca.com</sender>
<date>2007-06-26</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D02EC0BF3@exchange11.fed.cclrc.ac.uk</uri>
<subject>[SKOS] ISSUE-31 BasicLexicalLabelSemantics proposed resolution</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-06-26</date>
</email>
<email>
<uri>http://www.w3.org/mid/468175A4.6050104@few.vu.nl</uri>
<subject>[SKOS] question about SKOS semantics document (was Re: [SKOS] ISSUE-31  BasicLexicalLabelSemantics proposed resolution)</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-06-26</date>
</email>
<email>
<uri>http://www.w3.org/mid/46817A22.8030503@few.vu.nl</uri>
<subject>Re: [SKOS] ISSUE-31 BasicLexicalLabelSemantics proposed resolution</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-06-26</date>
</email>
<email>
<uri>http://www.w3.org/mid/46818CE0.8020106@mondeca.com</uri>
<subject>Re: [SKOS] ISSUE-31 BasicLexicalLabelSemantics proposed resolution</subject>
<sender>bernard.vatant@mondeca.com</sender>
<date>2007-06-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/46824F52.3010205@few.vu.nl</uri>
<subject>Re: [SKOS] central issues</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-06-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/46825EA9.8010408@mondeca.com</uri>
<subject>Re: [SKOS] central issues</subject>
<sender>bernard.vatant@mondeca.com</sender>
<date>2007-06-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/46891049.4070304@cs.vu.nl</uri>
<subject>Re: [SKOS] central issues</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-07-02</date>
</email>
<email>
<uri>http://www.w3.org/mid/468915BC.4000300@cs.vu.nl</uri>
<subject>[ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-07-02</date>
</email>
<email>
<uri>http://www.w3.org/mid/46891656.1040500@sun.com</uri>
<subject>Re: [ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>Bernard.Horan@sun.com</sender>
<date>2007-07-02</date>
</email>
<email>
<uri>http://www.w3.org/mid/46894F29.4010907@madcreek.com</uri>
<subject>Re: [SKOS] central issues</subject>
<sender>jphipps@madcreek.com</sender>
<date>2007-07-02</date>
</email>
<email>
<uri>http://www.w3.org/mid/4689FFFD.8080603@few.vu.nl</uri>
<subject>Re: [SKOS] central issues</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-07-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/468A58FC.2030303@madcreek.com</uri>
<subject>Re: [SKOS] central issues</subject>
<sender>jphipps@madcreek.com</sender>
<date>2007-07-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/468A5D1A.2000005@sandsoft.com</uri>
<subject>Re: [ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2007-07-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/52bd7c3d0707030743j62fc4bd7h96f373f578043100@mail.gmail.com</uri>
<subject>Re: [ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>simone.onofri@gmail.com</sender>
<date>2007-07-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/468A2950020000D8000156B0@ntgwgate.loc.gov</uri>
<subject>Re: [ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>juth@loc.gov</sender>
<date>2007-07-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/468AC9DE.8070503@cs.vu.nl</uri>
<subject>Re: [SKOS] central issues</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-07-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D030E3E5D@exchange11.fed.cclrc.ac.uk</uri>
<subject>belated regrets (was RE: [ALL] agenda July 3 telecon 1500 UTC)</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-07-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/6.2.5.6.2.20070705110516.047e10c8@med.stanford.edu</uri>
<subject>Minutes from July 3 tcon</subject>
<sender>rubin@med.stanford.edu</sender>
<date>2007-07-05</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070709172306.GA428@Octavius</uri>
<subject>[ALL] Agenda - July 10 2007 SWD telecon - 1500 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-07-09</date>
</email>
<email>
<uri>http://www.w3.org/mid/469272F6.7030501@sandsoft.com</uri>
<subject>Re: [ALL] Agenda - July 10 2007 SWD telecon - 1500 UTC</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2007-07-09</date>
</email>
<email>
<uri>http://www.w3.org/mid/46924D6B0200006A0000E91B@ntgwgate.loc.gov</uri>
<subject>Re: [ALL] Agenda - July 10 2007 SWD telecon - 1500 UTC</subject>
<sender>cred@loc.gov</sender>
<date>2007-07-09</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070716145919.GA2176@Octavius</uri>
<subject>[ALL] SWD telecon - July 17 2007 - agenda</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-07-16</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070716154620.GA2012@Octavius</uri>
<subject>Re: [ALL] SWD telecon - July 17 2007 - agenda</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-07-16</date>
</email>
<email>
<uri>http://www.w3.org/mid/46A4CE46.7060200@cs.vu.nl</uri>
<subject>[ALL] agenda July 24 telecon - 1500 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-07-23</date>
</email>
<email>
<uri>http://www.w3.org/mid/46A4CE78.9080208@adida.net</uri>
<subject>Re: [ALL] agenda July 24 telecon - 1500 UTC</subject>
<sender>ben@adida.net</sender>
<date>2007-07-23</date>
</email>
<email>
<uri>http://www.w3.org/mid/46A496E7020000D8000170B3@ntgwgate.loc.gov</uri>
<subject>Regrets - Re: [ALL] agenda July 24 telecon - 1500 UTC</subject>
<sender>juth@loc.gov</sender>
<date>2007-07-23</date>
</email>
<email>
<uri>http://www.w3.org/mid/46B7B1FB.7060402@cs.vu.nl</uri>
<subject>[ALL] agenda Aug 7 telecon - 1500 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-08-07</date>
</email>
<email>
<uri>http://www.w3.org/mid/6.2.5.6.2.20070806171917.0487fc18@med.stanford.edu</uri>
<subject>regrets for Aug 7 telecon - 1500 UTC</subject>
<sender>rubin@med.stanford.edu</sender>
<date>2007-08-06</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070820154014.GA2580@Octavius</uri>
<subject>Agenda - Aug 21 2007 SWD telecon - 1500 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-08-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/46C9B8D8.7080903@sun.com</uri>
<subject>Re: Agenda - Aug 21 2007 SWD telecon - 1500 UTC</subject>
<sender>Bernard.Horan@sun.com</sender>
<date>2007-08-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/46CAABAF020000D800019C6F@ntgwgate.loc.gov</uri>
<subject>Scribing - Re: Agenda - Aug 21 2007 SWD telecon - 1500 UTC</subject>
<sender>juth@loc.gov</sender>
<date>2007-08-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070822065936.GA2376@Octavius</uri>
<subject>[ALL] SWD face-to-face - draft agenda</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-08-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D033D4F83@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [ALL] SWD face-to-face - draft agenda</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-08-24</date>
</email>
<email>
<uri>http://www.w3.org/mid/46D2BA37.4070903@cs.vu.nl</uri>
<subject>[ALL] agenda 28 Aug telecon - 1500 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-08-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/46D2E6F9.1070403@few.vu.nl</uri>
<subject>Re: [ALL] SWD face-to-face - draft agenda</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-08-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/46D3A9D6.6040106@sandsoft.com</uri>
<subject>Re: [ALL] agenda 28 Aug telecon - 1500 UTC</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2007-08-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/46D3ED2B.9030506@sun.com</uri>
<subject>Re: [ALL] agenda 28 Aug telecon - 1500 UTC</subject>
<sender>Bernard.Horan@sun.com</sender>
<date>2007-08-28</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070903114838.GA4028@sub-tombaker</uri>
<subject>Agenda - Sep 04 2007 SWD telecon - 1500 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-09-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/768DACDC356ED04EA1F1130F97D29852012A4DD5@RZJC2EX.jr1.local</uri>
<subject>Meeting record: 2007-09-04</subject>
<sender>michael.hausenblas@joanneum.at</sender>
<date>2007-09-05</date>
</email>
<email>
<uri>http://www.w3.org/mid/46DE9B93020000D80001B06C@ntgwgate.loc.gov</uri>
<subject>LATE REGRETS - Re: Meeting record: 2007-09-04</subject>
<sender>juth@loc.gov</sender>
<date>2007-09-05</date>
</email>
<email>
<uri>http://www.w3.org/mid/46E5D599.4050003@cs.vu.nl</uri>
<subject>[ALL] agenda 11 Sep telecon - 1500 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-09-11</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D01B7D35A@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [ALL] agenda 11 Sep telecon - 1500 UTC</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-09-11</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D033D5CFF@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [SKOS] Amsterdam topic 'Labeling properties'</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-10-02</date>
</email>
<email>
<uri>http://www.w3.org/mid/47062449.2010801@csd.abdn.ac.uk</uri>
<subject>[SKOS] Amsterdam topic: 'Labeling properties'</subject>
<sender>qreul@csd.abdn.ac.uk</sender>
<date>2007-10-05</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D0499E457@exchange11.fed.cclrc.ac.uk</uri>
<subject>[SKOS] ISSUE-31 proposed resolution </subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2008-01-29</date>
</email>
<email>
<uri>http://www.w3.org/mid/2AD2401FC36E784094D0B3375FDA6CE802E5523F@VMAIL2.uoa.abdn.ac.uk</uri>
<subject>Meeting record: 2008-02-12 SWD telecon</subject>
<sender>q.reul@abdn.ac.uk</sender>
<date>2008-02-14</date>
</email>
</emails>
<notes>
<note>
<date>2007-03-19</date>
<text>Issues Sandbox:
http://www.w3.org/2006/07/SWD/wiki/SkosIssuesSandbox#head-5593998a47bf818e6bbcf40d289d95f6390c320a</text>
</note>
<note>
<date>2008-02-12</date>
<text>2008-02-12. RESOLVED ISSUE-31 is as per email
(http://lists.w3.org/Archives/Public/public-swd-wg/2008Jan/0191.html)</text>
</note>
</notes>
</issue>
<issue>
<id>32</id>
<title>ConceptSchemeLabellingInteractions</title>
<product>3</product>
<raisedby>17</raisedby>
<created>2007-03-19</created>
<description>Can two different concepts in the same concept scheme have any lexical labels in
common?

I.e. can two different concepts in the same concept scheme both have the same
preferred lexical label? Can two different concepts in the same concept scheme
both have the same alternative lexical label? Can a lexical label be preferred
for one concept and alternative for a different concept in the same concept
scheme? Can a lexical label be hidden for one concept and either preferred or
alternative for a different concept in the same concept scheme?

See also:
&lt;http://www.w3.org/2006/07/SWD/wiki/SkosDesign/ConceptSchemeLabellingInteractions&gt;

Imagine the SKOS vocabulary consists of only skos:prefLabel, skos:altLabel,
skos:hiddenLabel, skos:Concept, skos:ConcepScheme and skos:inScheme.

Now consider the following graph:

@prefix ex: &lt;http://www.example.com/examples#&gt;.
@prefix skos: &lt;http://www.w3.org/2004/02/skos/core#&gt;.

ex:fooscheme rdf:type skos:ConceptScheme.

ex:A rdf:type skos:Concept.
ex:A skos:prefLabel "orange"@en.
ex:A skos:scopeNote "The colour orange."@en.
ex:A skos:inScheme ex:fooscheme.

ex:B rdf:type skos:Concept.
ex:B skos:prefLabel "orange"@en.
ex:B skos:scopeNote "The citrus fruit."@en.
ex:B skos:inScheme ex:fooscheme.

This graph is not inherently inconsistent.

However, if we were to assume that ex:fooscheme was a thesaurus, and attempt to
generate a thesaurus from this graph, following the conventions and notation of
ISO 2788 and BS 8723, we would have a problem. The problem is that two concepts
in the ex:fooscheme concept scheme have the same preferred lexical label, and we
can't tell from the graph whether these two concepts are supposed to be
different or not.

If we assumed that ex:A and ex:B were different concepts, we could not generate
a thesaurus, because it is an axiom of thesaurus construction that each
preferred term in a thesaurus has one and only one meaning, i.e. there is a
one-to-one correspondance between preferred terms and concepts.

If we assumed that ex:A and ex:B were the same concept, we would get the
following thesaurus:

orange
  SN The colour orange.
  SN The citrus fruit.

... which obviously violates the original intention.

Consider a different example:

@prefix ex: &lt;http://www.example.com/examples#&gt;.
@prefix skos: &lt;http://www.w3.org/2004/02/skos/core#&gt;.

ex:fooscheme rdf:type skos:ConceptScheme.

ex:A rdf:type skos:Concept.
ex:A skos:prefLabel "orange (colour)"@en.
ex:A skos:altLabel "orange"@en.
ex:A skos:scopeNote "The colour orange."@en.
ex:A skos:inScheme ex:fooscheme.

ex:B rdf:type skos:Concept.
ex:B skos:prefLabel "orange"@en.
ex:B skos:scopeNote "The citrus fruit."@en.
ex:B skos:inScheme ex:fooscheme.

Again, this graph is not inherently inconsistent.

However, problems arise when trying to generate a thesaurus from this graph. In
this case it is simply not possible to generate the thesaurus under any
assumption, because the lexical label "orange"@en would be mapped to both a
preferred term and a non-preferred term. It is an axiom of thesaurus
construction that a term must be either preferred or non-preferred.

Consider a third example:

@prefix ex: &lt;http://www.example.com/examples#&gt;.
@prefix skos: &lt;http://www.w3.org/2004/02/skos/core#&gt;.

ex:fooscheme rdf:type skos:ConceptScheme.

ex:A rdf:type skos:Concept.
ex:A skos:prefLabel "orange (colour)"@en.
ex:A skos:altLabel "orange"@en.
ex:A skos:scopeNote "The colour orange."@en.
ex:A skos:inScheme ex:fooscheme.

ex:B rdf:type skos:Concept.
ex:B skos:prefLabel "orange (fruit)"@en.
ex:B skos:altLabel "orange"@en.
ex:B skos:scopeNote "The citrus fruit."@en.
ex:B skos:inScheme ex:fooscheme.

Again, this graph is not inherently inconsistent.

Again, however, problems arise when trying to generate a thesaurus from this
graph, which are summed up in SkosDesign/ThesaurusPatterns.

Summary

Thesauri are a major application of the SKOS vocabulary. However, to be usable
as a thesaurus, an RDF representation has to observe some syntactic constraints
on the usage of the SKOS vocabulary. These syntactic constraints should probably
be optional, because other types of vocabulary may not need them, but we still
have to say what they are.</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20070319142324.5EF5266367@dolph.w3.org</uri>
<subject>ISSUE-32: ConceptSchemeLabellingInteractions</subject>
<sender>dean+cgi@w3.org</sender>
<date>2007-03-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D0285A1CB@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [SKOS] Possible issue: Uniqueness of skos:prefLabel [was Re:  [SKOS]  inconsistency between Guide and Specification</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-03-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/46817A22.8030503@few.vu.nl</uri>
<subject>Re: [SKOS] ISSUE-31 BasicLexicalLabelSemantics proposed resolution</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-06-26</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070822065936.GA2376@Octavius</uri>
<subject>[ALL] SWD face-to-face - draft agenda</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-08-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D033D4F83@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [ALL] SWD face-to-face - draft agenda</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-08-24</date>
</email>
<email>
<uri>http://www.w3.org/mid/46D2E6F9.1070403@few.vu.nl</uri>
<subject>Re: [ALL] SWD face-to-face - draft agenda</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-08-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/479F6D3B.70606@few.vu.nl</uri>
<subject>[SKOS] ISSUE-32 ConceptSchemeLabellingInteractions</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-29</date>
</email>
<email>
<uri>http://www.w3.org/mid/5.1.0.14.2.20080205160438.05ea66e8@127.0.0.1</uri>
<subject>meeting record: 2008-02-05 SWD WG</subject>
<sender>swick@w3.org</sender>
<date>2008-02-05</date>
</email>
<email>
<uri>http://www.w3.org/mid/47AC1669.7050505@few.vu.nl</uri>
<subject>Re: [SKOS] ISSUE-32 ConceptSchemeLabellingInteractions</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-08</date>
</email>
<email>
<uri>http://www.w3.org/mid/6.2.5.6.2.20080208043655.04a23e70@med.stanford.edu</uri>
<subject>Re: [SKOS] ISSUE-32 ConceptSchemeLabellingInteractions</subject>
<sender>rubin@med.stanford.edu</sender>
<date>2008-02-08</date>
</email>
<email>
<uri>http://www.w3.org/mid/47AC4F97.2050700@few.vu.nl</uri>
<subject>Re: [SKOS] ISSUE-32 ConceptSchemeLabellingInteractions</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-08</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB669029DAEFD@hqgiex01.fao.org</uri>
<subject>RE: [SKOS] ISSUE-32 ConceptSchemeLabellingInteractions</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-02-08</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080208050548.rjmdkcx1c44s04s4@webmail.stanford.edu</uri>
<subject>RE: [SKOS] ISSUE-32 ConceptSchemeLabellingInteractions</subject>
<sender>rubin@med.stanford.edu</sender>
<date>2008-02-08</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB669029DAF08@hqgiex01.fao.org</uri>
<subject>RE: [SKOS] ISSUE-32 ConceptSchemeLabellingInteractions</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-02-10</date>
</email>
<email>
<uri>http://www.w3.org/mid/6.2.5.6.2.20080210074059.04cc9b98@med.stanford.edu</uri>
<subject>RE: [SKOS] ISSUE-32 ConceptSchemeLabellingInteractions</subject>
<sender>rubin@med.stanford.edu</sender>
<date>2008-02-10</date>
</email>
</emails>
<notes>
<note>
<date>2007-03-19</date>
<text>Issues Sandbox:
http://www.w3.org/2006/07/SWD/wiki/SkosIssuesSandbox#head-5593998a47bf818e6bbcf40d289d95f6390c320a
</text>
</note>
<note>
<date>2008-02-05</date>
<text>[rrs] RESOLVED 2008-02-05 to accept Antoine's proposal of 29-Jan
http://www.w3.org/2008/02/05-swd-minutes.html#item02</text>
</note>
</notes>
</issue>
<issue>
<id>33</id>
<title>GroupingInConceptHierarchies</title>
<product>3</product>
<raisedby>8</raisedby>
<created>2007-03-26</created>
<description>Thesaurus standards describe the use of "node labels" for convenient grouping
and display. Many thesauri use node labels in this way. Some thesauri use "guide
terms" for a similar purpose. In some social tagging systems, tags can be
grouped into "bundles".

The current vocabulary support in SKOS (called "Collections") for these kinds of
grouping construct is broken, in that it introduces a contradiction into the
SKOS specifications.

Requirement:
http://www.w3.org/TR/2007/WD-skos-ucr-20070516/#R-GroupingInConceptHierarchies

See further information at:

http://www.w3.org/2006/07/SWD/wiki/SkosDesign/GroupingConstructs</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20070326115742.7306EDAE4A@w3c4-bis.w3.org</uri>
<subject>ISSUE-33: GroupingConstructs</subject>
<sender>dean+cgi@w3.org</sender>
<date>2007-03-26</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D0285A5AD@exchange11.fed.cclrc.ac.uk</uri>
<subject>[SKOS] RE: ISSUE-33: GroupingConstructs</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-03-26</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D02A90C4C@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [SKOS] RE: ISSUE-33: GroupingConstructs</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-03-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/SEh2U0RkxUCGFAhr@mail.willpowerinfo.co.uk</uri>
<subject>Re: [SKOS] RE: ISSUE-33: GroupingConstructs</subject>
<sender>L.Will@willpowerinfo.co.uk</sender>
<date>2007-03-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D02CAB20D@exchange11.fed.cclrc.ac.uk</uri>
<subject>[SKOS] ISSUE-33 'Minimal Fix' Proposal</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-05-08</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D02CAB21E@exchange11.fed.cclrc.ac.uk</uri>
<subject>[SKOS] ISSUE-33 'Bundles' Proposal</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-05-08</date>
</email>
<email>
<uri>http://www.w3.org/mid/4649C935.3050404@cs.vu.nl</uri>
<subject>Re: [SKOS] ISSUE-33 'Bundles' Proposal</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-05-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/464C231E.60006@few.vu.nl</uri>
<subject>[SKOS] ISSUE-33 'Loosening domain and ranges' Proposal</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-05-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/46531A7F.10607@few.vu.nl</uri>
<subject>Re: [SKOS] ISSUE-33 'Minimal Fix' Proposal</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-05-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/46531B0E.4070900@few.vu.nl</uri>
<subject>Re: [SKOS] ISSUE-33 'Minimal Fix' Proposal</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-05-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/465C29E7.2030707@cs.vu.nl</uri>
<subject>ISSUE-26: SimpleExtension proposal</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-05-29</date>
</email>
<email>
<uri>http://www.w3.org/mid/6.2.5.6.2.20070529073905.0477aa78@med.stanford.edu</uri>
<subject>Re: ISSUE-26: SimpleExtension proposal</subject>
<sender>rubin@med.stanford.edu</sender>
<date>2007-05-29</date>
</email>
<email>
<uri>http://www.w3.org/mid/465C5F50.2000203@few.vu.nl</uri>
<subject>Re: ISSUE-26: SimpleExtension proposal</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-05-29</date>
</email>
<email>
<uri>http://www.w3.org/mid/465C65D8.3040804@few.vu.nl</uri>
<subject>Re: ISSUE-26: SimpleExtension proposal</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-05-29</date>
</email>
<email>
<uri>http://www.w3.org/mid/6.2.5.6.2.20070529150048.04778d18@med.stanford.edu</uri>
<subject>Re: ISSUE-26: SimpleExtension proposal</subject>
<sender>rubin@med.stanford.edu</sender>
<date>2007-05-29</date>
</email>
<email>
<uri>http://www.w3.org/mid/DC1481A1-51A7-4F6B-A644-A4B72BF9EA3F@manchester.ac.uk</uri>
<subject>Test Cases</subject>
<sender>sean.bechhofer@manchester.ac.uk</sender>
<date>2007-06-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D02EC07DE@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [SKOS] ISSUE-33 'Minimal Fix' Proposal</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-06-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/46729747.30109@few.vu.nl</uri>
<subject>Re: [SKOS] ISSUE-33 'Minimal Fix' Proposal</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-06-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D02EC07EA@exchange11.fed.cclrc.ac.uk</uri>
<subject>[SKOS] ISSUE-33 'SimpleExtension' proposal (was RE: [SKOS] 'Lexicalization' or 'term'?)</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-06-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D02EC07EB@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [SKOS] ISSUE-33 'Minimal Fix' Proposal</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-06-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/4672A1A7.8080806@few.vu.nl</uri>
<subject>Re: [SKOS] ISSUE-33 'Minimal Fix' Proposal</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-06-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/4672ACE7.3010600@few.vu.nl</uri>
<subject>Re: [SKOS] ISSUE-33 'SimpleExtension' proposal (was RE: [SKOS] 'Lexicalization'  or 'term'?)</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-06-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/4675130E.9070806@cs.vu.nl</uri>
<subject>Re: [SKOS] ISSUE-33 'SimpleExtension' proposal (was RE: [SKOS] 'Lexicalization'  or 'term'?)</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-06-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/467642BC.7090301@few.vu.nl</uri>
<subject>Re: [SKOS] ISSUE-33 'SimpleExtension' proposal (was RE: [SKOS] 'Lexicalization'   or 'term'?)</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-06-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D02EC0BF1@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [SKOS] ISSUE-33 'Minimal Fix' Proposal</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-06-26</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D02EC0BF2@exchange11.fed.cclrc.ac.uk</uri>
<subject>[SKOS] presentation information and thesaurus displays (views) (was RE: [SKOS] ISSUE-33 'Minimal Fix' Proposal)</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-06-26</date>
</email>
<email>
<uri>http://www.w3.org/mid/1E41AE9AC12EA549BE5BC51A08DD8DC1026DE975@OAEXCH5SERVER.oa.oclc.org</uri>
<subject>RE: [SKOS] presentation information and thesaurus displays (views) (was RE: [SKOS] ISSUE-33 'Minimal Fix' Proposal)</subject>
<sender>houghtoa@oclc.org</sender>
<date>2007-06-26</date>
</email>
<email>
<uri>http://www.w3.org/mid/46817F84.1020800@few.vu.nl</uri>
<subject>Re: [SKOS] ISSUE-33 'Minimal Fix' Proposal</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-06-26</date>
</email>
<email>
<uri>http://www.w3.org/mid/46820EF1.60603@few.vu.nl</uri>
<subject>Re: [SKOS] presentation information and thesaurus displays (views)  (was RE: [SKOS] ISSUE-33 'Minimal Fix' Proposal)</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-06-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/768DACDC356ED04EA1F1130F97D29852011C5874@RZJC2EX.jr1.local</uri>
<subject>Meeting record: 2007-06-26 SWD Telecon</subject>
<sender>michael.hausenblas@joanneum.at</sender>
<date>2007-06-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/000001c7ba26$5f45c500$0300000a@DELL</uri>
<subject>RE: [SKOS] presentation information and thesaurus displays (views) (was RE: [SKOS] ISSUE-33 'Minimal Fix' Proposal)</subject>
<sender>sdclarke@lukehouse.demon.co.uk</sender>
<date>2007-06-29</date>
</email>
<email>
<uri>http://www.w3.org/mid/468915BC.4000300@cs.vu.nl</uri>
<subject>[ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-07-02</date>
</email>
<email>
<uri>http://www.w3.org/mid/46891656.1040500@sun.com</uri>
<subject>Re: [ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>Bernard.Horan@sun.com</sender>
<date>2007-07-02</date>
</email>
<email>
<uri>http://www.w3.org/mid/468A5D1A.2000005@sandsoft.com</uri>
<subject>Re: [ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2007-07-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/52bd7c3d0707030743j62fc4bd7h96f373f578043100@mail.gmail.com</uri>
<subject>Re: [ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>simone.onofri@gmail.com</sender>
<date>2007-07-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/468A2950020000D8000156B0@ntgwgate.loc.gov</uri>
<subject>Re: [ALL] agenda July 3 telecon 1500 UTC</subject>
<sender>juth@loc.gov</sender>
<date>2007-07-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D030E3E5D@exchange11.fed.cclrc.ac.uk</uri>
<subject>belated regrets (was RE: [ALL] agenda July 3 telecon 1500 UTC)</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-07-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/6.2.5.6.2.20070705110516.047e10c8@med.stanford.edu</uri>
<subject>Minutes from July 3 tcon</subject>
<sender>rubin@med.stanford.edu</sender>
<date>2007-07-05</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070709172306.GA428@Octavius</uri>
<subject>[ALL] Agenda - July 10 2007 SWD telecon - 1500 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-07-09</date>
</email>
<email>
<uri>http://www.w3.org/mid/469272F6.7030501@sandsoft.com</uri>
<subject>Re: [ALL] Agenda - July 10 2007 SWD telecon - 1500 UTC</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2007-07-09</date>
</email>
<email>
<uri>http://www.w3.org/mid/46924D6B0200006A0000E91B@ntgwgate.loc.gov</uri>
<subject>Re: [ALL] Agenda - July 10 2007 SWD telecon - 1500 UTC</subject>
<sender>cred@loc.gov</sender>
<date>2007-07-09</date>
</email>
<email>
<uri>http://www.w3.org/mid/4694CB5E.5050909@sun.com</uri>
<subject>Meeting Record: 2007-07-10 SWD Telecon</subject>
<sender>Bernard.Horan@sun.com</sender>
<date>2007-07-11</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070716145919.GA2176@Octavius</uri>
<subject>[ALL] SWD telecon - July 17 2007 - agenda</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-07-16</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070716154620.GA2012@Octavius</uri>
<subject>Re: [ALL] SWD telecon - July 17 2007 - agenda</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-07-16</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080123095757.9498EC6DB6@barney.w3.org</uri>
<subject>ISSUE-84: ConstructionOfSystematicDisplaysFromGroupings</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-01-23</date>
</email>
<email>
<uri>http://www.w3.org/mid/47971152.5080107@few.vu.nl</uri>
<subject>Re: ISSUE-84: ConstructionOfSystematicDisplaysFromGroupings</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-23</date>
</email>
</emails>
<notes>
<note>
<date>2007-03-26</date>
<text>SKOS issues sandbox:
http://www.w3.org/2006/07/SWD/wiki/SkosIssuesSandbox#head-76037c2efdbe6b35874f4f6f69a6d4fe23c18703
http://www.w3.org/2006/07/SWD/wiki/SkosIssuesSandbox#head-599459b500012b323811e3c8d8a6baafc5cb41d7
</text>
</note>
<note>
<date>2007-07-17</date>
<text>RESOLVED with the design in
http://www.w3.org/2006/07/SWD/wiki/SKOS/Semantics/Grouping?action=recall&amp;rev=4
by consensus as detailed in the 07/17/2007 meeting minutes:
http://www.w3.org/2007/07/17-swd-irc#T15-35-16</text>
</note>
</notes>
</issue>
<issue>
<id>34</id>
<title>HREF attribute on elements other than A and LINK</title>
<product>2</product>
<raisedby>6</raisedby>
<created>2007-04-10</created>
<description>Should XHTML1.1+RDFa allow for HREF on elements other than A and LINK, where
XHTML1.1 does not? If so, should conforming agents make those elements clickable
links?

When considering XHTML2, the task force had the following discussion:
http://www.w3.org/2006/02/06-htmltf-minutes#item03

In a recent telecon, this was brought up, too:
http://www.w3.org/2007/04/02-rdfa-minutes.html#item03</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20070410195415.680A366364@dolph.w3.org</uri>
<subject>ISSUE-34: HREF attribute on elements other than A and LINK</subject>
<sender>dean+cgi@w3.org</sender>
<date>2007-04-10</date>
</email>
<email>
<uri>http://www.w3.org/mid/46927B15.3050806@adida.net</uri>
<subject>[RDFa] ISSUE-34: @href everywhere and non-information resources</subject>
<sender>ben@adida.net</sender>
<date>2007-07-09</date>
</email>
<email>
<uri>http://www.w3.org/mid/46970AEF.6050509@adida.net</uri>
<subject>[RDFa] ISSUE-34: partial resolution to @href everywhere</subject>
<sender>ben@adida.net</sender>
<date>2007-07-12</date>
</email>
<email>
<uri>http://www.w3.org/mid/46988337.7030403@w3.org</uri>
<subject>Re: [RDFa] ISSUE-34: partial resolution to @href everywhere</subject>
<sender>ivan@w3.org</sender>
<date>2007-07-14</date>
</email>
<email>
<uri>http://www.w3.org/mid/1184688743.4187.413.camel@pav</uri>
<subject>Re: [RDFa] ISSUE-8: RDF containers in RDFa</subject>
<sender>connolly@w3.org</sender>
<date>2007-07-17</date>
</email>
</emails>
<notes>
<note>
<date>2007-04-15</date>
<text>approved as an OPEN issue on 2007-04-11 telecon.</text>
</note>
<note>
<date>2007-06-13</date>
<text>This issue is intimately tied with, and thus should include, the discussion of
adding a @RESOURCE attribute that is like @HREF except not navigable, even in
XHTML2 and beyond.

http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2007May/0020.html</text>
</note>
<note>
<date>2007-07-23</date>
<text>@href and @resource appear on every element, and @resource overrides @href, as per:
http://www.w3.org/2007/07/19-rdfa-minutes.html
</text>
</note>
<note>
<date>2008-02-06</date>
<text>additional related resolution from 2008-01-24:

"@href/@resource complete hanging @rel's."

as per http://www.w3.org/2008/01/24-rdfa-minutes.html</text>
</note>
</notes>
</issue>
<issue>
<id>35</id>
<title>RulesAndConformance</title>
<product>3</product>
<raisedby>16</raisedby>
<created>2007-05-29</created>
<description>The SKOS Core Guide includes references to rules. If SKOS is to make use of
rules, this should be in terms of standards rather than particular
implementations. Definitions for conformance need to be identified. Should all
SKOS implementations implement rules?

Sean's initial email:
http://lists.w3.org/Archives/Public/public-swd-wg/2006Nov/0077.html</description>
<state>4</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20070529143030.D0BBC13AC6@seamus.w3.org</uri>
<subject>ISSUE-35: RulesAndConformance</subject>
<sender>dean+cgi@w3.org</sender>
<date>2007-05-29</date>
</email>
<email>
<uri>http://www.w3.org/mid/465C5B27.4040101@few.vu.nl</uri>
<subject>Re: ISSUE-35: RulesAndConformance</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-05-29</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070822065936.GA2376@Octavius</uri>
<subject>[ALL] SWD face-to-face - draft agenda</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-08-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D033D4F83@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [ALL] SWD face-to-face - draft agenda</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-08-24</date>
</email>
<email>
<uri>http://www.w3.org/mid/46D2E6F9.1070403@few.vu.nl</uri>
<subject>Re: [ALL] SWD face-to-face - draft agenda</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-08-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070915142535.GA680@Octavius</uri>
<subject>[ALL] Agenda - Sep 18 2007 SWD telecon - 1500 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-09-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/bd1d3fc00709180239m41ab82d3v39701872d80381b9@mail.gmail.com</uri>
<subject>Re: [ALL] Agenda - Sep 18 2007 SWD telecon - 1500 UTC</subject>
<sender>qreul@csd.abdn.ac.uk</sender>
<date>2007-09-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/46EF9DF6.9050006@few.vu.nl</uri>
<subject>Re: [ALL] Agenda - Sep 18 2007 SWD telecon - 1500 UTC</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-09-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/50317A43-A082-4BAA-9B9D-DCB8BF83711E@manchester.ac.uk</uri>
<subject>ISSUE-35: Proposed Resolution</subject>
<sender>sean.bechhofer@manchester.ac.uk</sender>
<date>2008-02-05</date>
</email>
<email>
<uri>http://www.w3.org/mid/5.1.0.14.2.20080205160438.05ea66e8@127.0.0.1</uri>
<subject>meeting record: 2008-02-05 SWD WG</subject>
<sender>swick@w3.org</sender>
<date>2008-02-05</date>
</email>
</emails>
<notes>
<note>
<date>2008-02-05</date>
<text>[rrs] POSTPONED per resolution of 2008-02-05
http://www.w3.org/2008/02/05-swd-minutes.html</text>
</note>
</notes>
</issue>
<issue>
<id>36</id>
<title>ConceptSchemeContainment</title>
<product>3</product>
<raisedby>16</raisedby>
<created>2007-05-29</created>
<description>SKOS defines a 'concept scheme' as: "a set of concepts, optionally including
statements about semantic relationships between those concepts."

SKOS relationships such as broader and narrower are represented as triples in
RDF. The fact that a particular broader/narrower relationship between two
concepts belongs to a concept scheme cannot then be represented without
resorting to reification.

A principled approach to representing this containment would be desirable.

Sean's initial email:
http://lists.w3.org/Archives/Public/public-swd-wg/2006Nov/0078.html

Requirement:
http://www.w3.org/TR/2007/WD-skos-ucr-20070516/#R-ConceptSchemeContainment</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20070529143428.3EDC93320C@kearny.w3.org</uri>
<subject>ISSUE-36: SemanticRelationshipContainment</subject>
<sender>dean+cgi@w3.org</sender>
<date>2007-05-29</date>
</email>
<email>
<uri>http://www.w3.org/mid/465C5B70.3010109@few.vu.nl</uri>
<subject>Re: ISSUE-36: SemanticRelationshipContainment</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-05-29</date>
</email>
<email>
<uri>http://www.w3.org/mid/46824F52.3010205@few.vu.nl</uri>
<subject>Re: [SKOS] central issues</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-06-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/46825EA9.8010408@mondeca.com</uri>
<subject>Re: [SKOS] central issues</subject>
<sender>bernard.vatant@mondeca.com</sender>
<date>2007-06-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/46826B5D.1080106@few.vu.nl</uri>
<subject>Re: [SKOS] central issues</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-06-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/468288C7.9040409@mondeca.com</uri>
<subject>Re: [SKOS] central issues</subject>
<sender>bernard.vatant@mondeca.com</sender>
<date>2007-06-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/46836268.8030503@few.vu.nl</uri>
<subject>[SKOS] About ISSUE-36, ISSUE-39, ISSUE-44, (was Re: [SKOS] central  issues)</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-06-28</date>
</email>
<email>
<uri>http://www.w3.org/mid/468A8D24.7060904@few.vu.nl</uri>
<subject>Re: [SKOS] on ISSUE-36, ISSUE-39, ISSUE-47 mapping and concept scheme  provenance and (was Re: [SKOS] central issues)</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-07-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/468ACEBB.5050006@cs.vu.nl</uri>
<subject>Re: [SKOS] on ISSUE-36</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-07-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/468B5303.8050204@few.vu.nl</uri>
<subject>Re: [SKOS] on ISSUE-36</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-07-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070822065936.GA2376@Octavius</uri>
<subject>[ALL] SWD face-to-face - draft agenda</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-08-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D033D4F83@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [ALL] SWD face-to-face - draft agenda</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-08-24</date>
</email>
<email>
<uri>http://www.w3.org/mid/46D2E6F9.1070403@few.vu.nl</uri>
<subject>Re: [ALL] SWD face-to-face - draft agenda</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-08-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/46F7799E.6080801@cs.vu.nl</uri>
<subject>[ALL] agenda 25 Sep telecon - 1500 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-09-24</date>
</email>
<email>
<uri>http://www.w3.org/mid/768DACDC356ED04EA1F1130F97D29852012E5917@RZJC2EX.jr1.local</uri>
<subject>RE: [ALL] agenda 25 Sep telecon - 1500 UTC</subject>
<sender>michael.hausenblas@joanneum.at</sender>
<date>2007-09-24</date>
</email>
<email>
<uri>http://www.w3.org/mid/316ADBDBFE4F4D4AA4FEEF7496ECAEF9158948@EVS1.ac.nuigalway.ie</uri>
<subject>RE: [ALL] agenda 25 Sep telecon - 1500 UTC</subject>
<sender>vit.novacek@deri.org</sender>
<date>2007-09-24</date>
</email>
<email>
<uri>http://www.w3.org/mid/46F7D948.7080404@w3.org</uri>
<subject>Re: [ALL] agenda 25 Sep telecon - 1500 UTC</subject>
<sender>jphipps@madcreek.com</sender>
<date>2007-09-24</date>
</email>
<email>
<uri>http://www.w3.org/mid/4784F7CC.2030502@few.vu.nl</uri>
<subject>[SKOS] About Closing ISSUE-36 ConceptSchemeContainment</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-09</date>
</email>
<email>
<uri>http://www.w3.org/mid/4783570E020000D8000266E9@ntgwgate.loc.gov</uri>
<subject>Regrets - Re: [ALL] agenda 8 Jan telecon 1600 UTC</subject>
<sender>juth@loc.gov</sender>
<date>2008-01-08</date>
</email>
<email>
<uri>http://www.w3.org/mid/47825367.10302@cs.vu.nl</uri>
<subject>[ALL] agenda 8 Jan telecon 1600 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2008-01-07</date>
</email>
<email>
<uri>http://www.w3.org/mid/477293E1.5060104@few.vu.nl</uri>
<subject>Re: TR : [ISSUE-36 related] Linking a ConceptScheme and a Concept  subclass  using OWL</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-12-26</date>
</email>
<email>
<uri>http://www.w3.org/mid/CAB44397-D95E-4696-B790-B22F63BB8A30@manchester.ac.uk</uri>
<subject>Meeting record: 2007-12-18 SWD telecon</subject>
<sender>sean.bechhofer@manchester.ac.uk</sender>
<date>2007-12-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/4767EDC5.7040000@sandsoft.com</uri>
<subject>Re: [ALL] Agenda - Dec 18 2007 SWD telecon - 1600 UTC</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2007-12-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/52bd7c3d0712180745x53d8c9d2o8087b56e66f13f79@mail.gmail.com</uri>
<subject>Re: [ALL] Agenda - Dec 18 2007 SWD telecon - 1600 UTC</subject>
<sender>simone.onofri@gmail.com</sender>
<date>2007-12-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/4767E4F3.1020305@deri.org</uri>
<subject>Re: [ALL] Agenda - Dec 18 2007 SWD telecon - 1600 UTC</subject>
<sender>vit.novacek@deri.org</sender>
<date>2007-12-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/20071218095958.GA3876@octavius</uri>
<subject>[ALL] Agenda - Dec 18 2007 SWD telecon - 1600 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-12-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/4761021E0200006A0001BF5B@ntgwgate.loc.gov</uri>
<subject>Minutes from 2007-12-11 telecon</subject>
<sender>cred@loc.gov</sender>
<date>2007-12-13</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB669029DADF1@hqgiex01.fao.org</uri>
<subject>RE: [SKOS] ISSUE-36 ConceptSchemeContainment,  skos:inScheme and rdfs:isDefinedBy</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2007-12-12</date>
</email>
<email>
<uri>http://www.w3.org/mid/475EDA83.5060100@few.vu.nl</uri>
<subject>[SKOS] ISSUE-36 ConceptSchemeContainment, skos:inScheme and rdfs:isDefinedBy</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-12-11</date>
</email>
<email>
<uri>http://www.w3.org/mid/47017183.2010400@cs.vu.nl</uri>
<subject>[ALL] agenda 2 Oct telecon  - 1500 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-10-02</date>
</email>
<email>
<uri>http://www.w3.org/mid/472762F5.8040709@few.vu.nl</uri>
<subject>[SKOS] inScheme and rdfs:isDefinedBy (cf. ISSUE-36 ConceptSchemeContainment)</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-10-30</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D0363C417@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [SKOS] inScheme and rdfs:isDefinedBy (cf. ISSUE-36 ConceptSchemeContainment)</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-11-06</date>
</email>
<email>
<uri>http://www.w3.org/mid/34b5049c0711080542y73bb5542w3f857576fabc04a7@mail.gmail.com</uri>
<subject>Re: [SKOS] inScheme and rdfs:isDefinedBy (cf. ISSUE-36 ConceptSchemeContainment)</subject>
<sender>jphipps@madcreek.com</sender>
<date>2007-11-08</date>
</email>
<email>
<uri>http://www.w3.org/mid/478BB65B.8080507@cs.vu.nl</uri>
<subject>[ALL] agenda 15 Jan telecon 1600 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2008-01-14</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB6690269F988@hqgiex01.fao.org</uri>
<subject>RE: [ALL] agenda 15 Jan telecon 1600 UTC</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-01-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/478CE1C7.8010400@sandsoft.com</uri>
<subject>Re: [ALL] agenda 15 Jan telecon 1600 UTC</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2008-01-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/478D1E24.50502@few.vu.nl</uri>
<subject>Re: [SKOS] About Closing ISSUE-36 ConceptSchemeContainment</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/478DB2D6.70308@fundacionctic.org</uri>
<subject>Meeting record: 2008-01-15 SWD telecon</subject>
<sender>diego.berrueta@fundacionctic.org</sender>
<date>2008-01-16</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D0499DF7F@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [SKOS] About Closing ISSUE-36 ConceptSchemeContainment</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2008-01-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/479243F6.3040108@few.vu.nl</uri>
<subject>Re: [SKOS] About Closing ISSUE-36 ConceptSchemeContainment</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080121175703.GA3684@octavius</uri>
<subject>[ALL] Agenda - Jan 22 2008 SWD telecon - 1600 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2008-01-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/479620AD.1020805@sandsoft.com</uri>
<subject>Re: [ALL] Agenda - Jan 22 2008 SWD telecon - 1600 UTC</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2008-01-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB66903408403@hqgiex01.fao.org</uri>
<subject>Several emails to reply to</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-02-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/47A7836B.2050501@few.vu.nl</uri>
<subject>Re: RIF: Comments on SKOS Primer</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/47A8B04E.9010507@few.vu.nl</uri>
<subject>[SKOS] TR : ISSUE 47 MappingProvenanceInformation</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-05</date>
</email>
<email>
<uri>http://www.w3.org/mid/47A99FB2.30003@dcs.gla.ac.uk</uri>
<subject>Re: [SKOS] TR : ISSUE 47 MappingProvenanceInformation</subject>
<sender>agray@dcs.gla.ac.uk</sender>
<date>2008-02-06</date>
</email>
<email>
<uri>http://www.w3.org/mid/47B8B900.40700@few.vu.nl</uri>
<subject>[SKOS] Proposal ISSUE 47 MappingProvenanceInformation</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/47B96B20.4010007@dcs.gla.ac.uk</uri>
<subject>Re: [SKOS] Proposal ISSUE 47 MappingProvenanceInformation</subject>
<sender>agray@dcs.gla.ac.uk</sender>
<date>2008-02-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BB2384.10600@few.vu.nl</uri>
<subject>[SKOS] Closing ISSUE 47 MappingProvenanceInformation</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/0F1C3BFC-85E4-49FC-BE79-4E43F0371E02@manchester.ac.uk</uri>
<subject>Re: [SKOS] Closing ISSUE-71 ParallelMappingVocabulary</subject>
<sender>sean.bechhofer@manchester.ac.uk</sender>
<date>2008-02-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BC05B9.70806@few.vu.nl</uri>
<subject>Re: [SKOS] Closing ISSUE-71 ParallelMappingVocabulary</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/68C22185DB90CA41A5ACBD8E834C5ECD0465B110@goofy.wpakb.kb.nl</uri>
<subject>[SKOS] Re: SKOS Concept schemes and OWL Ontologies (related to ISSUE-36)</subject>
<sender>Antoine.Isaac@KB.nl</sender>
<date>2008-03-07</date>
</email>
<email>
<uri>http://www.w3.org/mid/5DB9EA83-0017-4455-86B6-A77C0CBDAD5E@manchester.ac.uk</uri>
<subject>Re: [SKOS] Re: SKOS Concept schemes and OWL Ontologies (related to ISSUE-36)</subject>
<sender>simon.jupp@manchester.ac.uk</sender>
<date>2008-04-17</date>
</email>
</emails>
<notes>
<note>
<date>2007-06-16</date>
<text>Sean's initial mail on
http://lists.w3.org/Archives/Public/public-swd-wg/2006Nov/0077.html 

Corresponding requirement:
http://www.w3.org/TR/2007/WD-skos-ucr-20070516/#R-ConceptSchemeContainment</text>
</note>
<note>
<date>2008-01-22</date>
<text>2008-01-22 [rrs] Closed per Antoine's proposal in
http://lists.w3.org/Archives/Public/public-swd-wg/2008Jan/0093.html
(Alistair: with slightly different wording)
see http://www.w3.org/2008/01/22-swd-minutes.html#item01</text>
</note>
<note>
<date>2008-01-22</date>
<text>[rrs] closed, per http://www.w3.org/2008/01/22-swd-minutes.html#item01</text>
</note>
</notes>
</issue>
<issue>
<id>37</id>
<title>SkosSpecialization</title>
<product>3</product>
<raisedby>5</raisedby>
<created>2007-05-29</created>
<description>Local specialization of SKOS vocabulary: for particular situations, the designer
of a SKOS concept scheme should be able to introduce new model-level classes and
properties, and link them to existing SKOS constructs. Possible cases include
the creation of specific kinds of textual definitions or notes for concepts, or
the specification of new types of concepts.

How does a third party create and publish custom extensions to SKOS? What are
the design patterns, and what are best practices?

Requirement: http://www.w3.org/TR/2007/WD-skos-ucr-20070516/#R-SkosSpecialization</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20070529144012.A40686636B@dolph.w3.org</uri>
<subject>ISSUE-37: CustomExtensions</subject>
<sender>dean+cgi@w3.org</sender>
<date>2007-05-29</date>
</email>
<email>
<uri>http://www.w3.org/mid/465C52CE.3020005@few.vu.nl</uri>
<subject>Re: [SKOS] tracking SKOS issues</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-05-29</date>
</email>
<email>
<uri>http://www.w3.org/mid/46665CFA.2050703@few.vu.nl</uri>
<subject>Re: [SKOS] tracking SKOS issues - links to requirements</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-06-06</date>
</email>
<email>
<uri>http://www.w3.org/mid/466EC763.40106@few.vu.nl</uri>
<subject>Re: [SKOS] tracking SKOS issues - links to requirements and wording  issues</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-06-12</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070703161338.0366047BA3@mojo.w3.org</uri>
<subject>ISSUE-56: ReferenceSemanticRelationshipSpecializations</subject>
<sender>dean+cgi@w3.org</sender>
<date>2007-07-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070822065936.GA2376@Octavius</uri>
<subject>[ALL] SWD face-to-face - draft agenda</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-08-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D033D4F83@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [ALL] SWD face-to-face - draft agenda</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-08-24</date>
</email>
<email>
<uri>http://www.w3.org/mid/46D2E6F9.1070403@few.vu.nl</uri>
<subject>Re: [ALL] SWD face-to-face - draft agenda</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-08-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/47B8B1FB.1030902@few.vu.nl</uri>
<subject>[SKOS] Issues Review [From Alistair]</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD72BB.1010906@zoo.ox.ac.uk</uri>
<subject>[Fwd: [SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD9D4A.2090301@zoo.ox.ac.uk</uri>
<subject>[SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/f032cc060803011003j16953aei9318c574bc410f2b@mail.gmail.com</uri>
<subject>Meeting Record: 2008-02-27 SWD telecon</subject>
<sender>ehs@pobox.com</sender>
<date>2008-03-01</date>
</email>
<email>
<uri>http://www.w3.org/mid/47E11ECC0200006A00024B85@ntgwgate.loc.gov</uri>
<subject>Minutes from 2008-03-18 telecon</subject>
<sender>cred@loc.gov</sender>
<date>2008-03-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080415154659.GA4980@octavius</uri>
<subject>[SKOS] Issue owners - preparation for Washington</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2008-04-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/480C7E67.9090901@few.vu.nl</uri>
<subject>Re: [SKOS] Issue owners - preparation for Washington</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-04-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB66903B87AC7@hqgiex01.fao.org</uri>
<subject>List of resolutions from the Face-to-Face meeting</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-05-13</date>
</email>
<email>
<uri>http://www.w3.org/mid/482ADFEC.9070001@cs.vu.nl</uri>
<subject>Re: List of resolutions from the Face-to-Face meeting</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2008-05-14</date>
</email>
</emails>
<notes>
<note>
<date>2008-05-07</date>
<text>RESOLVED: Section 4.8 of the SKOS Primer resolves ISSUE-37
-- http://www.w3.org/2008/05/07-swd-minutes.html#item08</text>
</note>
</notes>
</issue>
<issue>
<id>38</id>
<title>CompatibilityWithOWL-DL</title>
<product>3</product>
<raisedby>8</raisedby>
<created>2007-05-29</created>
<description>What are best practices for using the SKOS vocabulary within the constraints
required for OWL-DL compatibility?

Requirement:
http://www.w3.org/TR/2007/WD-skos-ucr-20070516/#R-CompatibilityWithOWL-DL</description>
<state>4</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20070529144909.D39BD3320C@kearny.w3.org</uri>
<subject>ISSUE-38: OWLDLCompatibility</subject>
<sender>dean+cgi@w3.org</sender>
<date>2007-05-29</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D02EC07DB@exchange11.fed.cclrc.ac.uk</uri>
<subject>[SKOS] basis for the SKOS semantics and ISSUE-38: OWLDLCompatibility</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-06-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D030E42C0@exchange11.fed.cclrc.ac.uk</uri>
<subject>[SKOS] ISSUE-38 CompatibilityWithOWL-DL - use of '[OWL-Full]' tag in SKOS/Semantics wiki draft</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-07-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/46A4CE46.7060200@cs.vu.nl</uri>
<subject>[ALL] agenda July 24 telecon - 1500 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-07-23</date>
</email>
<email>
<uri>http://www.w3.org/mid/46A4CE78.9080208@adida.net</uri>
<subject>Re: [ALL] agenda July 24 telecon - 1500 UTC</subject>
<sender>ben@adida.net</sender>
<date>2007-07-23</date>
</email>
<email>
<uri>http://www.w3.org/mid/46A496E7020000D8000170B3@ntgwgate.loc.gov</uri>
<subject>Regrets - Re: [ALL] agenda July 24 telecon - 1500 UTC</subject>
<sender>juth@loc.gov</sender>
<date>2007-07-23</date>
</email>
<email>
<uri>http://www.w3.org/mid/46A5EEBB.5000100@few.vu.nl</uri>
<subject>Re: [SKOS] ISSUE-38 CompatibilityWithOWL-DL - use of '[OWL-Full]'  tag in SKOS/Semantics wiki draft</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-07-24</date>
</email>
<email>
<uri>http://www.w3.org/mid/46A6E13502000015003B23AB@ntgwgate.loc.gov</uri>
<subject>meeting record: 2007-07-24 telecon</subject>
<sender>edsu@loc.gov</sender>
<date>2007-07-25</date>
</email>
<email>
<uri>http://www.w3.org/mid/46B7B1FB.7060402@cs.vu.nl</uri>
<subject>[ALL] agenda Aug 7 telecon - 1500 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-08-07</date>
</email>
<email>
<uri>http://www.w3.org/mid/6.2.5.6.2.20070806171917.0487fc18@med.stanford.edu</uri>
<subject>regrets for Aug 7 telecon - 1500 UTC</subject>
<sender>rubin@med.stanford.edu</sender>
<date>2007-08-06</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070820154014.GA2580@Octavius</uri>
<subject>Agenda - Aug 21 2007 SWD telecon - 1500 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-08-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/46C9B8D8.7080903@sun.com</uri>
<subject>Re: Agenda - Aug 21 2007 SWD telecon - 1500 UTC</subject>
<sender>Bernard.Horan@sun.com</sender>
<date>2007-08-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/46CAABAF020000D800019C6F@ntgwgate.loc.gov</uri>
<subject>Scribing - Re: Agenda - Aug 21 2007 SWD telecon - 1500 UTC</subject>
<sender>juth@loc.gov</sender>
<date>2007-08-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070822065936.GA2376@Octavius</uri>
<subject>[ALL] SWD face-to-face - draft agenda</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-08-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D033D4F83@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [ALL] SWD face-to-face - draft agenda</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-08-24</date>
</email>
<email>
<uri>http://www.w3.org/mid/46D2BA37.4070903@cs.vu.nl</uri>
<subject>[ALL] agenda 28 Aug telecon - 1500 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-08-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/46D2E6F9.1070403@few.vu.nl</uri>
<subject>Re: [ALL] SWD face-to-face - draft agenda</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-08-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/46D3A9D6.6040106@sandsoft.com</uri>
<subject>Re: [ALL] agenda 28 Aug telecon - 1500 UTC</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2007-08-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/46D3ED2B.9030506@sun.com</uri>
<subject>Re: [ALL] agenda 28 Aug telecon - 1500 UTC</subject>
<sender>Bernard.Horan@sun.com</sender>
<date>2007-08-28</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070903114838.GA4028@sub-tombaker</uri>
<subject>Agenda - Sep 04 2007 SWD telecon - 1500 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-09-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D033D525A@exchange11.fed.cclrc.ac.uk</uri>
<subject>[SKOS] moving development forward &amp; compatibility with OWL-DL (ISSUE-38)</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-09-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/46DD83D0.5050701@few.vu.nl</uri>
<subject>Re: [SKOS] moving development forward &amp; compatibility with OWL-DL  (ISSUE-38)</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-09-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070905114919.GA3500@sub-tombaker</uri>
<subject>[SKOS] Compatibility with OWL-DL - Issue-26</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-09-05</date>
</email>
<email>
<uri>http://www.w3.org/mid/768DACDC356ED04EA1F1130F97D29852012A4DD5@RZJC2EX.jr1.local</uri>
<subject>Meeting record: 2007-09-04</subject>
<sender>michael.hausenblas@joanneum.at</sender>
<date>2007-09-05</date>
</email>
<email>
<uri>http://www.w3.org/mid/46DE9B93020000D80001B06C@ntgwgate.loc.gov</uri>
<subject>LATE REGRETS - Re: Meeting record: 2007-09-04</subject>
<sender>juth@loc.gov</sender>
<date>2007-09-05</date>
</email>
<email>
<uri>http://www.w3.org/mid/46E4F20F.5020503@cs.vu.nl</uri>
<subject>Re: [SKOS] moving development forward &amp; compatibility with OWL-DL  (ISSUE-38)</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-09-10</date>
</email>
<email>
<uri>http://www.w3.org/mid/46E5D599.4050003@cs.vu.nl</uri>
<subject>[ALL] agenda 11 Sep telecon - 1500 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-09-11</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D01B7D35A@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [ALL] agenda 11 Sep telecon - 1500 UTC</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-09-11</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070915142535.GA680@Octavius</uri>
<subject>[ALL] Agenda - Sep 18 2007 SWD telecon - 1500 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-09-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/bd1d3fc00709180239m41ab82d3v39701872d80381b9@mail.gmail.com</uri>
<subject>Re: [ALL] Agenda - Sep 18 2007 SWD telecon - 1500 UTC</subject>
<sender>qreul@csd.abdn.ac.uk</sender>
<date>2007-09-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/46EF9DF6.9050006@few.vu.nl</uri>
<subject>Re: [ALL] Agenda - Sep 18 2007 SWD telecon - 1500 UTC</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-09-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/A6C0A826-154B-4466-91DC-3A2758362604@manchester.ac.uk</uri>
<subject>SKOS and imports</subject>
<sender>sean.bechhofer@manchester.ac.uk</sender>
<date>2008-04-16</date>
</email>
</emails>
</issue>
<issue>
<id>39</id>
<title>ConceptualMappingLinks</title>
<product>3</product>
<raisedby>17</raisedby>
<created>2007-05-29</created>
<description>Is the current vocabulary for mapping between concepts in different concept
schemes (previously called "SKOS Mapping") sufficient? Could it be simplified?

Requirement:
http://www.w3.org/TR/2007/WD-skos-ucr-20070516/#R-ConceptualMappingLinks</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20070529145256.0A9F56636D@dolph.w3.org</uri>
<subject>ISSUE-39: SemanticMappingVocabulary</subject>
<sender>dean+cgi@w3.org</sender>
<date>2007-05-29</date>
</email>
<email>
<uri>http://www.w3.org/mid/4682400B.4030808@few.vu.nl</uri>
<subject>Re: ISSUE-39: ConceptualMappingLinks</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-06-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070822065936.GA2376@Octavius</uri>
<subject>[ALL] SWD face-to-face - draft agenda</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-08-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D033D4F83@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [ALL] SWD face-to-face - draft agenda</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-08-24</date>
</email>
<email>
<uri>http://www.w3.org/mid/46D2E6F9.1070403@few.vu.nl</uri>
<subject>Re: [ALL] SWD face-to-face - draft agenda</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-08-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/4783570E020000D8000266E9@ntgwgate.loc.gov</uri>
<subject>Regrets - Re: [ALL] agenda 8 Jan telecon 1600 UTC</subject>
<sender>juth@loc.gov</sender>
<date>2008-01-08</date>
</email>
<email>
<uri>http://www.w3.org/mid/47825367.10302@cs.vu.nl</uri>
<subject>[ALL] agenda 8 Jan telecon 1600 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2008-01-07</date>
</email>
<email>
<uri>http://www.w3.org/mid/CAB44397-D95E-4696-B790-B22F63BB8A30@manchester.ac.uk</uri>
<subject>Meeting record: 2007-12-18 SWD telecon</subject>
<sender>sean.bechhofer@manchester.ac.uk</sender>
<date>2007-12-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/4767EDC5.7040000@sandsoft.com</uri>
<subject>Re: [ALL] Agenda - Dec 18 2007 SWD telecon - 1600 UTC</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2007-12-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/52bd7c3d0712180745x53d8c9d2o8087b56e66f13f79@mail.gmail.com</uri>
<subject>Re: [ALL] Agenda - Dec 18 2007 SWD telecon - 1600 UTC</subject>
<sender>simone.onofri@gmail.com</sender>
<date>2007-12-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/4767E4F3.1020305@deri.org</uri>
<subject>Re: [ALL] Agenda - Dec 18 2007 SWD telecon - 1600 UTC</subject>
<sender>vit.novacek@deri.org</sender>
<date>2007-12-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/20071218095958.GA3876@octavius</uri>
<subject>[ALL] Agenda - Dec 18 2007 SWD telecon - 1600 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-12-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB669029DAE0D@hqgiex01.fao.org</uri>
<subject>RE: [SKOS] A new proposal for ISSUE-39 ConceptualMappingLinks</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2007-12-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB669029DAE0C@hqgiex01.fao.org</uri>
<subject>RE: [SKOS] A revised proposal for ISSUE-39 ConceptualMappingLinks  [CORRECTION]</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2007-12-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB669029DAE0B@hqgiex01.fao.org</uri>
<subject>RE: [SKOS] A new proposal for ISSUE-39 ConceptualMappingLinks</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2007-12-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/476654D6.70208@dcs.gla.ac.uk</uri>
<subject>Re: [SKOS] A new proposal for ISSUE-39 ConceptualMappingLinks</subject>
<sender>agray@dcs.gla.ac.uk</sender>
<date>2007-12-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/47659465.1090802@few.vu.nl</uri>
<subject>Re: [SKOS] A revised proposal for ISSUE-39 ConceptualMappingLinks  [CORRECTION]</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-12-16</date>
</email>
<email>
<uri>http://www.w3.org/mid/4761021E0200006A0001BF5B@ntgwgate.loc.gov</uri>
<subject>Minutes from 2007-12-11 telecon</subject>
<sender>cred@loc.gov</sender>
<date>2007-12-13</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D03B3FABA@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [SKOS] A new proposal for ISSUE-39 ConceptualMappingLinks</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-12-12</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D03B3FAB9@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [SKOS] A new proposal for ISSUE-39 ConceptualMappingLinks</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-12-12</date>
</email>
<email>
<uri>http://www.w3.org/mid/475EE0DE.3080602@few.vu.nl</uri>
<subject>Re: [SKOS] A revised proposal for ISSUE-39 ConceptualMappingLinks</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-12-11</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D03B3F206@exchange11.fed.cclrc.ac.uk</uri>
<subject>[SKOS] top priorities</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-11-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/474C9618.2050701@few.vu.nl</uri>
<subject>[SKOS] A new proposal for ISSUE-39 ConceptualMappingLinks</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-11-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/BED9D15F73EDDE48BF480604236A456004BBC16B@ex1.ad.dcs.gla.ac.uk</uri>
<subject>RE: [SKOS] A new proposal for ISSUE-39 ConceptualMappingLinks</subject>
<sender>agray@dcs.gla.ac.uk</sender>
<date>2007-11-29</date>
</email>
<email>
<uri>http://www.w3.org/mid/474EA6E0.5000705@few.vu.nl</uri>
<subject>Re: [SKOS] A new proposal for ISSUE-39 ConceptualMappingLinks</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-11-29</date>
</email>
<email>
<uri>http://www.w3.org/mid/6.2.5.6.2.20071201074627.04846340@smi.stanford.edu</uri>
<subject>RE: [SKOS] A new proposal for ISSUE-39 ConceptualMappingLinks</subject>
<sender>rubin@smi.stanford.edu</sender>
<date>2007-12-01</date>
</email>
<email>
<uri>http://www.w3.org/mid/475478DE.1090205@few.vu.nl</uri>
<subject>Re: SKOS ISSUE-39: clarification?</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-12-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/2C50F05E7BE301499FDE5A2820E4CFE0627C36@BE-SCAM2.ds.strath.ac.uk</uri>
<subject>RE: SKOS ISSUE-39: clarification?</subject>
<sender>e.mcculloch@strath.ac.uk</sender>
<date>2007-12-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB6690269F7AD@hqgiex01.fao.org</uri>
<subject>RE: [SKOS] A new proposal for ISSUE-39 ConceptualMappingLinks</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2007-12-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB669029DADC5@hqgiex01.fao.org</uri>
<subject>RE: [SKOS] A new proposal for ISSUE-39 ConceptualMappingLinks</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2007-12-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/47556EF8.6040802@few.vu.nl</uri>
<subject>Re: [SKOS] A new proposal for ISSUE-39 ConceptualMappingLinks</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-12-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/47557082.0@few.vu.nl</uri>
<subject>Re: SKOS ISSUE-39: clarification?</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-12-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB6690269F7B4@hqgiex01.fao.org</uri>
<subject>RE: [SKOS] A new proposal for ISSUE-39 ConceptualMappingLinks</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2007-12-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB669029DADC6@hqgiex01.fao.org</uri>
<subject>RE: SKOS ISSUE-39: clarification?</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2007-12-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/47558836.80109@few.vu.nl</uri>
<subject>Re: SKOS ISSUE-39: clarification?</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-12-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D03B3F7C4@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [SKOS] A new proposal for ISSUE-39 ConceptualMappingLinks</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-12-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D03B3F7C8@exchange11.fed.cclrc.ac.uk</uri>
<subject>[SKOS] ISSUE-39A Grouping for Mapping? (was RE: [SKOS] A new proposal for ISSUE-39 ConceptualMappingLinks)</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-12-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/4755A88B.5080609@few.vu.nl</uri>
<subject>Re: SKOS ISSUE-39: clarification?</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-12-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/uIg5HcJ8HeVHFA6w@mail.willpowerinfo.co.uk</uri>
<subject>Re: SKOS ISSUE-39: clarification?</subject>
<sender>L.Will@willpowerinfo.co.uk</sender>
<date>2007-12-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/4756CC46.3030905@dcs.gla.ac.uk</uri>
<subject>Re: [SKOS] A new proposal for ISSUE-39 ConceptualMappingLinks</subject>
<sender>agray@dcs.gla.ac.uk</sender>
<date>2007-12-05</date>
</email>
<email>
<uri>http://www.w3.org/mid/4756F25B.7010801@few.vu.nl</uri>
<subject>[SKOS] ISSUE-39B Parallel vocabulary for Mapping? (was RE: [SKOS]  A new proposal for ISSUE-39 ConceptualMappingLinks)</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-12-05</date>
</email>
<email>
<uri>http://www.w3.org/mid/47570A73.9050309@few.vu.nl</uri>
<subject>Re: [SKOS] ISSUE-39A Grouping for Mapping? (was RE: [SKOS] A new  proposal for ISSUE-39 ConceptualMappingLinks)</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-12-05</date>
</email>
<email>
<uri>http://www.w3.org/mid/47570D3C.3050900@few.vu.nl</uri>
<subject>Re: [SKOS] ISSUE-39C Related vs Overlapping match (was Re: SKOS ISSUE-39:  clarification?)</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-12-05</date>
</email>
<email>
<uri>http://www.w3.org/mid/002a01c838e7$f90cddf0$0300000a@DELL</uri>
<subject>RE: [SKOS] A new proposal for ISSUE-39 ConceptualMappingLinks</subject>
<sender>sdclarke@lukehouse.demon.co.uk</sender>
<date>2007-12-07</date>
</email>
<email>
<uri>http://www.w3.org/mid/f99la3JH8bWHFAXz@mail.willpowerinfo.co.uk</uri>
<subject>A new proposal for ISSUE-39 ConceptualMappingLinks</subject>
<sender>L.Will@willpowerinfo.co.uk</sender>
<date>2007-12-07</date>
</email>
<email>
<uri>http://www.w3.org/mid/475D19D9.3080009@few.vu.nl</uri>
<subject>Re: [SKOS] A new proposal for ISSUE-39 ConceptualMappingLinks</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-12-10</date>
</email>
<email>
<uri>http://www.w3.org/mid/002001c83b1d$a1cee3c0$0300000a@DELL</uri>
<subject>RE: [SKOS] A new proposal for ISSUE-39 ConceptualMappingLinks</subject>
<sender>sdclarke@lukehouse.demon.co.uk</sender>
<date>2007-12-10</date>
</email>
<email>
<uri>http://www.w3.org/mid/475D21D7.1080805@few.vu.nl</uri>
<subject>Re: A new proposal for ISSUE-39 ConceptualMappingLinks</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-12-10</date>
</email>
<email>
<uri>http://www.w3.org/mid/20071210151751.GA2940@octavius</uri>
<subject>[ALL] Agenda - Dec 11 2007 SWD telecon - 1600 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-12-10</date>
</email>
<email>
<uri>http://www.w3.org/mid/004b01c83b43$72306140$0300000a@DELL</uri>
<subject>RE: A new proposal for ISSUE-39 ConceptualMappingLinks</subject>
<sender>sdclarke@lukehouse.demon.co.uk</sender>
<date>2007-12-10</date>
</email>
<email>
<uri>http://www.w3.org/mid/475D84E8.305@few.vu.nl</uri>
<subject>[SKOS] A revised proposal for ISSUE-39 ConceptualMappingLinks</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-12-10</date>
</email>
<email>
<uri>http://www.w3.org/mid/475DA0DD.6050807@few.vu.nl</uri>
<subject>Re: A new proposal for ISSUE-39 ConceptualMappingLinks</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-12-10</date>
</email>
<email>
<uri>http://www.w3.org/mid/E92D1644-9044-4011-92A6-8455F0380B38@madcreek.com</uri>
<subject>Re: [ALL] Agenda - Dec 11 2007 SWD telecon - 1600 UTC</subject>
<sender>jphipps@madcreek.com</sender>
<date>2007-12-11</date>
</email>
<email>
<uri>http://www.w3.org/mid/475EA699.3010609@adida.net</uri>
<subject>Re: [ALL] Agenda - Dec 11 2007 SWD telecon - 1600 UTC</subject>
<sender>ben@adida.net</sender>
<date>2007-12-11</date>
</email>
<email>
<uri>http://www.w3.org/mid/52bd7c3d0712110703s522fee13p1b16e6708e333418@mail.gmail.com</uri>
<subject>Re: [ALL] Agenda - Dec 11 2007 SWD telecon - 1600 UTC</subject>
<sender>simone.onofri@gmail.com</sender>
<date>2007-12-11</date>
</email>
<email>
<uri>http://www.w3.org/mid/2AD2401FC36E784094D0B3375FDA6CE802788761@VMAIL2.uoa.abdn.ac.uk</uri>
<subject>RE: [ALL] Agenda - Dec 11 2007 SWD telecon - 1600 UTC</subject>
<sender>q.reul@abdn.ac.uk</sender>
<date>2007-12-11</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB6690269F81F@hqgiex01.fao.org</uri>
<subject>RE: SKOS ISSUE-39: clarification?</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2007-12-11</date>
</email>
<email>
<uri>http://www.w3.org/mid/7C1F4F6C-FD48-46FF-814E-E84AB89D0987@madcreek.com</uri>
<subject>Meeting record: 2008-01-08 SWD telecon</subject>
<sender>jphipps@madcreek.com</sender>
<date>2008-01-11</date>
</email>
<email>
<uri>http://www.w3.org/mid/478BB65B.8080507@cs.vu.nl</uri>
<subject>[ALL] agenda 15 Jan telecon 1600 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2008-01-14</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB6690269F988@hqgiex01.fao.org</uri>
<subject>RE: [ALL] agenda 15 Jan telecon 1600 UTC</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-01-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/478CE1C7.8010400@sandsoft.com</uri>
<subject>Re: [ALL] agenda 15 Jan telecon 1600 UTC</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2008-01-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/478DB2D6.70308@fundacionctic.org</uri>
<subject>Meeting record: 2008-01-15 SWD telecon</subject>
<sender>diego.berrueta@fundacionctic.org</sender>
<date>2008-01-16</date>
</email>
<email>
<uri>http://www.w3.org/mid/47B8B622.8060206@few.vu.nl</uri>
<subject>Re: [SKOS] On ISSUE-71 ParallelMappingVocabulary and ISSUE-74 MappingPropertyConventions</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB669029DAF56@hqgiex01.fao.org</uri>
<subject>RE: [SKOS] On ISSUE-71 ParallelMappingVocabulary and ISSUE-74  MappingPropertyConventions</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-02-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BB2300.8010702@few.vu.nl</uri>
<subject>[SKOS] Closing ISSUE-71 ParallelMappingVocabulary</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080219110910.3gcob74r340swck4@webmail.stanford.edu</uri>
<subject>Re: [SKOS] Closing ISSUE-71 ParallelMappingVocabulary</subject>
<sender>dlrubin@stanford.edu</sender>
<date>2008-02-19</date>
</email>
</emails>
<notes>
<note>
<date>2007-12-18</date>
<text>In [1] Alistair proposed dropping all grouping constructs from the Rec.
This was discussed during the 18-Dec telecon [2].  During that telecon
we resolved to proceed per Alistair's recommendation and drop the legacy
AND, OR, ...

[1] http://lists.w3.org/Archives/Public/public-swd-wg/2007Dec/0025.html
[2] http://www.w3.org/2007/12/18-swd-minutes</text>
</note>
<note>
<date>2008-01-15</date>
<text>[rrs]
RESOLUTION: Accept Antoine's proposal 
http://lists.w3.org/Archives/Public/public-swd-wg/2007Dec/0083.html

&lt;p&gt;
-- http://www.w3.org/2007/12/18-swd-minutes#item02</text>
</note>
</notes>
</issue>
<issue>
<id>40</id>
<title>ConceptCoordination</title>
<product>3</product>
<raisedby>8</raisedby>
<created>2007-05-29</created>
<description>Many subject vocabularies are designed to be "coordinated". For example, when
using MeSH, main descriptors can be "coordinated with" modifiers to create more
specific meanings, e.g. "aspirin" coordinated with "side-effects". SKOS does not
provide any support for coordination.

See also http://www.w3.org/2006/07/SWD/wiki/SkosDesign/Coordination .

Requirement: http://www.w3.org/TR/2007/WD-skos-ucr-20070516/#R-ConceptCoordination
</description>
<state>4</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20070529145521.121866B64C@tibor.w3.org</uri>
<subject>ISSUE-40: Coordination</subject>
<sender>dean+cgi@w3.org</sender>
<date>2007-05-29</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070616124931.AE5056B644@kent.w3.org</uri>
<subject>ISSUE-45: NaryLinksBetweenDescriptorsAndNonDescriptors</subject>
<sender>dean+cgi@w3.org</sender>
<date>2007-06-16</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070822065936.GA2376@Octavius</uri>
<subject>[ALL] SWD face-to-face - draft agenda</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-08-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D033D4F83@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [ALL] SWD face-to-face - draft agenda</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-08-24</date>
</email>
<email>
<uri>http://www.w3.org/mid/46D2E6F9.1070403@few.vu.nl</uri>
<subject>Re: [ALL] SWD face-to-face - draft agenda</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-08-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/4767EDC5.7040000@sandsoft.com</uri>
<subject>Re: [ALL] Agenda - Dec 18 2007 SWD telecon - 1600 UTC</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2007-12-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/52bd7c3d0712180745x53d8c9d2o8087b56e66f13f79@mail.gmail.com</uri>
<subject>Re: [ALL] Agenda - Dec 18 2007 SWD telecon - 1600 UTC</subject>
<sender>simone.onofri@gmail.com</sender>
<date>2007-12-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/4767E4F3.1020305@deri.org</uri>
<subject>Re: [ALL] Agenda - Dec 18 2007 SWD telecon - 1600 UTC</subject>
<sender>vit.novacek@deri.org</sender>
<date>2007-12-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/20071218095958.GA3876@octavius</uri>
<subject>[ALL] Agenda - Dec 18 2007 SWD telecon - 1600 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-12-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB669029DAE0C@hqgiex01.fao.org</uri>
<subject>RE: [SKOS] A revised proposal for ISSUE-39 ConceptualMappingLinks  [CORRECTION]</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2007-12-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/47659465.1090802@few.vu.nl</uri>
<subject>Re: [SKOS] A revised proposal for ISSUE-39 ConceptualMappingLinks  [CORRECTION]</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-12-16</date>
</email>
<email>
<uri>http://www.w3.org/mid/475EE0DE.3080602@few.vu.nl</uri>
<subject>Re: [SKOS] A revised proposal for ISSUE-39 ConceptualMappingLinks</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-12-11</date>
</email>
<email>
<uri>http://www.w3.org/mid/475478DE.1090205@few.vu.nl</uri>
<subject>Re: SKOS ISSUE-39: clarification?</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-12-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/2C50F05E7BE301499FDE5A2820E4CFE0627C36@BE-SCAM2.ds.strath.ac.uk</uri>
<subject>RE: SKOS ISSUE-39: clarification?</subject>
<sender>e.mcculloch@strath.ac.uk</sender>
<date>2007-12-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/47557082.0@few.vu.nl</uri>
<subject>Re: SKOS ISSUE-39: clarification?</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-12-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/47558836.80109@few.vu.nl</uri>
<subject>Re: SKOS ISSUE-39: clarification?</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-12-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/4755A88B.5080609@few.vu.nl</uri>
<subject>Re: SKOS ISSUE-39: clarification?</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-12-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/47570A73.9050309@few.vu.nl</uri>
<subject>Re: [SKOS] ISSUE-39A Grouping for Mapping? (was RE: [SKOS] A new  proposal for ISSUE-39 ConceptualMappingLinks)</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-12-05</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD72BB.1010906@zoo.ox.ac.uk</uri>
<subject>[Fwd: [SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD9D4A.2090301@zoo.ox.ac.uk</uri>
<subject>[SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/68C22185DB90CA41A5ACBD8E834C5ECD04953D70@goofy.wpakb.kb.nl</uri>
<subject>RE : ISSUE 77 and postcoordination [and ISSUE-40!]</subject>
<sender>Antoine.Isaac@KB.nl</sender>
<date>2008-03-10</date>
</email>
<email>
<uri>http://www.w3.org/mid/47D539BA.9060501@gbv.de</uri>
<subject>Re: ISSUE 77 and postcoordination [and ISSUE-40!]</subject>
<sender>jakob.voss@gbv.de</sender>
<date>2008-03-10</date>
</email>
<email>
<uri>http://www.w3.org/mid/O14MrDFEYn1HFANZ@mail.willpowerinfo.co.uk</uri>
<subject>Re: ISSUE 77 and postcoordination [and ISSUE-40!]</subject>
<sender>L.Will@willpowerinfo.co.uk</sender>
<date>2008-03-11</date>
</email>
<email>
<uri>http://www.w3.org/mid/47DA58CD.6020406@lukehouse.org</uri>
<subject>Re: ISSUE 77 and postcoordination [and ISSUE-40!]</subject>
<sender>stella@lukehouse.org</sender>
<date>2008-03-14</date>
</email>
<email>
<uri>http://www.w3.org/mid/47DAA274.3060600@gbv.de</uri>
<subject>Re: ISSUE 77 and postcoordination [and ISSUE-40!]</subject>
<sender>jakob.voss@gbv.de</sender>
<date>2008-03-14</date>
</email>
<email>
<uri>http://www.w3.org/mid/229614.35279.qm@web44814.mail.sp1.yahoo.com</uri>
<subject>Re: ISSUE 77 and postcoordination [and ISSUE-40!]</subject>
<sender>nabonitaguha@yahoo.com</sender>
<date>2008-03-14</date>
</email>
<email>
<uri>http://www.w3.org/mid/47DE408B.8050208@gbv.de</uri>
<subject>Re: ISSUE 77 and postcoordination [and ISSUE-40!]</subject>
<sender>jakob.voss@gbv.de</sender>
<date>2008-03-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/47DEA249.4070801@gbv.de</uri>
<subject>Re: ISSUE 77 and postcoordination [and ISSUE-40!]</subject>
<sender>jakob.voss@gbv.de</sender>
<date>2008-03-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/47DF77C5.3000209@few.vu.nl</uri>
<subject>[SKOS] ISSUE 77 and ISSUE-40: proposal for postcoordination</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-03-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/47DF9683.8070700@dcs.gla.ac.uk</uri>
<subject>Re: ISSUE 77 and postcoordination [and ISSUE-40!]</subject>
<sender>agray@dcs.gla.ac.uk</sender>
<date>2008-03-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/47E11ECC0200006A00024B85@ntgwgate.loc.gov</uri>
<subject>Minutes from 2008-03-18 telecon</subject>
<sender>cred@loc.gov</sender>
<date>2008-03-19</date>
</email>
</emails>
<notes>
<note>
<date>2008-01-29</date>
<text>[rrs] Alistair agrees to make a proposal, though he feels that SKOS could go to
REC without resolving this</text>
</note>
<note>
<date>2008-05-07</date>
<text>RESOLUTION: to postpone issue 40, due to lack of time, lack of implementation
experience with tentative solutions, and unclear interaction between SKOS and OWL.
-- http://www.w3.org/2008/05/07-swd-minutes.html#item04</text>
</note>
</notes>
</issue>
<issue>
<id>41</id>
<title>UseLangTagsInExamples</title>
<product>3</product>
<raisedby>8</raisedby>
<created>2007-05-29</created>
<description>The SKOS Core Guide should use language tags with literals throughout, as
examples of good practice.</description>
<state>3</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20070529145846.CF0FF3320C@kearny.w3.org</uri>
<subject>ISSUE-41: UseLangTagsInExamples</subject>
<sender>dean+cgi@w3.org</sender>
<date>2007-05-29</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070822065936.GA2376@Octavius</uri>
<subject>[ALL] SWD face-to-face - draft agenda</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-08-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D033D4F83@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [ALL] SWD face-to-face - draft agenda</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-08-24</date>
</email>
<email>
<uri>http://www.w3.org/mid/46D2E6F9.1070403@few.vu.nl</uri>
<subject>Re: [ALL] SWD face-to-face - draft agenda</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-08-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/479E554A.4020607@few.vu.nl</uri>
<subject>Re: [SKOS] Re: Review of the SKOS Primer</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-28</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D0499E45B@exchange11.fed.cclrc.ac.uk</uri>
<subject>[SKOS] ISSUE-41</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2008-01-29</date>
</email>
<email>
<uri>http://www.w3.org/mid/479F6E52.5020509@few.vu.nl</uri>
<subject>Re: [SKOS] ISSUE-41</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-29</date>
</email>
<email>
<uri>http://www.w3.org/mid/f032cc060801291151p6cedd4f8y96df92440cbab812@mail.gmail.com</uri>
<subject>Re: [SKOS] ISSUE-41</subject>
<sender>ehs@pobox.com</sender>
<date>2008-01-29</date>
</email>
<email>
<uri>http://www.w3.org/mid/47B8B1FB.1030902@few.vu.nl</uri>
<subject>[SKOS] Issues Review [From Alistair]</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD72BB.1010906@zoo.ox.ac.uk</uri>
<subject>[Fwd: [SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD9D4A.2090301@zoo.ox.ac.uk</uri>
<subject>[SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080415154659.GA4980@octavius</uri>
<subject>[SKOS] Issue owners - preparation for Washington</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2008-04-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/480C7E67.9090901@few.vu.nl</uri>
<subject>Re: [SKOS] Issue owners - preparation for Washington</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-04-21</date>
</email>
</emails>
<notes>
<note>
<date>2008-01-29</date>
<text>[rrs] The WG believes this no longer applies to the current SKOS Reference. 
Alistair will inform the commenter.</text>
</note>
</notes>
</issue>
<issue>
<id>42</id>
<title>How does RDFa handle the @SRC attribute?</title>
<product>2</product>
<raisedby>6</raisedby>
<created>2007-06-13</created>
<description>We need to come to a conclusion on what @SRC does. The most recent consensus
was: @SRC is like @HREF, but there has been some dissent on this topic.</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20070613165649.61CF5BDAF@w3c4.w3.org</uri>
<subject>ISSUE-42: How does RDFa handle the @SRC attribute?</subject>
<sender>dean+cgi@w3.org</sender>
<date>2007-06-13</date>
</email>
<email>
<uri>http://www.w3.org/mid/469011A1.5000305@adida.net</uri>
<subject>[RDFa] ISSUE-42: @src, following up, proposal to resolve</subject>
<sender>ben@adida.net</sender>
<date>2007-07-07</date>
</email>
<email>
<uri>http://www.w3.org/mid/4690B30D.8090908@w3.org</uri>
<subject>Re: [RDFa] ISSUE-42: @src, following up, proposal to resolve</subject>
<sender>ivan@w3.org</sender>
<date>2007-07-08</date>
</email>
<email>
<uri>http://www.w3.org/mid/469266E9.4000503@adida.net</uri>
<subject>Re: [RDFa] ISSUE-42: @src, following up, proposal to resolve</subject>
<sender>ben@adida.net</sender>
<date>2007-07-09</date>
</email>
<email>
<uri>http://www.w3.org/mid/46926887.8050803@aptest.com</uri>
<subject>Re: [RDFa] ISSUE-42: @src, following up, proposal to resolve</subject>
<sender>shane@aptest.com</sender>
<date>2007-07-09</date>
</email>
<email>
<uri>http://www.w3.org/mid/469268B5.30402@w3.org</uri>
<subject>Re: [RDFa] ISSUE-42: @src, following up, proposal to resolve</subject>
<sender>ivan@w3.org</sender>
<date>2007-07-09</date>
</email>
<email>
<uri>http://www.w3.org/mid/46926950.2090504@adida.net</uri>
<subject>Re: [RDFa] ISSUE-42: @src, following up, proposal to resolve</subject>
<sender>ben@adida.net</sender>
<date>2007-07-09</date>
</email>
<email>
<uri>http://www.w3.org/mid/469358D6.9000106@w3.org</uri>
<subject>Re: [RDFa] ISSUE-42: @src, following up, proposal to resolve</subject>
<sender>ivan@w3.org</sender>
<date>2007-07-10</date>
</email>
<email>
<uri>http://www.w3.org/mid/46935E25.1010003@w3.org</uri>
<subject>Re: [RDFa] ISSUE-42: @src, following up, proposal to resolve</subject>
<sender>ivan@w3.org</sender>
<date>2007-07-10</date>
</email>
<email>
<uri>http://www.w3.org/mid/46935EB1.8080408@w3.org</uri>
<subject>Re: [RDFa] ISSUE-42: @src, following up, proposal to resolve</subject>
<sender>ivan@w3.org</sender>
<date>2007-07-10</date>
</email>
<email>
<uri>http://www.w3.org/mid/46967A6B.90904@adida.net</uri>
<subject>[RDFa] ISSUE-42: the @src attribute</subject>
<sender>ben@adida.net</sender>
<date>2007-07-12</date>
</email>
<email>
<uri>http://www.w3.org/mid/46973F72.9010908@w3.org</uri>
<subject>Re: [RDFa] ISSUE-42: the @src attribute</subject>
<sender>ivan@w3.org</sender>
<date>2007-07-13</date>
</email>
<email>
<uri>http://www.w3.org/mid/469C0776.7010601@adida.net</uri>
<subject>Re: [RDFa] ISSUE-42: the @src attribute</subject>
<sender>ben@adida.net</sender>
<date>2007-07-16</date>
</email>
<email>
<uri>http://www.w3.org/mid/469ECA95.3020701@adida.net</uri>
<subject>Re: [RDFa] ISSUE-42: the @src attribute</subject>
<sender>ben@adida.net</sender>
<date>2007-07-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/cf8107640707190738u60f995e3lc89c20a6267ad193@mail.gmail.com</uri>
<subject>Re: [RDFa] ISSUE-42: the @src attribute</subject>
<sender>lindstream@gmail.com</sender>
<date>2007-07-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/47044893.6070506@adida.net</uri>
<subject>ISSUE-42: @src attribute</subject>
<sender>ben@adida.net</sender>
<date>2007-10-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/47049AEB.5040002@w3.org</uri>
<subject>Re: ISSUE-42: @src attribute</subject>
<sender>ivan@w3.org</sender>
<date>2007-10-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/cf8107640710040148k6681018bo64c47418a4cc03d3@mail.gmail.com</uri>
<subject>Re: ISSUE-42: @src attribute</subject>
<sender>lindstream@gmail.com</sender>
<date>2007-10-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/a707f8300710040228k6d5a7780y2d532ec7480e36cd@mail.gmail.com</uri>
<subject>Re: ISSUE-42: @src attribute</subject>
<sender>mark.birbeck@formsPlayer.com</sender>
<date>2007-10-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/4704F031.1070100@digitalbazaar.com</uri>
<subject>Re: ISSUE-42: @src attribute</subject>
<sender>msporny@digitalbazaar.com</sender>
<date>2007-10-04</date>
</email>
</emails>
<notes>
<note>
<date>2007-10-18</date>
<text>RESOLVED: @src on IMG behaves just @href and @resource, and it is overridden by
@href and @resource, in that order.

(for some reason, some of the mailing list links on the tracker are dead...)</text>
</note>
<note>
<date>2008-02-06</date>
<text>this resolution was modified on 2008-01-24, as follows:

"@src behaves like @about and is overridden by @about"

telecon: http://www.w3.org/2008/01/24-rdfa-minutes.html</text>
</note>
</notes>
</issue>
<issue>
<id>43</id>
<title>Primer should link to the URIs of the assumed namespaces (e.g. cc, foaf,...)</title>
<product>2</product>
<raisedby>6</raisedby>
<created>2007-06-13</created>
<description>http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2007Apr/0003.html</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20070613172919.6A1D06B643@tibor.w3.org</uri>
<subject>ISSUE-43: Primer should link to the URIs of the assumed namespaces (e.g. cc, foaf,...)</subject>
<sender>dean+cgi@w3.org</sender>
<date>2007-06-13</date>
</email>
<email>
<uri>http://www.w3.org/mid/46FAEE7D.6010609@adida.net</uri>
<subject>[RDFa] ISSUE-43: Primer should link to URIs of assumed namespaces</subject>
<sender>ben@adida.net</sender>
<date>2007-09-26</date>
</email>
<email>
<uri>http://www.w3.org/mid/768DACDC356ED04EA1F1130F97D29852016638B9@RZJC2EX.jr1.local</uri>
<subject>meeting record: 2008-04-24 RDF-in-XHTML TF telecon</subject>
<sender>michael.hausenblas@joanneum.at</sender>
<date>2008-04-25</date>
</email>
<email>
<uri>http://www.w3.org/mid/768DACDC356ED04EA1F1130F97D298520166398A@RZJC2EX.jr1.local</uri>
<subject>[RDFa] Comments on the RDFa Primer</subject>
<sender>michael.hausenblas@joanneum.at</sender>
<date>2008-04-28</date>
</email>
</emails>
<notes>
<note>
<date>2008-04-30</date>
<text>RESOLVED as "Michael to answer Lee's comments for Issue 43 in the same e-mail as
Issue 11, noting that the Primer and Syntax Document have changed significantly
and issues seem to have been addressed. Invite for further comments. This issue
is closed, no changes to the documents."</text>
</note>
</notes>
</issue>
<issue>
<id>44</id>
<title>BroaderNarrowerSemantics</title>
<product>3</product>
<raisedby>16</raisedby>
<created>2007-06-15</created>
<description>What are the semantics of skos:broader and skos:narrower? There are several open
questions:

 * Are they transitive? Intransitive? Or can the application choose?
 * Are they reflexive? Irreflexive? Or can the application choose?
 * Should the transitive closure be irreflexive (i.e. a cycle is a
contradiction)? Or can the application choose?</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20070615092507.87D2EC1F7@nelson.w3.org</uri>
<subject>ISSUE-44: BroaderNarrowerSemantics</subject>
<sender>dean+cgi@w3.org</sender>
<date>2007-06-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070615040030.zd82d9tqmsw04s00@webmail.stanford.edu</uri>
<subject>Re: ISSUE-44: BroaderNarrowerSemantics</subject>
<sender>dlrubin@stanford.edu</sender>
<date>2007-06-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/1182425449.4846.18.camel@duncan.fundacionctic.org</uri>
<subject>Re: ISSUE-44: BroaderNarrowerSemantics</subject>
<sender>diego.berrueta@fundacionctic.org</sender>
<date>2007-06-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D02EC0BF0@exchange11.fed.cclrc.ac.uk</uri>
<subject>[SKOS] central issues</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-06-26</date>
</email>
<email>
<uri>http://www.w3.org/mid/46814CEA.3000004@mondeca.com</uri>
<subject>Re: [SKOS] central issues</subject>
<sender>bernard.vatant@mondeca.com</sender>
<date>2007-06-26</date>
</email>
<email>
<uri>http://www.w3.org/mid/46824F52.3010205@few.vu.nl</uri>
<subject>Re: [SKOS] central issues</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-06-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/46825EA9.8010408@mondeca.com</uri>
<subject>Re: [SKOS] central issues</subject>
<sender>bernard.vatant@mondeca.com</sender>
<date>2007-06-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/46891049.4070304@cs.vu.nl</uri>
<subject>Re: [SKOS] central issues</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-07-02</date>
</email>
<email>
<uri>http://www.w3.org/mid/46894F29.4010907@madcreek.com</uri>
<subject>Re: [SKOS] central issues</subject>
<sender>jphipps@madcreek.com</sender>
<date>2007-07-02</date>
</email>
<email>
<uri>http://www.w3.org/mid/4689FFFD.8080603@few.vu.nl</uri>
<subject>Re: [SKOS] central issues</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-07-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/468A58FC.2030303@madcreek.com</uri>
<subject>Re: [SKOS] central issues</subject>
<sender>jphipps@madcreek.com</sender>
<date>2007-07-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/468AC9DE.8070503@cs.vu.nl</uri>
<subject>Re: [SKOS] central issues</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-07-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070822065936.GA2376@Octavius</uri>
<subject>[ALL] SWD face-to-face - draft agenda</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-08-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D033D4F83@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [ALL] SWD face-to-face - draft agenda</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-08-24</date>
</email>
<email>
<uri>http://www.w3.org/mid/46D2E6F9.1070403@few.vu.nl</uri>
<subject>Re: [ALL] SWD face-to-face - draft agenda</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-08-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/47865A88.4050108@mondeca.com</uri>
<subject>Re: [SKOS] The return of ISSUE-44 (was Re: TR : SKOS Reference  Editor's    Draft 23 December 2007)</subject>
<sender>bernard.vatant@mondeca.com</sender>
<date>2008-01-10</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080110083519.pd3bcl1aqs8k4s88@webmail.stanford.edu</uri>
<subject>Re: [SKOS] The return of ISSUE-44 (was Re: TR : SKOS Reference    	Editor's   Draft 23 December 2007)</subject>
<sender>rubin@med.stanford.edu</sender>
<date>2008-01-10</date>
</email>
<email>
<uri>http://www.w3.org/mid/4786461D.6030404@few.vu.nl</uri>
<subject>Re: [SKOS] The return of ISSUE-44 (was Re: TR : SKOS Reference    Editor's   Draft 23 December 2007)</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-10</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080110074342.5xlew9uwbo0048wc@webmail.stanford.edu</uri>
<subject>Re: [SKOS] The return of ISSUE-44 (was Re: TR : SKOS Reference   	Editor's   Draft 23 December 2007)</subject>
<sender>rubin@med.stanford.edu</sender>
<date>2008-01-10</date>
</email>
<email>
<uri>http://www.w3.org/mid/478637BF.5080809@few.vu.nl</uri>
<subject>Re: [SKOS] The return of ISSUE-44 (was Re: TR : SKOS Reference    Editor's   Draft 23 December 2007)</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-10</date>
</email>
<email>
<uri>http://www.w3.org/mid/6.2.5.6.2.20080110065848.04a0f5a8@med.stanford.edu</uri>
<subject>Re: [SKOS] The return of ISSUE-44 (was Re: TR : SKOS Reference   Editor's   Draft 23 December 2007)</subject>
<sender>rubin@med.stanford.edu</sender>
<date>2008-01-10</date>
</email>
<email>
<uri>http://www.w3.org/mid/6.2.5.6.2.20080110065354.04a039c8@med.stanford.edu</uri>
<subject>Re: [SKOS] The return of ISSUE-44 (was Re: TR : SKOS Reference    Editor's   Draft 23 December 2007)</subject>
<sender>rubin@med.stanford.edu</sender>
<date>2008-01-10</date>
</email>
<email>
<uri>http://www.w3.org/mid/47861B85.5000700@few.vu.nl</uri>
<subject>Re: [SKOS] The return of ISSUE-44 (was Re: TR : SKOS Reference Editor's  Draft 23 December 2007)</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-10</date>
</email>
<email>
<uri>http://www.w3.org/mid/12B58E38-84DC-40F7-A890-F05947AABCE3@gmail.com</uri>
<subject>Re: [SKOS] The return of ISSUE-44 (was Re: TR : SKOS Reference Editor's   Draft 23 December 2007)</subject>
<sender>sesuncedu@gmail.com</sender>
<date>2008-01-10</date>
</email>
<email>
<uri>http://www.w3.org/mid/4D7608C1-EF26-4D70-BCB7-508CC72040D2@gmail.com</uri>
<subject>Re: [SKOS] The return of ISSUE-44 (was Re: TR : SKOS Reference Editor's Draft 23 December 2007)</subject>
<sender>sesuncedu@gmail.com</sender>
<date>2008-01-10</date>
</email>
<email>
<uri>http://www.w3.org/mid/746215BF-3FF6-42F9-939A-6A0862A79C9A@manchester.ac.uk</uri>
<subject>Re: [SKOS] The return of ISSUE-44 (was Re: TR : SKOS Reference Editor's  Draft 23 December 2007)</subject>
<sender>sean.bechhofer@manchester.ac.uk</sender>
<date>2008-01-10</date>
</email>
<email>
<uri>http://www.w3.org/mid/4785EE6E.3070804@mondeca.com</uri>
<subject>Re: [SKOS] The return of ISSUE-44 (was Re: TR : SKOS Reference Editor's   Draft 23 December 2007)</subject>
<sender>bernard.vatant@mondeca.com</sender>
<date>2008-01-10</date>
</email>
<email>
<uri>http://www.w3.org/mid/4785E95A.3040900@few.vu.nl</uri>
<subject>Re: [SKOS] The return of ISSUE-44 (was Re: TR : SKOS Reference Editor's   Draft 23 December 2007)</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-10</date>
</email>
<email>
<uri>http://www.w3.org/mid/4785E7A1.5060706@few.vu.nl</uri>
<subject>Re: [SKOS] The return of ISSUE-44 (was Re: TR : SKOS Reference  Editor's   Draft 23 December 2007)</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-10</date>
</email>
<email>
<uri>http://www.w3.org/mid/6.2.5.6.2.20080109142807.02d93ff0@med.stanford.edu</uri>
<subject>Re: [SKOS] The return of ISSUE-44 (was Re: TR : SKOS Reference   Editor's  Draft 23 December 2007)</subject>
<sender>rubin@med.stanford.edu</sender>
<date>2008-01-09</date>
</email>
<email>
<uri>http://www.w3.org/mid/D2721347-6B91-4EAD-8AD6-2E26A85929B6@gmail.com</uri>
<subject>Re: [SKOS] The return of ISSUE-44 (was Re: TR : SKOS Reference Editor's  Draft 23 December 2007)</subject>
<sender>sesuncedu@gmail.com</sender>
<date>2008-01-09</date>
</email>
<email>
<uri>http://www.w3.org/mid/478539B3.20907@few.vu.nl</uri>
<subject>[SKOS] The return of ISSUE-44 (was Re: TR : SKOS Reference Editor's  Draft 23 December 2007)</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-09</date>
</email>
<email>
<uri>http://www.w3.org/mid/475D87BF.7010801@few.vu.nl</uri>
<subject>Re: [ALL] Agenda - Dec 11 2007 SWD telecon - 1600 UTC</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-12-10</date>
</email>
<email>
<uri>http://www.w3.org/mid/6.2.5.6.2.20080110101818.04793948@med.stanford.edu</uri>
<subject>Re: [SKOS] The return of ISSUE-44 (was Re: TR : SKOS Reference    Editor's    Draft 23 December 2007)</subject>
<sender>rubin@med.stanford.edu</sender>
<date>2008-01-10</date>
</email>
<email>
<uri>http://www.w3.org/mid/47866CEB.2040702@mondeca.com</uri>
<subject>Re: [SKOS] The return of ISSUE-44 (was Re: TR : SKOS Reference     Editor's    Draft 23 December 2007)</subject>
<sender>bernard.vatant@mondeca.com</sender>
<date>2008-01-10</date>
</email>
<email>
<uri>http://www.w3.org/mid/6.2.5.6.2.20080112055253.0435b758@med.stanford.edu</uri>
<subject>Re: [SKOS] The return of ISSUE-44 (was Re: TR : SKOS Reference     Editor's    Draft 23 December 2007)</subject>
<sender>rubin@med.stanford.edu</sender>
<date>2008-01-12</date>
</email>
<email>
<uri>http://www.w3.org/mid/6DA97EFF2763174B8BDC409CA1972984067F6B54@dbf-ex.AD.DDB.DE</uri>
<subject>AW: [SKOS] The return of ISSUE-44 (was Re: TR : SKOS Reference     Editor's    Draft 23 December 2007)</subject>
<sender>l.svensson@d-nb.de</sender>
<date>2008-01-14</date>
</email>
<email>
<uri>http://www.w3.org/mid/478B1DE8.3060204@few.vu.nl</uri>
<subject>Re: AW: [SKOS] The return of ISSUE-44 (was Re: TR : SKOS Reference      Editor's    Draft 23 December 2007)</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-14</date>
</email>
<email>
<uri>http://www.w3.org/mid/6DA97EFF2763174B8BDC409CA1972984067F6B5C@dbf-ex.AD.DDB.DE</uri>
<subject>AW: AW: [SKOS] The return of ISSUE-44 (was Re: TR : SKOS Reference     Editor's    Draft 23 December 2007)</subject>
<sender>l.svensson@d-nb.de</sender>
<date>2008-01-14</date>
</email>
<email>
<uri>http://www.w3.org/mid/6.2.5.6.2.20080114082411.04afe3f0@med.stanford.edu</uri>
<subject>Re: AW: [SKOS] The return of ISSUE-44 (was Re: TR : SKOS   Reference     Editor's    Draft 23 December 2007)</subject>
<sender>rubin@med.stanford.edu</sender>
<date>2008-01-14</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB669029DAE64@hqgiex01.fao.org</uri>
<subject>RE: [SKOS] Transitive broader and ISSUE-56 (was The return of ISSUE-44  )</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-01-14</date>
</email>
<email>
<uri>http://www.w3.org/mid/478BB65B.8080507@cs.vu.nl</uri>
<subject>[ALL] agenda 15 Jan telecon 1600 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2008-01-14</date>
</email>
<email>
<uri>http://www.w3.org/mid/478C8BA1.3080201@few.vu.nl</uri>
<subject>Re: AW: AW: [SKOS] Transitive broader and ISSUE-56 (was The return   of ISSUE-44 )</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB6690269F988@hqgiex01.fao.org</uri>
<subject>RE: [ALL] agenda 15 Jan telecon 1600 UTC</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-01-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/478CE1C7.8010400@sandsoft.com</uri>
<subject>Re: [ALL] agenda 15 Jan telecon 1600 UTC</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2008-01-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/003001c856d5$12d30060$6702a8c0@TFJOHAN</uri>
<subject>RE: AW: AW: [SKOS] Transitive broader and ISSUE-56 (was The return  of ISSUE-44 )</subject>
<sender>johan.de-smedt@tenforce.com</sender>
<date>2008-01-14</date>
</email>
<email>
<uri>http://www.w3.org/mid/478DDBCA.4010601@few.vu.nl</uri>
<subject>Re: [SKOS] proposed resolution for Issue 4 - BroaderNarrowerSemantics</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-16</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080116153050.38D2CBEF0@nelson.w3.org</uri>
<subject>ISSUE-69: BroaderIrreflexive</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-01-16</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080116153440.4745C5F70C@stu.w3.org</uri>
<subject>ISSUE-70: BroaderCycles</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-01-16</date>
</email>
<email>
<uri>http://www.w3.org/mid/478E245D.7090403@few.vu.nl</uri>
<subject>Re: ISSUE-69: BroaderIrreflexive</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-16</date>
</email>
<email>
<uri>http://www.w3.org/mid/478F2594.7020002@few.vu.nl</uri>
<subject>Re: ISSUE-70: BroaderCycles</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D0499DF75@exchange11.fed.cclrc.ac.uk</uri>
<subject>[SKOS] SKOS Reference Editor's Draft 18 January 2008</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2008-01-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D0499DF79@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [SKOS] SKOS Reference Editor's Draft 23 December 2007</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2008-01-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/2AD2401FC36E784094D0B3375FDA6CE802ACF9DD@VMAIL2.uoa.abdn.ac.uk</uri>
<subject>RE: [SKOS] SKOS Reference Editor's Draft 18 January 2008</subject>
<sender>q.reul@abdn.ac.uk</sender>
<date>2008-01-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080121175703.GA3684@octavius</uri>
<subject>[ALL] Agenda - Jan 22 2008 SWD telecon - 1600 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2008-01-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47960E40.2070703@cs.vu.nl</uri>
<subject>Re: [ALL] Agenda - Jan 22 2008 SWD telecon - 1600 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2008-01-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/479620AD.1020805@sandsoft.com</uri>
<subject>Re: [ALL] Agenda - Jan 22 2008 SWD telecon - 1600 UTC</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2008-01-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/47971236.404@few.vu.nl</uri>
<subject>Re: ISSUE-69: BroaderIrreflexive</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-23</date>
</email>
<email>
<uri>http://www.w3.org/mid/479E064F.6000309@cs.vu.nl</uri>
<subject>[ALL] agenda 29 Jan telecon -- 16:00 UTC </subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2008-01-28</date>
</email>
<email>
<uri>http://www.w3.org/mid/479E2C33.6020307@cs.vu.nl</uri>
<subject>Re: [ALL] agenda 29 Jan telecon -- 16:00 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2008-01-28</date>
</email>
<email>
<uri>http://www.w3.org/mid/A492AE2F-6DCF-4F65-93EA-A7EF9E80D5E7@manchester.ac.uk</uri>
<subject>Meeting Record: 2008-01-29 telecon</subject>
<sender>sean.bechhofer@manchester.ac.uk</sender>
<date>2008-01-31</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB66903408403@hqgiex01.fao.org</uri>
<subject>Several emails to reply to</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-02-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/000601c8b5e0$5ee5a830$1cb0f890$@miles@zoo.ox.ac.uk</uri>
<subject>[SKOS] ISSUE-44 (was: Suggestion for SKOS FAQ)</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-05-14</date>
</email>
<email>
<uri>http://www.w3.org/mid/483E6C2A.2060901@few.vu.nl</uri>
<subject>Re: [SKOS] ISSUE-44 (was: Suggestion for SKOS FAQ)</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-05-29</date>
</email>
<email>
<uri>http://www.w3.org/mid/005701c8c17c$2ade3410$6973a8c0@TFJOHAN</uri>
<subject>RE: [SKOS] ISSUE-44 (was: Suggestion for SKOS FAQ)</subject>
<sender>johan.de-smedt@tenforce.com</sender>
<date>2008-05-29</date>
</email>
</emails>
<notes>
<note>
<date>2007-08-21</date>
<text>Assigned to Sean during 21 August WG telecon</text>
</note>
<note>
<date>2008-01-22</date>
<text>[rrs] Guus proposes a resolution in
http://lists.w3.org/Archives/Public/public-swd-wg/2008Jan/0090.html</text>
</note>
<note>
<date>2008-01-22</date>
<text>[rrs] closed per http://www.w3.org/2008/01/22-swd-minutes.html#item01
Alistair: separate issues have been opened for transitivity (68, 69) and cycles (70)</text>
</note>
</notes>
</issue>
<issue>
<id>45</id>
<title>NaryLinksBetweenDescriptorsAndNonDescriptors</title>
<product>3</product>
<raisedby>8</raisedby>
<created>2007-06-16</created>
<description>Normally in a thesaurus, every non-descriptor (non-preferred term) points to one
and only one descriptor (preferred term). However, the ISO 2788 standard also
allows instructions of the form "USE X + Y" and "USE X OR Y". 

Related wiki page: http://www.w3.org/2006/07/SWD/wiki/SkosDesign/ThesaurusPatterns

Alistair's initial email:
http://lists.w3.org/Archives/Public/public-swd-wg/2007Feb/0036

Related issue: ISSUE-40 ConceptCoordination,
http://www.w3.org/2006/07/SWD/track/issues/40</description>
<state>4</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20070616124931.AE5056B644@kent.w3.org</uri>
<subject>ISSUE-45: NaryLinksBetweenDescriptorsAndNonDescriptors</subject>
<sender>dean+cgi@w3.org</sender>
<date>2007-06-16</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070822065936.GA2376@Octavius</uri>
<subject>[ALL] SWD face-to-face - draft agenda</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-08-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D033D4F83@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [ALL] SWD face-to-face - draft agenda</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-08-24</date>
</email>
<email>
<uri>http://www.w3.org/mid/46D2E6F9.1070403@few.vu.nl</uri>
<subject>Re: [ALL] SWD face-to-face - draft agenda</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-08-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/4767EDC5.7040000@sandsoft.com</uri>
<subject>Re: [ALL] Agenda - Dec 18 2007 SWD telecon - 1600 UTC</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2007-12-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/52bd7c3d0712180745x53d8c9d2o8087b56e66f13f79@mail.gmail.com</uri>
<subject>Re: [ALL] Agenda - Dec 18 2007 SWD telecon - 1600 UTC</subject>
<sender>simone.onofri@gmail.com</sender>
<date>2007-12-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/4767E4F3.1020305@deri.org</uri>
<subject>Re: [ALL] Agenda - Dec 18 2007 SWD telecon - 1600 UTC</subject>
<sender>vit.novacek@deri.org</sender>
<date>2007-12-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/20071218095958.GA3876@octavius</uri>
<subject>[ALL] Agenda - Dec 18 2007 SWD telecon - 1600 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-12-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB669029DAE0C@hqgiex01.fao.org</uri>
<subject>RE: [SKOS] A revised proposal for ISSUE-39 ConceptualMappingLinks  [CORRECTION]</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2007-12-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/47659465.1090802@few.vu.nl</uri>
<subject>Re: [SKOS] A revised proposal for ISSUE-39 ConceptualMappingLinks  [CORRECTION]</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-12-16</date>
</email>
<email>
<uri>http://www.w3.org/mid/475EE0DE.3080602@few.vu.nl</uri>
<subject>Re: [SKOS] A revised proposal for ISSUE-39 ConceptualMappingLinks</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-12-11</date>
</email>
<email>
<uri>http://www.w3.org/mid/47570A73.9050309@few.vu.nl</uri>
<subject>Re: [SKOS] ISSUE-39A Grouping for Mapping? (was RE: [SKOS] A new  proposal for ISSUE-39 ConceptualMappingLinks)</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-12-05</date>
</email>
<email>
<uri>http://www.w3.org/mid/4799B34E.7040203@few.vu.nl</uri>
<subject>Re: RIF: Comments on SKOS Primer</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-25</date>
</email>
<email>
<uri>http://www.w3.org/mid/47A7836B.2050501@few.vu.nl</uri>
<subject>Re: RIF: Comments on SKOS Primer</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD72BB.1010906@zoo.ox.ac.uk</uri>
<subject>[Fwd: [SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD9D4A.2090301@zoo.ox.ac.uk</uri>
<subject>[SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
</emails>
<notes>
<note>
<date>2008-01-29</date>
<text>[rrs] Deferred pending a resolution of issue-40.  Guus notes that some of the
use cases assume this feature.</text>
</note>
<note>
<date>2008-05-07</date>
<text>RESOLVED: to postpone issue 45, due to lack of time, lack of implementation
experience with tentative solutions, and unclear interaction between SKOS and OWL. 
-- http://www.w3.org/2008/05/07-swd-minutes.html#item09</text>
</note>
</notes>
</issue>
<issue>
<id>46</id>
<title>IndexingAndNonIndexingConcepts</title>
<product>3</product>
<raisedby>17</raisedby>
<created>2007-06-16</created>
<description>SKOS should provide different classes for conceptual entities that can be used
for indexing resources and for those that cannot be used for such a purpose
(e.g. specific qualifiers that can only be used to narrow down the meaning of an
existing concept).

Requirement:
http://www.w3.org/TR/2007/WD-skos-ucr-20070516/#R-IndexingAndNonIndexingConcepts</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20070616125310.04C0D6B644@kent.w3.org</uri>
<subject>ISSUE-46: IndexingAndNonIndexingConcepts</subject>
<sender>dean+cgi@w3.org</sender>
<date>2007-06-16</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070822065936.GA2376@Octavius</uri>
<subject>[ALL] SWD face-to-face - draft agenda</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-08-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D033D4F83@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [ALL] SWD face-to-face - draft agenda</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-08-24</date>
</email>
<email>
<uri>http://www.w3.org/mid/46D2E6F9.1070403@few.vu.nl</uri>
<subject>Re: [ALL] SWD face-to-face - draft agenda</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-08-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD72BB.1010906@zoo.ox.ac.uk</uri>
<subject>[Fwd: [SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD9D4A.2090301@zoo.ox.ac.uk</uri>
<subject>[SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
</emails>
<notes>
<note>
<date>2008-02-05</date>
<text>[rrs] accepted as OPEN on 2008-02-05</text>
</note>
<note>
<date>2008-05-07</date>
<text>RESOLUTION: Close issue 46 as we have decided that the indexing vocabulary is
not part of SKOS
-- http://www.w3.org/2008/05/07-swd-minutes.html#item10</text>
</note>
</notes>
</issue>
<issue>
<id>47</id>
<title>MappingProvenanceInformation</title>
<product>3</product>
<raisedby>5</raisedby>
<created>2007-06-16</created>
<description>It shall be possible to record provenance information on mappings between
concepts in different concept schemes.

Requirement:
http://www.w3.org/TR/2007/WD-skos-ucr-20070516/#R-MappingProvenanceInformation</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20070616125926.153C247BA8@mojo.w3.org</uri>
<subject>ISSUE-47: MappingProvenanceInformation</subject>
<sender>dean+cgi@w3.org</sender>
<date>2007-06-16</date>
</email>
<email>
<uri>http://www.w3.org/mid/468A8D24.7060904@few.vu.nl</uri>
<subject>Re: [SKOS] on ISSUE-36, ISSUE-39, ISSUE-47 mapping and concept scheme  provenance and (was Re: [SKOS] central issues)</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-07-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070822065936.GA2376@Octavius</uri>
<subject>[ALL] SWD face-to-face - draft agenda</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-08-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D033D4F83@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [ALL] SWD face-to-face - draft agenda</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-08-24</date>
</email>
<email>
<uri>http://www.w3.org/mid/46D2E6F9.1070403@few.vu.nl</uri>
<subject>Re: [ALL] SWD face-to-face - draft agenda</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-08-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/47B8B900.40700@few.vu.nl</uri>
<subject>[SKOS] Proposal ISSUE 47 MappingProvenanceInformation</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/47B96B20.4010007@dcs.gla.ac.uk</uri>
<subject>Re: [SKOS] Proposal ISSUE 47 MappingProvenanceInformation</subject>
<sender>agray@dcs.gla.ac.uk</sender>
<date>2008-02-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BB2384.10600@few.vu.nl</uri>
<subject>[SKOS] Closing ISSUE 47 MappingProvenanceInformation</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD72BB.1010906@zoo.ox.ac.uk</uri>
<subject>[Fwd: [SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD9D4A.2090301@zoo.ox.ac.uk</uri>
<subject>[SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
</emails>
<notes>
<note>
<date>2008-02-05</date>
<text>[rrs] accepted as OPEN on 5-Feb</text>
</note>
<note>
<date>2008-05-07</date>
<text>RESOLVED: Provenance of mappings is not handled by the introduction of specific
SKOS vocabulary. In the SKOS reference documents (Reference and maybe Primer),
SKOS users are instead pointed at other RDF containment mechanisms (E.g. the URI
of a mapping information source can be used in a SPARQL query).
-- http://www.w3.org/2008/05/07-swd-minutes.html#item11</text>
</note>
</notes>
</issue>
<issue>
<id>48</id>
<title>IndexingRelationship</title>
<product>3</product>
<raisedby>17</raisedby>
<created>2007-06-16</created>
<description>The SKOS model should contain mechanisms to attach a given resource (e.g.
corresponding to a document) to a concept the resource is about, e.g. to query
for the resources described by a given concept.

Requirement: http://www.w3.org/TR/2007/WD-skos-ucr-20070516/#R-IndexingRelationship</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20070616130155.A9AD613AC7@seamus.w3.org</uri>
<subject>ISSUE-48: IndexingRelationship</subject>
<sender>dean+cgi@w3.org</sender>
<date>2007-06-16</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070822065936.GA2376@Octavius</uri>
<subject>[ALL] SWD face-to-face - draft agenda</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-08-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D033D4F83@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [ALL] SWD face-to-face - draft agenda</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-08-24</date>
</email>
<email>
<uri>http://www.w3.org/mid/46D2E6F9.1070403@few.vu.nl</uri>
<subject>Re: [ALL] SWD face-to-face - draft agenda</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-08-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/4799C6D9.8000907@few.vu.nl</uri>
<subject>[SKOS] Re: Review of the SKOS Primer</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-25</date>
</email>
<email>
<uri>http://www.w3.org/mid/2AD2401FC36E784094D0B3375FDA6CE802C2BA9C@VMAIL2.uoa.abdn.ac.uk</uri>
<subject>RE: [SKOS] Re: Review of the SKOS Primer</subject>
<sender>q.reul@abdn.ac.uk</sender>
<date>2008-01-25</date>
</email>
<email>
<uri>http://www.w3.org/mid/68C22185DB90CA41A5ACBD8E834C5ECD0465B0C3@goofy.wpakb.kb.nl</uri>
<subject>RE : RE : [ISSUE-77] [ISSUE-48] Skos subject properties  are deprecated</subject>
<sender>Antoine.Isaac@KB.nl</sender>
<date>2008-01-28</date>
</email>
<email>
<uri>http://www.w3.org/mid/479E554A.4020607@few.vu.nl</uri>
<subject>Re: [SKOS] Re: Review of the SKOS Primer</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-28</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB66903408403@hqgiex01.fao.org</uri>
<subject>Several emails to reply to</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-02-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/47B8B1FB.1030902@few.vu.nl</uri>
<subject>[SKOS] Issues Review [From Alistair]</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD72BB.1010906@zoo.ox.ac.uk</uri>
<subject>[Fwd: [SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD9D4A.2090301@zoo.ox.ac.uk</uri>
<subject>[SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080415154659.GA4980@octavius</uri>
<subject>[SKOS] Issue owners - preparation for Washington</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2008-04-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/480C7E67.9090901@few.vu.nl</uri>
<subject>Re: [SKOS] Issue owners - preparation for Washington</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-04-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/48187F16.6060201@few.vu.nl</uri>
<subject>[SKOS] Material for ISSUE-48 and ISSUE-77</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-04-30</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080430153626.GA1784@octavius</uri>
<subject>Re: [SKOS] Material for ISSUE-48 and ISSUE-77</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2008-04-30</date>
</email>
</emails>
<notes>
<note>
<date>2008-05-07</date>
<text>See also ISSUE-77 SubjectIndexing</text>
</note>
<note>
<date>2008-05-07</date>
<text>RESOLUTION: to not include the SKOS indexing properties because
1) it's the role of SKOS to publish vocabularies and not to indicate how they
should be used for indexing purposes
2) there appear to be enough support from existing metadata vocabularies to
handle links between resources and SKOS concepts
-- http://www.w3.org/2008/05/07-swd-minutes.html#item05</text>
</note>
</notes>
</issue>
<issue>
<id>49</id>
<title>LexicalMappingLinks</title>
<product>3</product>
<raisedby>17</raisedby>
<created>2007-06-16</created>
<description>In the process of mapping different concept schemes, it should be possible to
identify correspondence links not only between concepts from these concept
schemes, but also between the labels that can be attached to these concepts.

Requirement: http://www.w3.org/TR/2007/WD-skos-ucr-20070516/#R-LexicalMappingLinks</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20070616162313.024306B644@kent.w3.org</uri>
<subject>ISSUE-49: LexicalMappingLinks</subject>
<sender>dean+cgi@w3.org</sender>
<date>2007-06-16</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070822065936.GA2376@Octavius</uri>
<subject>[ALL] SWD face-to-face - draft agenda</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-08-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D033D4F83@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [ALL] SWD face-to-face - draft agenda</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-08-24</date>
</email>
<email>
<uri>http://www.w3.org/mid/46D2E6F9.1070403@few.vu.nl</uri>
<subject>Re: [ALL] SWD face-to-face - draft agenda</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-08-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD72BB.1010906@zoo.ox.ac.uk</uri>
<subject>[Fwd: [SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD9D4A.2090301@zoo.ox.ac.uk</uri>
<subject>[SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
</emails>
<notes>
<note>
<date>2008-05-07</date>
<text>RESOLUTION: the XL appendix provides a framework for asserting lexical mapping links
-- http://www.w3.org/2008/05/07-swd-minutes.html#item12</text>
</note>
</notes>
</issue>
<issue>
<id>50</id>
<title>CompatibilityWithDC</title>
<product>3</product>
<raisedby>17</raisedby>
<created>2007-06-16</created>
<description>Using SKOS model shall be compatible with using Dublin Core Abstract Model
(http://dublincore.org/documents/abstract-model/). When there are links between
SKOS features and Dublin Core ones, these shall be specified.

Requirement: http://www.w3.org/TR/2007/WD-skos-ucr-20070516/#R-CompatibilityWithDC

</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20070616162515.464216B644@kent.w3.org</uri>
<subject>ISSUE-50: CompatibilityWithDC</subject>
<sender>dean+cgi@w3.org</sender>
<date>2007-06-16</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070822065936.GA2376@Octavius</uri>
<subject>[ALL] SWD face-to-face - draft agenda</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-08-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D033D4F83@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [ALL] SWD face-to-face - draft agenda</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-08-24</date>
</email>
<email>
<uri>http://www.w3.org/mid/46D2E6F9.1070403@few.vu.nl</uri>
<subject>Re: [ALL] SWD face-to-face - draft agenda</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-08-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD72BB.1010906@zoo.ox.ac.uk</uri>
<subject>[Fwd: [SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD9D4A.2090301@zoo.ox.ac.uk</uri>
<subject>[SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
</emails>
<notes>
<note>
<date>2008-05-07</date>
<text>RESOLUTION: the use of concept scheme URI in DC metadata as a vocabulary scheme
URI does not raise compatibility issues
-- http://www.w3.org/2008/05/07-swd-minutes.html#item06</text>
</note>
</notes>
</issue>
<issue>
<id>51</id>
<title>CompatibilityWithISO11179</title>
<product>3</product>
<raisedby>17</raisedby>
<created>2007-06-16</created>
<description>SKOS model shall be compatible with part 3 of ISO 11179 specifications for a
metadata registry metamodel (http://metadata-standards.org/11179/#11179-3 )

Requirement:
http://www.w3.org/TR/2007/WD-skos-ucr-20070516/#R-CompatibilityWithISO11179</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20070616162724.1B19A6B644@kent.w3.org</uri>
<subject>ISSUE-51: CompatibilityWithISO11179</subject>
<sender>dean+cgi@w3.org</sender>
<date>2007-06-16</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070822065936.GA2376@Octavius</uri>
<subject>[ALL] SWD face-to-face - draft agenda</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-08-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D033D4F83@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [ALL] SWD face-to-face - draft agenda</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-08-24</date>
</email>
<email>
<uri>http://www.w3.org/mid/46D2E6F9.1070403@few.vu.nl</uri>
<subject>Re: [ALL] SWD face-to-face - draft agenda</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-08-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD72BB.1010906@zoo.ox.ac.uk</uri>
<subject>[Fwd: [SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD9D4A.2090301@zoo.ox.ac.uk</uri>
<subject>[SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB66903B87AC7@hqgiex01.fao.org</uri>
<subject>List of resolutions from the Face-to-Face meeting</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-05-13</date>
</email>
<email>
<uri>http://www.w3.org/mid/482ADFEC.9070001@cs.vu.nl</uri>
<subject>Re: List of resolutions from the Face-to-Face meeting</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2008-05-14</date>
</email>
</emails>
<notes>
<note>
<date>2008-05-07</date>
<text>2008-05-07: RESOLVED to close ISSUE-53 by saying that we see no incompatibility
between SKOS and ISO 11179 http://www.w3.org/2008/05/07-swd-minutes.html#item06</text>
</note>
</notes>
</issue>
<issue>
<id>52</id>
<title>CompatibilityWithISO2788</title>
<product>3</product>
<raisedby>17</raisedby>
<created>2007-06-16</created>
<description>SKOS model shall be compatible with ISO 2788 specifications for monolingual
thesauri (http://www.collectionscanada.ca/iso/tc46sc9/standard/2788e.htm )

Requirement:
http://www.w3.org/TR/2007/WD-skos-ucr-20070516/#R-CompatibilityWithISO2788</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20070616164743.ECFEEC1F7@nelson.w3.org</uri>
<subject>ISSUE-52: CompatibilityWithISO2788</subject>
<sender>dean+cgi@w3.org</sender>
<date>2007-06-16</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070822065936.GA2376@Octavius</uri>
<subject>[ALL] SWD face-to-face - draft agenda</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-08-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D033D4F83@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [ALL] SWD face-to-face - draft agenda</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-08-24</date>
</email>
<email>
<uri>http://www.w3.org/mid/46D2E6F9.1070403@few.vu.nl</uri>
<subject>Re: [ALL] SWD face-to-face - draft agenda</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-08-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD72BB.1010906@zoo.ox.ac.uk</uri>
<subject>[Fwd: [SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD9D4A.2090301@zoo.ox.ac.uk</uri>
<subject>[SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB66903B87AC7@hqgiex01.fao.org</uri>
<subject>List of resolutions from the Face-to-Face meeting</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-05-13</date>
</email>
<email>
<uri>http://www.w3.org/mid/482ADFEC.9070001@cs.vu.nl</uri>
<subject>Re: List of resolutions from the Face-to-Face meeting</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2008-05-14</date>
</email>
</emails>
<notes>
<note>
<date>2008-05-07</date>
<text>RESOLUTION: to close ISSUE-52 by adding a table to the Primer with
correspondences between ISO-2788 and SKOS constructs
-- http://www.w3.org/2008/05/07-swd-minutes.html#item06</text>
</note>
<note>
<date>2008-05-07</date>
<text>RESOLUTION: to close ISSUE-52 by adding a table to the Primer with
correspondences between ISO-2788 and SKOS constructs
http://www.w3.org/2008/05/07-swd-minutes.html#item06</text>
</note>
</notes>
</issue>
<issue>
<id>53</id>
<title>CompatibilityWithISO5964</title>
<product>3</product>
<raisedby>17</raisedby>
<created>2007-06-16</created>
<description>SKOS model shall be compatible with ISO 5964 specifications for multilingual
thesauri (http://www.collectionscanada.ca/iso/tc46sc9/standard/5964e.htm)

Requirement:
http://www.w3.org/TR/2007/WD-skos-ucr-20070516/#R-CompatibilityWithISO5964</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20070616165243.F03ADC1F7@nelson.w3.org</uri>
<subject>ISSUE-53: CompatibilityWithISO5964</subject>
<sender>dean+cgi@w3.org</sender>
<date>2007-06-16</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070822065936.GA2376@Octavius</uri>
<subject>[ALL] SWD face-to-face - draft agenda</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-08-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D033D4F83@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [ALL] SWD face-to-face - draft agenda</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-08-24</date>
</email>
<email>
<uri>http://www.w3.org/mid/46D2E6F9.1070403@few.vu.nl</uri>
<subject>Re: [ALL] SWD face-to-face - draft agenda</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-08-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD72BB.1010906@zoo.ox.ac.uk</uri>
<subject>[Fwd: [SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD9D4A.2090301@zoo.ox.ac.uk</uri>
<subject>[SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
</emails>
<notes>
<note>
<date>2008-05-07</date>
<text>RESOLVED to close ISSUE-53 by saying that we see no imcompatibility between SKOS
and ISO5964
http://www.w3.org/2008/05/07-swd-minutes.html#item06</text>
</note>
</notes>
</issue>
<issue>
<id>54</id>
<title>ConceptSemantics</title>
<product>3</product>
<raisedby>17</raisedby>
<created>2007-06-26</created>
<description>What are the semantics of skos:Concept?

skos:Concept is currently declared as { skos:Concept rdf:type rdfs:Class . } ...
is this ok? Is this enough? What about the OWL universe?</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20070626160934.3BAB06B651@tibor.w3.org</uri>
<subject>ISSUE-54: ConceptSemantics</subject>
<sender>dean+cgi@w3.org</sender>
<date>2007-06-26</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D02EC0BF0@exchange11.fed.cclrc.ac.uk</uri>
<subject>[SKOS] central issues</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-06-26</date>
</email>
<email>
<uri>http://www.w3.org/mid/46814CEA.3000004@mondeca.com</uri>
<subject>Re: [SKOS] central issues</subject>
<sender>bernard.vatant@mondeca.com</sender>
<date>2007-06-26</date>
</email>
<email>
<uri>http://www.w3.org/mid/46824F52.3010205@few.vu.nl</uri>
<subject>Re: [SKOS] central issues</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-06-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/46825EA9.8010408@mondeca.com</uri>
<subject>Re: [SKOS] central issues</subject>
<sender>bernard.vatant@mondeca.com</sender>
<date>2007-06-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/46891049.4070304@cs.vu.nl</uri>
<subject>Re: [SKOS] central issues</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-07-02</date>
</email>
<email>
<uri>http://www.w3.org/mid/46894F29.4010907@madcreek.com</uri>
<subject>Re: [SKOS] central issues</subject>
<sender>jphipps@madcreek.com</sender>
<date>2007-07-02</date>
</email>
<email>
<uri>http://www.w3.org/mid/4689FFFD.8080603@few.vu.nl</uri>
<subject>Re: [SKOS] central issues</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-07-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/468A58FC.2030303@madcreek.com</uri>
<subject>Re: [SKOS] central issues</subject>
<sender>jphipps@madcreek.com</sender>
<date>2007-07-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/468AC9DE.8070503@cs.vu.nl</uri>
<subject>Re: [SKOS] central issues</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2007-07-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070822065936.GA2376@Octavius</uri>
<subject>[ALL] SWD face-to-face - draft agenda</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-08-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D033D4F83@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [ALL] SWD face-to-face - draft agenda</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-08-24</date>
</email>
<email>
<uri>http://www.w3.org/mid/46D2E6F9.1070403@few.vu.nl</uri>
<subject>Re: [ALL] SWD face-to-face - draft agenda</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-08-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D0363C425@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [SKOS] Resolutions on concept semantics (ISSUE-54)</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-11-06</date>
</email>
<email>
<uri>http://www.w3.org/mid/4730A1CE.5000402@few.vu.nl</uri>
<subject>Re: [SKOS] Resolutions on concept semantics (ISSUE-54)</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-11-06</date>
</email>
<email>
<uri>http://www.w3.org/mid/4730B089.3000607@few.vu.nl</uri>
<subject>Re: [SKOS] Resolutions on concept semantics (ISSUE-54)</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-11-06</date>
</email>
<email>
<uri>http://www.w3.org/mid/4733298B.50906@few.vu.nl</uri>
<subject>Re: [SKOS] Resolutions on concept semantics (ISSUE-54)</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-11-08</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080117132525.4BAB3C6DB6@barney.w3.org</uri>
<subject>ISSUE-80: SKOS-OWL-Patterns</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-01-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/47B1EF98.7090608@few.vu.nl</uri>
<subject>[SKOS] Proposed resolution to close ISSUE-54</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-12</date>
</email>
<email>
<uri>http://www.w3.org/mid/47B8B1FB.1030902@few.vu.nl</uri>
<subject>[SKOS] Issues Review [From Alistair]</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080218163809.GA3304@octavius</uri>
<subject>[All] Agenda - Feb 19 2008 SWD telecon - 1600 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2008-02-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/34b5049c0802181029q5c534978m87acdc4c4f6a334d@mail.gmail.com</uri>
<subject>Re: [All] Agenda - Feb 19 2008 SWD telecon - 1600 UTC</subject>
<sender>jphipps@madcreek.com</sender>
<date>2008-02-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB669029DAF5E@hqgiex01.fao.org</uri>
<subject>RE: [All] Agenda - Feb 19 2008 SWD telecon - 1600 UTC</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-02-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/52bd7c3d0802181458o4267f179lf9b25fbbe0e46971@mail.gmail.com</uri>
<subject>Re: [All] Agenda - Feb 19 2008 SWD telecon - 1600 UTC</subject>
<sender>simone.onofri@gmail.com</sender>
<date>2008-02-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD72BB.1010906@zoo.ox.ac.uk</uri>
<subject>[Fwd: [SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BDA2FE.3020004@zoo.ox.ac.uk</uri>
<subject>Minutes of 2008-02-19 telcon</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD9D4A.2090301@zoo.ox.ac.uk</uri>
<subject>[SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BEEB3F.60801@few.vu.nl</uri>
<subject>[SKOS] ISSUE--54 closed, ISSUE-80 opened</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080415154659.GA4980@octavius</uri>
<subject>[SKOS] Issue owners - preparation for Washington</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2008-04-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/480C7E67.9090901@few.vu.nl</uri>
<subject>Re: [SKOS] Issue owners - preparation for Washington</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-04-21</date>
</email>
</emails>
<notes>
<note>
<date>2007-08-21</date>
<text>Assigned to Antoine during 21 August WG telecon</text>
</note>
<note>
<date>2008-02-22</date>
<text>2008-02-19 [rrs] Closed per Antoine's proposal in
http://lists.w3.org/Archives/Public/public-swd-wg/2008Feb/0053.html
Section 3 of the SKOS reference
http://www.w3.org/TR/2008/WD-skos-reference-20080125/#L1289 is adopted as a
partial solution to ISSUE-54. ISSUE-54 is CLOSEd. ISSUE-80 is now OPENed. 

2008-02-19 [rrs] closed per  http://www.w3.org/2008/02/19-swd-minutes.html#item03</text>
</note>
</notes>
</issue>
<issue>
<id>55</id>
<title>CURIEs or QNames in XHTML1.1+RDFa, </title>
<product>2</product>
<raisedby>6</raisedby>
<created>2007-06-27</created>
<description>Ivan requests that we drop CURIEs and opt for QNames at this point. Shane adds
that it's dangerous to base our specification on the CURIE spec, which itself is
not finished.</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20070627021747.04AB1C200@nelson.w3.org</uri>
<subject>ISSUE-55: CURIEs or QNames in XHTML1.1+RDFa, </subject>
<sender>dean+cgi@w3.org</sender>
<date>2007-06-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/46967313.3040508@adida.net</uri>
<subject>[RDFa] ISSUE-55: CURIEs or QNames in XHTML1.1+RDFa</subject>
<sender>ben@adida.net</sender>
<date>2007-07-12</date>
</email>
<email>
<uri>http://www.w3.org/mid/768DACDC356ED04EA1F1130F97D2985201211B9F@RZJC2EX.jr1.local</uri>
<subject>RE: [RDFa] ISSUE-55: CURIEs or QNames in XHTML1.1+RDFa</subject>
<sender>michael.hausenblas@joanneum.at</sender>
<date>2007-07-12</date>
</email>
<email>
<uri>http://www.w3.org/mid/46967F76.3060702@adida.net</uri>
<subject>Re: [RDFa] ISSUE-55: CURIEs or QNames in XHTML1.1+RDFa</subject>
<sender>ben@adida.net</sender>
<date>2007-07-12</date>
</email>
<email>
<uri>http://www.w3.org/mid/46973DAF.2030700@w3.org</uri>
<subject>Re: [RDFa] ISSUE-55: CURIEs or QNames in XHTML1.1+RDFa</subject>
<sender>ivan@w3.org</sender>
<date>2007-07-13</date>
</email>
<email>
<uri>http://www.w3.org/mid/4697D02B.4080100@aptest.com</uri>
<subject>Re: [RDFa] ISSUE-55: CURIEs or QNames in XHTML1.1+RDFa</subject>
<sender>shane@aptest.com</sender>
<date>2007-07-13</date>
</email>
<email>
<uri>http://www.w3.org/mid/640dd5060707131304j42d33146w60eeb59208d0a117@mail.gmail.com</uri>
<subject>Re: [RDFa] ISSUE-55: CURIEs or QNames in XHTML1.1+RDFa</subject>
<sender>mark.birbeck@x-port.net</sender>
<date>2007-07-13</date>
</email>
<email>
<uri>http://www.w3.org/mid/768DACDC356ED04EA1F1130F97D2985201211CB0@RZJC2EX.jr1.local</uri>
<subject>RE: [RDFa] ISSUE-55: CURIEs or QNames in XHTML1.1+RDFa</subject>
<sender>michael.hausenblas@joanneum.at</sender>
<date>2007-07-13</date>
</email>
</emails>
<notes>
<note>
<date>2007-08-16</date>
<text>resolved as: "RDFa does not use QNames for shortening URIs, as that is technically incorrect. We use the 
equivalent of CURIEs, exactly as SPARQL. We will include the definition of CURIES inline with the RDFa 
syntax, though we may eventually choose to refer to the CURIE doc instead."</text>
</note>
</notes>
</issue>
<issue>
<id>56</id>
<title>ReferenceSemanticRelationshipSpecializations</title>
<product>3</product>
<raisedby>5</raisedby>
<created>2007-07-03</created>
<description>Additionally to guidelines on how to create custom extensions to SKOS (ISSUE-37,
[1]) the WG could take the responsability to publish a reference list of
semantic relationships mirroring established needs like [2,3]

Currently there is a proposal containing 8 such specializations for SKOS
broader, narrower and related properties [4]:  
- broaderGeneric
- broaderInstantive
- broaderPartitive
- narrowerGeneric
- narrowerInstantive
- narrowerPartitive
- relatedHasPart
- relatedPartOf

Are these enough, are some of these not needed?

References:
[1] http://www.w3.org/2006/07/SWD/track/issues/37 
[2] http://lists.w3.org/Archives/Public/public-swd-wg/2007Jun/0216.html 
[3] http://lists.w3.org/Archives/Public/public-swd-wg/2007Jun/0120.html 
[4] http://www.w3.org/2004/02/skos/extensions/spec/


</description>
<state>4</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20070703161338.0366047BA3@mojo.w3.org</uri>
<subject>ISSUE-56: ReferenceSemanticRelationshipSpecializations</subject>
<sender>dean+cgi@w3.org</sender>
<date>2007-07-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070822065936.GA2376@Octavius</uri>
<subject>[ALL] SWD face-to-face - draft agenda</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-08-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D033D4F83@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [ALL] SWD face-to-face - draft agenda</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-08-24</date>
</email>
<email>
<uri>http://www.w3.org/mid/46D2E6F9.1070403@few.vu.nl</uri>
<subject>Re: [ALL] SWD face-to-face - draft agenda</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-08-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D03B3F206@exchange11.fed.cclrc.ac.uk</uri>
<subject>[SKOS] top priorities</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-11-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/478B5599.8070104@few.vu.nl</uri>
<subject>Re: AW: AW: [SKOS] Transitive broader and ISSUE-56 (was The return  of ISSUE-44 )</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-14</date>
</email>
<email>
<uri>http://www.w3.org/mid/D1E85BF9-6DD9-46F1-BFC0-E7495CD99122@madcreek.com</uri>
<subject>Re: AW: AW: [SKOS] Transitive broader and ISSUE-56 (was The return  of ISSUE-44 )</subject>
<sender>jphipps@madcreek.com</sender>
<date>2008-01-14</date>
</email>
<email>
<uri>http://www.w3.org/mid/A1C143B9-31FB-478E-88CB-812E99D5AA90@gmail.com</uri>
<subject>Re: AW: AW: [SKOS] Transitive broader and ISSUE-56 (was The return  of ISSUE-44 )</subject>
<sender>sesuncedu@gmail.com</sender>
<date>2008-01-14</date>
</email>
<email>
<uri>http://www.w3.org/mid/478B8CCE.9090008@few.vu.nl</uri>
<subject>Re: AW: AW: [SKOS] Transitive broader and ISSUE-56 (was The return   of ISSUE-44 )</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-14</date>
</email>
<email>
<uri>http://www.w3.org/mid/478B90FC.10804@few.vu.nl</uri>
<subject>Re: AW: AW: [SKOS] Transitive broader and ISSUE-56 (was The return   of ISSUE-44 )</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-14</date>
</email>
<email>
<uri>http://www.w3.org/mid/1af06bde0801140908x481af966xac40c59e228ea32a@mail.gmail.com</uri>
<subject>Re: AW: AW: [SKOS] Transitive broader and ISSUE-56 (was The return of ISSUE-44 )</subject>
<sender>sesuncedu@gmail.com</sender>
<date>2008-01-14</date>
</email>
<email>
<uri>http://www.w3.org/mid/478B9B21.7030100@few.vu.nl</uri>
<subject>Re: AW: AW: [SKOS] Transitive broader and ISSUE-56 (was The return  of ISSUE-44 )</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-14</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB669029DAE64@hqgiex01.fao.org</uri>
<subject>RE: [SKOS] Transitive broader and ISSUE-56 (was The return of ISSUE-44  )</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-01-14</date>
</email>
<email>
<uri>http://www.w3.org/mid/6.2.5.6.2.20080114184316.02ddb6c8@med.stanford.edu</uri>
<subject>RE: [SKOS] Transitive broader and ISSUE-56 (was The return of   ISSUE-44  )</subject>
<sender>rubin@med.stanford.edu</sender>
<date>2008-01-14</date>
</email>
<email>
<uri>http://www.w3.org/mid/478C8BA1.3080201@few.vu.nl</uri>
<subject>Re: AW: AW: [SKOS] Transitive broader and ISSUE-56 (was The return   of ISSUE-44 )</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/003001c856d5$12d30060$6702a8c0@TFJOHAN</uri>
<subject>RE: AW: AW: [SKOS] Transitive broader and ISSUE-56 (was The return  of ISSUE-44 )</subject>
<sender>johan.de-smedt@tenforce.com</sender>
<date>2008-01-14</date>
</email>
<email>
<uri>http://www.w3.org/mid/658901D9-165C-4046-9D96-FCE68332B367@gmail.com</uri>
<subject>Re: AW: AW: [SKOS] Transitive broader and ISSUE-56 (was The return of ISSUE-44 )</subject>
<sender>sesuncedu@gmail.com</sender>
<date>2008-01-24</date>
</email>
<email>
<uri>http://www.w3.org/mid/4799C6D9.8000907@few.vu.nl</uri>
<subject>[SKOS] Re: Review of the SKOS Primer</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-25</date>
</email>
<email>
<uri>http://www.w3.org/mid/4799E003.1020806@few.vu.nl</uri>
<subject>Re: AW: AW: [SKOS] Transitive broader and ISSUE-56 (was The return  of ISSUE-44 )</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-25</date>
</email>
<email>
<uri>http://www.w3.org/mid/2AD2401FC36E784094D0B3375FDA6CE802C2BA9C@VMAIL2.uoa.abdn.ac.uk</uri>
<subject>RE: [SKOS] Re: Review of the SKOS Primer</subject>
<sender>q.reul@abdn.ac.uk</sender>
<date>2008-01-25</date>
</email>
<email>
<uri>http://www.w3.org/mid/479E554A.4020607@few.vu.nl</uri>
<subject>Re: [SKOS] Re: Review of the SKOS Primer</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-28</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB66903408403@hqgiex01.fao.org</uri>
<subject>Several emails to reply to</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-02-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD72BB.1010906@zoo.ox.ac.uk</uri>
<subject>[Fwd: [SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD9D4A.2090301@zoo.ox.ac.uk</uri>
<subject>[SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB66903B87AC7@hqgiex01.fao.org</uri>
<subject>List of resolutions from the Face-to-Face meeting</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-05-13</date>
</email>
<email>
<uri>http://www.w3.org/mid/482ADFEC.9070001@cs.vu.nl</uri>
<subject>Re: List of resolutions from the Face-to-Face meeting</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2008-05-14</date>
</email>
</emails>
<notes>
<note>
<date>2008-05-07</date>
<text>RESOLVED: To postpone Reference Semantic Relation Specialisations (ISSUE-56)
becuase we do not yet have sufficient information on how to embed these
specializations in the current SKOS model
-- http://www.w3.org/2008/05/07-swd-minutes.html#item02</text>
</note>
</notes>
</issue>
<issue>
<id>57</id>
<title>xml:base meaningful in XHTML1.1+RDFa?</title>
<product>2</product>
<raisedby>6</raisedby>
<created>2007-07-05</created>
<description>xml:base may present problem with clickability of links.</description>
<state>2</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20070705161543.CB6923320A@kearny.w3.org</uri>
<subject>ISSUE-57: xml:base meaningful in XHTML1.1+RDFa?</subject>
<sender>dean+cgi@w3.org</sender>
<date>2007-07-05</date>
</email>
</emails>
</issue>
<issue>
<id>58</id>
<title>.htaccess 'accept header' ONLY responds to a header which EXACTLY matches </title>
<product>5</product>
<raisedby>18</raisedby>
<created>2007-07-17</created>
<description>Per Tim BL

"The recipe for responding to an accept header only responds to a header which
EXACTLY matches "application/rdf+xml". However, a client may send (and often
will) a header with many  comma-separated values, and they may have quality
parameters (q=0.xx).

This is a serious problem as people are copying the recipe, and making sites
which do not work."

This applies to Recipes 3, 4, 5 and references this part of the .htaccess Apache
configuration:

"...

# Rewrite rule to serve RDF/XML content if requested 
RewriteCond %{HTTP_ACCEPT} application/rdf\+xml

..."

The rewrite condition regular expression: "application/rdf\+xml" 
needs to be rewritten
</description>
<state>0</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20070717121239.2E01B6B644@kent.w3.org</uri>
<subject>ISSUE-58: .htaccess \\'accept header\\' ONLY responds to a header which EXACTLY matches \\'application/rdf+xml\\'</subject>
<sender>dean+cgi@w3.org</sender>
<date>2007-07-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/1184768175.4685.76.camel@duncan.fundacionctic.org</uri>
<subject>Re: [Recipes] ISSUE-58: .htaccess 'accept header' ONLY responds to 	a header which EXACTLY matches \\'application/rdf+xml\\'</subject>
<sender>diego.berrueta@fundacionctic.org</sender>
<date>2007-07-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D030E4485@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [Recipes] ISSUE-58: .htaccess 'accept header' ONLY responds to 	a header which EXACTLY matches \\'application/rdf+xml\\'</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-07-24</date>
</email>
<email>
<uri>http://www.w3.org/mid/1185359793.4730.49.camel@duncan.fundacionctic.org</uri>
<subject>Re: [Recipes] ISSUE-58: .htaccess 'accept header' ONLY responds to 	a header which EXACTLY matches \\'application/rdf+xml\\'</subject>
<sender>diego.berrueta@fundacionctic.org</sender>
<date>2007-07-25</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D030E460A@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: [Recipes] ISSUE-58: .htaccess 'accept header' ONLY responds to 	a header which EXACTLY matches \\'application/rdf+xml\\'</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-07-30</date>
</email>
<email>
<uri>http://www.w3.org/mid/1186424707.9838.27.camel@daneel.berrueta.net</uri>
<subject>RE: [Recipes] ISSUE-58: .htaccess 'accept header' ONLY responds to 	a header which EXACTLY matches \\'application/rdf+xml\\'</subject>
<sender>diego.berrueta@fundacionctic.org</sender>
<date>2007-08-06</date>
</email>
<email>
<uri>http://www.w3.org/mid/1188919889.5666.29.camel@duncan.fundacionctic.org</uri>
<subject>Re: Agenda - Sep 04 2007 SWD telecon - 1500 UTC</subject>
<sender>diego.berrueta@fundacionctic.org</sender>
<date>2007-09-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070904144244.GB1040@sub-tombaker</uri>
<subject>[ALL] Discussion of 'Recipes' in Amsterdam</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-09-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070915142535.GA680@Octavius</uri>
<subject>[ALL] Agenda - Sep 18 2007 SWD telecon - 1500 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-09-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/20070915150038.GG2612@Octavius</uri>
<subject>[RECIPES] Amsterdam topic 'Recipes'</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2007-09-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/bd1d3fc00709180239m41ab82d3v39701872d80381b9@mail.gmail.com</uri>
<subject>Re: [ALL] Agenda - Sep 18 2007 SWD telecon - 1500 UTC</subject>
<sender>qreul@csd.abdn.ac.uk</sender>
<date>2007-09-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/46EF9DF6.9050006@few.vu.nl</uri>
<subject>Re: [ALL] Agenda - Sep 18 2007 SWD telecon - 1500 UTC</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-09-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/1205246076.4829.11.camel@duncan.fundacionctic.org</uri>
<subject>[Recipes] roadmap to the next draft</subject>
<sender>diego.berrueta@fundacionctic.org</sender>
<date>2008-03-11</date>
</email>
<email>
<uri>http://www.w3.org/mid/B0AAC07C-6A27-421A-8E62-523A40EC6D0A@madcreek.com</uri>
<subject>Re: [Recipes] roadmap to the next draft</subject>
<sender>jphipps@madcreek.com</sender>
<date>2008-03-11</date>
</email>
<email>
<uri>http://www.w3.org/mid/47D83672.7040701@few.vu.nl</uri>
<subject>Meeting record: 2008-03-11 telecon</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-03-12</date>
</email>
</emails>
</issue>
<issue>
<id>59</id>
<title>xml:base support</title>
<product>2</product>
<raisedby>14</raisedby>
<created>2007-08-10</created>
<description>Does RDFa (regarding a certain hostlanguage: HTML 4, XHTML1, XHTML2) support 
the usage of xml:base?

See Also and Related:
 + Ivan has asked for xml:base in the Test Cases [1]
 + As Shane points out [2], the decision to support xml:base would have far-
reaching ramifications (cf. also his action [3])

[1] http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2007Aug/0038.html
[2] http://www.w3.org/2007/08/09-rdfa-irc#T15-16-05
[3] http://www.w3.org/2007/06/28-rdfa-minutes.html#action02</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20070810193650.E8F5DC235@nelson.w3.org</uri>
<subject>ISSUE-59: xml:base support</subject>
<sender>dean+cgi@w3.org</sender>
<date>2007-08-10</date>
</email>
</emails>
<notes>
<note>
<date>2007-08-16</date>
<text>opened on 2007-08-16</text>
</note>
<note>
<date>2007-08-23</date>
<text>As per discussion and resolution on telecon:

http://www.w3.org/2007/08/16-rdfa-minutes.html

xml:base is not supported in XHTML 1.1 + RDFa, as it has no effect on @href.

In general, this is dependent on the host language's use of xml:base.</text>
</note>
</notes>
</issue>
<issue>
<id>60</id>
<title>Guidelines needed for proper construction of vocabulary scheme and 'term' URIs</title>
<product>5</product>
<raisedby>18</raisedby>
<created>2007-09-18</created>
<description>The recipes don't spend very much time discussing best practices for URI
construction for vocabulary schemes and 'terms'.

Based on a request by the International Press Telecommunications Council:
http://lists.w3.org/Archives/Public/public-swd-wg/2007Sep/0023.html

They are seeking guidance wrt construction of URIs to identify taxonomy schemes
and "terms". They have two questions:

1.  Should we opt for "#" or "#_" or "/" or "?" or "?&lt;foo&gt;=" or 
    some other string as the scheme URI terminator?

2.  What mechanism should we adopt for constructing code URIs?
(By "Code URIs" they mean a mapping of URI to existing term codes: "...we
decided to continue using the large number of existing codes that are used in
News and related industries today.")

Below is the full text of the email that raised the questions:

Introduction
------------

Below is a draft statement of matters on which the International 
Press Telecommunications Council [1] seeks help from the W3C and 
from the broader Semantic Web community.

The statement hasn't yet been reviewed by the relevant IPTC 
groups, but to save time I'm sending it in draft form.  We would 
very much like to have these matters resolved by the time of the 
next IPTC meeting on 15-17 October 2007, in Prague.


Background
----------

The IPTC decided a few years ago that its new G2 family of News 
Exchange standards must be compatible with the Semantic Web.  We 
decided that:

1.  Terms from taxonomies used for News would be associated with 
    individual URIs.

2.  We would encourage the use of GRDDL to convert News marked 
    up with metadata into forms understood by SemWeb tools.

At the same time we decided to continue using the large number 
of existing codes that are used in News and related industries 
today.

To reconcile these two requirements (SemWeb plus existing codes), 
we chose an approach somewhat similar to QNAMEs, though with 
several significant differences. The approach is:

-  Codes exist within (coding) schemes.  Familiar examples are:
      ISO 4217 alpha codes
      ISO 4217 numeric codes
      ISO 3166-1 two-letter alpha codes
      ISO 3166-1 three-letter alpha codes
      ISO 3166-1 numeric alpha codes
      IETF BCP 47 language tags

    Possibly less familar examples are:
      CUSIPs (eg "037833100", Apple Computer)
      ISBNs(eg "0-321-18578-1", The Unicode Standard, Version 4.0)
      ISSNs (eg "0261-3077", The Guardian)
      SEDOLs (eg "0263494", BAE Systems)
      Valorens (eg "1203203", UBS)

-  Each coding scheme is associated with a URI.  That URI *must* 
   resolve to a resource (or resources) containing information 
   about the scheme.

-  Each scheme URI is locally mapped to a prefix.

-  There are almost no constraints on the values of codes.  For 
   example, a code may start with a digit.

-  A qualified code (QCODE) is expressed in the form:
      prefix:code

-  We shall define rules for how scheme URIs should be terminated.
   These rules may take the form of guidelines.

-  We shall define rules for the construction of a code URI from 
   the corresponding scheme URI and the code.  These rules may or 
   may not specify simple concatenation.

-  In the case of schemes controlled by the News industry, each 
   code URI *must* resolve to a resource or (content negotiated) 
   resources containing information about the code.

-  In the case of schemes used but not not controlled by the News 
   industry, each code URI *should* resolve to a resource or 
   (content negotiated) resources containing information about 
   the code.


Matters we need help with
-------------------------

1.  Should we opt for "#" or "#_" or "/" or "?" or "?&lt;foo&gt;=" or 
    some other string as the scheme URI terminator?

2.  What mechanism should we adopt for constructing code URIs?

    Simple concatenation would work for (made up) URIs such as:
       www.iptc.org/taxonomies/subjects#_
       www.iptc.org/taxonomies/subjects/
       www.iptc.org/taxonomies/subjects?
       www.iptc.org/taxonomies/subjects?code=

    It would not work for:
       www.iptc.org/taxonomies/subjects#
    as the resulting URI would not be legal for HTML if the code 
    started with a digit.

    The alternative is to inject some buffer string during the 
    construction of the code URI.  This would probably have to be 
    a fixed string for all News taxonomies, as the alternative of 
    retrieving (from the scheme URI?) per-scheme rules seems too 
    burdensome for the recipient.

    Such a string could be, eg "_", so allowing a scheme URI such 
    as:
       www.iptc.org/taxonomies/subjects#
    and a code URI such as:
       www.iptc.org/taxonomies/subjects#_12345678

    Alternatively, such a string could be, eg "#_", so allowing a 
    scheme URI such as:
       www.iptc.org/taxonomies/subjects
    and a code URI such as:
       www.iptc.org/taxonomies/subjects#_12345678

    The disadvantage of both approaches is that such a rule would 
    make it difficult for people to use scheme URIs such as:
       www.iptc.org/taxonomies/subjects/
       www.iptc.org/taxonomies/subjects?
       www.iptc.org/taxonomies/subjects?code=

3.  We would very much appreciate help in developing a GRDDL 
    script for our G2 standards.  Nearly two years ago we 
    developed a script to convert NewsML-G2 to RDF triples 
    (N-Triples).  We were not, however, able to figure out how to 
    handle statements about statements.  Note that for each piece 
    of descriptive metadata we support attributes such as:
       creator
       date modified
       confidence
       relevance
       why present

    Thus one can, losely speaking, express:

       On 7 September 2007, Reuters stated that this News item 
       has a subject of:
       -  George W. Bush (with 60% confidence)
       -  George H. W. Bush (with 40% confidence)

    We appreciate that the best way to handle statements about 
    statements may still be unresolved within the SemWeb 
    community.

4.  We request that the W3C and the broader Semantic Web 
    community take our requirements into consideration in the 
    development of new specifications and tools, and in the 
    enhancement of existing ones.  We are aware that some of 
    these assume particular URI formats, eg the presence of a "#" 
    as a separator or the absence of a digit after such a "#".

[1] http://www.iptc.org/

Thank you

Misha Wolf
News Standards Manager
Reuters

</description>
<state>2</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20070918151812.A5BD0C6DA3@barney.w3.org</uri>
<subject>ISSUE-60: Guidelines needed for proper construction of vocabulary scheme and \\'term\\' URIs</subject>
<sender>dean+cgi@w3.org</sender>
<date>2007-09-18</date>
</email>
</emails>
</issue>
<issue>
<id>61</id>
<title>namespace for non-prefixed values of @rel</title>
<product>2</product>
<raisedby>6</raisedby>
<created>2007-10-04</created>
<description>We've been dancing around the following for a while:
PROPOSAL - "RDFa parsers should ignore non-prefixed values of @rel that
are not part o the reserved words."

See telecon discussion record of 2007-10-04
http://www.w3.org/2007/10/04-rdfa-minutes.html</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20071004154436.2DEF45F70B@stu.w3.org</uri>
<subject>ISSUE-61: namespace for non-prefixed values of @rel</subject>
<sender>dean+cgi@w3.org</sender>
<date>2007-10-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/470514CF.4060706@w3.org</uri>
<subject>Re: ISSUE-61: namespace for non-prefixed values of @rel</subject>
<sender>ivan@w3.org</sender>
<date>2007-10-04</date>
</email>
</emails>
<notes>
<note>
<date>2008-02-06</date>
<text>resolved as follows:

"@rel/@rev non-prefixed values other than reserved keywords are ignored.
Reserved keywords resolve to vocab#[keyword]."

as per telecon on 2008-01-24: http://www.w3.org/2008/01/24-rdfa-minutes.html</text>
</note>
</notes>
</issue>
<issue>
<id>62</id>
<title>phentermine</title>
<product>2</product>
<raisedby>20</raisedby>
<created>2007-11-06</created>
<description>New information about this medication! &lt;a
href="http://agtc.wayne.edu/agtc/portal_memberdata/portraits/phen"&gt; &lt;b&gt;
phentermine &lt;/b&gt; &lt;/a&gt; phentermine
[url=http://agtc.wayne.edu/agtc/portal_memberdata/portraits/phen] phentermine
[/url] http://agtc.wayne.edu/agtc/portal_memberdata/portraits/phen phentermine
&lt;a href=" http://agtc.wayne.edu/agtc/portal_memberdata/portraits/phen "&gt;
phentermine &lt;/a&gt;</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20071106021319.372236B5EA@tibor.w3.org</uri>
<subject>ISSUE-62: phentermine</subject>
<sender>dean+cgi@w3.org</sender>
<date>2007-11-06</date>
</email>
</emails>
<notes>
<note>
<date>2007-11-06</date>
<text>spam -- identified to sysreq on 6-Nov by R. Swick to find the hole</text>
</note>
</notes>
</issue>
<issue>
<id>63</id>
<title>White-Space Canonicalization of XML Literals</title>
<product>2</product>
<raisedby>6</raisedby>
<created>2007-11-09</created>
<description>There is  question as to what canonicalization of white-space literals we should
do, as per this thread:

http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2007Nov/0000.html

The XPath normalize-space() function can be used on plain literals, but there
are issues to discuss for XML 
Literals, as per Ivan's point:

http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2007Oct/0173.html
</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20071109025325.6878F6B62B@kent.w3.org</uri>
<subject>ISSUE-63: White-Space Canonicalization of XML Literals</subject>
<sender>dean+cgi@w3.org</sender>
<date>2007-11-09</date>
</email>
</emails>
<notes>
<note>
<date>2008-02-19</date>
<text>2008-02-14 [RRS] http://www.w3.org/2008/02/14-rdfa-minutes.html
RESOLUTION: RDFa will state that whitespace is preserved and note that some
implementations might not behave this way</text>
</note>
<note>
<date>2008-02-19</date>
<text>Manu tested several Javascript implementations for XML Literal and reported his
results in
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2007Nov/0022.html
[[
In short - Firefox's implementation allows you to retrieve the original
whitespace and line breaks using Javascript. IE7 does not.

IE7 normalizes all of the whitespace before inserting it into the DOM,
which means that Javascript does not have access to the original text in
the XHTML file.
]]</text>
</note>
<note>
<date>2008-02-19</date>
<text>[RRS] Niklas Lindström followed up Manu's tests in IE7 in more detail and
reported in
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2007Nov/0027.html
[[
I just did these quick tests in case the capabilities of IE7 is what
would put an end to any hope of keeping non-canonicalized XMLLiterals.
There seems to be some  possibilities, but perhaps not stable enough?
So if nothing else, it should be noted that requiring normalized space
from RDFa parsers in such a case would require manual processing (DOM
walking + normalizing) in some (at least non-XHTML-aware..) client
implementations.
]]</text>
</note>
<note>
<date>2008-02-19</date>
<text>[2007-11-15] telecon discussion record in
http://www.w3.org/2007/11/15-rdfa-minutes.html#item04 -
RESOLVED plain literals are normalized using XPath normalized-space
...
[[
Ben: for XMLLiterals, I'd like us to preserve them if we can
... but if browsers do canonicalize, I think we have to allow it
... I don't expect canonicalization to change how the literal is rendered
... conclusion; we'll normalize plain literals and element content but not
normalize @content value except perhaps for special rule about leading newlines
depending on what browsers do
]]</text>
</note>
</notes>
</issue>
<issue>
<id>65</id>
<title>XMLLiteralNotes</title>
<product>3</product>
<raisedby>8</raisedby>
<created>2007-11-20</created>
<description>How do you annotate concepts with different types of XML content? 

Some use cases might be...

(1) "E=MC&lt;sup&gt;2&lt;/sup&gt;" -- Text using XHTML for basic styling (superscript,
subscript etc.)

(2) MathML for complex mathematical formulas.

(3) Text or XHTML content marked up with Ruby annotations.

(4) Speech Synthesis Markup (SSML)

</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20071120145658.3A8B76B62B@kent.w3.org</uri>
<subject>ISSUE-65: XMLLiteralNotes</subject>
<sender>dean+cgi@w3.org</sender>
<date>2007-11-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D03B3F206@exchange11.fed.cclrc.ac.uk</uri>
<subject>[SKOS] top priorities</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2007-11-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/474316D0.5040209@few.vu.nl</uri>
<subject>Re: ISSUE-65: XMLLiteralNotes</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2007-11-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/47B8B1FB.1030902@few.vu.nl</uri>
<subject>[SKOS] Issues Review [From Alistair]</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD72BB.1010906@zoo.ox.ac.uk</uri>
<subject>[Fwd: [SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD9D4A.2090301@zoo.ox.ac.uk</uri>
<subject>[SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080415154659.GA4980@octavius</uri>
<subject>[SKOS] Issue owners - preparation for Washington</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2008-04-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/480C7E67.9090901@few.vu.nl</uri>
<subject>Re: [SKOS] Issue owners - preparation for Washington</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-04-21</date>
</email>
</emails>
<notes>
<note>
<date>2008-05-07</date>
<text>This isue is conderied out of scope
http://www.w3.org/2008/05/06-swd-minutes.html#xmlliterals</text>
</note>
</notes>
</issue>
<issue>
<id>66</id>
<title>What is the Subject of @instanceof ?</title>
<product>2</product>
<raisedby>2</raisedby>
<created>2007-11-29</created>
<description>To what node does the instanceof attribute apply?

From Manu's summary [1], which of the following options do we choose:

(a) @instanceof applies to the current element it is defined on.
(b) @instanceof applies to the chaining node.

[1] http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2007Nov/0044.html

See most recent (as of 2007-11-29) threads:
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2007Nov/0001.html
"@about/@instanceof discussion"
and
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2007Nov/thread.html#msg30
 "chaining-friendly rules for @instanceof"</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20071129162419.D26385F70A@stu.w3.org</uri>
<subject>ISSUE-66: What is the Subject of @instanceof ?</subject>
<sender>dean+cgi@w3.org</sender>
<date>2007-11-29</date>
</email>
</emails>
<notes>
<note>
<date>2008-02-06</date>
<text>resolved as:

"@href/@resource without @rel/@rev/@about sets the subject for @instanceof on
same element."

Note related resolution:

"@href/@resource without @rel/@rev/@about sets the subject for @property on the
same element."

all on 2008-01-24: http://www.w3.org/2008/01/24-rdfa-minutes.html</text>
</note>
</notes>
</issue>
<issue>
<id>67</id>
<title>StatingFormalDefinitions</title>
<product>3</product>
<raisedby>8</raisedby>
<created>2008-01-08</created>
<description>In the SKOS Reference Editor's Draft 23 December 2007 [1], the formal class and
property definitions, and the integrity conditions, are stated in the main body
of the document as prose. 

For example, from section 4.3:

 "skos:ConceptScheme has type Class."

 "skos:inScheme, skos:hasTopConcept habe type Object Property."

 "skos:ConceptScheme is Disjoint with skos:Concept."

For example, from section 7.3:

 "The Domain and Range of skos:semanticRelation is skos:Concept."

This style of stating the formal definitions is potentially confusing. To reduce
confusion, should the formal definitions be stated instead using prose in some
other style (e.g. as in the RDFS spec [2])? Or as triples, wherever possible? Or
something else? 

[1] http://www.w3.org/2006/07/SWD/SKOS/reference/20071223
[2] http://www.w3.org/TR/2004/REC-rdf-schema-20040210/</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/2AD2401FC36E784094D0B3375FDA6CE8028EE7D1@VMAIL2.uoa.abdn.ac.uk</uri>
<subject>ISSUE-67: StatingFormalDefinitions</subject>
<sender>q.reul@abdn.ac.uk</sender>
<date>2008-01-08</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D0499DAA4@exchange11.fed.cclrc.ac.uk</uri>
<subject>ISSUE-67: StatingFormalDefinitions (was: Comments on SKOS Reference)</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2008-01-08</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080108150235.37D2B5F70B@stu.w3.org</uri>
<subject>ISSUE-67: StatingFormalDefinitions</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-01-08</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB6690269F968@hqgiex01.fao.org</uri>
<subject>RE: ISSUE-67: StatingFormalDefinitions</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-01-14</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D0499DF7B@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: Comments on SKOS Reference</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2008-01-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/47B8B1FB.1030902@few.vu.nl</uri>
<subject>[SKOS] Issues Review [From Alistair]</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD72BB.1010906@zoo.ox.ac.uk</uri>
<subject>[Fwd: [SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD9D4A.2090301@zoo.ox.ac.uk</uri>
<subject>[SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/f032cc060803011003j16953aei9318c574bc410f2b@mail.gmail.com</uri>
<subject>Meeting Record: 2008-02-27 SWD telecon</subject>
<sender>ehs@pobox.com</sender>
<date>2008-03-01</date>
</email>
<email>
<uri>http://www.w3.org/mid/47D514FD.5060104@zoo.ox.ac.uk</uri>
<subject>[SKOS] ISSUE-67 StatingFormalDefinitions</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-03-10</date>
</email>
<email>
<uri>http://www.w3.org/mid/47E11ECC0200006A00024B85@ntgwgate.loc.gov</uri>
<subject>Minutes from 2008-03-18 telecon</subject>
<sender>cred@loc.gov</sender>
<date>2008-03-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080415154659.GA4980@octavius</uri>
<subject>[SKOS] Issue owners - preparation for Washington</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2008-04-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/480C7E67.9090901@few.vu.nl</uri>
<subject>Re: [SKOS] Issue owners - preparation for Washington</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-04-21</date>
</email>
</emails>
<notes>
<note>
<date>2008-01-08</date>
<text>See also mail from Tom Baker:
http://lists.w3.org/Archives/Public/public-swd-wg/2008Jan/0000.html </text>
</note>
<note>
<date>2008-01-15</date>
<text>Better formal specifications for Turtle and N3 were published yesterday:
http://www.w3.org/TeamSubmission/2008/SUBM-turtle-20080114/
http://www.w3.org/TeamSubmission/2008/SUBM-n3-20080114/

I recommend using those citations for whichever of Turtle or N3 is chosen.</text>
</note>
<note>
<date>2008-01-15</date>
<text>[rrs]
sigh.  "I recommend" in the note above is me, Ralph.</text>
</note>
<note>
<date>2008-04-14</date>
<text>RESOLVED: To state formal aspects of the SKOS data model in the main body of the
SKOS Reference as sentences of prose following the style of prose used in the
RDF Schema specification &lt;http://www.w3.org/TR/2004/REC-rdf-schema-20040210/&gt;.
An OWL ontology will also be given as an appendix to the SKOS Reference, however
the prose in the main body of the SKOS Reference will take precedence. -- 
http://lists.w3.org/Archives/Public/public-swd-wg/2008Mar/0027.html.

For resolution decision, see http://www.w3.org/2008/03/18-swd-minutes.html</text>
</note>
</notes>
</issue>
<issue>
<id>68</id>
<title>RelatedIrreflexive</title>
<product>3</product>
<raisedby>8</raisedby>
<created>2008-01-16</created>
<description>Currently, skos:related is *not* defined as an irreflexive property.

Therefore, graphs such as:

&lt;A&gt; skos:related &lt;A&gt; .

... are consistent with the SKOS data model.

However, such a graph would never be found in a representation of a thesaurus 
or classification scheme, and if it did, would probably indicate some sort of 
error.

If skos:related were formally defined as an irreflexive property in the 
normative specification, this would endorse stronger checking of instance data 
against the SKOS data model, which would probably be both useful and 
appropriate to most SKOS use cases.

Should skos:related be normatively irreflexive?</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080116150111.1A9F7BEF0@nelson.w3.org</uri>
<subject>ISSUE-68: RelatedIrreflexive</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-01-16</date>
</email>
<email>
<uri>http://www.w3.org/mid/478E1F87.6040001@few.vu.nl</uri>
<subject>Re: ISSUE-68: RelatedIrreflexive</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-16</date>
</email>
<email>
<uri>http://www.w3.org/mid/47B8B1FB.1030902@few.vu.nl</uri>
<subject>[SKOS] Issues Review [From Alistair]</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD72BB.1010906@zoo.ox.ac.uk</uri>
<subject>[Fwd: [SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD9D4A.2090301@zoo.ox.ac.uk</uri>
<subject>[SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080415154659.GA4980@octavius</uri>
<subject>[SKOS] Issue owners - preparation for Washington</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2008-04-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/480C7E67.9090901@few.vu.nl</uri>
<subject>Re: [SKOS] Issue owners - preparation for Washington</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-04-21</date>
</email>
</emails>
<notes>
<note>
<date>2008-05-07</date>
<text>http://www.w3.org/2008/05/06-swd-minutes.html#irreflexive

RESOLUTION: to resolve skos:related, skos:broader and skos:broaderTransitive are
not normatively irreflexive</text>
</note>
</notes>
</issue>
<issue>
<id>69</id>
<title>BroaderIrreflexive</title>
<product>3</product>
<raisedby>8</raisedby>
<created>2008-01-16</created>
<description>This is a sub-issue of ISSUE-44.

Currently, skos:broader is *not* defined as an irreflexive property.

Therefore, graphs such as:

&lt;A&gt; skos:broader &lt;A&gt; .

... are consistent with the SKOS data model.

However, such a graph would never be found in a representation of a thesaurus 
or classification scheme, and if it did, would probably indicate some sort of 
error.

If skos:broader were formally defined as an irreflexive property in the 
normative specification, this would endorse stronger checking of instance data 
against the SKOS data model, which would probably be both useful and 
appropriate to most SKOS use cases.

Should skos:broader be normatively irreflexive?</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080116153050.38D2CBEF0@nelson.w3.org</uri>
<subject>ISSUE-69: BroaderIrreflexive</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-01-16</date>
</email>
<email>
<uri>http://www.w3.org/mid/478E245D.7090403@few.vu.nl</uri>
<subject>Re: ISSUE-69: BroaderIrreflexive</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-16</date>
</email>
<email>
<uri>http://www.w3.org/mid/47971236.404@few.vu.nl</uri>
<subject>Re: ISSUE-69: BroaderIrreflexive</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-23</date>
</email>
<email>
<uri>http://www.w3.org/mid/D79DD37AAC57EB4582A756C175CEB8890170AA3F@KFSVS1.utk.tennessee.edu</uri>
<subject>Comment: ISSUE-69</subject>
<sender>rde2@utk.edu</sender>
<date>2008-02-10</date>
</email>
<email>
<uri>http://www.w3.org/mid/47B8B1FB.1030902@few.vu.nl</uri>
<subject>[SKOS] Issues Review [From Alistair]</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD72BB.1010906@zoo.ox.ac.uk</uri>
<subject>[Fwd: [SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD9D4A.2090301@zoo.ox.ac.uk</uri>
<subject>[SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080415154659.GA4980@octavius</uri>
<subject>[SKOS] Issue owners - preparation for Washington</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2008-04-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/480C7E67.9090901@few.vu.nl</uri>
<subject>Re: [SKOS] Issue owners - preparation for Washington</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-04-21</date>
</email>
</emails>
<notes>
<note>
<date>2008-05-07</date>
<text>http://www.w3.org/2008/05/06-swd-minutes.html#irreflexive

RESOLUTION: to resolve skos:related, skos:broader and skos:broaderTransitive are
not normatively irreflexive</text>
</note>
</notes>
</issue>
<issue>
<id>70</id>
<title>BroaderCycles</title>
<product>3</product>
<raisedby>8</raisedby>
<created>2008-01-16</created>
<description>This is a sub-issue of ISSUE-44.

Currently, skos:broaderTransitive is *not* defined as an irreflexive property.

Therefore, graphs such as:

&lt;A&gt; skos:broader &lt;B&gt; .
&lt;B&gt; skos:broader &lt;A&gt; .

... are consistent with the SKOS data model.

However, such a graph would never be found in a representation of a thesaurus 
or classification scheme, and if it did, would probably indicate some sort of 
error.

If skos:broaderTransitive were formally defined as an irreflexive property in 
the normative specification, this would endorse stronger checking of instance 
data against the SKOS data model, which would probably be both useful and 
appropriate to most SKOS use cases.

Should skos:broaderTransitive be normatively irreflexive?</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080116153440.4745C5F70C@stu.w3.org</uri>
<subject>ISSUE-70: BroaderCycles</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-01-16</date>
</email>
<email>
<uri>http://www.w3.org/mid/478F2594.7020002@few.vu.nl</uri>
<subject>Re: ISSUE-70: BroaderCycles</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/D79DD37AAC57EB4582A756C175CEB8890170AA40@KFSVS1.utk.tennessee.edu</uri>
<subject>Comment:  ISSUE-70</subject>
<sender>rde2@utk.edu</sender>
<date>2008-02-10</date>
</email>
<email>
<uri>http://www.w3.org/mid/99BBE409-1A4A-475C-9C9D-685678AC33FC@manchester.ac.uk</uri>
<subject>Re: Comment:  ISSUE-70</subject>
<sender>sean.bechhofer@manchester.ac.uk</sender>
<date>2008-02-12</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB669029DAF18@hqgiex01.fao.org</uri>
<subject>RE: Comment:  ISSUE-70</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-02-12</date>
</email>
<email>
<uri>http://www.w3.org/mid/D79DD37AAC57EB4582A756C175CEB8890170AED4@KFSVS1.utk.tennessee.edu</uri>
<subject>RE: Comment:  ISSUE-70</subject>
<sender>rde2@utk.edu</sender>
<date>2008-02-12</date>
</email>
<email>
<uri>http://www.w3.org/mid/7728477E-2627-4254-AA7E-AA21DB96CF05@manchester.ac.uk</uri>
<subject>Re: Comment:  ISSUE-70</subject>
<sender>sean.bechhofer@manchester.ac.uk</sender>
<date>2008-02-12</date>
</email>
<email>
<uri>http://www.w3.org/mid/D79DD37AAC57EB4582A756C175CEB8890170AF2C@KFSVS1.utk.tennessee.edu</uri>
<subject>RE: Comment:  ISSUE-70</subject>
<sender>rde2@utk.edu</sender>
<date>2008-02-12</date>
</email>
<email>
<uri>http://www.w3.org/mid/56EA6C1D-AB3C-4565-BA7F-85A5EB353E79@manchester.ac.uk</uri>
<subject>Re: Comment:  ISSUE-70</subject>
<sender>sean.bechhofer@manchester.ac.uk</sender>
<date>2008-02-13</date>
</email>
<email>
<uri>http://www.w3.org/mid/D79DD37AAC57EB4582A756C175CEB8890170B0C2@KFSVS1.utk.tennessee.edu</uri>
<subject>RE: Comment:  ISSUE-70</subject>
<sender>rde2@utk.edu</sender>
<date>2008-02-13</date>
</email>
<email>
<uri>http://www.w3.org/mid/47B8B1FB.1030902@few.vu.nl</uri>
<subject>[SKOS] Issues Review [From Alistair]</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD72BB.1010906@zoo.ox.ac.uk</uri>
<subject>[Fwd: [SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD9D4A.2090301@zoo.ox.ac.uk</uri>
<subject>[SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080415154659.GA4980@octavius</uri>
<subject>[SKOS] Issue owners - preparation for Washington</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2008-04-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/480C7E67.9090901@few.vu.nl</uri>
<subject>Re: [SKOS] Issue owners - preparation for Washington</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-04-21</date>
</email>
</emails>
<notes>
<note>
<date>2008-05-07</date>
<text>http://www.w3.org/2008/05/06-swd-minutes.html#irreflexive

RESOLUTION: to resolve skos:related, skos:broader and skos:broaderTransitive are
not normatively irreflexive</text>
</note>
</notes>
</issue>
<issue>
<id>71</id>
<title>ParallelMappingVocabulary</title>
<product>3</product>
<raisedby>17</raisedby>
<created>2008-01-16</created>
<description>Currently, the SKOS vocabulary includes two "parallel" sets of URIs vocabulary
for hierarchical and associative links between conceptual resources. The
semantic relation properties skos:semanticRelation, skos:broader, skos:narrower
and skos:related are mirrored in skos:mappingRelation, skos:broadMatch,
skos:narrowMatch and skos:relatedMatch.

A separate, parallel mapping vocabulary provides a convenient way to
differentiate links *within* a scheme from links *between* a scheme (given that
certain conventions of practice are followed). However, there may also be other
mechanisms for making such a differentiation that do not require a separate
vocabulary, by e.g. keeping links between concepts within a scheme in a separate
RDF graph from mapping links. 

With a separate vocabulary for mapping relations, a number of interactions
between the parallel vocabularies then have to be considered, which increases
the size and complexity of the SKOS data model. Many of these interactions have
not yet been considered by the Working Group, and as such the model currently
leads to a number of counter-intuitive results. E.g. 

&lt;A&gt; skos:broader &lt;B&gt; .
&lt;A&gt; skos:exactMatch &lt;B&gt; .

is consistent with the SKOS data model (this is one of a number of similar
scenarios). 

Should we keep skos:broadMatch, skos:narrowMatch and skos:relatedMatch? 

Or should we drop them, and use skos:broader, skos:narrower and skos:related for
mapping, providing guidance on how to make a distinction between intra-scheme
and inter-scheme links by managing RDF graphs (or some other mechanism)?</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080116174249.CC3356B5EA@tibor.w3.org</uri>
<subject>ISSUE-71: ParallelMappingVocabulary</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-01-16</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080116212347.DF07B6B62C@kent.w3.org</uri>
<subject>ISSUE-74: MappingPropertyConventions</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-01-16</date>
</email>
<email>
<uri>http://www.w3.org/mid/4794661E.2000101@few.vu.nl</uri>
<subject>Re: ISSUE-74: MappingPropertyConventions</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/479505A7.7040309@few.vu.nl</uri>
<subject>Re: ISSUE-71: ParallelMappingVocabulary</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB66903408403@hqgiex01.fao.org</uri>
<subject>Several emails to reply to</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-02-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/D79DD37AAC57EB4582A756C175CEB8890170AA20@KFSVS1.utk.tennessee.edu</uri>
<subject>Comment: ISSUE-71</subject>
<sender>rde2@utk.edu</sender>
<date>2008-02-09</date>
</email>
<email>
<uri>http://www.w3.org/mid/47B8B1FB.1030902@few.vu.nl</uri>
<subject>[SKOS] Issues Review [From Alistair]</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/47B8B4DB.6020705@few.vu.nl</uri>
<subject>[SKOS] On ISSUE-71 ParallelMappingVocabulary and ISSUE-74 MappingPropertyConventions  [From Alistair Miles!]</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/47B8B622.8060206@few.vu.nl</uri>
<subject>Re: [SKOS] On ISSUE-71 ParallelMappingVocabulary and ISSUE-74 MappingPropertyConventions</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/47B8B900.40700@few.vu.nl</uri>
<subject>[SKOS] Proposal ISSUE 47 MappingProvenanceInformation</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB669029DAF56@hqgiex01.fao.org</uri>
<subject>RE: [SKOS] On ISSUE-71 ParallelMappingVocabulary and ISSUE-74  MappingPropertyConventions</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-02-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/47B96B20.4010007@dcs.gla.ac.uk</uri>
<subject>Re: [SKOS] Proposal ISSUE 47 MappingProvenanceInformation</subject>
<sender>agray@dcs.gla.ac.uk</sender>
<date>2008-02-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BB2300.8010702@few.vu.nl</uri>
<subject>[SKOS] Closing ISSUE-71 ParallelMappingVocabulary</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BB2352.4050705@few.vu.nl</uri>
<subject>[SKOS] Closing ISSUE-74 MappingPropertyConventions</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BB2384.10600@few.vu.nl</uri>
<subject>[SKOS] Closing ISSUE 47 MappingProvenanceInformation</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080219110910.3gcob74r340swck4@webmail.stanford.edu</uri>
<subject>Re: [SKOS] Closing ISSUE-71 ParallelMappingVocabulary</subject>
<sender>dlrubin@stanford.edu</sender>
<date>2008-02-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/0F1C3BFC-85E4-49FC-BE79-4E43F0371E02@manchester.ac.uk</uri>
<subject>Re: [SKOS] Closing ISSUE-71 ParallelMappingVocabulary</subject>
<sender>sean.bechhofer@manchester.ac.uk</sender>
<date>2008-02-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BC05B9.70806@few.vu.nl</uri>
<subject>Re: [SKOS] Closing ISSUE-71 ParallelMappingVocabulary</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BDC7D9.3080503@zoo.ox.ac.uk</uri>
<subject>[SKOS] on ISSUE-71 and ISSUE-74</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD72BB.1010906@zoo.ox.ac.uk</uri>
<subject>[Fwd: [SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD9D4A.2090301@zoo.ox.ac.uk</uri>
<subject>[SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BE9BE7.7070900@few.vu.nl</uri>
<subject>Re: [SKOS] on ISSUE-71 and ISSUE-74</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/47C540D3.8050509@cs.vu.nl</uri>
<subject>Re: [SKOS] on ISSUE-71 and ISSUE-74</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2008-02-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/47C5450C.8050608@few.vu.nl</uri>
<subject>Re: [SKOS] on ISSUE-71 and ISSUE-74</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/0BA7EE4D4646E0409D458D347C508B780419A945@MAILSERV1.uni.glam.ac.uk</uri>
<subject>RE: [SKOS] on ISSUE-71 and ISSUE-74</subject>
<sender>dstudhope@glam.ac.uk</sender>
<date>2008-02-28</date>
</email>
<email>
<uri>http://www.w3.org/mid/f032cc060803011003j16953aei9318c574bc410f2b@mail.gmail.com</uri>
<subject>Meeting Record: 2008-02-27 SWD telecon</subject>
<sender>ehs@pobox.com</sender>
<date>2008-03-01</date>
</email>
<email>
<uri>http://www.w3.org/mid/000801c87d33$194203e0$0300000a@DELL</uri>
<subject>RE: [SKOS] on ISSUE-71 and ISSUE-74</subject>
<sender>sdclarke@lukehouse.demon.co.uk</sender>
<date>2008-03-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/47E11ECC0200006A00024B85@ntgwgate.loc.gov</uri>
<subject>Minutes from 2008-03-18 telecon</subject>
<sender>cred@loc.gov</sender>
<date>2008-03-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/47F0C02B.3040400@ninebynine.org</uri>
<subject>Comment: ISSUE-71</subject>
<sender>GK@ninebynine.org</sender>
<date>2008-03-31</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080331130017.GA3808@octavius</uri>
<subject>[ALL] Agenda - SWD telecon Apr 01 - 1500 UTC - Europeans back to normal time</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2008-03-31</date>
</email>
<email>
<uri>http://www.w3.org/mid/47F24A4F.4080404@sandsoft.com</uri>
<subject>Re: [ALL] Agenda - SWD telecon Apr 01 - 1500 UTC - Europeans back  to normal time</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2008-04-01</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB669037A04D3@hqgiex01.fao.org</uri>
<subject>Minutes from 2008-04-01 telecon</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-04-02</date>
</email>
<email>
<uri>http://www.w3.org/mid/47FA3FE3.9050908@cs.vu.nl</uri>
<subject>[ALL] agenda 8 April telecon 1500 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2008-04-07</date>
</email>
<email>
<uri>http://www.w3.org/mid/47FAF3EC.1050309@sandsoft.com</uri>
<subject>Re: [ALL] agenda 8 April telecon 1500 UTC</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2008-04-07</date>
</email>
<email>
<uri>http://www.w3.org/mid/52bd7c3d0804080609t10266db0s930f8a6b84bca1b3@mail.gmail.com</uri>
<subject>Re: [ALL] agenda 8 April telecon 1500 UTC</subject>
<sender>simone.onofri@gmail.com</sender>
<date>2008-04-08</date>
</email>
<email>
<uri>http://www.w3.org/mid/5.1.0.14.2.20080408132657.03313ea8@127.0.0.1</uri>
<subject>meeting record: 2008-04-08 SWD telecon</subject>
<sender>swick@w3.org</sender>
<date>2008-04-08</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080414083109.GA1736@octavius</uri>
<subject>[ALL] Agenda - Apr 15 SWD telecon - 1500 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2008-04-14</date>
</email>
<email>
<uri>http://www.w3.org/mid/000001c89f07$e921e800$bb65b800$@miles@zoo.ox.ac.uk</uri>
<subject>RE: [ALL] Agenda - Apr 15 SWD telecon - 1500 UTC</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-04-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/52bd7c3d0804150811j42e98896i7ad5be7ed68f64d2@mail.gmail.com</uri>
<subject>Re: [ALL] Agenda - Apr 15 SWD telecon - 1500 UTC</subject>
<sender>simone.onofri@gmail.com</sender>
<date>2008-04-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080415154659.GA4980@octavius</uri>
<subject>[SKOS] Issue owners - preparation for Washington</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2008-04-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/4804EEB4.4000305@deri.org</uri>
<subject>meeting record: 2008-04-15 SWD telecon</subject>
<sender>vit.novacek@deri.org</sender>
<date>2008-04-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/480597C6.5090004@sandsoft.com</uri>
<subject>Re: [ALL] Agenda - Apr 15 SWD telecon - 1500 UTC</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2008-04-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/480C7E67.9090901@few.vu.nl</uri>
<subject>Re: [SKOS] Issue owners - preparation for Washington</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-04-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/480C93F1.50901@cs.vu.nl</uri>
<subject>[ALL] agenda 22 April telecon 1500 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2008-04-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/34b5049c0804220701l5d151ca4udf70a325129fc494@mail.gmail.com</uri>
<subject>Re: [ALL] agenda 22 April telecon 1500 UTC</subject>
<sender>jphipps@madcreek.com</sender>
<date>2008-04-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/480DF981.4090404@sandsoft.com</uri>
<subject>Re: [ALL] agenda 22 April telecon 1500 UTC</subject>
<sender>ekendall@sandsoft.com</sender>
<date>2008-04-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/2B5F6004-902E-48F0-A5B1-5549EBB4CAAB@manchester.ac.uk</uri>
<subject>meeting record: 2008-04-22 SWD telecon</subject>
<sender>sean.bechhofer@manchester.ac.uk</sender>
<date>2008-04-23</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080428161756.GA3328@octavius</uri>
<subject>[ALL] Agenda - Apr 29 2008 SWD telecon - 1500 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2008-04-28</date>
</email>
<email>
<uri>http://www.w3.org/mid/5C0FCE75-D11B-4659-8353-40FEA348CF02@manchester.ac.uk</uri>
<subject>Re: [ALL] Agenda - Apr 29 2008 SWD telecon - 1500 UTC</subject>
<sender>sean.bechhofer@manchester.ac.uk</sender>
<date>2008-04-29</date>
</email>
<email>
<uri>http://www.w3.org/mid/006001c8aafd$f3f4e5a0$dbdeb0e0$@miles@zoo.ox.ac.uk</uri>
<subject>[SKOS] ISSUE-71, ISSUE-74 preparation for Washington</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-04-30</date>
</email>
<email>
<uri>http://www.w3.org/mid/48198F3A.4060100@few.vu.nl</uri>
<subject>Re: [SKOS] ISSUE-71, ISSUE-74 preparation for Washington</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-05-01</date>
</email>
<email>
<uri>http://www.w3.org/mid/000301c8ab9d$2b6b8120$82428360$@miles@zoo.ox.ac.uk</uri>
<subject>RE: [SKOS] ISSUE-71, ISSUE-74 preparation for Washington</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-05-01</date>
</email>
<email>
<uri>http://www.w3.org/mid/38100CBF-4FD1-4BA2-B7A7-C143A91AE1F4@madcreek.com</uri>
<subject>meeting record: 2008-04-29 SWD WG</subject>
<sender>jphipps@madcreek.com</sender>
<date>2008-05-01</date>
</email>
<email>
<uri>http://www.w3.org/mid/4828264C.8000402@cs.vu.nl</uri>
<subject>[ALL] agenda 13 May telecon 1500 UTC</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2008-05-12</date>
</email>
<email>
<uri>http://www.w3.org/mid/1210756051.4662.4.camel@duncan.fundacionctic.org</uri>
<subject>Meeting record: 2008-05-13 SWD telecon</subject>
<sender>diego.berrueta@fundacionctic.org</sender>
<date>2008-05-14</date>
</email>
</emails>
<notes>
<note>
<date>2008-04-22</date>
<text>See also issue 74 MappingPropertyConventions
http://www.w3.org/2006/07/SWD/track/issues/74</text>
</note>
<note>
<date>2008-05-07</date>
<text>RESOLUTION: 1. keep the mapping vocabulary broadMatch, narrowMatch, 2.
broadMatch, narrowMatch, etc. are rdfs:subPropertyOf broader, narrower, 3. there
are no semantic conditions on broadMatch, narrowMatch; i.e. graphs 1-6 are all
consistent, 4. there is some text about cultural conventions explaining where we
expect broadMatch to be used, 5. by convention, mapping properties are only used
to link concepts in different schemes, 6. in the Last Call WD we'll note that
the mapping vocabulary may be dropped
-- http://www.w3.org/2008/05/06-swd-minutes.html#item04</text>
</note>
</notes>
</issue>
<issue>
<id>72</id>
<title>ExactMatchTransitive</title>
<product>3</product>
<raisedby>8</raisedby>
<created>2008-01-16</created>
<description>Currently, skos:exactMatch is not defined as a transitive property. However, it
would seem reasonable and useful to define skos:exactMatch as transitive, which
would mean e.g. that the graph:

&lt;A&gt; skos:exactMatch &lt;B&gt;.
&lt;B&gt; skos:exactMatch &lt;C&gt;.

... would entail:

&lt;A&gt; skos:exactMatch &lt;C&gt;.

Should skos:exactMatch be transitive?</description>
<state>0</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080116205428.AD9F35F70A@stu.w3.org</uri>
<subject>ISSUE-72: ExactMatchTransitive</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-01-16</date>
</email>
<email>
<uri>http://www.w3.org/mid/D79DD37AAC57EB4582A756C175CEB8890170AA1F@KFSVS1.utk.tennessee.edu</uri>
<subject>Comment: ISSUE-75</subject>
<sender>rde2@utk.edu</sender>
<date>2008-02-09</date>
</email>
<email>
<uri>http://www.w3.org/mid/D79DD37AAC57EB4582A756C175CEB8890170AA1E@KFSVS1.utk.tennessee.edu</uri>
<subject>Comment: ISSUE-72</subject>
<sender>rde2@utk.edu</sender>
<date>2008-02-09</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD72BB.1010906@zoo.ox.ac.uk</uri>
<subject>[Fwd: [SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD9D4A.2090301@zoo.ox.ac.uk</uri>
<subject>[SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
</emails>
</issue>
<issue>
<id>73</id>
<title>ExactMatchDisjoints</title>
<product>3</product>
<raisedby>8</raisedby>
<created>2008-01-16</created>
<description>Currently, the property skos:exactMatch is not stated as disjoint with any of
the other concept mapping properties (or with any of the semantic relation
properties). 

Therefore e.g. the graph below is consistent with the SKOS data model.

&lt;A&gt; 
  skos:exactMatch &lt;B&gt; ; 
  skos:broadMatch &lt;B&gt; ;  
  skos:exactMatch &lt;C&gt; ; 
  skos:relatedMatch &lt;C&gt; .

Intuitively, an exact mapping link asserts something fundamentally different
from a hierarchical or associative link. Therefore, it might be reasonable and
useful to define skos:exactMatch as disjoint with skos:broadMatch (and/or
skos:broader), and disjoint with skos:relatedMatch (and/or skos:related). Should
these disjointness conditions be stated in the normative specification?</description>
<state>0</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080116210550.4C253BEF0@nelson.w3.org</uri>
<subject>ISSUE-73: ExactMatchDisjoints</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-01-16</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB66903408403@hqgiex01.fao.org</uri>
<subject>Several emails to reply to</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-02-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/47B8B4DB.6020705@few.vu.nl</uri>
<subject>[SKOS] On ISSUE-71 ParallelMappingVocabulary and ISSUE-74 MappingPropertyConventions  [From Alistair Miles!]</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/47B8B622.8060206@few.vu.nl</uri>
<subject>Re: [SKOS] On ISSUE-71 ParallelMappingVocabulary and ISSUE-74 MappingPropertyConventions</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB669029DAF56@hqgiex01.fao.org</uri>
<subject>RE: [SKOS] On ISSUE-71 ParallelMappingVocabulary and ISSUE-74  MappingPropertyConventions</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-02-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BB2300.8010702@few.vu.nl</uri>
<subject>[SKOS] Closing ISSUE-71 ParallelMappingVocabulary</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080219110910.3gcob74r340swck4@webmail.stanford.edu</uri>
<subject>Re: [SKOS] Closing ISSUE-71 ParallelMappingVocabulary</subject>
<sender>dlrubin@stanford.edu</sender>
<date>2008-02-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD72BB.1010906@zoo.ox.ac.uk</uri>
<subject>[Fwd: [SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD9D4A.2090301@zoo.ox.ac.uk</uri>
<subject>[SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
</emails>
</issue>
<issue>
<id>74</id>
<title>MappingPropertyConventions</title>
<product>3</product>
<raisedby>8</raisedby>
<created>2008-01-16</created>
<description>Currently, given separate vocabularies for semantic relations (skos:broader,
skos:narrower, skos:related etc.) and for concept mapping relations
(skos:broadMatch, skos:narrowMatch, skos:relatedMatch etc.), our assumption is
that, *by convention*, the SKOS semantic relation properties are *only* used to
state links between conceptual resources within the *same* concept scheme, and
the SKOS concept mapping properties are *only* used to state links between
conceptual resources in *different* concept schemes. 

Is this usage convention appropriate, useful and viable? Are there circumstances
where we would recommend *not* adhering to this convention?

Note that it is difficult to formally state any integrity conditions which could
be used to enforce this usage convention. No such integrity conditions are
currently stated in the SKOS reference. Therefore, graphs such as:

&lt;A&gt; skos:broader &lt;B&gt; ; skos:related &lt;C&gt; .
&lt;A&gt; skos:inScheme &lt;MyScheme&gt; .
&lt;B&gt; skos:inScheme &lt;AnotherScheme&gt; .
&lt;C&gt; skos:inScheme &lt;AnotherScheme&gt; .
&lt;MyScheme&gt; owl:differentFrom &lt;AnotherScheme&gt; . 

... and:

&lt;A&gt; skos:broadMatch &lt;B&gt; ; skos:relatedMatch &lt;C&gt; .
&lt;A&gt; skos:inScheme &lt;MyScheme&gt; .
&lt;B&gt; skos:inScheme &lt;MyScheme&gt; .
&lt;C&gt; skos:inScheme &lt;MyScheme&gt; .

... are both consistent with the SKOS data model. If we agree on the usage
convention, can we live without any supporting integrity conditions?

Note finally that if we chose *not* to have a separate vocabulary for concept
mapping relations and for semantic relations, and we use only semantic relations
to assert links between conceptual resources, this issue goes away. I.e. the
resolution of this issue is dependant on the resolution of ISSUE-71.


</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080116212347.DF07B6B62C@kent.w3.org</uri>
<subject>ISSUE-74: MappingPropertyConventions</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-01-16</date>
</email>
<email>
<uri>http://www.w3.org/mid/4794661E.2000101@few.vu.nl</uri>
<subject>Re: ISSUE-74: MappingPropertyConventions</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/479505A7.7040309@few.vu.nl</uri>
<subject>Re: ISSUE-71: ParallelMappingVocabulary</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB66903408403@hqgiex01.fao.org</uri>
<subject>Several emails to reply to</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-02-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/47B8B1FB.1030902@few.vu.nl</uri>
<subject>[SKOS] Issues Review [From Alistair]</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/47B8B4DB.6020705@few.vu.nl</uri>
<subject>[SKOS] On ISSUE-71 ParallelMappingVocabulary and ISSUE-74 MappingPropertyConventions  [From Alistair Miles!]</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/47B8B622.8060206@few.vu.nl</uri>
<subject>Re: [SKOS] On ISSUE-71 ParallelMappingVocabulary and ISSUE-74 MappingPropertyConventions</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB669029DAF56@hqgiex01.fao.org</uri>
<subject>RE: [SKOS] On ISSUE-71 ParallelMappingVocabulary and ISSUE-74  MappingPropertyConventions</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-02-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BB2300.8010702@few.vu.nl</uri>
<subject>[SKOS] Closing ISSUE-71 ParallelMappingVocabulary</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BB2352.4050705@few.vu.nl</uri>
<subject>[SKOS] Closing ISSUE-74 MappingPropertyConventions</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080219110910.3gcob74r340swck4@webmail.stanford.edu</uri>
<subject>Re: [SKOS] Closing ISSUE-71 ParallelMappingVocabulary</subject>
<sender>dlrubin@stanford.edu</sender>
<date>2008-02-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/0F1C3BFC-85E4-49FC-BE79-4E43F0371E02@manchester.ac.uk</uri>
<subject>Re: [SKOS] Closing ISSUE-71 ParallelMappingVocabulary</subject>
<sender>sean.bechhofer@manchester.ac.uk</sender>
<date>2008-02-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BC05B9.70806@few.vu.nl</uri>
<subject>Re: [SKOS] Closing ISSUE-71 ParallelMappingVocabulary</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD72BB.1010906@zoo.ox.ac.uk</uri>
<subject>[Fwd: [SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD9D4A.2090301@zoo.ox.ac.uk</uri>
<subject>[SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/0BA7EE4D4646E0409D458D347C508B780419A945@MAILSERV1.uni.glam.ac.uk</uri>
<subject>RE: [SKOS] on ISSUE-71 and ISSUE-74</subject>
<sender>dstudhope@glam.ac.uk</sender>
<date>2008-02-28</date>
</email>
<email>
<uri>http://www.w3.org/mid/f032cc060803011003j16953aei9318c574bc410f2b@mail.gmail.com</uri>
<subject>Meeting Record: 2008-02-27 SWD telecon</subject>
<sender>ehs@pobox.com</sender>
<date>2008-03-01</date>
</email>
<email>
<uri>http://www.w3.org/mid/000901c87c61$b7f4ba00$6802a8c0@TFJOHAN</uri>
<subject>Comment: ISSUE-74</subject>
<sender>johan.de-smedt@tenforce.com</sender>
<date>2008-03-02</date>
</email>
<email>
<uri>http://www.w3.org/mid/000801c87d33$194203e0$0300000a@DELL</uri>
<subject>RE: [SKOS] on ISSUE-71 and ISSUE-74</subject>
<sender>sdclarke@lukehouse.demon.co.uk</sender>
<date>2008-03-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/47E11ECC0200006A00024B85@ntgwgate.loc.gov</uri>
<subject>Minutes from 2008-03-18 telecon</subject>
<sender>cred@loc.gov</sender>
<date>2008-03-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080415154659.GA4980@octavius</uri>
<subject>[SKOS] Issue owners - preparation for Washington</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2008-04-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/480C7E67.9090901@few.vu.nl</uri>
<subject>Re: [SKOS] Issue owners - preparation for Washington</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-04-21</date>
</email>
</emails>
<notes>
<note>
<date>2008-04-22</date>
<text>See also issue 71 ParallelMappingVocabulary
ParallelMappingVocabulary</text>
</note>
<note>
<date>2008-04-22</date>
<text>http://www.w3.org/2006/07/SWD/track/issues/71</text>
</note>
<note>
<date>2008-05-07</date>
<text>RESOLUTION: 1. keep the mapping vocabulary broadMatch, narrowMatch, 2.
broadMatch, narrowMatch, etc. are rdfs:subPropertyOf broader, narrower, 3. there
are no semantic conditions on broadMatch, narrowMatch; i.e. graphs 1-6 are all
consistent, 4. there is some text about cultural conventions explaining where we
expect broadMatch to be used, 5. by convention, mapping properties are only used
to link concepts in different schemes, 6. in the Last Call WD we'll note that
the mapping vocabulary may be dropped
-- http://www.w3.org/2008/05/06-swd-minutes.html#item04</text>
</note>
</notes>
</issue>
<issue>
<id>75</id>
<title>ExactMatchInclusions</title>
<product>3</product>
<raisedby>8</raisedby>
<created>2008-01-16</created>
<description>Can any property chain inclusion axioms be stated for skos:exactMatch?

E.g. SubObjectPropertyOf(SubObjectPropertyChain(broadMatch exactMatch) broadMatch) ?

This axiom would mean that the graph:

&lt;A&gt; skos:broadMatch &lt;B&gt; .
&lt;B&gt; skos:exactMatch &lt;C&gt; .

... entails:

&lt;A&gt; skos:broadMatch &lt;C&gt; .

E.g. SubObjectPropertyOf(SubObjectPropertyChain(relatedMatch exactMatch)
relatedMatch) ?

This axiom would mean that the graph:

&lt;A&gt; skos:relatedMatch &lt;B&gt; .
&lt;B&gt; skos:exactMatch &lt;C&gt; .

... entails:

&lt;A&gt; skos:relatedMatch &lt;C&gt; .

E.g. SubObjectPropertyOf(SubObjectPropertyChain(broader exactMatch) broader) ?

E.g. SubObjectPropertyOf(SubObjectPropertyChain(related exactMatch) related) ?</description>
<state>0</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080116225508.9AEA5C6DB9@barney.w3.org</uri>
<subject>ISSUE-75: ExactMatchInclusions</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-01-16</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB66903408403@hqgiex01.fao.org</uri>
<subject>Several emails to reply to</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-02-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/D79DD37AAC57EB4582A756C175CEB8890170AA1F@KFSVS1.utk.tennessee.edu</uri>
<subject>Comment: ISSUE-75</subject>
<sender>rde2@utk.edu</sender>
<date>2008-02-09</date>
</email>
<email>
<uri>http://www.w3.org/mid/47B8B4DB.6020705@few.vu.nl</uri>
<subject>[SKOS] On ISSUE-71 ParallelMappingVocabulary and ISSUE-74 MappingPropertyConventions  [From Alistair Miles!]</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/47B8B622.8060206@few.vu.nl</uri>
<subject>Re: [SKOS] On ISSUE-71 ParallelMappingVocabulary and ISSUE-74 MappingPropertyConventions</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB669029DAF56@hqgiex01.fao.org</uri>
<subject>RE: [SKOS] On ISSUE-71 ParallelMappingVocabulary and ISSUE-74  MappingPropertyConventions</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-02-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BB2300.8010702@few.vu.nl</uri>
<subject>[SKOS] Closing ISSUE-71 ParallelMappingVocabulary</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080219110910.3gcob74r340swck4@webmail.stanford.edu</uri>
<subject>Re: [SKOS] Closing ISSUE-71 ParallelMappingVocabulary</subject>
<sender>dlrubin@stanford.edu</sender>
<date>2008-02-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD72BB.1010906@zoo.ox.ac.uk</uri>
<subject>[Fwd: [SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD9D4A.2090301@zoo.ox.ac.uk</uri>
<subject>[SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
</emails>
</issue>
<issue>
<id>76</id>
<title>SymbolicLabels</title>
<product>3</product>
<raisedby>8</raisedby>
<created>2008-01-17</created>
<description>Previous drafts of SKOS included skos:prefSymbol and skos:altSymbol. Should
these be carried forward into the SKOS Reference? Or should they be dropped?</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080117130109.53328BEF0@nelson.w3.org</uri>
<subject>ISSUE-76: SymbolicLabels</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-01-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080121170414.GA1108@octavius</uri>
<subject>Re: ISSUE-76: SymbolicLabels</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2008-01-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB669029DAE87@hqgiex01.fao.org</uri>
<subject>RIF: Comments on SKOS Primer</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-01-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/4799B34E.7040203@few.vu.nl</uri>
<subject>Re: RIF: Comments on SKOS Primer</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-25</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB66903408403@hqgiex01.fao.org</uri>
<subject>Several emails to reply to</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-02-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/47A7836B.2050501@few.vu.nl</uri>
<subject>Re: RIF: Comments on SKOS Primer</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD72BB.1010906@zoo.ox.ac.uk</uri>
<subject>[Fwd: [SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD9D4A.2090301@zoo.ox.ac.uk</uri>
<subject>[SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
</emails>
<notes>
<note>
<date>2008-05-27</date>
<text>RESOLVED not to carry forward SKOS: prefSymbol and altSymbol into the new
namespace for lack clear requirements --
http://www.w3.org/2008/05/27-swd-minutes.html#item02</text>
</note>
</notes>
</issue>
<issue>
<id>77</id>
<title>SubjectIndexing</title>
<product>3</product>
<raisedby>8</raisedby>
<created>2008-01-17</created>
<description>Previous drafts of the SKOS specification included the properties skos:subject,
skos:isSubjectOf, skos:primarySubject and skos:isPrimarySubjectOf as "subject
indexing properties". Should these properties be carried forward to the SKOS
Reference? Or should they be dropped?</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080117130354.94FD55F70A@stu.w3.org</uri>
<subject>ISSUE-77: SubjectIndexing</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-01-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/478F5F3B.6010302@few.vu.nl</uri>
<subject>Re: ISSUE-77: SubjectIndexing</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/68C22185DB90CA41A5ACBD8E834C5ECD0465B0C3@goofy.wpakb.kb.nl</uri>
<subject>RE : RE : [ISSUE-77] [ISSUE-48] Skos subject properties  are deprecated</subject>
<sender>Antoine.Isaac@KB.nl</sender>
<date>2008-01-28</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB66903408403@hqgiex01.fao.org</uri>
<subject>Several emails to reply to</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-02-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/47B8B1FB.1030902@few.vu.nl</uri>
<subject>[SKOS] Issues Review [From Alistair]</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD72BB.1010906@zoo.ox.ac.uk</uri>
<subject>[Fwd: [SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD9D4A.2090301@zoo.ox.ac.uk</uri>
<subject>[SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080415154659.GA4980@octavius</uri>
<subject>[SKOS] Issue owners - preparation for Washington</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2008-04-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/480C7E67.9090901@few.vu.nl</uri>
<subject>Re: [SKOS] Issue owners - preparation for Washington</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-04-21</date>
</email>
</emails>
<notes>
<note>
<date>2008-05-07</date>
<text>See also ISSUE-48 IndexingRelationship</text>
</note>
<note>
<date>2008-05-07</date>
<text>RESOLUTION: to not include the SKOS indexing properties because
1) it's the role of SKOS to publish vocabularies and not to indicate how they
should be used for indexing purposes
2) there appear to be enough support from existing metadata vocabularies to
handle links between resources and SKOS concepts
-- http://www.w3.org/2008/05/07-swd-minutes.html#item05</text>
</note>
</notes>
</issue>
<issue>
<id>78</id>
<title>SubjectIndicators</title>
<product>3</product>
<raisedby>8</raisedby>
<created>2008-01-17</created>
<description>Previous drafts of the SKOS specification included the property
skos:subjectIndicator, which was intended as a bridge between SKOS and topic
maps. Should this property be carried forward in the SKOS Reference? Or should
it be dropped?</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080117130632.9368C6B5E9@tibor.w3.org</uri>
<subject>ISSUE-78: SubjectIndicators</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-01-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB66903408403@hqgiex01.fao.org</uri>
<subject>Several emails to reply to</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-02-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD72BB.1010906@zoo.ox.ac.uk</uri>
<subject>[Fwd: [SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD9D4A.2090301@zoo.ox.ac.uk</uri>
<subject>[SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
</emails>
<notes>
<note>
<date>2008-05-27</date>
<text>RESOLVED: to not carry forward skos:subjectIndicator, as it is out of scope
-- http://www.w3.org/2008/05/27-swd-minutes.html#item02</text>
</note>
</notes>
</issue>
<issue>
<id>79</id>
<title>Notations</title>
<product>3</product>
<raisedby>27</raisedby>
<created>2008-01-17</created>
<description>What is best practice for assigning a notation to a conceptual resource
(notations are codes used in some thesauri and classification schemes)? Do we
need some explicit vocabulary for expressing notations (e.g. skos:notation)? Or
can it be done using existing features (e.g. skos:prefLabel @art)?</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080117131530.13B8B6B5E9@tibor.w3.org</uri>
<subject>ISSUE-79: Notations</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-01-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/47A1A05C.3080900@gbv.de</uri>
<subject>SKOS comment: Notations</subject>
<sender>jakob.voss@gbv.de</sender>
<date>2008-01-31</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB66903408403@hqgiex01.fao.org</uri>
<subject>Several emails to reply to</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-02-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/47B8B1FB.1030902@few.vu.nl</uri>
<subject>[SKOS] Issues Review [From Alistair]</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD72BB.1010906@zoo.ox.ac.uk</uri>
<subject>[Fwd: [SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD9D4A.2090301@zoo.ox.ac.uk</uri>
<subject>[SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080415154659.GA4980@octavius</uri>
<subject>[SKOS] Issue owners - preparation for Washington</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2008-04-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/480C7E67.9090901@few.vu.nl</uri>
<subject>Re: [SKOS] Issue owners - preparation for Washington</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-04-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/483BD9A50200006A0002B254@ntgwgate.loc.gov</uri>
<subject>Notations in SKOS</subject>
<sender>cred@loc.gov</sender>
<date>2008-05-27</date>
</email>
</emails>
<notes>
<note>
<date>2008-05-07</date>
<text>RESOLVED: to introduce skos:notation a rdf:Property whose value is a typed
literal.  The datatype of the literal specifies a syntax encoding scheme and the
value of the literal is the classification code from that encoding scheme.  As
prefLabel is optional, SKOS tools may want to display notations as labels.
-- http://www.w3.org/2008/05/07-swd-minutes.html#item01</text>
</note>
</notes>
</issue>
<issue>
<id>80</id>
<title>SKOS-OWL-Patterns</title>
<product>3</product>
<raisedby>8</raisedby>
<created>2008-01-17</created>
<description>Some patterns have been proposed for working with SKOS and OWL in combination.

E.g. http://www.w3.org/2006/07/SWD/wiki/SkosDesign/ConceptSemantics

E.g. http://isegserv.itd.rl.ac.uk/public/skos/2007/10/f2f/skos-owl-patterns.html

So what are the recommended patterns?

See also ISSUE-54</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080117132525.4BAB3C6DB6@barney.w3.org</uri>
<subject>ISSUE-80: SKOS-OWL-Patterns</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-01-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB66903408403@hqgiex01.fao.org</uri>
<subject>Several emails to reply to</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-02-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/47B1EF98.7090608@few.vu.nl</uri>
<subject>[SKOS] Proposed resolution to close ISSUE-54</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-12</date>
</email>
<email>
<uri>http://www.w3.org/mid/47B8B1FB.1030902@few.vu.nl</uri>
<subject>[SKOS] Issues Review [From Alistair]</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/47B99D63.2090301@few.vu.nl</uri>
<subject>[SKOS] Re: TR : Broader, collections and the difference between SKOS  and OWL</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080218163809.GA3304@octavius</uri>
<subject>[All] Agenda - Feb 19 2008 SWD telecon - 1600 UTC</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2008-02-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/34b5049c0802181029q5c534978m87acdc4c4f6a334d@mail.gmail.com</uri>
<subject>Re: [All] Agenda - Feb 19 2008 SWD telecon - 1600 UTC</subject>
<sender>jphipps@madcreek.com</sender>
<date>2008-02-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB669029DAF5E@hqgiex01.fao.org</uri>
<subject>RE: [All] Agenda - Feb 19 2008 SWD telecon - 1600 UTC</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-02-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/52bd7c3d0802181458o4267f179lf9b25fbbe0e46971@mail.gmail.com</uri>
<subject>Re: [All] Agenda - Feb 19 2008 SWD telecon - 1600 UTC</subject>
<sender>simone.onofri@gmail.com</sender>
<date>2008-02-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BDA2FE.3020004@zoo.ox.ac.uk</uri>
<subject>Minutes of 2008-02-19 telcon</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD72BB.1010906@zoo.ox.ac.uk</uri>
<subject>[Fwd: [SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD9D4A.2090301@zoo.ox.ac.uk</uri>
<subject>[SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BEEB3F.60801@few.vu.nl</uri>
<subject>[SKOS] ISSUE--54 closed, ISSUE-80 opened</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/f032cc060803011003j16953aei9318c574bc410f2b@mail.gmail.com</uri>
<subject>Meeting Record: 2008-02-27 SWD telecon</subject>
<sender>ehs@pobox.com</sender>
<date>2008-03-01</date>
</email>
<email>
<uri>http://www.w3.org/mid/47E11ECC0200006A00024B85@ntgwgate.loc.gov</uri>
<subject>Minutes from 2008-03-18 telecon</subject>
<sender>cred@loc.gov</sender>
<date>2008-03-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080415154659.GA4980@octavius</uri>
<subject>[SKOS] Issue owners - preparation for Washington</subject>
<sender>baker@sub.uni-goettingen.de</sender>
<date>2008-04-15</date>
</email>
<email>
<uri>http://www.w3.org/mid/480C7E67.9090901@few.vu.nl</uri>
<subject>Re: [SKOS] Issue owners - preparation for Washington</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-04-21</date>
</email>
</emails>
<notes>
<note>
<date>2008-04-22</date>
<text>"SKOS and imports" [Sean, 2008-04-16]
http://lists.w3.org/Archives/Public/public-swd-wg/2008Apr/0078.html</text>
</note>
<note>
<date>2008-05-27</date>
<text>Closed, per agreement that the technical issues of SKOS/OWL have already been
dealt with -- http://www.w3.org/2008/05/27-swd-minutes.html#item02</text>
</note>
</notes>
</issue>
<issue>
<id>81</id>
<title>LabelRelationsNaming</title>
<product>3</product>
<raisedby>9</raisedby>
<created>2008-01-17</created>
<description>From http://lists.w3.org/Archives/Public/public-swd-wg/2008Jan/0008.html ...

The draft SKOS Reference [1] very helpfully points out the
symmetry between mappingRelation (with its subproperties
broadMatch, narrowMatch, and relatedMatch) and semanticRelation
(with its subproperties broader, narrower, and related).

However, I find that this naming pattern subtly gets in the
way of grasping the much different concept of label relations.
The problem becomes clear if one puts the names side-by-side:

    Properties:   labelRelated    mappingRelation  semanticRelation
    Classes:      LabelRelation

I cannot think of a better name than LabelRelation, but I would
find it less confusing if labelRelated were renamed relatedLabel:

    Properties:   relatedLabel    mappingRelation  semanticRelation
    Classes:      LabelRelation

[1] http://www.w3.org/2006/07/SWD/SKOS/reference/20071223
</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080117175104.EE84DC6DBA@barney.w3.org</uri>
<subject>ISSUE-81: LabelRelationsNaming</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-01-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/677CE4DD24B12C4B9FA138534E29FB1D0499DF7D@exchange11.fed.cclrc.ac.uk</uri>
<subject>RE: Label relations confusingly named?</subject>
<sender>A.J.Miles@rl.ac.uk</sender>
<date>2008-01-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB66903408403@hqgiex01.fao.org</uri>
<subject>Several emails to reply to</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-02-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/D79DD37AAC57EB4582A756C175CEB8890170AA21@KFSVS1.utk.tennessee.edu</uri>
<subject>Comment: ISSUE-81</subject>
<sender>rde2@utk.edu</sender>
<date>2008-02-09</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD72BB.1010906@zoo.ox.ac.uk</uri>
<subject>[Fwd: [SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD9D4A.2090301@zoo.ox.ac.uk</uri>
<subject>[SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB66903B87AC7@hqgiex01.fao.org</uri>
<subject>List of resolutions from the Face-to-Face meeting</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-05-13</date>
</email>
<email>
<uri>http://www.w3.org/mid/482ADFEC.9070001@cs.vu.nl</uri>
<subject>Re: List of resolutions from the Face-to-Face meeting</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2008-05-14</date>
</email>
</emails>
<notes>
<note>
<date>2008-05-07</date>
<text>RESOLVED: ISSUE-81 is resolved because the property in question "labelRelated",
has been dropped
-- http://www.w3.org/2008/05/07-swd-minutes.html#item06</text>
</note>
</notes>
</issue>
<issue>
<id>82</id>
<title>PropertyNames</title>
<product>3</product>
<raisedby>17</raisedby>
<created>2008-01-22</created>
<description>From http://lists.w3.org/Archives/Public/public-swd-wg/2008Jan/0150.html
or http://lists.w3.org/Archives/Public/public-swd-wg/2008Jan/0075.html
or http://lists.w3.org/Archives/Public/public-swd-wg/2008Jan/0089.html

=======
For all relationships as already mentioned I suggest to make
them more clear by adding the verb. For example:
 - skos:hasNarrowerConcept
 - skos:hasBroaderConcept
 - skos:hasRelatedConcept
=======

The current SKOS specification uses the URI skos:broader, skos:narrower,
skos:related. Should these be changed?

The same hold for other properties, such as skos:note or skos:scopeNote</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080122150156.21B895F70C@stu.w3.org</uri>
<subject>ISSUE-82: PropertyNames</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-01-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/2AD2401FC36E784094D0B3375FDA6CE802B8A526@VMAIL2.uoa.abdn.ac.uk</uri>
<subject>RE: ISSUE-82: PropertyNames</subject>
<sender>q.reul@abdn.ac.uk</sender>
<date>2008-01-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/47960E40.6030203@few.vu.nl</uri>
<subject>Re: ISSUE-82: PropertyNames</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB66903408403@hqgiex01.fao.org</uri>
<subject>Several emails to reply to</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-02-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD72BB.1010906@zoo.ox.ac.uk</uri>
<subject>[Fwd: [SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD9D4A.2090301@zoo.ox.ac.uk</uri>
<subject>[SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB66903B87AC7@hqgiex01.fao.org</uri>
<subject>List of resolutions from the Face-to-Face meeting</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-05-13</date>
</email>
<email>
<uri>http://www.w3.org/mid/482ADFEC.9070001@cs.vu.nl</uri>
<subject>Re: List of resolutions from the Face-to-Face meeting</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2008-05-14</date>
</email>
</emails>
<notes>
<note>
<date>2008-05-07</date>
<text>RESOLVED: to close ISSUE-82 by adding editorial changes to the documents
highlighting the intended interpretation of broader and narrower
-- http://www.w3.org/2008/05/07-swd-minutes.html#item06</text>
</note>
</notes>
</issue>
<issue>
<id>83</id>
<title>SemanticsOfSchemeContainmentProperties</title>
<product>3</product>
<raisedby>17</raisedby>
<created>2008-01-22</created>
<description>From [1]:

======
considering the skos:inScheme tag. I personally not used it in
the agrovoc skos version, because i preferred to make use of the
skos:hasTopConcept to associate concepts to the ConceptSchemes. Using this i
define the full hierarchy of the scheme, because i consider all the
skos:hasTopConcept plus all the skos:narrower to build the full hierarchy of
the classification scheme.
Therefore I do not use the skos:inScheme for every concept in the thesaurus
because this information again can be inferred.
======

Currently the SKOS Reference [2] does not support that kind of inference. Should
it do so?

[1] http://lists.w3.org/Archives/Public/public-swd-wg/2008Jan/0150.html
[2] http://www.w3.org/2006/07/SWD/SKOS/reference/20080118</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080122154612.8C9E2C6DBB@barney.w3.org</uri>
<subject>ISSUE-83: SemanticsOfSchemeContainmentProperties</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-01-22</date>
</email>
<email>
<uri>http://www.w3.org/mid/4799B34E.7040203@few.vu.nl</uri>
<subject>Re: RIF: Comments on SKOS Primer</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-25</date>
</email>
<email>
<uri>http://www.w3.org/mid/47A1ADA3.2020806@few.vu.nl</uri>
<subject>Re: SKOS comment: Grouping Concept Schemes</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-31</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB66903408403@hqgiex01.fao.org</uri>
<subject>Several emails to reply to</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-02-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/47A7836B.2050501@few.vu.nl</uri>
<subject>Re: RIF: Comments on SKOS Primer</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/47B8B4DB.6020705@few.vu.nl</uri>
<subject>[SKOS] On ISSUE-71 ParallelMappingVocabulary and ISSUE-74 MappingPropertyConventions  [From Alistair Miles!]</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/47B8B622.8060206@few.vu.nl</uri>
<subject>Re: [SKOS] On ISSUE-71 ParallelMappingVocabulary and ISSUE-74 MappingPropertyConventions</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB669029DAF56@hqgiex01.fao.org</uri>
<subject>RE: [SKOS] On ISSUE-71 ParallelMappingVocabulary and ISSUE-74  MappingPropertyConventions</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-02-18</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BB2300.8010702@few.vu.nl</uri>
<subject>[SKOS] Closing ISSUE-71 ParallelMappingVocabulary</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080219110910.3gcob74r340swck4@webmail.stanford.edu</uri>
<subject>Re: [SKOS] Closing ISSUE-71 ParallelMappingVocabulary</subject>
<sender>dlrubin@stanford.edu</sender>
<date>2008-02-19</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD72BB.1010906@zoo.ox.ac.uk</uri>
<subject>[Fwd: [SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD9D4A.2090301@zoo.ox.ac.uk</uri>
<subject>[SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/483C322E.8010703@few.vu.nl</uri>
<subject>[SKOS] proposal for ISSUE-83 SemanticsOfSchemeContainmentProperties</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-05-27</date>
</email>
<email>
<uri>http://www.w3.org/mid/000001c8c1d7$e57ad160$b0707420$@miles@zoo.ox.ac.uk</uri>
<subject>RE: [SKOS] proposal for ISSUE-83 SemanticsOfSchemeContainmentProperties</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-05-29</date>
</email>
</emails>
<notes>
<note>
<date>2008-06-17</date>
<text>RESOLVED to adopt the solution proposed in
http://lists.w3.org/Archives/Public/public-swd-wg/2008May/0068.html
per http://www.w3.org/2008/06/17-swd-minutes.html#item03</text>
</note>
</notes>
</issue>
<issue>
<id>84</id>
<title>ConstructionOfSystematicDisplaysFromGroupings</title>
<product>3</product>
<raisedby>17</raisedby>
<created>2008-01-23</created>
<description>From [1]:

&gt; I propose the following section of the SKOS Semantics wiki draft as resolution
of ISSUE-33 "Grouping Constructs" [2]:
&gt;
&gt; http://www.w3.org/2006/07/SWD/wiki/SKOS/Semantics/Grouping?action=recall&amp;rev=2&gt;
&gt;
&gt; This section implements the "Minimal Fix" proposal [2], with a few additional
&gt; axiomatic triples to make explicit the OWL typing of properties and the
&gt; disjointness of skos:Collection and skos:ConceptScheme.
&gt;
&gt; Note that this section does not address the issue of constructing a systematic
&gt; hierarchical display, but delegates this responsibility to the SKOS Primer.
&gt; Note also that the SKOS Primer section on grouping constructs is yet to be 
&gt;done, and that in particular I have not met Antoine's concerns below regarding
&gt; nested collections.
&gt;
&gt; However, I suggest we accept this resolution for now (because it does fix the
&gt; actual issue), and raise a new issue regarding the representation and 
&gt; construction of systematic hierarchical displays.

(Antoine's comment on nested collections are at [3])

Now from [4] (no need to thank me Alistair ;-p)

&gt; However, in the absence of any presentational information, there could be a
&gt; default method of constructing a systematic display. To handle SKOS grouping
&gt; constructs, this would require an algorithm which is *fairly* sophisticated -
&gt; certainly not straightforward to a novice hacker. The onus is on me to provide
&gt; a reference implementation :)

This was reflected in [5]:

&gt;(Statement 2) The SWDWG MAY publish an algorithm to generate a default 
&gt; thesaurus systematic display from an RDF graph using the SKOS vocabulary.
&gt; However, applications are not required to use the algorithm, and MAY use any
&gt; means to convey information required to construct a thesaurus systematic 
&gt;display.

The current Primer [6] in its section on Collections of Concepts (4.1) does not
propose anything:

&gt;  A systematic (hierarchical) display can then be generated including the
&gt; concept grouping "milk by source animal", as presented in the example 
&gt;introducing this sub-section. The skos:broader hierarchy and the collection 
&gt;membership information can be used for this, but the process still requires a 
&gt;dedicated algorithm, the implementation of which is left to specific 
&gt; applications.

Shall we change this? 


[1] http://lists.w3.org/Archives/Public/public-esw-thes/2007Jun/0012.html
[2] http://www.w3.org/2006/07/SWD/track/issues/33
[3] http://lists.w3.org/Archives/Public/public-esw-thes/2007May/0010.html
[4] http://lists.w3.org/Archives/Public/public-esw-thes/2007Jun/0016.html
[5] http://www.w3.org/2006/07/SWD/wiki/SkosDesign/PresentationInformation
[6] http://www.w3.org/2006/07/SWD/wiki/SKOS/DraftPrimer
</description>
<state>0</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080123095757.9498EC6DB6@barney.w3.org</uri>
<subject>ISSUE-84: ConstructionOfSystematicDisplaysFromGroupings</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-01-23</date>
</email>
<email>
<uri>http://www.w3.org/mid/47971152.5080107@few.vu.nl</uri>
<subject>Re: ISSUE-84: ConstructionOfSystematicDisplaysFromGroupings</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-23</date>
</email>
<email>
<uri>http://www.w3.org/mid/4797BA74.907@fundacionctic.org</uri>
<subject>Re: ISSUE-84: ConstructionOfSystematicDisplaysFromGroupings</subject>
<sender>diego.berrueta@fundacionctic.org</sender>
<date>2008-01-23</date>
</email>
<email>
<uri>http://www.w3.org/mid/4799B34E.7040203@few.vu.nl</uri>
<subject>Re: RIF: Comments on SKOS Primer</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-25</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB66903408403@hqgiex01.fao.org</uri>
<subject>Several emails to reply to</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-02-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/47A7836B.2050501@few.vu.nl</uri>
<subject>Re: RIF: Comments on SKOS Primer</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD72BB.1010906@zoo.ox.ac.uk</uri>
<subject>[Fwd: [SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
<email>
<uri>http://www.w3.org/mid/47BD9D4A.2090301@zoo.ox.ac.uk</uri>
<subject>[SKOS] Issues Review</subject>
<sender>alistair.miles@zoo.ox.ac.uk</sender>
<date>2008-02-21</date>
</email>
</emails>
</issue>
<issue>
<id>85</id>
<title>Self-describing Web - media type</title>
<product>2</product>
<raisedby>14</raisedby>
<created>2008-02-15</created>
<description>In http://www.w3.org/2001/tag/doc/selfDescribingDocuments#UsingRDFa the 
following is stated:

Note: at this time, drafts of the [RDFa] specification are available, but the 
media-type registration for HTML itself has not been updated to reflect RDFa. 
As described in TAG Finding [AuthoritativeMetadata], conventions like RDFa are 
normative only if provided for in the applicable specification for the media-
type in which they are used. Thus, for RDFa to be fully integrated with 2 The 
Web's Standard Retrieval Algorithm, the HTML and/or XHTML media-type 
registrations must be be updated. Use of RDFa is in any case encouraged in the 
interim until that happens. 

We need to state our position regarding this (feedback to TAG, explicitely 
invite to last call comments, etc.)</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/4799B34E.7040203@few.vu.nl</uri>
<subject>Re: RIF: Comments on SKOS Primer</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-01-25</date>
</email>
<email>
<uri>http://www.w3.org/mid/47A7836B.2050501@few.vu.nl</uri>
<subject>Re: RIF: Comments on SKOS Primer</subject>
<sender>aisaac@few.vu.nl</sender>
<date>2008-02-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/20080215143015.942CE6B62B@kent.w3.org</uri>
<subject>ISSUE-85: Self-describing Web - media type</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-02-15</date>
</email>
</emails>
<notes>
<note>
<date>2008-05-08</date>
<text>status: The task force has no control over that RFC. The XHTML2 Working Group
has informed us that the RFC covers all XTHML family markup languages as it is
currently written, and requires no changes to accommodate XHTML+RDFa.</text>
</note>
<note>
<date>2008-05-19</date>
<text>In response to a related request from the TAG for comments on their
Self-Describing Web document, I have sent the following:

The Media Type definition indicates that XHTML Family document types can use
application/xhtml+xml.  The specification defines XHTML+RDFa, a markup language.
 Further, the specification declares that the document type is in fact part of
that family.  The specification also (obviously) defines how RDF is embedded in
XHTML. So the specification, per force, defines the connection and enables the
use use of RDFa in XHTML+RDFa.  

I have suggested that this closes this issue, and therefore am marking it closed.</text>
</note>
</notes>
</issue>
<issue>
<id>86</id>
<title>SkosURIDereferenceBehaviour</title>
<product>3</product>
<raisedby>8</raisedby>
<created>2008-02-21</created>
<description>What is the recommended URI dereference behaviour for resources of type
skos:Concept? What is the minimum required behaviour?

What is the recommended URI dereference behaviour for resources of type
skos:ConceptScheme? What is the minimum required behaviour?
</description>
<state>0</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080221150858.191176B62D@tibor.w3.org</uri>
<subject>ISSUE-86: SkosURIDereferenceBehaviour</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-02-21</date>
</email>
</emails>
<notes>
<note>
<date>2008-02-21</date>
<text>Would a required minimum dereference behaviour exclude the use of using HTTP
schemes like info: or urn: as URI for SKOS concepts?</text>
</note>
</notes>
</issue>
<issue>
<id>87</id>
<title>Last Call Comment: text bugs in Sections 5.3, 5.4, 5.5 of Syntax </title>
<product>2</product>
<raisedby>6</raisedby>
<created>2008-02-26</created>
<description>"
5.3. Chaining

The first code example

&lt;div about="http://dbpedia.org/resource/Albert_Einstein"&gt;
  ...
  &lt;img rel="foaf:depiction"
src="http://en.wikipedia.org/wiki/Image:Albert_Einstein_Head.jpg" /&gt;

seems to indicate that a triple

&lt;http://dbpedia.org/resource/Albert_Einstein&gt;
  foaf:depiction
  &lt;http://en.wikipedia.org/wiki/Image:Albert_Einstein_Head.jpg&gt; .

should be created. But according to section 5.5 step 5 and section 6.1.1.3 the
rel attribute would have to be on the div element, not the img element. The
example as is IMHO creates an incomplete triple

&lt;http://en.wikipedia.org/wiki/Image:Albert_Einstein_Head.jpg&gt;
  foaf:depiction
  ? .

5.4. wording regarding non-prefixed CURIEs

as per:

http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Feb/0161.html

"
5.4.4. Use of CURIEs in Specific Attributes

"Note that only values in the link type list have this special 
behaviour, which means that any value that is not in the list and is not 
a valid CURIE MUST not generate triples in the [default graph] ."

Even "foobar" is a valid CURIE according to section 7, because it "is 
also possible to omit both the prefix and the colon, leaving just a 
reference."

However "the mapping to use when there is no prefix is not defined;"

If your intent is to disallow unprefixed CURIEs you may want to change 
the text above to

"Note that only values in the link type list have this special 
behaviour, which means that any value that is not in the list and is not 
a valid and prefixed CURIE MUST not generate triples in the [default 
graph]."
"

5.5. Sequence

* step 5:
"Note that final value of the [current object resource] will either be null
(from initialization), a full URI or a bnode."
According to the algorithm, [current object resource] is never set to a bnode.

* After step 8 follows step 10: Probably the numbering is incorrect. 
"

by Johannes Koch in:

http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Feb/0116.html

Probable Resolution: fix the text of the spec to use @rel in the parent DIV for
5.3, use Johannes's suggested text for 5.4, and address typos and small editing
mistakes in 5.5.</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080226162358.77DD86B62C@tibor.w3.org</uri>
<subject>ISSUE-87: @src bug in Section 5.3 of Syntax </subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-02-26</date>
</email>
</emails>
<notes>
<note>
<date>2008-02-26</date>
<text>added other "bugs" from Johannes's message into this same issue, separating out
only the parts of his email that require discussion.</text>
</note>
<note>
<date>2008-02-26</date>
<text>changed title to include "Last Call Comment"</text>
</note>
<note>
<date>2008-03-04</date>
<text>merged with additional text bug brought up by Johannes about 5.4</text>
</note>
<note>
<date>2008-03-04</date>
<text>added full text of Johannes comment on 5.4</text>
</note>
<note>
<date>2008-05-08</date>
<text>assigning this to Shane.</text>
</note>
<note>
<date>2008-05-09</date>
<text>This issue has 3 parts.  Part 1 was overcome by events.  Part 2 was implemented
as suggested.  Part 3 was fixed by removing the reference to a bnode.</text>
</note>
<note>
<date>2008-06-12</date>
<text>ACTION:Accept</text>
</note>
<note>
<date>2008-06-12</date>
<text>CHANGE-TYPE:Editorial</text>
</note>
<note>
<date>2008-06-12</date>
<text>RESOLUTION:This issue has 3 parts. Part 1 was overcome by events. Part 2 was
implemented as suggested. Part 3 was fixed by removing the reference to a bnode.</text>
</note>
</notes>
</issue>
<issue>
<id>88</id>
<title>Last Call Comment: processing bug in setting of datatype with @content in Syntax</title>
<product>2</product>
<raisedby>6</raisedby>
<created>2008-02-26</created>
<description>"
5.5. Sequence

[...]

* step 10 (9?):
"as a [plain literal] if:
  * @content is present;
  * or all children of the [current element] are text nodes;
  * or there are no child nodes;
  * or the body of the [current element] does have non-text child
    nodes but @datatype is present, with an empty value."
According to this the example in 6.3.1.2

&lt;span property="cal:dtstart" content="20070916T1600-0500"
      datatype="xsd:datetime"&gt;
  September 16th at 4pm
&lt;/span&gt;.

would not create a typed literal (@content is present). Or can the following
bullets (XML literal, typed literal) "overwrite" the result from the first
bullet (plain literal)?

"

by Johannes Koch in:
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Feb/0116.html

Probable Resolution by MarkB in:
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Feb/0117.html

"the simplest solution is to make the minor change of moving the third step
(that checks for typed literals) to become the first."

RESOLVED in http://www.w3.org/2008/03/06-rdfa-minutes as per MarkB.</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080226163405.87B436B62C@tibor.w3.org</uri>
<subject>ISSUE-88: bug in setting of datatype with @content in Syntax</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-02-26</date>
</email>
</emails>
<notes>
<note>
<date>2008-02-26</date>
<text>added "Last Call Comment" in title.</text>
</note>
<note>
<date>2008-03-12</date>
<text>Johannes: approves of resolution
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Mar/0086.html</text>
</note>
<note>
<date>2008-04-30</date>
<text>CLOSED, since it is resolved.</text>
</note>
<note>
<date>2008-06-12</date>
<text>ACTION:Accept</text>
</note>
<note>
<date>2008-06-12</date>
<text>CHANGE-TYPE:bug fix</text>
</note>
<note>
<date>2008-06-12</date>
<text>RESOLUTION: moved the third step (that checks for typed literals) to become the
first. This is a small bug fix that implementors were able to integrate immediately.</text>
</note>
<note>
<date>2008-06-12</date>
<text>COMMENTER-RESPONSE: Accept</text>
</note>
</notes>
</issue>
<issue>
<id>89</id>
<title>Last Call Comment: confusion regarding completion of hanging triples across intermediate HTML elements</title>
<product>2</product>
<raisedby>6</raisedby>
<created>2008-02-26</created>
<description>"
6.1.1.5.2. Using an implicit object

second example:
&lt;div about="http://dbpedia.org/resource/Baruch_Spinoza" rel="dbp:influenced"&gt;
  &lt;div&gt;
    &lt;span property="foaf:name"&gt;Albert Einstein&lt;/span&gt;
    &lt;span property="dbp:dateOfBirth" datatype="xsd:date"&gt;1879-03-14&lt;/span&gt;
  &lt;/div&gt;
&lt;/div&gt;

Because the inner div element has no instanceof attribute, according to section
5.5 step 4 [new subject] is set to the [evaluation context]'s [parent object],
which is &lt;http://dbpedia.org/resource/Baruch_Spinoza&gt;, because the [current
object resource] for the outer div was null.

The incomplete triple
  &lt;http://dbpedia.org/resource/Baruch_Spinoza&gt;
    dbp:influenced ? .
never gets completed. And because no bnode was created, the foaf:name and
dbp:dateOfBirth properties apply to &lt;http://dbpedia.org/resource/Baruch_Spinoza&gt;.

Similar things happen with the third and forth examples in 6.1.1.5.2 and the
sixth example in 6.2:

&lt;div about="http://dbpedia.org/resource/Baruch_Spinoza" rel="dbp:influenced"&gt;
  &lt;span property="foaf:name"&gt;Albert Einstein&lt;/span&gt;
  &lt;span property="dbp:dateOfBirth" datatype="xsd:date"&gt;1879-03-14&lt;/span&gt;
  &lt;div rel="dbp:citizenship"&gt;
    &lt;span about="http://dbpedia.org/resource/Germany" /&gt;
    &lt;span about="http://dbpedia.org/resource/United_States" /&gt;
  &lt;/div&gt;
&lt;/div&gt;
"

by Johannes Koch in:
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Feb/0116.html

Probable Resolution: this looks like confusion, may require small tweak in
language to specifically call out the case of intermediate HTML elements.

Update 2008-03-05: actually, there's a deeper issue:
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Mar/0043.html</description>
<state>5</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080226163654.3A6F75F74E@stu.w3.org</uri>
<subject>ISSUE-89: Last Call Comment: confusion regarding completion of hanging triples across intermediate HTML elements</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-02-26</date>
</email>
</emails>
<notes>
<note>
<date>2008-02-27</date>
<text>followup by Johannes:
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Feb/0118.html</text>
</note>
<note>
<date>2008-03-06</date>
<text>added the note about the deeper issue:
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Mar/0043.html</text>
</note>
<note>
<date>2008-05-08</date>
<text>Status on 2008-05-08: checking with Mark to confirm that we handled this issue
with the 20080501 draft.</text>
</note>
<note>
<date>2008-06-03</date>
<text>this issue was already solved with ISSUE-108, and indeed this is fixed.</text>
</note>
<note>
<date>2008-06-12</date>
<text>ACTION: Accept</text>
</note>
<note>
<date>2008-06-12</date>
<text>CHANGE-TYPE: bug fix</text>
</note>
<note>
<date>2008-06-12</date>
<text>RESOLUTION: this issue was already solved with ISSUE-108, and indeed this is fixed.</text>
</note>
</notes>
</issue>
<issue>
<id>90</id>
<title>Last Call Comment: adding top and first as reserved @rel and @rev values</title>
<product>2</product>
<raisedby>6</raisedby>
<created>2008-02-26</created>
<description>"
9.3. @rel/@rev attribute values

* While there is a "last" value listed, there is no "first".
* What about "top"?
"

by Johannes Koch in:
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Feb/0116.html

Probable Resolution: ensure we have all existing reserved words in XHTML,
otherwise leave this decision to the XHTML WG.</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080226164007.2F3685F74E@stu.w3.org</uri>
<subject>ISSUE-90: Last Call Comment: adding \\'top\\' and \\'first\\' to reserved values of @rel/@rev</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-02-26</date>
</email>
<email>
<uri>http://www.w3.org/mid/5.1.0.14.2.20080313122858.02dbb8c0@127.0.0.1</uri>
<subject>meeting record: 2008-03-13 RDF-in-XHTML TF telecon</subject>
<sender>swick@w3.org</sender>
<date>2008-03-13</date>
</email>
</emails>
<notes>
<note>
<date>2008-03-04</date>
<text>fixed title to make it visible in the listing (no single quotes.)</text>
</note>
<note>
<date>2008-03-20</date>
<text>RESOLVED in http://www.w3.org/2008/03/13-rdfa-minutes as "accept XHTML2 WG
decision on reserved keywords", which in this case includes accepting "top" and
"first".</text>
</note>
<note>
<date>2008-03-20</date>
<text>note sent to Johannes:
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Mar/0239.html</text>
</note>
<note>
<date>2008-04-30</date>
<text>CLOSED, since it is resolved.</text>
</note>
<note>
<date>2008-06-12</date>
<text>ACTION: Accept</text>
</note>
<note>
<date>2008-06-12</date>
<text>CHANGE-TYPE: Editorial</text>
</note>
<note>
<date>2008-06-12</date>
<text>RESOLUTION: inquired with the XHTML WG, who agreed that these additional
reserved terms should be added to the XHTML namespace for consistency. Updated
the RDFa specification accordingly.</text>
</note>
<note>
<date>2008-06-12</date>
<text>COMMENTER-RESPONSE: Accept</text>
</note>
<note>
<date>2008-06-12</date>
<text>Johannes acknowledged the change:
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Mar/0255.html</text>
</note>
</notes>
</issue>
<issue>
<id>93</id>
<title>Last Call Comment: editorial bug in 5.5 processing rule 4</title>
<product>2</product>
<raisedby>6</raisedby>
<created>2008-03-04</created>
<description>raised by Shane:
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Feb/0162.html

"
In Section 5.5, processing rule 4, it says "If no URI is provided by a 
resource attribute, then..."

This is a little confusing, since we of course have an attribute named 
"resource".  What is meant is "If no new subject URI is obtained via 
these rules, then..."  I hope, anyway.
"

Proposed Resolution: accept Shane's wording.</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080304042223.94AD7C6DC0@barney.w3.org</uri>
<subject>ISSUE-93: Last Call Comment: editorial bug in 5.5 processing rule 4</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-03-04</date>
</email>
</emails>
<notes>
<note>
<date>2008-03-21</date>
<text>RESOLVED as "If no new subject URI is obtained via these rules, then...", as per
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Mar/0286.html</text>
</note>
<note>
<date>2008-04-30</date>
<text>CLOSED, since it is resolved.</text>
</note>
<note>
<date>2008-06-12</date>
<text>ACTION: Accept</text>
</note>
<note>
<date>2008-06-12</date>
<text>CHANGE-TYPE: Editorial</text>
</note>
<note>
<date>2008-06-12</date>
<text>RESOLUTION: accepted Shane's wording.</text>
</note>
<note>
<date>2008-06-12</date>
<text>COMMENTER-RESPONSE: Accept</text>
</note>
</notes>
</issue>
<issue>
<id>91</id>
<title>Last Call Comment: informative section on other XML dialects states a requirement</title>
<product>2</product>
<raisedby>6</raisedby>
<created>2008-02-26</created>
<description>"
A. Other XML Languages

"If a language includes @xml:base [XMLBASE], an RDFa parser for that host
language must process it, and use its value to set [base]."
Is this a requirement? The section is marked "informative".
"

by Johannes Koch in:
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Feb/0116.html

Probable Resolution: we may not want to state any *requirements* about other
host languages, probably only indications. Requires further discussion.</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080226164201.7B0615F74E@stu.w3.org</uri>
<subject>ISSUE-91: Last Call Comment: informative section on other XML dialects states a requirement</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-02-26</date>
</email>
<email>
<uri>http://www.w3.org/mid/5.1.0.14.2.20080313122858.02dbb8c0@127.0.0.1</uri>
<subject>meeting record: 2008-03-13 RDF-in-XHTML TF telecon</subject>
<sender>swick@w3.org</sender>
<date>2008-03-13</date>
</email>
</emails>
<notes>
<note>
<date>2008-03-20</date>
<text>RESOLVED in http://www.w3.org/2008/03/13-rdfa-minutes as "we remove the xml:base
example, and move the xml:base description (minus example) into the main text,
removing appendix A."</text>
</note>
<note>
<date>2008-03-20</date>
<text>sent note to Johannes:
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Mar/0240.html</text>
</note>
<note>
<date>2008-04-30</date>
<text>CLOSED, since it is resolved.</text>
</note>
<note>
<date>2008-06-12</date>
<text>ACTION: Accept</text>
</note>
<note>
<date>2008-06-12</date>
<text>CHANGE-TYPE: Editorial</text>
</note>
<note>
<date>2008-06-12</date>
<text>RESOLUTION: we remove the xml:base example, and move the xml:base description
(minus example) into the main text, removing appendix A.</text>
</note>
<note>
<date>2008-06-12</date>
<text>Johannes acknowledges response:
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Mar/0257.html</text>
</note>
<note>
<date>2008-06-12</date>
<text>COMMENTER-RESPONSE: Accept</text>
</note>
</notes>
</issue>
<issue>
<id>92</id>
<title>Last Call Comment: resolution of @about=</title>
<product>2</product>
<raisedby>6</raisedby>
<created>2008-02-27</created>
<description>Johannes worries that @about="" will resolve to the parent directory of the
current URI, not the full URI:

"
section 5.5 step 4:

"if the element is the head or body element then act as if there is an 
empty @about present, and process it according to the rule for @about, 
above;"

As the type of @about is URIorCURIE, and "" (empty attribute) is no 
valid safe CURIE, it will be treated as a URI reference, which is to be 
resolved to the current base.

So e.g.

""
resolved to
http://www.example.org/foo/bar
results in
http://www.example.org/foo/

Is that what is intended?
"

in:
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Feb/0121.html

Probable Resolution: base actually resolves to the complete URI.</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080227164846.3DE16C6DB0@barney.w3.org</uri>
<subject>ISSUE-92: Last Call Comment: resolution of @about=\\'\\'</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-02-27</date>
</email>
</emails>
<notes>
<note>
<date>2008-03-04</date>
<text>Johannes states that we have correctly explained this on the list, no change
needed to the spec:

http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Mar/0042.html</text>
</note>
<note>
<date>2008-06-12</date>
<text>ACTION: Accept</text>
</note>
<note>
<date>2008-06-12</date>
<text>CHANGE-TYPE: None</text>
</note>
<note>
<date>2008-06-12</date>
<text>RESOLUTION: clarification in email conversion, no change needed.</text>
</note>
<note>
<date>2008-06-12</date>
<text>COMMENTER-RESPONSE: Accept</text>
</note>
</notes>
</issue>
<issue>
<id>94</id>
<title>Last Call Comment: editorial bug in 5.5 processing rule 13</title>
<product>2</product>
<raisedby>6</raisedby>
<created>2008-03-04</created>
<description>raised by Shane:
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Feb/0163.html

"
In section 5.5 Sequence, processing rule 13 (really rule 12) it says "a 
value of 'true' should be returned from this level of processing. 
Otherwise a value of false should be returned." 

Two things:

1) change false to 'false' or change 'true' to true.
2) change should to MUST.  This section is normative, and that is a 
conformance requirement.  The use of "should" is polite, but not what is 
intended I think.
"

Proposed Resolution: uncontroversial, accept Shane's changes.</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080304042552.92B71C6DBB@barney.w3.org</uri>
<subject>ISSUE-94: Last Call Comment: editorial bug in 5.5 processing rule 13</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-03-04</date>
</email>
</emails>
<notes>
<note>
<date>2008-03-21</date>
<text>RESOLVED as Shane proposes above, as per
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Mar/0286.html</text>
</note>
<note>
<date>2008-04-30</date>
<text>CLOSED, since it is resolved.</text>
</note>
<note>
<date>2008-06-12</date>
<text>ACTION: Accept</text>
</note>
<note>
<date>2008-06-12</date>
<text>CHANGE-TYPE: Editorial</text>
</note>
<note>
<date>2008-06-12</date>
<text>RESOLUTION: accept Shane's suggested wording.</text>
</note>
<note>
<date>2008-06-12</date>
<text>COMMENTER-RESPONSE: Accept</text>
</note>
</notes>
</issue>
<issue>
<id>95</id>
<title>Last Call Comment: editorial typo in 5.4, paragraph 3</title>
<product>2</product>
<raisedby>6</raisedby>
<created>2008-03-04</created>
<description>raised by Shane:
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Mar/0027.html

"
Section 5.4 paragraph 3 reads:
"For example, the full URI for Albert Einstein on DPPedia is:"

It should of course be
"For example, the full URI for Albert Einstein on DBPedia is:"
"

Proposed Resolution: obviously accept Shane's comment.</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080304043058.D3A32C6DB0@barney.w3.org</uri>
<subject>ISSUE-95: Last Call Comment: editorial typo in 5.4, paragraph 3</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-03-04</date>
</email>
</emails>
<notes>
<note>
<date>2008-03-21</date>
<text>RESOLVED to fix typo, as per
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Mar/0286.html</text>
</note>
<note>
<date>2008-04-30</date>
<text>CLOSED, since it is resolved.</text>
</note>
<note>
<date>2008-06-12</date>
<text>ACTION: Accept</text>
</note>
<note>
<date>2008-06-12</date>
<text>CHANGE-TYPE: Editorial</text>
</note>
<note>
<date>2008-06-12</date>
<text>RESOLUTION: fixed typo.</text>
</note>
<note>
<date>2008-06-12</date>
<text>COMMENTER-RESPONSE: Accept</text>
</note>
</notes>
</issue>
<issue>
<id>96</id>
<title>Last Call Comment: editorial imprecision in 5.4.3</title>
<product>2</product>
<raisedby>6</raisedby>
<created>2008-03-04</created>
<description>raised by Shane:
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Mar/0028.html

"
Section 5.4.3 reads (in part):

There are a number of ways that attributes will make use of CURIEs, and 
they need to be dealt with differently. These are:

   1. An attribute may be CURIE-only, disallowing other types of values.
      In this case any value that is not a 'curie' according to the
      definition in the section CURIE Syntax Definition
      &lt;http://www.w3.org/TR/rdfa-syntax/#s_curies&gt; should not affect
      processing in any way; this means that not only will there be no
      error reporting, but also the RDFa processor should act as if the
      value simply did not exist.
   2. An attribute may allow CURIEs, as well as a full URI. In this case
      any value that is not surrounded by square brackets, as defined by
      'safe_curie' in the section CURIE Syntax Definition
      &lt;http://www.w3.org/TR/rdfa-syntax/#s_curies&gt;, will be processed as
      if it was a URI. If the value /is/ surrounded by square brackets,
      then the inner content must conform to the 'curie' definiton, and
      as before, if it does not then the value should have no effect on
      processing.

Since this is normative content, the shoulds in need to be "MUST".  
Second, "no effect on processing" is a little ambiguous for my tastes.  
I would prefer "be ignored".  So, these clauses could read:

There are a number of ways that attributes will make use of CURIEs, and 
they need to be dealt with differently. These are:

   1. An attribute may be CURIE-only, disallowing other types of values.
      In this case any value that is not a 'curie' according to the
      definition in the section CURIE Syntax Definition
      &lt;http://www.w3.org/TR/rdfa-syntax/#s_curies&gt; MUST be ignored; this
      means that not only will there be no error reporting, but also the
      RDFa processor MUST act as if the value simply did not exist.
   2. An attribute may allow CURIEs, as well as a full URI. In this case
      any value that is not surrounded by square brackets, as defined by
      'safe_curie' in the section CURIE Syntax Definition
      &lt;http://www.w3.org/TR/rdfa-syntax/#s_curies&gt;, will be processed as
      if it was a URI. If the value /is/ surrounded by square brackets,
      then the inner content must conform to the 'curie' definiton, and
      as before, if it does not then the value MUST be ignored.
"

Proposed Resolution: easy recommendations, accept Shane's wording.</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080304043356.0A4BDC6DB0@barney.w3.org</uri>
<subject>ISSUE-96: Last Call Comment: editorial imprecision in 5.4.3</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-03-04</date>
</email>
</emails>
<notes>
<note>
<date>2008-03-21</date>
<text>continued discussion between Mark and Ben:
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Mar/0285.html</text>
</note>
<note>
<date>2008-06-03</date>
<text>fixed in draft. Mark says: "I've changed the two points that Shane refers to, to 'MUST'. I've also
added a couple of words to make it clear that we're dealing with a
list of items, and that if any one is invalid, it doesn't mean that
the others should not be processed."</text>
</note>
<note>
<date>2008-06-12</date>
<text>ACTION: Accept</text>
</note>
<note>
<date>2008-06-12</date>
<text>CHANGE-TYPE: Editorial</text>
</note>
<note>
<date>2008-06-12</date>
<text>RESOLUTION: changed the two points to 'MUST'. Added a couple of words to make it
clear that we're dealing with a list of items, and that if any one is invalid,
it doesn't mean that the others should not be processed.</text>
</note>
<note>
<date>2008-06-12</date>
<text>COMMENTER-RESPONSE: Accept</text>
</note>
</notes>
</issue>
<issue>
<id>97</id>
<title>Last Call Comment: handing of namespaces and canonicalization of XML literals</title>
<product>2</product>
<raisedby>6</raisedby>
<created>2008-03-06</created>
<description>pointed out by Johannes in this thread:
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Mar/0049.html

What transformation should be applied to XML literals? Specifically, should they
carry the XHTML namespace on all elements? If so, how? Mark points out that the
RDF spec references the Exclusive Canonicalization of XML, which requires at
least an XML parser/serializer and which could get complicated.</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080306004359.63D3A6B62D@kent.w3.org</uri>
<subject>ISSUE-97: Last Call Comment: handing of namespaces and canonicalization of XML literals</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-03-06</date>
</email>
</emails>
<notes>
<note>
<date>2008-03-25</date>
<text>resolved as "the RDFa syntax does not need any change with respect to XMLLiterals. We note that the easy 
way to generate a valid serialization of the XMLLiteral is to dump the namespaces and xml:lang into all 
top-level elements of the xml literal, including xmlns, watching out for redeclarations." on 03/20: http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Mar/0278.html</text>
</note>
<note>
<date>2008-04-30</date>
<text>CLOSED, since it is resolved.</text>
</note>
<note>
<date>2008-06-12</date>
<text>Johannes agrees with resolution:
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Mar/0324.html</text>
</note>
<note>
<date>2008-06-12</date>
<text>ACTION: Accept</text>
</note>
<note>
<date>2008-06-12</date>
<text>CHANGE-TYPE: None</text>
</note>
<note>
<date>2008-06-12</date>
<text>RESOLUTION: the RDFa syntax does not need any change with respect to
XMLLiterals. We note that the easy way to generate a valid serialization of the
XMLLiteral is to dump the namespaces and xml:lang into all top-level elements of
the xml literal, including xmlns, watching out for redeclarations.</text>
</note>
<note>
<date>2008-06-12</date>
<text>COMMENTER-RESPONSE: Accept</text>
</note>
</notes>
</issue>
<issue>
<id>98</id>
<title>URI escaping in SPARQL query in Recipe 6</title>
<product>5</product>
<raisedby>15</raisedby>
<created>2008-03-16</created>
<description>Escape sequences in URIs (such as %20 for whitespaces) must be double-escaped to
build a SPARQL query in the implementation of Recipe 6, pattern 2. The issue and
a potential solution were raised by Josh Tauberer (2008-01-20):

[[[
(...)
I ran into a problem when I created some URIs with %20's in them, 
because the redirect would need to double-escape the %20's when they are 
put into the query string.

After some chin-scratching I found out that mod_rewrite could be used to 
do a proper redirect, and I've documented it here:

   http://rdfabout.com/demo/census/htaccess.txt

There's more explanation in the link, but the short story is putting 
into the main httpd.conf:

   RewriteMap esc int:escape

and then into .htaccess:

   RewriteEngine on
   RewriteBase "/"
   RewriteRule ^(rdf/.*) http://%{HTTP_HOST}/sparql?   (..all one line..)
               query=DESCRIBE+&lt;http://%{HTTP_HOST}/${esc:$1}&gt; [R]
]]]

Source:
http://simile.mit.edu/mail/ReadMsg?listName=Linking%20Open%20Data&amp;msgId=23498

[[[
# When we get URIs with %20s or other escaped characters in them,
# a simple RedirectMatch won't do because in the query string
# DESCRIBE query, the escaped characters will be unescaped at
# some point during processing. So this is bad:
#
# RedirectMatch 303 (/rdf/.*)
http://rdfabout.com/sparql?query=DESCRIBE+%3Chttp://www.rdfabout.com$1%3E
#
# Instead, we need to double-escape the characters: The percent
# signs should ultimately be escaped so the processor gets back
# the original escaping when unescaping is applied.
#
# To do this, we need to use mod_rewrite. However, mod_rewrite is
# operating on the unescaped URI, so we need the 'escape' mapping
# function, which needs to be activated in httpd.conf with:
#     RewriteMap esc int:escape
# The rewrite rule below re-escapes the unescaped URI (getting back
# the problematic URL we started with), and then mod_rewrite
# escapes it again when it sends the redirect, finally achieving
# the double-escape.

RewriteEngine on
RewriteBase "/"
RewriteRule ^(rdf/.*)
http://%{HTTP_HOST}/sparql?query=DESCRIBE+&lt;http://%{HTTP_HOST}/${esc:$1}&gt; [R]
]]]

Source: http://rdfabout.com/demo/census/htaccess.txt
</description>
<state>2</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080316115025.75C096B62C@tibor.w3.org</uri>
<subject>ISSUE-98: URI escaping in SPARQL query in Recipe 6</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-03-16</date>
</email>
</emails>
</issue>
<issue>
<id>99</id>
<title>Last Call Comment: Editorial Bug in @src example in Section 5.3</title>
<product>2</product>
<raisedby>6</raisedby>
<created>2008-03-20</created>
<description>raised by Micah Dubinko in [1].

"""
If I am reading the 21 Feb spec correctly, @src now can stand in for the 
subject of a triple in the absence of @about. Can somebody set me 
straight on how this squares with the leading example in section 5.3?

&lt;div about="http://dbpedia.org/resource/Albert_Einstein"&gt;
  &lt;span property="foaf:name"&gt;Albert Einstein&lt;/span&gt;
  &lt;span property="dbp:dateOfBirth" datatype="xsd:date"&gt;1879-03-14&lt;/span&gt;
  &lt;div rel="dbp:birthPlace" resource="http://dbpedia.org/resource/Germany"&gt;
    &lt;span property="dbp:conventionalLongName"&gt;Federal Republic of Germany&lt;/span&gt;
  &lt;/div&gt;
  &lt;img rel="foaf:depiction"
src="http://en.wikipedia.org/wiki/Image:Albert_Einstein_Head.jpg" /&gt;
&lt;/div&gt;


In particular, how does foaf:depiction fit in here? Given the image 
resource as a subject, shouldn't it use foaf:depicts?
"""

Probably Resolution: this is an editorial bug in section 5.3 where the usage of
@src hasn't been updated to the latest spec. Updating the example to bring the
@rel up one level is the way to fix this.


[1] http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Mar/0114.html</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080320012933.3DE766B62C@tibor.w3.org</uri>
<subject>ISSUE-99: Last Call Comment: Editorial Bug in @src example mistaken in Section 5.3</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-03-20</date>
</email>
</emails>
<notes>
<note>
<date>2008-05-08</date>
<text>This has been fixed in the latest draft (20080501).</text>
</note>
<note>
<date>2008-05-08</date>
<text>following up with Micah:
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008May/0043.html</text>
</note>
<note>
<date>2008-05-21</date>
<text>no response from Micah, but this is fixed and now closed.</text>
</note>
<note>
<date>2008-06-12</date>
<text>ACTION: Accept</text>
</note>
<note>
<date>2008-06-12</date>
<text>CHANGE-TYPE: bug fix</text>
</note>
<note>
<date>2008-06-12</date>
<text>RESOLUTION: fixed the example (wasn't updated from a pre-Last-Call draft).</text>
</note>
<note>
<date>2008-06-13</date>
<text>Micah agrees with resolution:
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Jun/0078.html</text>
</note>
<note>
<date>2008-06-13</date>
<text>COMMENTER-RESPONSE: Accept</text>
</note>
</notes>
</issue>
<issue>
<id>100</id>
<title>Last Call Comment: Bug in Step 11 of Processing rules, as evidenced by Test Case 58</title>
<product>2</product>
<raisedby>6</raisedby>
<created>2008-03-20</created>
<description>raised by Shane in [1]

"""
Test 58 reveals a problem in the processing rules.   Rule 11 says that 
incomplete triples are only completed when a bnode is NOT created, but 
the P elements in test 58 create BNodes - so the incomplete triple from 
the parent DIV should never be completed.
"""

Likely a bug in the presentation of step 11, but needs review.

[1] http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Mar/0087.html</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080320014246.EDFDA6B62C@kent.w3.org</uri>
<subject>ISSUE-100: Last Call Comment: Bug in Step 11 of Processing rules, as evidenced by Test Case 58</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-03-20</date>
</email>
</emails>
<notes>
<note>
<date>2008-05-08</date>
<text>assigned to Shane</text>
</note>
<note>
<date>2008-05-09</date>
<text>This issue was overcome by events - the related rules were changed.</text>
</note>
<note>
<date>2008-06-12</date>
<text>ACTION: Accept</text>
</note>
<note>
<date>2008-06-12</date>
<text>CHANGE-TYPE: bug fix</text>
</note>
<note>
<date>2008-06-12</date>
<text>RESOLUTION: issue overcome by other edits, subsumed.</text>
</note>
<note>
<date>2008-06-12</date>
<text>COMMENTER-RESPONSE: Accept</text>
</note>
</notes>
</issue>
<issue>
<id>101</id>
<title>Last Call Comment: garbage collecting </title>
<product>2</product>
<raisedby>6</raisedby>
<created>2008-03-20</created>
<description>raised by Ben in [1]:

"""
I don't believe it is necessary, and it may be harmful, to garbage 
collect so-called "useless" triples in cases like:

&lt;div rel="foaf:knows"&gt;
   &lt;div rel="foaf:knows"&gt;
     &lt;div rel="foaf:knows"&gt;
       ...
     &lt;/div&gt;
   &lt;/div&gt;
&lt;/div&gt;

So what if someone writes useless triples? That's their intent, so let 
it be :) This step in the processing adds notable complexity to the 
parser rules. It also may make life difficult for authors who are 
progressively writing RDFa, building up a skeleton of bnodes before 
hanging properties onto them: they wouldn't see any triples at all until 
they add a @property, at which point a slew of triples would appear.

There's a notable cost here, and questionable value.
"""

[1] http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Mar/0242.html</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080320014508.B31766B62B@kent.w3.org</uri>
<subject>ISSUE-101: Last Call Comment: garbage collecting \\'useless\\' triples doesn\\'t  seem necessary and could hurt authors as they write RDFa</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-03-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/5.1.0.14.2.20080403145210.04afad50@127.0.0.1</uri>
<subject>meeting record: 2008-04-03 RDF-in-XHTML TF</subject>
<sender>swick@w3.org</sender>
<date>2008-04-03</date>
</email>
</emails>
<notes>
<note>
<date>2008-04-03</date>
<text>further comments by Micah Dubinko:
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Mar/0380.html</text>
</note>
<note>
<date>2008-04-10</date>
<text>RESOLVED to indeed keep these "useless triples" in
http://www.w3.org/2008/04/03-rdfa-minutes.html</text>
</note>
<note>
<date>2008-04-11</date>
<text>RESOLUTION: Modify processing rules per ISSUE-101 to process and produce triples
consisting of only bnodes
-- http://www.w3.org/2008/04/03-rdfa-minutes.html#item03</text>
</note>
<note>
<date>2008-06-12</date>
<text>ACTION: Accept</text>
</note>
<note>
<date>2008-06-12</date>
<text>RESOLUTION: Modify processing rules to process and produce triples consisting of
only bnodes.</text>
</note>
<note>
<date>2008-06-12</date>
<text>COMMENTER-RESPONSE: Accept</text>
</note>
<note>
<date>2008-06-16</date>
<text>CHANGE-TYPE: outstanding issue resolution (BenA had objected)</text>
</note>
</notes>
</issue>
<issue>
<id>102</id>
<title>Last Call Comment: Better name than 'instanceof' is needed</title>
<product>2</product>
<raisedby>6</raisedby>
<created>2008-03-20</created>
<description>raised by John Boyer in [1]:

"""
...
Instantiation does not appear to be what is happening in the case of RDFa. 
 Instead, the element to which you attach "instanceof" is something to 
which you simply seem to be attaching some RDF type information.  A name 
that more accurately reflects that behavior would be preferable.
...
"""


[1] http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Mar/0211.html</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080320031955.DFAB0C6DB0@barney.w3.org</uri>
<subject>ISSUE-102: Last Call Comment: Better name than \\'instanceof\\' is needed</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-03-20</date>
</email>
<email>
<uri>http://www.w3.org/mid/5.1.0.14.2.20080403145210.04afad50@127.0.0.1</uri>
<subject>meeting record: 2008-04-03 RDF-in-XHTML TF</subject>
<sender>swick@w3.org</sender>
<date>2008-04-03</date>
</email>
</emails>
<notes>
<note>
<date>2008-04-03</date>
<text>further comments by Elias:
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Mar/0315.html</text>
</note>
<note>
<date>2008-04-10</date>
<text>RESOLVED to @typeof in http://www.w3.org/2008/04/03-rdfa-minutes.html</text>
</note>
<note>
<date>2008-06-12</date>
<text>ACTION: Accept</text>
</note>
<note>
<date>2008-06-12</date>
<text>RESOLUTION: changed @instanceof to @typeof</text>
</note>
<note>
<date>2008-06-16</date>
<text>CHANGE-TYPE: outstanding issue resolution (StevenP had objected)</text>
</note>
<note>
<date>2008-06-18</date>
<text>John accepts:
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Jun/0106.html</text>
</note>
<note>
<date>2008-06-18</date>
<text>COMMENTER-RESPONSE: Accept</text>
</note>
</notes>
</issue>
<issue>
<id>103</id>
<title>Last Call Comment: a URI-centric approach to CURIEs</title>
<product>2</product>
<raisedby>6</raisedby>
<created>2008-04-03</created>
<description>brought up by Jonathan Rees in [1]:

"""
Hal Abelson of MIT pointed out to me that the [...] syntax
    effectively introduces a new kind of URI - it extends the URI space.
    However, we already have a standard way to extend the URI space,
    namely the creation of new URI schemes.  Did you consider doing this
    (curie:prefix:suffix or cu:prefix:suffix or ...)?  It would have
    some advantages over [...]:

    . it would eliminate the need for a new URIor[safe]CURIE datatype
      since you could just use URI

    . it would protect against possible conflicting future extensions of
      the URI space that include [...]

    . it would avoid ambiguity with relative URIrefs that happen to be
      spelled [...]

    . it would avoid setting a precedent; by introducing [...] you
      pave the way for other notations that extend URI syntax in other
      ways, e.g. {...}, &lt;...&gt;

    I know this makes the mapping of the lexical space to the value
    space for the URI datatype context-sensitive (in the same way that
    the mapping for URIor[safe]CURIE is).  I haven't worked through the
    implications of this.
"""

This requires further discussion.

[1] http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Mar/0294.html</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080403014414.303F3BF63@nelson.w3.org</uri>
<subject>ISSUE-103: Last Call Comment: a URI-centric approach to CURIEs</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-04-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/5.1.0.14.2.20080529122700.052d08b8@127.0.0.1</uri>
<subject>meeting record: 2008-05-29 RDF-in-XHTML Task Force</subject>
<sender>swick@w3.org</sender>
<date>2008-05-29</date>
</email>
</emails>
<notes>
<note>
<date>2008-05-08</date>
<text>Status: needs discussion ASAP</text>
</note>
<note>
<date>2008-05-29</date>
<text>[rrs]
[[
RESOLUTION: ISSUE-103 closed, CURIEs are not URI schemes, they are a macro
expansion mechanism. No need to change the Syntax document. CURIEs are also
QName-like, allowing legacy languages to migrate forward cleanly.
]]
-- http://www.w3.org/2008/05/29-rdfa-minutes.html#item05</text>
</note>
<note>
<date>2008-06-02</date>
<text>resolved in telecon, closing issue.</text>
</note>
<note>
<date>2008-06-12</date>
<text>ACTION: Reject</text>
</note>
<note>
<date>2008-06-12</date>
<text>RESOLUTION: CURIEs are not URI schemes, they are a macro expansion mechanism. No
need to change the Syntax document. CURIEs are also QName-like, allowing legacy
languages to migrate forward cleanly.</text>
</note>
<note>
<date>2008-06-12</date>
<text>CHANGE-TYPE: None</text>
</note>
<note>
<date>2008-06-12</date>
<text>response from Jonathan, doesn't agree with our resolution:
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Jun/0073.html.
Further explanation from Mark:
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Jun/0075.html</text>
</note>
<note>
<date>2008-06-12</date>
<text>COMMENTER-RESPONSE: Disagree</text>
</note>
</notes>
</issue>
<issue>
<id>104</id>
<title>Last Call Comment: Provide complete datatype definitions</title>
<product>2</product>
<raisedby>6</raisedby>
<created>2008-04-03</created>
<description>brought up by Jonathan Rees in [1]:

"""
9.1 Please provide complete datatype definitions (CURIE, etc) at a
    level of detail approaching that of the XML Schema
    documentation (e.g. see http://www.w3.org/TR/xmlschema11-2/#QName).
"""

requires further discussion.

[1] http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Mar/0294.html</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080403014511.466FFBF63@nelson.w3.org</uri>
<subject>ISSUE-104: Last Call Comment: Provide complete datatype definitions</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-04-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/5.1.0.14.2.20080501123531.04398fb0@127.0.0.1</uri>
<subject>meeting record: 2008-05-01 RDFa telecon</subject>
<sender>swick@w3.org</sender>
<date>2008-05-01</date>
</email>
</emails>
<notes>
<note>
<date>2008-05-08</date>
<text>RESOLVED as "Copy the CURIE datatype definition from
WD-curie-20080402/#s_schema" in telecon
http://www.w3.org/2008/05/01-rdfa-minutes.html

On a related note, also RESOLVED: change the wording from URIorCURIE to
URIorSafeCURIE.</text>
</note>
<note>
<date>2008-06-12</date>
<text>ACTION: Accept</text>
</note>
<note>
<date>2008-06-12</date>
<text>CHANGE-TYPE: Editorial</text>
</note>
<note>
<date>2008-06-12</date>
<text>RESOLUTION: Copy the CURIE datatype definition from WD-curie-20080402/#s_schema</text>
</note>
<note>
<date>2008-06-16</date>
<text>COMMENTER-RESPONSE: would prefer more editorial details</text>
</note>
</notes>
</issue>
<issue>
<id>105</id>
<title>Last Call Comment: a few editorial notes</title>
<product>2</product>
<raisedby>6</raisedby>
<created>2008-04-03</created>
<description>as brought up by Jonathan Rees in [1]:

"""
- Microformats are mentioned in the abstract. Please give a citation,
   as these might not be familiar to all readers.

- I find the term 'URIorCURIE' to be very confusing, because a CURIE is
   not a URIorCURIE.  It is very easy to interpret the name to imply
   you have created a syntactic context that admits either a URI or a
   CURIE, which would create an alarming ambiguity; but you have been
   careful not to do this.  'URIorSafeCURIE' would be more appropriate.
   (But I'm bothered by 'safe CURIE' for a similar reason - a safe
   CURIE is not a kind of CURIE.)

- 3.6 Turtle: Incomplete sentence beginning "However, there are ..."

- I know that "recurse" is in wide use in the sense in which you use
   it, but this is very poor English.  To "recurse" is to curse again;
   what you mean is "recur".  Follow the pattern of "incur /
   incursion".

- 5.4.1 extraneous "then" in first sentence.

- 5.4.2 extraneous "then" in last sentence of note.
"""

more or less straight-forward. Requires some sanity checks from Mark and Shane.

[1] http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Mar/0294.html</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080403014728.B4AD7BF63@nelson.w3.org</uri>
<subject>ISSUE-105: Last Call Comment: a few editorial notes</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-04-03</date>
</email>
</emails>
<notes>
<note>
<date>2008-05-08</date>
<text>assigned to Shane</text>
</note>
<note>
<date>2008-05-09</date>
<text>This issue has several parts:

Added a reference to microformats.org.

Changed term to be URIorSafeCURIE.

Fixed the missing content.

We agree that propert English should be the term "recur" but the conventional
computer science term is "recurse" and we are loathe to change it.

Removed the extraneous "then" statements.


</text>
</note>
<note>
<date>2008-06-12</date>
<text>ACTION: Accept</text>
</note>
<note>
<date>2008-06-12</date>
<text>CHANGE-TYPE: Editorial</text>
</note>
<note>
<date>2008-06-12</date>
<text>RESOLUTION: Added a reference to microformats.org. Changed term to be
URIorSafeCURIE. Fixed the missing content. We agree that propert English should
be the term "recur" but the conventional computer science term is "recurse" and
we are loathe to change it. Removed the extraneous "then" statements.</text>
</note>
<note>
<date>2008-06-16</date>
<text>Jonathan Rees responds:
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Jun/0086.html</text>
</note>
<note>
<date>2008-06-16</date>
<text>COMMENTER-RESPONSE: Partial Accept</text>
</note>
</notes>
</issue>
<issue>
<id>106</id>
<title>Last Call Comment: TimBL on a few architectural points of RDFa</title>
<product>2</product>
<raisedby>6</raisedby>
<created>2008-04-03</created>
<description>raised by TimBL in
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Mar/0297.html</description>
<state>0</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080403014850.25497BF63@nelson.w3.org</uri>
<subject>ISSUE-106: Last Call Comment: TimBL on a few architectural points of RDFa</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-04-03</date>
</email>
</emails>
<notes>
<note>
<date>2008-04-10</date>
<text>responded in
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Apr/0069.html</text>
</note>
<note>
<date>2008-06-09</date>
<text>full response in
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Jun/0037.html</text>
</note>
<note>
<date>2008-06-12</date>
<text>ACTION: Partial Accept</text>
</note>
<note>
<date>2008-06-12</date>
<text>CHANGE-TYPE: None</text>
</note>
<note>
<date>2008-06-12</date>
<text>RESOLUTION: answered the point on Follow-Your-Nose with XHTML-namespace
solution, explained why DTDs are unavoidable for now, simplified language on
[default graph]</text>
</note>
<note>
<date>2008-06-19</date>
<text>RESOLUTION: Move the two items "SHOULD be a DOCTYPE" and "SHOULD be a @profile"
from Section 4.1 to a new Informational Appendix "Deployment Advice". Replace
sentence "This is called the [default graph]" with "This specification uses the
term &lt;tref&gt;default graph&lt;/tref&gt; to mean all of the triples asserted by a
document according to the &lt;a href="#s_model"&gt;Processing Model&lt;/a&gt; section."</text>
</note>
<note>
<date>2008-06-19</date>
<text>resolutions noted in telecon: http://www.w3.org/2008/06/19-rdfa-minutes.html.
TimBL had objected in
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Jun/0098.html.
Ralph explains to TimBL resolutions in
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Jun/0114.html,
and TimBL approves in
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Jun/0115.html</text>
</note>
<note>
<date>2008-06-19</date>
<text>ACTION: Accept</text>
</note>
<note>
<date>2008-06-19</date>
<text>CHANGE-TYPE: Editorial</text>
</note>
<note>
<date>2008-06-19</date>
<text>COMMENTER-RESPONSE: Accept</text>
</note>
</notes>
</issue>
<issue>
<id>107</id>
<title>Last Call Comment: missing summary text</title>
<product>2</product>
<raisedby>6</raisedby>
<created>2008-04-03</created>
<description>raised by Micah Dubinko in [1]

"""
Section 5.5 step #10 summary

Currently says:
 &gt;The next step of the iteration is to establish any [current object 
literal];

But should also have words to the effect of:
...and create the triple, if this is not a skipped element
"""

[1] http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Mar/0301.html</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080403015040.A8362BF63@nelson.w3.org</uri>
<subject>ISSUE-107: Last Call Comment: missing summary text</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-04-03</date>
</email>
</emails>
<notes>
<note>
<date>2008-05-08</date>
<text>assigned to Shane.</text>
</note>
<note>
<date>2008-05-09</date>
<text>This was clarified in the processing step.</text>
</note>
<note>
<date>2008-06-12</date>
<text>ACTION: Accept</text>
</note>
<note>
<date>2008-06-12</date>
<text>CHANGE-TYPE: Editorial</text>
</note>
<note>
<date>2008-06-12</date>
<text>RESOLUTION: added language to clarify processing step, as requested.</text>
</note>
<note>
<date>2008-06-13</date>
<text>Micah agrees with resolution:
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Jun/0078.html</text>
</note>
<note>
<date>2008-06-13</date>
<text>COMMENTER-RESPONSE: Accept</text>
</note>
</notes>
</issue>
<issue>
<id>108</id>
<title>Last Call Comment: Ambiguous otherwise step</title>
<product>2</product>
<raisedby>1</raisedby>
<created>2008-04-03</created>
<description>raised by Micah Dubinko in [1]

"""
Section 5.5 step #4
 &gt;/otherwise/, if [parent object] is present, [new subject] is set to 
that /and/ the [skip element] flag is set to 'true';

Spec is unclear on what to do if processing gets to this final step and 
[parent object] is not "present" and ("present" should be more specific, 
e.g. "not null").

Additionally, it seems like an error to set the [skip element] flag in 
this step. In the case of an element with @property and no other 
attributes, the element definitely shouldn't be skipped.
"""

[1] http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Mar/0302.html</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080403015122.A4966BF63@nelson.w3.org</uri>
<subject>ISSUE-108: Last Call Comment: Ambiguous otherwise step</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-04-03</date>
</email>
</emails>
<notes>
<note>
<date>2008-04-30</date>
<text>resolved quickly by Mark, and approved by Micah:
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Apr/0150.html</text>
</note>
<note>
<date>2008-06-12</date>
<text>ACTION: Accept</text>
</note>
<note>
<date>2008-06-12</date>
<text>CHANGE-TYPE: bug fix</text>
</note>
<note>
<date>2008-06-12</date>
<text>RESOLUTION: updated language to prevent confusion.</text>
</note>
<note>
<date>2008-06-12</date>
<text>COMMENTER-RESPONSE: Accept</text>
</note>
</notes>
</issue>
<issue>
<id>109</id>
<title>Last Call Comment: do something with @cite</title>
<product>2</product>
<raisedby>6</raisedby>
<created>2008-04-03</created>
<description>raised by Laurens Holst in [1]:

"""
First of all, I think the @cite attribute on blockquote and q elements 
should have the same status as @href (be considered as @resource), so 
that RDFa can pick up on existing cite attribute annotations in 
documents, and to avoid authors having to write the citation URI twice, 
one for RDFa and one for HTML. See the example in section 6.3.2.1.
"""

Discussion already under way with a good explanation by Mark as to why we didn't
do this [2]. May be sufficient, will confirm with task force.

[1] http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Mar/0309.html
[2] http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Mar/0311.html</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080403015517.99FEEBF63@nelson.w3.org</uri>
<subject>ISSUE-109: Last Call Comment: do something with @cite</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-04-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/768DACDC356ED04EA1F1130F97D29852016638B9@RZJC2EX.jr1.local</uri>
<subject>meeting record: 2008-04-24 RDF-in-XHTML TF telecon</subject>
<sender>michael.hausenblas@joanneum.at</sender>
<date>2008-04-25</date>
</email>
<email>
<uri>http://www.w3.org/mid/5.1.0.14.2.20080501123531.04398fb0@127.0.0.1</uri>
<subject>meeting record: 2008-05-01 RDFa telecon</subject>
<sender>swick@w3.org</sender>
<date>2008-05-01</date>
</email>
</emails>
<notes>
<note>
<date>2008-04-30</date>
<text>RESOLVED as: "We considered @cite but realized that many other attributes would
then require RDFa interpretation and that doing so is not simple. We defer this
issue to a future version of RDFa."</text>
</note>
<note>
<date>2008-05-21</date>
<text>Laurens Holst accepts resolution:
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008May/0155.html</text>
</note>
<note>
<date>2008-06-12</date>
<text>ACTION: Reject</text>
</note>
<note>
<date>2008-06-12</date>
<text>CHANGE-TYPE: None</text>
</note>
<note>
<date>2008-06-12</date>
<text>RESOLUTION: We considered @cite but realized that many other attributes would
then require RDFa interpretation and that doing so is not simple. We defer this
issue to a future version of RDFa.</text>
</note>
<note>
<date>2008-06-12</date>
<text>COMMENTER-RESPONSE: Accept</text>
</note>
</notes>
</issue>
<issue>
<id>110</id>
<title>Last Call Comment: why is @src the same as @about instead of @href?</title>
<product>2</product>
<raisedby>6</raisedby>
<created>2008-04-03</created>
<description>raised by Laurens Holst in [1]:

"""
Second, are you sure that it is a good idea to give @src different 
semantics than @href? I think it would probably be better if they had 
the same semantics in RDFa. The reason for this is that I find the 
difference between overriding @src and @href values (as explained in the 
Primer [2] section 3.6) confusing, and it is not really clear to me why 
they are treated differently. After all, they both reference a resource 
in a very similar manner, only differing in the way the resource is 
displayed.

The usefulness of treating @src as @about also seems to be rather 
limited, as &lt;img&gt; can not have child content and you can thus specify at 
most three triples; one with a literal object, one with a resource 
object, and one reverse relation of the resource. Or, maybe @href should 
also be treated as @about?
"""

A good response by Mark in [2]. May be enough, will discuss with task force.

[1] http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Mar/0309.html
[2] http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Mar/0311.html</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080403015639.6D1E1BF63@nelson.w3.org</uri>
<subject>ISSUE-110: Last Call Comment: why is @src the same as @about instead of @href?</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-04-03</date>
</email>
</emails>
<notes>
<note>
<date>2008-04-30</date>
<text>RESOLVED in http://www.w3.org/2008/04/17-rdfa-minutes.html as "we considered
@src in both subject and object positions, and resolved that the current
situation - it's equivalent to @about - is more useful to authors."</text>
</note>
<note>
<date>2008-05-21</date>
<text>Laurens Holst accepts resolution:
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008May/0156.html</text>
</note>
<note>
<date>2008-06-12</date>
<text>ACTION: Reject</text>
</note>
<note>
<date>2008-06-12</date>
<text>CHANGE-TYPE: None</text>
</note>
<note>
<date>2008-06-12</date>
<text>RESOLUTION: we considered @src in both subject and object positions, and
resolved that the current situation - it's equivalent to @about - is more useful
to authors.</text>
</note>
<note>
<date>2008-06-12</date>
<text>COMMENTER-RESPONSE: Accept</text>
</note>
</notes>
</issue>
<issue>
<id>111</id>
<title>Last Call Comment: XSLT and Conformance Levels</title>
<product>2</product>
<raisedby>6</raisedby>
<created>2008-04-03</created>
<description>raised by Micah Dubinko in [1]:

"""
When the RDFa specification enters Candidate Recommendation, please 
include as part of the exit criteria the requirement for at least one 
100% conforming implementation in XSLT 1.0.

If it turns out to be difficult to fully implement RDFa in XSLT 1.0 (as 
other comments may indicate), please either revise the specification or 
consider a separate conformance level for XSLT processors.
"""

Requires discussion.

[1] http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Mar/0378.html</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080403020016.21692C6DC0@barney.w3.org</uri>
<subject>ISSUE-111: Last Call Comment: XSLT and Conformance Levels</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-04-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/48470299.3040002@adida.net</uri>
<subject>[RDFa] Telecon Thursday - 1500 UTC</subject>
<sender>ben@adida.net</sender>
<date>2008-06-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/768DACDC356ED04EA1F1130F97D29852014C624C@RZJC2EX.jr1.local</uri>
<subject>RE: [RDFa] Telecon Thursday - 1500 UTC</subject>
<sender>michael.hausenblas@joanneum.at</sender>
<date>2008-06-05</date>
</email>
<email>
<uri>http://www.w3.org/mid/5.1.0.14.2.20080605123059.043f0678@127.0.0.1</uri>
<subject>meeting record: 2008-06-05 RDF-in-XHTML task force</subject>
<sender>swick@w3.org</sender>
<date>2008-06-05</date>
</email>
</emails>
<notes>
<note>
<date>2008-05-27</date>
<text>Manu, Fabien, and Ivan are investigating.</text>
</note>
<note>
<date>2008-06-05</date>
<text>RESOLUTION: in response to ISSUE-111, we do not believe a change in the spec is
justifiable. We believe that, architecturally, whitespace and namespace
preservation are important. We will rely on deployment experience to inform
specific implementation techniques.
-- http://www.w3.org/2008/06/05-rdfa-minutes#item03</text>
</note>
<note>
<date>2008-06-09</date>
<text>RESOLVED as: "we do not believe a change in the spec is justifiable. We believe
that, architecturally, whitespace and namespace preservation are important. We
will rely on deployment experience to inform specific implementation techniques."

in telecon:
http://www.w3.org/2008/06/05-rdfa-minutes#item02

and Micah responded:
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Jun/0008.html</text>
</note>
<note>
<date>2008-06-12</date>
<text>ACTION: Reject</text>
</note>
<note>
<date>2008-06-12</date>
<text>CHANGE-TYPE: None</text>
</note>
<note>
<date>2008-06-12</date>
<text>RESOLUTION: we do not believe a change in the spec is justifiable. We believe
that, architecturally, whitespace and namespace preservation are important. We
will rely on deployment experience to inform specific implementation techniques.</text>
</note>
<note>
<date>2008-06-12</date>
<text>COMMENTER-RESPONSE: Accept</text>
</note>
</notes>
</issue>
<issue>
<id>112</id>
<title>Last Call Comment: describe algorithm in functional terms, too</title>
<product>2</product>
<raisedby>6</raisedby>
<created>2008-04-03</created>
<description>raised by Micah Dubinko in [1]:

"""
In addition to the procedural "Sequence" description in section 5.5, 
include a functional description of the algorithm.

Often times, a functional description is better suited for describing an 
algorithm to implementers, even if the eventual code will closely follow 
the sequence of steps given in section 5.5.

The process of translating the sequence description into functional 
terms will help improve the quality of the specification, make any 
algorithm errors or areas that are unclear or difficult to implement 
stand out better, resulting in a smoother call-for-implementations period.

Obviously, people actually implementing in a functional language 
(including XSLT/GRDDL) will find the beneficial as well.

What is a functional description? Any number of possible descriptions 
would qualify, but the essential constraints of a functional description 
are:
* no side-effects or state
* no mutable variables
&lt;http://en.wikipedia.org/wiki/Functional_programming&gt;

For example, a functional description be structured as a series of 
statements like this:
* For each &lt;condition on node&gt; produce a triple with &lt;rule for subject&gt; 
&lt;rule for predicate&gt; &lt;rule for object&gt;

I am personally interested in contributing on the list or wiki to flesh 
out the details of a functional description. I prefer a final result 
with normative weight, though.
"""

Requires discussion.

[1] http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Mar/0379.html</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080403020230.ADD31C6DC0@barney.w3.org</uri>
<subject>ISSUE-112: Last Call Comment: describe algorithm in functional terms, too</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-04-03</date>
</email>
</emails>
<notes>
<note>
<date>2008-04-23</date>
<text>RESOLUTION: "on ISSUE-112, we sympathize with the comment, but, given the
community pull to finalize RDFa, it would take too long to write up a functional
description."

http://www.w3.org/2008/04/17-rdfa-minutes.html#item06</text>
</note>
<note>
<date>2008-04-23</date>
<text>Commentor has accepted this resolution
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Apr/0128.html</text>
</note>
<note>
<date>2008-04-30</date>
<text>CLOSED, since it is resolved.</text>
</note>
<note>
<date>2008-06-12</date>
<text>ACTION: Reject</text>
</note>
<note>
<date>2008-06-12</date>
<text>CHANGE-TYPE: None</text>
</note>
<note>
<date>2008-06-12</date>
<text>RESOLUTION: we sympathize with the comment, but, given the community pull to
finalize RDFa, it would take too long to write up a functional description.</text>
</note>
<note>
<date>2008-06-12</date>
<text>COMMENTER-RESPONSE: Accept</text>
</note>
</notes>
</issue>
<issue>
<id>113</id>
<title>Last Call Comment: clarify situation around document fragments containing RDFa</title>
<product>2</product>
<raisedby>6</raisedby>
<created>2008-04-03</created>
<description>raised by Micah Dubinko in [1]:

"""
In many cases, such as clipboard operations, fragments of XHTML+RDFa 
might be passed around, in which case valuable triples still might be 
extracted from the fragment. Of course, there will always be potential 
cases where the process of extracting the fragment "breaks" the triple 
(or relies on additional context before being processed). But there will 
also be cases where complete triples remain intact in the fragment.

If the RDFa spec doesn't describe what to do in these cases, ad-hoc 
solutions might take hold without the benefit of careful discussion.

Please mention this possibility in the specification, describe normative 
behavior, and produce test cases for the behavior.

The Last Call specification specifies special handling for the &lt;head&gt; 
and &lt;body&gt; elements. Please specify processing rules and conditions that 
apply to document fragments containing RDFa, in particular for cases 
where no &lt;head&gt; nor &lt;body&gt; element would be encountered.
"""

[1] http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Mar/0381.html</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080403020645.BAFF7C6DC0@barney.w3.org</uri>
<subject>ISSUE-113: Last Call Comment: clarify situation around document fragments containing RDFa</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-04-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/768DACDC356ED04EA1F1130F97D29852016638B9@RZJC2EX.jr1.local</uri>
<subject>meeting record: 2008-04-24 RDF-in-XHTML TF telecon</subject>
<sender>michael.hausenblas@joanneum.at</sender>
<date>2008-04-25</date>
</email>
<email>
<uri>http://www.w3.org/mid/5.1.0.14.2.20080501123531.04398fb0@127.0.0.1</uri>
<subject>meeting record: 2008-05-01 RDFa telecon</subject>
<sender>swick@w3.org</sender>
<date>2008-05-01</date>
</email>
<email>
<uri>http://www.w3.org/mid/48470299.3040002@adida.net</uri>
<subject>[RDFa] Telecon Thursday - 1500 UTC</subject>
<sender>ben@adida.net</sender>
<date>2008-06-04</date>
</email>
<email>
<uri>http://www.w3.org/mid/768DACDC356ED04EA1F1130F97D29852014C624C@RZJC2EX.jr1.local</uri>
<subject>RE: [RDFa] Telecon Thursday - 1500 UTC</subject>
<sender>michael.hausenblas@joanneum.at</sender>
<date>2008-06-05</date>
</email>
<email>
<uri>http://www.w3.org/mid/5.1.0.14.2.20080605123059.043f0678@127.0.0.1</uri>
<subject>meeting record: 2008-06-05 RDF-in-XHTML task force</subject>
<sender>swick@w3.org</sender>
<date>2008-06-05</date>
</email>
</emails>
<notes>
<note>
<date>2008-05-08</date>
<text>proposed paragraph in
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008May/0030.html</text>
</note>
<note>
<date>2008-06-05</date>
<text>RESOLUTION: close ISSUE-113 as "we will not be specifying processing rules for
fragments, though a future version of the spec may do so. We don't rule out the
use case."
-- http://www.w3.org/2008/06/05-rdfa-minutes#item03</text>
</note>
<note>
<date>2008-06-09</date>
<text>RESOLVED as "we will not be specifying processing rules for fragments, though a
future version of the spec may do so. We don't rule out the use case."

in telecon:

http://www.w3.org/2008/06/05-rdfa-minutes#item03</text>
</note>
<note>
<date>2008-06-12</date>
<text>Micah ACCEPTs the resolution:
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Jun/0066.html</text>
</note>
<note>
<date>2008-06-12</date>
<text>ACTION: Partial Accept</text>
</note>
<note>
<date>2008-06-12</date>
<text>CHANGE-TYPE: Editorial</text>
</note>
<note>
<date>2008-06-12</date>
<text>RESOLUTION: we will not be specifying processing rules for fragments, though a
future version of the spec may do so. We don't rule out the use case. We added a
non-normative explanation of how fragments may contain RDFa.</text>
</note>
<note>
<date>2008-06-12</date>
<text>COMMENTER-RESPONSE: Accept</text>
</note>
</notes>
</issue>
<issue>
<id>114</id>
<title>Last Call Comment: RDFa specified for static pages, what about dynamic content?</title>
<product>2</product>
<raisedby>6</raisedby>
<created>2008-04-03</created>
<description>raised by PFWG in [1]

"""
2.1 Processing described for static information only (section 5)

RDFa in XHTML seems to be scoped for static information only, and the processing
model is described for a static DOM that does not account for dynamic changes
after the document has been loaded. (Cf. first sentence in 5.5: “Processing
would normally begin after the document to be parsed has been completely
loaded”.)  This processing model seems restricted with regard to Web 2.0
applications that dynamically add or remove information while interacting with
the user.  Has the use of RDFa for dynamic information in XHTML pages been
considered? 
"""

[1] http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Apr/0031.html</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080403171326.77A56BF64@nelson.w3.org</uri>
<subject>ISSUE-114: Last Call Comment: RDFa specified for static pages, what about dynamic content?</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-04-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/768DACDC356ED04EA1F1130F97D29852016638B9@RZJC2EX.jr1.local</uri>
<subject>meeting record: 2008-04-24 RDF-in-XHTML TF telecon</subject>
<sender>michael.hausenblas@joanneum.at</sender>
<date>2008-04-25</date>
</email>
<email>
<uri>http://www.w3.org/mid/5.1.0.14.2.20080501123531.04398fb0@127.0.0.1</uri>
<subject>meeting record: 2008-05-01 RDFa telecon</subject>
<sender>swick@w3.org</sender>
<date>2008-05-01</date>
</email>
</emails>
<notes>
<note>
<date>2008-04-17</date>
<text>Ralph proposes a response in
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Apr/0116.html</text>
</note>
<note>
<date>2008-04-30</date>
<text>RESOLVED in http://www.w3.org/2008/04/24-rdfa-minutes.html as "No change in the
syntax document needed as it is not obvious that there is a tractable solution
to the full problem. We will create a section on the RDFa community Wiki to
address dynamic modification of XHTML."

Manu to contact PFWG.</text>
</note>
<note>
<date>2008-06-02</date>
<text>Waited 1 month for response from PFWG, haven't received one. Closing Issue.

Email requesting feedback:
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Apr/0155.html</text>
</note>
<note>
<date>2008-06-12</date>
<text>ACTION: Partial Accept</text>
</note>
<note>
<date>2008-06-12</date>
<text>CHANGE-TYPE: Editorial</text>
</note>
<note>
<date>2008-06-12</date>
<text>RESOLUTION: No change in the syntax document needed as it is not obvious that
there is a tractable solution to the full problem. We will create a section on
the RDFa community Wiki to address dynamic modification of XHTML.</text>
</note>
<note>
<date>2008-06-12</date>
<text>COMMENTER-RESPONSE: No Response after 1 month</text>
</note>
</notes>
</issue>
<issue>
<id>115</id>
<title>Last Call Comment: issues with @content</title>
<product>2</product>
<raisedby>6</raisedby>
<created>2008-04-03</created>
<description>raised by PFWG in [1]

"""
2.2 Issues with @content (section 6.3.1.1)

@content may be used to indicate a plain literal which would overwrite the
element content for RDF generation purposes.


(a) What is the rationale for having the @content value replace the element
content in terms of RDF statements?  Why not make the @content value an
alternative object in the statement (with the element content being the other
alternative object)?  - This would give the end user the option to choose
between the two alternatives.


(b) The use of @content bears the drawback that its value cannot be marked up. 
The most prominent need for markup of text for assistive technology is the
indication of language.  The spec addresses this issue (section 6.3.1.1.1) by
making a sibling @xml:lang reign over @content.  However, this does not solve
the problem of language changes inside the @content value (foreign words).   We
propose to add a note that warns about the drawback of @content with regard to
marking up foreign words within its value, and recommend using the (marked-up)
element content instead of @content, wherever possible.
"""

[1] http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Apr/0031.html</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080403171407.A8274BF63@nelson.w3.org</uri>
<subject>ISSUE-115: Last Call Comment: issues with @content</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-04-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/5.1.0.14.2.20080501123531.04398fb0@127.0.0.1</uri>
<subject>meeting record: 2008-05-01 RDFa telecon</subject>
<sender>swick@w3.org</sender>
<date>2008-05-01</date>
</email>
</emails>
<notes>
<note>
<date>2008-05-08</date>
<text>RESOLVED by adding a short non-normative paragraph approximately as follows
"Note that the use of @content prohibits the inclusion of rich markup in your
content. If the inline content of an element is what you are trying to convey,
then documents should rely upon that rather than duplicating that content using
the @content attribute."

in telecon

http://www.w3.org/2008/05/01-rdfa-minutes.html</text>
</note>
<note>
<date>2008-06-12</date>
<text>ACTION: Accept</text>
</note>
<note>
<date>2008-06-12</date>
<text>CHANGE-TYPE: Editorial</text>
</note>
<note>
<date>2008-06-12</date>
<text>RESOLUTION: added a short non-normative paragraph approximately as follows "Note
that the use of @content prohibits the inclusion of rich markup in your content.
If the inline content of an element is what you are trying to convey, then
documents should rely upon that rather than duplicating that content using the
@content attribute."</text>
</note>
<note>
<date>2008-06-12</date>
<text>PFWG responded that they can live with this resolution:
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008May/0164.html</text>
</note>
<note>
<date>2008-06-12</date>
<text>COMMENTER-RESPONSE: can live with it</text>
</note>
</notes>
</issue>
<issue>
<id>116</id>
<title>Last Call Comment: use CURIE prefix other than xmlns for future HTML compatibility</title>
<product>2</product>
<raisedby>6</raisedby>
<created>2008-04-03</created>
<description>raised by PFWG in [1]

"""
2.5 RDFa in HTML documents

This specification does not address using RDFa in HTML documents (only for XHTML
documents).  While most of the specification could also be applied to HTML
documents, the mapping of CURIE prefixes will have to be rewritten for HTML
documents (since there is no namespace concept in HTML).

This and the complexity problem mentioned in 2.4 make us wonder if the concept
of CURIEs should be modified to not use the “xmlns:[prefix]” attribute for
prefix mapping.  Have you considered alternatives that would allow a consistent
use of RDFa in HTML and XHTML documents?  From the perspective of accessibility,
consistency between HTML and XHTML documents should be a goal of the specification.
"""

[1] http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Apr/0031.html</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080403171502.C9FAEC6DC5@barney.w3.org</uri>
<subject>ISSUE-116: Last Call Comment: use CURIE prefix other than xmlns for future HTML compatibility</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-04-03</date>
</email>
<email>
<uri>http://www.w3.org/mid/768DACDC356ED04EA1F1130F97D29852016638B9@RZJC2EX.jr1.local</uri>
<subject>meeting record: 2008-04-24 RDF-in-XHTML TF telecon</subject>
<sender>michael.hausenblas@joanneum.at</sender>
<date>2008-04-25</date>
</email>
</emails>
<notes>
<note>
<date>2008-04-17</date>
<text>Ralph proposes a response in
http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Apr/0115.html</text>
</note>
<note>
<date>2008-04-30</date>
<text>RESOLVED in http://www.w3.org/2008/04/24-rdfa-minutes.html as "No change in the
syntax document needed." and use Ralph's response to the WG.

Manu to contact PFWG.</text>
</note>
<note>
<date>2008-06-02</date>
<text>waited 1 month for comments from PFWG. Closing Issue. Email requesting feedback:

http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Apr/0156.html</text>
</note>
<note>
<date>2008-06-12</date>
<text>ACTION: Reject</text>
</note>
<note>
<date>2008-06-12</date>
<text>CHANGE-TYPE: None</text>
</note>
<note>
<date>2008-06-12</date>
<text>RESOLUTION: No change in the syntax document needed.</text>
</note>
<note>
<date>2008-06-12</date>
<text>COMMENTER-RESPONSE: None after 1 month.</text>
</note>
</notes>
</issue>
<issue>
<id>117</id>
<title>Deprecated Vocabulary</title>
<product>3</product>
<raisedby>16</raisedby>
<created>2008-04-17</created>
<description>How should we handle the deprecated (legacy) SKOS vocabulary in the SKOS
namespace document?  Should the RDF schema for SKOS include the deprecated
vocabulary or not?

Action assigned to Sean to write a proposal:
http://www.w3.org/2008/02/12-swd-minutes.html#action06</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080417121830.9A64E5F74E@stu.w3.org</uri>
<subject>ISSUE-117: Deprecated Vocabulary</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-04-17</date>
</email>
<email>
<uri>http://www.w3.org/mid/19DA38A9-C4EC-4CE0-8FDB-9D9A231EF0D4@manchester.ac.uk</uri>
<subject>Draft SKOS Scheme </subject>
<sender>sean.bechhofer@manchester.ac.uk</sender>
<date>2008-04-29</date>
</email>
</emails>
<notes>
<note>
<date>2008-04-17</date>
<text>2008-04-07: Sean writes a proposal
http://lists.w3.org/Archives/Public/public-swd-wg/2008Apr/0032.html</text>
</note>
<note>
<date>2008-04-17</date>
<text>2008-04-08: Sean's proposal discussesd during telecon
http://www.w3.org/2008/04/08-swd-minutes.html#item03</text>
</note>
<note>
<date>2008-04-17</date>
<text>2008-04-15: Telecon notes that our rationale for decising this issue should be
documented in the WG's Vocabulary Management Note deliverable
http://www.w3.org/2008/04/15-swd-minutes.html</text>
</note>
<note>
<date>2008-04-17</date>
<text>See also: issue 118 "Deprecating Terms or Modifying Terms" on VM
http://www.w3.org/2006/07/SWD/track/issues/118</text>
</note>
<note>
<date>2008-05-07</date>
<text>Closed through resolution on new SKOS namespace
http://www.w3.org/2008/05/06-swd-minutes.html#skosnamespace</text>
</note>
</notes>
</issue>
<issue>
<id>118</id>
<title>Deprecating Terms or Modifying Terms</title>
<product>4</product>
<raisedby>2</raisedby>
<created>2008-04-17</created>
<description>What detailed guidance can we give to designers faced with the question of
whether to create a new namespace name or modify an existing namespace document
when deprecating old vocabulary or modifying the semantics of old vocabulary?
</description>
<state>2</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080417124331.7C4C45F74E@stu.w3.org</uri>
<subject>ISSUE-118: Deprecating Terms or Modifying Terms</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-04-17</date>
</email>
</emails>
<notes>
<note>
<date>2008-04-17</date>
<text>Related: issue 117 "Deprecated Vocabulary" on SKOS
http://www.w3.org/2006/07/SWD/track/issues/117</text>
</note>
<note>
<date>2008-04-17</date>
<text>Related: issue 106 "reuse OWL 1.0 namespace?" on OWL 2
http://www.w3.org/2007/OWL/tracker/issues/106</text>
</note>
<note>
<date>2008-04-17</date>
<text>See also: issue 109 "What is the namespace for elements and attributes in the
XML serialization" on OWL 2
http://www.w3.org/2007/OWL/tracker/issues/109</text>
</note>
</notes>
</issue>
<issue>
<id>119</id>
<title>SkosImports</title>
<product>3</product>
<raisedby>8</raisedby>
<created>2008-04-29</created>
<description>From http://lists.w3.org/Archives/Public/public-esw-thes/2008Mar/0005.html ...

---

So consider an OWL ontology called ONT1, it contains the following  
instances.

ex1:csA rdf:type skos:ConceptScheme

ex1:csB rdf:type skos:ConceptScheme

I also have an Ontology called ONT2 that conatins:

ex2:csC rdf:type skos:ConceptScheme

ex2:csC owl:imports ex1:csA

What should I expect to get imported into ONT2. I get two different  
results depending on how I interpret skos:ConceptSchema (i.e as a  
owl:Class or an owl:Ontology - If I am correct it is consistent in  
SKOS to do both)

1) ONT2 imports only the concepts that are in concept scheme csA?  
(which is what I want to happen)

2) ONT2 imports all of ONT1? (which is how it could be interpreted  
because of the semantics of owl:imports)

If owl:imports is to be used with concept schemes then why not always  
treat concept schemes to be the same as owl:Ontologies?  Was the  
possibility of a skos:imports ever discussed by the working group?</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080429143759.EF21E5F74F@stu.w3.org</uri>
<subject>ISSUE-119: SkosImports</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-04-29</date>
</email>
<email>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB66903B87AC7@hqgiex01.fao.org</uri>
<subject>List of resolutions from the Face-to-Face meeting</subject>
<sender>Margherita.Sini@fao.org</sender>
<date>2008-05-13</date>
</email>
<email>
<uri>http://www.w3.org/mid/482ADFEC.9070001@cs.vu.nl</uri>
<subject>Re: List of resolutions from the Face-to-Face meeting</subject>
<sender>schreiber@cs.vu.nl</sender>
<date>2008-05-14</date>
</email>
</emails>
<notes>
<note>
<date>2008-05-07</date>
<text>RESOLVED: That SKOS does not have its own specific import mechanism and that
documents will have appropriate text on how to use existing owl:import mechanisms
-- http://www.w3.org/2008/05/07-swd-minutes.html#item03</text>
</note>
</notes>
</issue>
<issue>
<id>120</id>
<title>Last Call Comment: Ambiguous Situation with nested @rel where inner @rel is neither CURIE nor link type</title>
<product>2</product>
<raisedby>6</raisedby>
<created>2008-05-09</created>
<description>As per Ben's email [1]

"""
Here's the markup that we believe is ambiguous:

&lt;div about="" rel="dc:creator"&gt;
    &lt;img rel="myfoobarrel" href="ben.jpg" /&gt;
&lt;/div&gt;

The question here is: does &lt;ben.jpg&gt; complete dc:creator, because 
myfoobarrel is neither a CURIE nor a link type? In other words, do we 
get the following triple:

   &lt;&gt; dc:creator &lt;ben.jpg&gt; .

?

My interpretation of the spec is that rel="myfoobarrel" is completely 
ignored, meaning that the triple completion behaves as if there was no 
@rel on the img, which means that &lt;ben.jpg&gt; indeed completes dc:creator. 
And I think that's a bad outcome.

Instead, I think the *presence* of @rel, no matter what it contains, 
should cause completion of the incomplete triples. Then, once the 
triples are completed, the *contents* of the @rel are considered for new 
triple creation.

Consider what would happen if you had a different @rel:

&lt;div about="" rel="dc:creator"&gt;
    &lt;img rel="foaf:img" href="ben.jpg" /&gt;
&lt;/div&gt;

which would then yield:

   &lt;&gt; dc:creator _:bnode1 .
   _:bnode1 foaf:img &lt;ben.jpg&gt; .

Changing the @rel value on img should certainly kill the second triple, 
but I don't see why it should change the first triple at all.

"""


[1] http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008May/0045.html</description>
<state>1</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080509003840.70408153720@plopper.w3.org</uri>
<subject>ISSUE-120: Ambiguous Situation with nested @rel where inner @rel is neither CURIE nor link type</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-05-09</date>
</email>
<email>
<uri>http://www.w3.org/mid/5.1.0.14.2.20080529122700.052d08b8@127.0.0.1</uri>
<subject>meeting record: 2008-05-29 RDF-in-XHTML Task Force</subject>
<sender>swick@w3.org</sender>
<date>2008-05-29</date>
</email>
</emails>
<notes>
<note>
<date>2008-05-29</date>
<text>[[
RESOLUTION: Resolve ISSUE-120 having made a minor change to the Syntax Document
specifying that the presence of a @rel is sufficient to complete an incomplete
triple.
]]
-- http://www.w3.org/2008/05/29-rdfa-minutes.html#item04</text>
</note>
<note>
<date>2008-06-02</date>
<text>resolved in telecon, closing issue.</text>
</note>
<note>
<date>2008-06-12</date>
<text>ACTION: Accept</text>
</note>
<note>
<date>2008-06-12</date>
<text>CHANGE-TYPE: bug fix</text>
</note>
<note>
<date>2008-06-12</date>
<text>RESOLUTION: a minor change to the Syntax Document specifying that the presence
of a @rel is sufficient to complete an incomplete triple.</text>
</note>
<note>
<date>2008-06-12</date>
<text>COMMENTER-RESPONSE: Accept</text>
</note>
</notes>
</issue>
<issue>
<id>121</id>
<title>CR Comment: clarification of default namespace</title>
<product>2</product>
<raisedby>6</raisedby>
<created>2008-06-19</created>
<description>Florian Schmedding wants clarification of default namespace language [1]

"""
section 7 says the RDFa default prefix mapping is
http://www.w3.org/1999/xhtml/vocab# and has to be used when the prefix but
not the colon is omitted in a CURIE. At the bottom of page 53 is then said
that "the mapping to use with the default prefix is the current default
mapping" which would be the value of @xmlns in scope and therefore normally
http://www.w3.org/1999/xhtml (section 4.1).

According to that, in Test 63 the predicate would be
http://www.w3.org/1999/xhtmlnext rather than
http://www.w3.org/1999/xhtml/vocab#next (rel=":next"). Additionally, page 29
states that the prefix http://www.w3.org/1999/xhtml/vocab# should be used
only for values in @rel/@rev without prefix and colon. Please correct me if
I misunderstood this part.
"""

[1] http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2008Jun/0101.html</description>
<state>2</state>
<emails>
<email>
<uri>http://www.w3.org/mid/20080619164034.3206C6B62B@tibor.w3.org</uri>
<subject>ISSUE-121: CR Comment: clarification of default namespace</subject>
<sender>dean+cgi@w3.org</sender>
<date>2008-06-19</date>
</email>
</emails>
</issue>
</issues>
<actions>
<action>
<id>1</id>
<user>14</user>
<action>Michael to set up a RDFa Test Suite together with Wing Yung</action>
<opened>2007-02-07</opened>
<uri/>
<due>2007-02-26</due>
<state>1</state>
</action>
<action>
<id>2</id>
<user>18</user>
<action>ISSUE-14: Edit "Apache configuration" section of Recipes</action>
<opened>2007-02-13</opened>
<uri/>
<due>2007-03-17</due>
<state>0</state>
</action>
<action>
<id>4</id>
<user>15</user>
<action>ISSUE-17: Write first draft of Recipe 6</action>
<opened>2007-02-13</opened>
<uri/>
<due>2007-03-13</due>
<state>0</state>
</action>
<action>
<id>3</id>
<user>2</user>
<action>ISSUE-16: Write brief summary of User Agent-based content negotiation issues</action>
<opened>2007-02-13</opened>
<uri/>
<due>2007-03-13</due>
<state>0</state>
</action>
<action>
<id>5</id>
<user>18</user>
<action>ISSUE-18: Make changes as requested in the QA doc</action>
<opened>2007-02-13</opened>
<uri/>
<due>2007-03-13</due>
<state>0</state>
</action>
<action>
<id>6</id>
<user>18</user>
<action>ISSUE-15: Remove @@TODO from "Extended Configuration" section of Recipes</action>
<opened>2007-02-13</opened>
<uri/>
<due>2007-03-13</due>
<state>0</state>
</action>
<action>
<id>7</id>
<user>15</user>
<action>ISSUE-20: Provide a timeline for implementing a CN validation service</action>
<opened>2007-02-14</opened>
<uri/>
<due>2007-03-14</due>
<state>0</state>
</action>
<action>
<id>8</id>
<user>18</user>
<action>ISSUE-21: Add mod_rewrite required to Apache Configuration in Recipes</action>
<opened>2007-02-14</opened>
<uri/>
<due>2007-03-14</due>
<state>0</state>
</action>
<action>
<id>9</id>
<user>17</user>
<action>ISSUE-26 Owner</action>
<opened>2007-02-20</opened>
<uri/>
<due>2007-03-20</due>
<state>0</state>
</action>
</actions>
<resolutions>
<resolution>
<id>1</id>
<title>that 11/06 meeeting will take place and 11/13 meeting</title>
<uri>None</uri>
<made>2007-10-23</made>
</resolution>
<resolution>
<id>2</id>
<title>Michael to forward comments to SWEO noting that the</title>
<uri>None</uri>
<made>2007-10-23</made>
</resolution>
<resolution>
<id>3</id>
<title>to approve publications of RDFa Primer as a working</title>
<uri>None</uri>
<made>2007-10-23</made>
</resolution>
<resolution>
<id>4</id>
<title>that 11/06 meeeting will take place and 11/13 meeting</title>
<uri>http://www.w3.org/mid/471E011D0200006A00017852@ntgwgate.loc.gov</uri>
<made>2007-10-23</made>
</resolution>
<resolution>
<id>5</id>
<title>Michael to forward comments to SWEO noting that the</title>
<uri>http://www.w3.org/mid/471E011D0200006A00017852@ntgwgate.loc.gov</uri>
<made>2007-10-23</made>
</resolution>
<resolution>
<id>6</id>
<title>to approve publications of RDFa Primer as a working</title>
<uri>http://www.w3.org/mid/471E011D0200006A00017852@ntgwgate.loc.gov</uri>
<made>2007-10-23</made>
</resolution>
<resolution>
<id>7</id>
<title>Minutes accepted.</title>
<uri>http://www.w3.org/mid/4761021E0200006A0001BF5B@ntgwgate.loc.gov</uri>
<made>2007-12-13</made>
</resolution>
<resolution>
<id>8</id>
<title>to accept minutes of the Feb 12 telecon</title>
<uri>http://www.w3.org/mid/47BDA2FE.3020004@zoo.ox.ac.uk</uri>
<made>2008-02-21</made>
</resolution>
<resolution>
<id>9</id>
<title>that RDFa syntax editors' draft 18 Feb 2008 be published as </title>
<uri>http://www.w3.org/mid/47BDA2FE.3020004@zoo.ox.ac.uk</uri>
<made>2008-02-21</made>
</resolution>
<resolution>
<id>10</id>
<title>to have 4 week period for last call for rdfa syntax (ending </title>
<uri>http://www.w3.org/mid/47BDA2FE.3020004@zoo.ox.ac.uk</uri>
<made>2008-02-21</made>
</resolution>
<resolution>
<id>11</id>
<title>Section 3 of the SKOS reference </title>
<uri>http://www.w3.org/mid/47BDA2FE.3020004@zoo.ox.ac.uk</uri>
<made>2008-02-21</made>
</resolution>
<resolution>
<id>12</id>
<title>Minutes from March 11 accepted. Next meeting 25 March</title>
<uri>http://www.w3.org/mid/47E11ECC0200006A00024B85@ntgwgate.loc.gov</uri>
<made>2008-03-19</made>
</resolution>
<resolution>
<id>13</id>
<title>StatingFormalDefinitions ISSUE-67 accepted</title>
<uri>http://www.w3.org/mid/47E11ECC0200006A00024B85@ntgwgate.loc.gov</uri>
<made>2008-03-19</made>
</resolution>
<resolution>
<id>14</id>
<title>Minutes from March 18 accepted.</title>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB669037A04D3@hqgiex01.fao.org</uri>
<made>2008-04-02</made>
</resolution>
<resolution>
<id>15</id>
<title>F-2-F meeting dates will be 6-7</title>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB669037A04D3@hqgiex01.fao.org</uri>
<made>2008-04-02</made>
</resolution>
<resolution>
<id>16</id>
<title>Mark will do the review</title>
<uri>http://www.w3.org/mid/BA453B6B6B217B4D95AF12DBA0BFB669037A04D3@hqgiex01.fao.org</uri>
<made>2008-04-02</made>
</resolution>
<resolution>
<id>17</id>
<title>not to carry</title>
<uri>http://www.w3.org/mid/6.2.5.6.2.20080528050511.06bef348@stanford.edu</uri>
<made>2008-05-28</made>
</resolution>
<resolution>
<id>18</id>
<title>not to carry forward skos:prefSymbol and skos:altSymbol into the new namespace for lack of clear requirements&lt;/strong&gt;&lt;/p&gt;</title>
<uri>http://www.w3.org/mid/6.2.5.6.2.20080528050511.06bef348@stanford.edu</uri>
<made>2008-05-28</made>
</resolution>
<resolution>
<id>19</id>
<title> to close issue 80 as the technical issues of SKOS/OWL have already been dealt with&lt;/strong&gt;&lt;/p&gt;</title>
<uri>http://www.w3.org/mid/6.2.5.6.2.20080528050511.06bef348@stanford.edu</uri>
<made>2008-05-28</made>
</resolution>
<resolution>
<id>20</id>
<title>technical</title>
<uri>http://www.w3.org/mid/6.2.5.6.2.20080528050511.06bef348@stanford.edu</uri>
<made>2008-05-28</made>
</resolution>
</resolutions>
</database>