[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: RE: [xdi] Groups - draft-xdi-metaschema-v7.xsd uploaded
Drummond, I know the feeling..things are crazy on my end trying to get a demo together, with major feature requirements added 2 weeks before the demo. > 1) WRT extensibility, it was a conscious decision to make the > "Data" element... No problem, I thought that it might be to keep the resource branch clean and some of the extensibility can be had by using other namespaces in the data elements of a resources child resources. > 2) WRT a more generic container for XRIs, I can see both > approaches. Most of > the benefits you describe can be provided without modifying the v7 > metaschema by defining an "$xri" resource in the XDI service Hmm, have to think more on this but it definitely looks more elegant than my solution, and possibly more extensible so my gut reaction is that I like it. Only worry is that we should IMHO keep specxial XCRIs few in number or even better establish the following for $ xris .. Registry or concreate mechanism for maintaining separateness .. Documented process for registry operation .. Authority that manages registry The authority will probably be xdi.org, but not sure on process. Btw, I am meeting with a higher up today and one of the topics will be getting Booz Allen to sponsor xdi.org. > I trust with your new baby you're not going to be at Digital ID > World next > week, but will you be able to join one of the two f2f sessions via > telecon?It would be great as I'm sure we'll be discussing this in > depth. I will try, I'm actually on travel myself giving a demo for the client, but if I can get away during the times I will. Our baby is still in the NICU, though I still hate leaving Jen right now even for a couple days. We expected Caitlynn would still be on the way by the time the demo finished, so this is another fallout from the premie surprise. Caitlynn and Jen are doing great though, so I'm counting my blessings. Caitlynn's up to 3 lbs 12 oz, so still very small, but is healthy. I'll lookup the F2F telecon times from the list and see if I can get internet from our hotel (I doubt it, for some reason they've booked us in some no-name hotel), or possibly from the conference center. Failing that I can try the cell again. Best regards, Bill ----- Original Message ----- From: "Drummond Reed" <drummond.reed@cordance.net> Date: Friday, October 22, 2004 1:25 am Subject: RE: [xdi] Groups - draft-xdi-metaschema-v7.xsd uploaded > Bill, > > I apologize for taking so long to reply to this - you put a lot of > good work > into this. It's just been crazy getting ready for Digital ID World > next week > and the launch of the first XRI services by Identity Commons. > > Quick replies to your two key points: > > 1) WRT extensibility, it was a conscious decision to make the > "Data" element > the point at which the "Any" sequence was allowed. The purpose was > to keep > the Resource tree clean. Think of it like branches and leaves. The > branches(Resources) stay smooth and lean, but the Data nodes can > spread out and > contain anything. > > 2) WRT a more generic container for XRIs, I can see both > approaches. Most of > the benefits you describe can be provided without modifying the v7 > metaschema by defining an "$xri" resource in the XDI service > dictionary.This resource would allow any other resource to > describe (to any depth of > complexity or granularity) the XRIs that identify the resource. > Example: > <resource> > <xri>foo</xri> > <xri>bar</xri> > <resource> > <xri>$xri</xri> > <resource> > <xri>foo</xri> > <data>This is the primary name to use.</data> > </resource> > <resource> > <xri>bar</xri> > <data>This is an old name still sometimes > used.</data> > </resource> > </resource> > </resource> > > > I trust with your new baby you're not going to be at Digital ID > World next > week, but will you be able to join one of the two f2f sessions via > telecon?It would be great as I'm sure we'll be discussing this in > depth. > Best, > > =Drummond > > > -----Original Message----- > From: Barnhill William [mailto:barnhill_william@bah.com] > Sent: Wednesday, October 13, 2004 1:17 PM > To: xdi@lists.oasis-open.org > Subject: Re: [xdi] Groups - draft-xdi-metaschema-v7.xsd uploaded > > Hello all, > > I won't be able to attend the meeting tonight, but I took a quick > run > through on the new schema and came up with the following: > > 1. The new proposed schema could benefit from being more > extensible. To > add extensibility you would need to add one or more of the > following in > the appropriate places: > <xsd:any > namespace="##other" > processContents="lax" > minOccurs="0" > maxOccurs="unbounded" > > > <xsd:annotation> > <xsd:documentation> > This free-form extension may > include additional, > namespace-qualified XML. > </xsd:documentation> > </xsd:annotation> > </xsd:any> > > My recommendation would be to change the resource definition to: > <element name="resource"> > <complexType> > <sequence> > <element > ref="xdi:xri" > maxOccurs="unbounded" /> > <element > ref="xdi:data" > minOccurs="0" /> > <element > ref="xdi:resource" > minOccurs="0" > maxOccurs="unbounded" /> > <xsd:any > namespace="##other" > processContents="lax" > minOccurs="0" > maxOccurs="unbounded" > > > <xsd:annotation> > <xsd:documentation> > This free-form extension may > include additional, > namespace-qualified XML. > </xsd:documentation> > </xsd:annotation> > </xsd:any> > </sequence> > </complexType> > </element> > > 2. I know I brought this up earlier but I still think a more > generic > container for the XRIs is appropriate, so would further alter the > resource def into: > <element name="resource"> > <complexType> > <sequence> > <element > ref="xdi:addressing" /> > <!-- Note:default minOccurs and maxOccurs is 1 --> > <element > ref="xdi:data" > minOccurs="0" /> > <element > ref="xdi:resource" > minOccurs="0" > maxOccurs="unbounded" /> > <xsd:any > namespace="##other" > processContents="lax" > minOccurs="0" > maxOccurs="unbounded" > > > <xsd:annotation> > <xsd:documentation> > This free-form extension may > include additional, > namespace-qualified XML. > </xsd:documentation> > </xsd:annotation> > </xsd:any> > </sequence> > </complexType> > </element> > > And add an addressing def of: > <element name="addressing"> > <complexType> > <sequence> > <element > ref="xdi:xri" > maxOccurs="unbounded" /> > <xsd:any > namespace="##other" > processContents="lax" > minOccurs="0" > maxOccurs="unbounded" > > > <xsd:annotation> > <xsd:documentation> > This free-form extension may > include additional, > namespace-qualified XML. > </xsd:documentation> > </xsd:annotation> > </xsd:any> > </sequence> > </complexType> > </element> > > I'd also make the following changes: > 3. Change xri element to xriaddress element with a cxhild xri > element, > and add an xsd:any within the xriaddress element, allowing > metadata > about the xri address itself. > 4. Add an xdi:resource element with minOccurs 0,maxOccurs > unbounded to > the xdi:data def > 5. Add an xsd:any w/ namespacxe other, maxOccurs unbounds, min > unbounded to the xdi:data def > > This would bring the schema to: > > <?xml version="1.0" encoding="ISO-8859-1" ?> > > <schema > targetNamespace="http://xdi.oasis-open.org"; > elementFormDefault="qualified" > xmlns="http://www.w3.org/2001/XMLSchema"; > xmlns:xdi="http://xdi.oasis-open.org"; > > > <element name="resource"> > <complexType> > <sequence> > <element > ref="xdi:addressing" /> > <!-- Note:default minOccurs and maxOccurs is 1 --> > <element > ref="xdi:data" > minOccurs="0" /> > <element > ref="xdi:resource" > minOccurs="0" > maxOccurs="unbounded" /> > <any > namespace="##other" > processContents="lax" > minOccurs="0" > maxOccurs="unbounded" > > > <annotation> > <documentation> > This free-form extension may > include additional, > namespace-qualified XML. > </documentation> > > > </sequence> > </complexType> > </element> > > <element name="addressing"> > <complexType> > <sequence> > <element > ref="xdi:xriaddress" > maxOccurs="unbounded" /> > <xsd:any > namespace="##other" > processContents="lax" > minOccurs="0" > maxOccurs="unbounded" > > > <annotation> > <documentation> > This free-form extension may > include additional, > namespace-qualified XML. > </documentation> > > > </sequence> > </complexType> > </element> > > <element name="xriaddress"> > <complexType> > <sequence> > <element > ref="xdi:xri" > maxOccurs="unbounded" /> > <xsd:any > namespace="##other" > processContents="lax" > minOccurs="0" > maxOccurs="unbounded" > > > <annotation> > <documentation> > This free-form extension may > include additional, > namespace-qualified XML. > </documentation> > > > </sequence> > </complexType> > </element> > > <element name="xri"> > <simpleType> > <restriction base="string"> > <annotation> > <documentation> > This element definition may be enhanced > to include an XML pattern element matching > the XRI ABNF, so a standard XML schema > validating parser will be able to validate > that an XRI value is legal. > </documentation> > > </restriction> > </simpleType> > </element> > > <element name="data"> > <complexType mixed="true"> > <sequence> > <any > minOccurs="0" > maxOccurs="unbounded" /> > </sequence> > </complexType> > </element> > </schema> > > Some or all of the above pts may have been discussed and decided > against while I was in the hospital, if so sorry for beating a > dead > parrot. > > If there's no consensus after tonight's meeting (if everyone > agrees to > V7 as it is then I've no problems with that, but I do think the > above > will increase flexibility, implementation, and adoption), then > perhaps > a matrix could be distributed that maps elements and the options > for > the schema. That matrix could be filled out with +1/-1/0 and the > winning set of features captured into a schema? > > Bill > > ----- Original Message ----- > From: drummond.reed@cordance.net > Date: Wednesday, October 13, 2004 2:06 pm > Subject: [xdi] Groups - draft-xdi-metaschema-v7.xsd uploaded > > > The document draft-xdi-metaschema-v7.xsd has been submitted by > > Drummond Reed (drummond.reed@cordance.net) to the OASIS XRI Data > > Interchange (XDI) TC document repository. > > > > Document Description: > > v7 of the proposed XDI metaschema (now harmonized full with the > > RDF 3-tuple model - see following message to the list) > > > > Download Document: > > http://www.oasis- > > open.org/apps/org/workgroup/xdi/download.php/9649/draft-xdi- > > metaschema-v7.xsd > > > > View Document Details: > > http://www.oasis- > > open.org/apps/org/workgroup/xdi/document.php?document_id=9649 > > > > PLEASE NOTE: If the above links do not work for you, your email > > applicationmay be breaking the link into two pieces. You may be > > able to copy and paste > > the entire link address into the address field of your web browser. > > > > > > > > > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]