W3C home > Mailing lists > Public > public-sml@w3.org > July 2007

RE: [Bug 4865] clearly doc requirements for defining a reference scheme

From: Wilson, Kirk D <Kirk.Wilson@ca.com>
Date: Thu, 19 Jul 2007 12:54:00 -0400
Message-ID: <F9576E62032243419E097FED5F0E75F303275E9C@USILMS12.ca.com>
To: <bugzilla@wiggum.w3.org>, <public-sml@w3.org>

One small "nit" in item #2.  sml:EPR is not a defined element, there are
just <wsa:EndpointReference>s.  It is just the "URI and EPR schemes."

Kirk Wilson, Ph.D.
Research Staff Member
CA Labs
603 823-7146
 

-----Original Message-----
From: public-sml-request@w3.org [mailto:public-sml-request@w3.org] On
Behalf Of bugzilla@wiggum.w3.org
Sent: Wednesday, July 18, 2007 11:48 AM
To: public-sml@w3.org
Subject: [Bug 4865] clearly doc requirements for defining a reference
scheme


http://www.w3.org/Bugs/Public/show_bug.cgi?id=4865

           Summary: clearly doc requirements for defining a reference
scheme
           Product: SML
           Version: unspecified
          Platform: PC
               URL: http://www.w3.org/2005/06/tracker/sml/actions/81
        OS/Version: Windows XP
            Status: NEW
          Keywords: needsAgreement
          Severity: normal
          Priority: P2
         Component: Core+Interchange Format
        AssignedTo: cmsmcq@w3.org
        ReportedBy: johnarwe@us.ibm.com
         QAContact: public-sml@w3.org


refs: smlif 3.3.2 P 1,4; smlif 3.3.3; sml 3.3.1, 3.3.2
all section numbers based on submission copy

There is a muddled distribution of content on the SML-defined schemes
between
the two specs. I think a better approach would be to:

1. Define what a scheme definition must contain (in SML 3.3 or a
separate
document entirely, possibly a Note... the SMLIF-imposed reqt pattern
could
occur again, and I'd like to not have to rev SML for it).
   - MUST the content comprising/marking the scheme, e.g. sml:uri
   - MUST where the scheme's content occurs, e.g. child of reference
element;  
     probably should ALWAYS be "where, wrt the ref element"
   - SHOULD whether or not the scheme MAY/MUST/etc be interpreted as an
SML-IF 
     reference (SMLIF 3.3.2 defines normative rules if they are not
explicit)

2. Define the sml:uri and sml:EPR schemes, current sections, making sure
   above conditions are satisfied.

3. Add to SML 3.3.1 the fact that its semantic includes the implication
that
   it can be dereferenced using the default action for the scheme (as
stated
   in SMLIF 3.3.2 P 4) so the two sections agree.

4. SMLIF 3.3.3 P 1 S 2 end, add reference to SML 3.3.

5. SMLIF 3.3.3 P 1 S 3 end, add reference to SMLIF 3.3.2

6. SMLIF 3.3.3 change heading "that are not" to "may not be"

7. Re-write SMLIF 3.3.3 P 1 (new text)
   SML [1] defines two reference schemes, the URI reference scheme and
the 
   EPR reference scheme; it also permits new reference schemes to be
defined 
   without limit.  Reference schemes 
   MAY be inter-document references in the context of SML-IF [SMLIF
3.3.2].
   Three consequences flow from this.

8. Re-write SMLIF 3.3.3 P 2 (new text)
   First, to successfully interchange models using reference schemes
that
   are not inter-document references in the context of SML-IF, each
reference
   element must be represented using least one reference scheme that IS 
   an inter-document reference in the context of SML-IF.  For example,
[...
   rest of existing example].

9. Change SMLIF 3.3.3 P 3 "of ... [end of sentence]" to 
   "must agree on at least one
   reference scheme that is an inter-document reference in the context
of 
   SML-IF for each reference element in the interchange set."

10. Change SMLIF 3.3.3 P 4 "sml:ref" to "reference"

11. SMLIF 3.3.2 work in the fact that something may also be an
inter-document
    ref (or not) if explicitly declared by its reference scheme
definition.
    If the ref scheme definition does not make any such declaration, the
ref
    scheme's content is treated as ordinary content under the rules
above
    for xs:anyURI.
Received on Thursday, 19 July 2007 16:54:11 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:56:04 UTC