[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

FW: SIX 1.0 Spec. Online

• From: Peter Jones <peterj@w...>
• To: "'xml-dev@l...'" <xml-dev@l...>
• Date: Fri, 26 Jan 2001 11:47:09 +0000

Sending this again because it didn't seem to get through last time.

Peter
-----Original Message-----
From: Peter Jones 
Sent: 17 January 2001 15:57
To: 'xml-dev@l...'
Subject: ANN: SIX 1.0 Spec. Online


The Specification for SIX v.1.0 is now available online for comment at 
http://www.inpreparation.com/six/

SIX is designed to provide a uniform transport and interchange syntax for
many types of data or information structures. It is designed to support the
transport of representations of both data and information, and any
relationships between them in single documents.

It is envisaged that the types of information transported between parties
will be agreed by those parties in advance where necessary. The
specification does not state significant processing restrictions in order to
facilitate creative use of SIX.

I hope to be able to post a nice example of SIX at work soon. The use model
I envisage is that of SIX plus SAX plus XSLT (plus knowledgebase, database,
agent, or whatever). In the meantime, I have created a small example of an
agent aided database transaction SIX document below.

Please post comments directly or cc'ed to me (as I am only subscribed to the
digest for xml-dev and I don't want to miss any).

I hope it proves to be useful.

Sincerely,
Peter J

Please note that my email address does not imply any endorsement of SIX by
my employer, Wrox.

The Example:
You could pass Stuff between databases in an agent-aided fashion.

<?xml version="1.0" ?>
<six type="http://mydb.org/six/dbtype.cgi?schematype=777">
<statement ID="DB1"  grouped="yes" namespace="mydb.org/DB-0A1" >
   <subject>
      <predicate predicatename="has-part-types">
         <object objstring="part"></object>
      </predicate>
   </subject> 
  <object objstring="AB"></object>
  <object objstring="CD"></object>
  <object objstring="EF"></object>
  <wcvar varstring="GH"></wcvar>
</statement>
<statement ID="DB3"  grouped="yes" namespace="mydb.org/DB-0A1" >
   <subject>
      <predicate predicatename="has-cost-price">
         <object objstring="#567"></object>
         <object objstring="#578"></object>
         <object objstring="#599"></object>
         <object objstring="#677"></object>
         <wcvar varstring="#899"></wcvar>
      </predicate>
   </subject> 
   <object objstring="5.99" ></object>
</statement>
<statement  ID="DB3" namespace="mydb.org/DB-0A1">
<subject>
      <predicate predicatename="is-type">
             <object objstring="#567"></object>
             <object objstring="#599"></object>
             ...
      </predicate>
      <object objstring="AB"></object>
   </subject> 
</statement>
<statement ID="DB4"  reciprocal="yes" namespace="mydb.org/DB-0A1" >
   <subject>
      <predicate predicatename="has-alias">
         <object objstring="part"></object>
      </predicate>
   </subject> 
  <object objstring="y_part"></object>
  <object objstring="xPart"></object>
  <wcvar varstring="Partypart"></wcvar>
</statement>
<statement ID="DB5"  reciprocal="yes">
   <subject>
      <predicate predicatename="permitted-map-to-namespace">
         <object objstring="mydb.org/DB-0A1"></object>
      </predicate>
   </subject> 
  <object objstring="yourdb.org/BigDB-x98"></object>
  ...
</statement>
<ruledoc type="RulesML" rulesref="http://..." >Some text describing the
RulesML ruleset for inferencing over this metadata</ruledoc>
...
<ruledoc type="..." rulesref="http://..." ></ruledoc>
</six>

• Prev by Date: New W3C XML Schema facet ? [was: RDDL Schematron Schema]
• Next by Date: What is the nature of HTML 4.0? was RE: Proposal for new RDDL naturesand purpose
• Previous by thread: Re: What is the nature of HTML 4.0? was RE: Proposal for newRDDLnatures and purpose
• Next by thread: RE: New W3C XML Schema facet ? [was: RDDL Schematron Schema]
• Index(es):
  • Date
  • Thread