# $Id: HomeNetworkIssues.n3,v 1.1 2003/01/06 18:40:05 graham Exp $
#
# Home network access control
# Issues list
#
# (Attempting to adapt my document issue-tracking to software issues)
#
#--------+---------+---------+---------+---------+---------+---------+---------+
#
# Copyright (c) 2003, G. KLYNE
# All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions
# are met:
# 1. Redistributions of source code must retain the above copyright
#    notice, this list of conditions and the following disclaimer.
# 2. Redistributions in binary form must reproduce the above copyright
#    notice, this list of conditions and the following disclaimer in the
#    documentation and/or other materials provided with the distribution.
# 3. The name of the author may not be used to endorse or promote products
#    derived from this software without specific prior written permission.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
# IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
# OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
# IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
# INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
# NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
# DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
# THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
# (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
# THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
#
#--------+---------+---------+---------+---------+---------+---------+---------+
# $Source: /Users/graham/cvs/cvsweb/ninebynine.org/docs/SWAD-E/Scenario-HomeNetwork/HomeNetworkIssues.n3,v $
# $Author: graham $
# $Date: 2003/01/06 18:40:05 $
# $Id: HomeNetworkIssues.n3,v 1.1 2003/01/06 18:40:05 graham Exp $
#--------+---------+---------+---------+---------+---------+---------+---------+
#        1         2         3         4         5         6         7         8

@prefix rdf:      <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs:     <http://www.w3.org/2000/01/rdf-schema#> .
@prefix foaf:     <http://xmlns.com/foaf/0.1/> .
@prefix dc:       <http://purl.org/dc/elements/1.1/> .
@prefix iss:      <http://id.ninebynine.org/wip/2002/DocIssues#> .

# About this document:
<> rdfs:label "Home network access control - issues" ;
   iss:about  <http://www.ninebynine.org/SWAD-E/Intro.html#HomeNetAccessDemo> ;
   dc:author  "Graham Klyne" ;
   rdfs:comment
     """
     List of issues and current status for the software and
     documentation for home network access control.
     """ .

# About the target document and software editors

<#Editor-GK>
   foaf:mbox <mailto:GK@ninebynine.org> ;
   foaf:name "Graham Klyne" ;
   foaf:initials "GK" .

# About the home network access control document:
<http://www.ninebynine.org/SWAD-E/Scenario-HomeNetwork/HomeNetworkConfig.html>
   rdf:type iss:Document ;
   iss:name "HomeNetworkConfig" ;
   rdfs:label "Using RDF for Home Network Configuration" ;
   iss:cite <http://www.ninebynine.org/SWAD-E/Scenario-HomeNetwork/HomeNetworkConfig.html> ;
   iss:editor <#Editor-GK> ;
   iss:history                     # document history
    (
      [ iss:status iss:PublicRelease ;
        iss:when   "2002-12-22" ;
        iss:cite   <http://www.ninebynine.org/SWAD-E/Scenario-HomeNetwork/HomeNetworkConfig-20021222.html> ;
        rdfs:comment
           """
           Document version announced to public-esw list.
           """ ]
    ) ;
   rdfs:comment
      """
      This memo describes the use of RDF metadata in configuring
      Internet access from a home network.
      Its goal is to demonstrate the practical applicability of
      common semantic web technologies in a simple real-world
      based scenario.
      The work has been inspired in part by an architectural
      proposal for XML network configuration submitted to the IETF.
      """ ;

   ### Document/system issues follow ###


################ Issue 001 ################

   iss:issue
    [ iss:name     "001-DHCP-Options" ;
      rdfs:label   "Should DHCP options be URIs; editorial" ;
      iss:raisedBy
       [ foaf:mbox     <mailto:wkearney99@hotmail.com> ;
         foaf:name     "Bill Kearney" ;
         foaf:initials "BK" ] ;
      iss:raisedDate   "2002-12-18" ;
      iss:raisedCite   <http://lists.w3.org/Archives/Public/www-rdf-calendar/2002Dec/0021.html> ;
      #iss:resolvedDate "..." ;
      #iss:resolvedCite <http://...> ;
      iss:owner        <#Editor-GK> ;
      iss:status       iss:Raised ;
      iss:when         "2002-12-18" ;
      iss:history
       (
         [ iss:status iss:Raised ;
           iss:when   "2002-12-18" ;
           iss:cite   <http://lists.w3.org/Archives/Public/www-rdf-calendar/2002Dec/0021.html> ;
           rdfs:comment
              """
              Issue raised in private reply to the announcement cited.
              <p/>
              Use of element names (rather than literals?) restricts use of
              DHCP options.
              <p/>
              Suggestion for editorial improvement.
              """ ]
         [ iss:status iss:Comment ;
           #iss:when   "..." ;
           iss:cite   <http://...> ;
           rdfs:comment
              """
              ...
              """ ]
         [ iss:status iss:Response ;
           #iss:when   "..." ;
           iss:cite   <http://...> ;
           rdfs:comment
              """
              ...
              """ ]
         [ iss:status iss:Resolved ;
           #iss:when   "..." ;
           iss:cite   <http://...> ;
           rdfs:comment
              """
              ...
              """ ]
         [ iss:status iss:Closed ;
           #iss:when   "2002-??-??" ;
           iss:cite   <http://www.ninebynine.org/wip/RDF-concepts/2002-??-??/rdf-concepts.html> ;
           rdfs:comment
              """
              Material incorporated into to publicly accessible document.
              """ ]
       ) ;
      iss:sectionRef   <http://www.ninebynine.org/SWAD-E/Scenario-HomeNetwork/HomeNetworkConfig-20021222.html> ;
      rdfs:comment
"""
Given how DHCP has a mechanisms to allow extensibility, is using element names
an improvement?  What if I want to express many of the other DHCP variables that
don't have element names in your namespace?  Granted using an element name is
simpler than using it's DHCP option number.  Most folks don't understand DHCP
let alone the use of options so most probably wouldn't care.

Nice looking work otherwise. (a quick spell check seems in order though).  I
sympathize with your desire to have better disjunction and inference handling.
You may want to reword "I feel that formal structures for representing
disjunction as well as disjunction are needed to support sufficiently powerful
inference processes."
""" ] ;
# -- End of issue --

################ Issue 002 ################

   iss:issue
    [ iss:name     "002-UnfinishedWork" ;
      rdfs:label   "Work items remaining for completing this stage" ;
      iss:raisedBy <#Editor-GK> ;
      iss:raisedDate   "2003-01-06" ;
      iss:raisedCite   <http://www.ninebynine.org/SWAD-E/Scenario-HomeNetwork/HomeNetworkConfig-20021222.html> ;
      #iss:resolvedDate "..." ;
      #iss:resolvedCite <http://...> ;
      iss:owner        <#Editor-GK> ;
      iss:status       iss:Raised ;
      iss:when         "2003-01-06" ;
      iss:history
       (
         [ iss:status iss:Raised ;
           iss:when   "2003-01-06" ;
           iss:cite   <http://www.ninebynine.org/SWAD-E/Scenario-HomeNetwork/HomeNetworkConfig-20021222.html> ;
           iss:cite   <http://www.w3.org/2001/sw/Europe/reports/dev_workshop_report_2/Overview.html> ;
           iss:cite   <http://www.w3.org/2002/12/cal/> ;
           iss:cite   <http://www.w3.org/2001/sw/Europe/reports/dev_workshop_report_2/Overview.html> ;
           rdfs:comment
              """
              In addition to the further work mentioned in the cited document,
              remaining work to do inclodes items noted.
              """ ]
         [ iss:status iss:Comment ;
           #iss:when   "..." ;
           iss:cite   <http://...> ;
           rdfs:comment
              """
              ...
              """ ]
         [ iss:status iss:Response ;
           #iss:when   "..." ;
           iss:cite   <http://...> ;
           rdfs:comment
              """
              ...
              """ ]
         [ iss:status iss:Resolved ;
           #iss:when   "..." ;
           iss:cite   <http://...> ;
           rdfs:comment
              """
              ...
              """ ]
         [ iss:status iss:Closed ;
           #iss:when   "2002-??-??" ;
           iss:cite   <http://www.ninebynine.org/wip/RDF-concepts/2002-??-??/rdf-concepts.html> ;
           rdfs:comment
              """
              Material incorporated into to publicly accessible document.
              """ ]
       ) ;
      iss:sectionRef   <http://www.ninebynine.org/SWAD-E/Scenario-HomeNetwork/HomeNetworkConfig-20021222.html> ;
      iss:sectionRef   <> ;
      iss:sectionRef   <> ;
      rdfs:comment
"""
Immediate work items to complete this phase:

1. Create and publish schema for new vocabularies.

2. Convert vCalendar events to new schema, per
   http://www.w3.org/2001/sw/Europe/reports/dev_workshop_report_2/Overview.html

""" ] ;
# -- End of issue --






################ Issue skeleton ################

   iss:issue
    [ iss:name     "nnn-..." ;
      rdfs:label   "..." ;
      iss:raisedBy
       [ foaf:mbox     <mailto:...@...> ;
         foaf:name     "..." ;
         foaf:initials "..." ] ;
      iss:raisedDate   "..." ;
      iss:raisedCite   <...> ;
      #iss:resolvedDate "..." ;
      #iss:resolvedCite <http://...> ;
      iss:owner        <#Editor-GK> ;
      iss:status       iss:Raised ;
      iss:when         "..." ;
      iss:history
       (
         [ iss:status iss:Raised ;
           iss:when   "..." ;
           iss:cite   <http://...> ;
           rdfs:comment
              """
              ...
              """ ]
         [ iss:status iss:Comment ;
           #iss:when   "..." ;
           iss:cite   <http://...> ;
           rdfs:comment
              """
              ...
              """ ]
         [ iss:status iss:Response ;
           #iss:when   "..." ;
           iss:cite   <http://...> ;
           rdfs:comment
              """
              ...
              """ ]
         [ iss:status iss:Resolved ;
           #iss:when   "..." ;
           iss:cite   <http://...> ;
           rdfs:comment
              """
              ...
              """ ]
         [ iss:status iss:Closed ;
           #iss:when   "2002-??-??" ;
           iss:cite   <http://www.ninebynine.org/wip/RDF-concepts/2002-??-??/rdf-concepts.html> ;
           rdfs:comment
              """
              Material incorporated into to publicly accessible document.
              """ ]
       ) ;
      iss:sectionRef   <http://www.ninebynine.org/SWAD-E/Scenario-HomeNetwork/HomeNetworkConfig-20021222.html#...> ;
      iss:sectionRef   <> ;
      iss:sectionRef   <> ;
      rdfs:comment
"""
... text of issue presented
""" ] ;
# -- End of issue --

   iss:theEnd "PlaceHolder" .

#
# End of issue list for Home network access control
#
#--------+---------+---------+---------+---------+---------+---------+---------+
# $Log: HomeNetworkIssues.n3,v $
# Revision 1.1  2003/01/06 18:40:05  graham
# Add issue list to CVS
#