[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xdi] Resource type representation
Treating both attributes of a resource as "first class objects" as well as the attribute *type* as a "first class object" (i.e. as resources identified by XRIs as well) is precisely what RDF (http://www.w3.org/RDF) does. I've mentioned this to Drummond before in private, and I've seen he's compared XDI to RDF on paper (don't recall exactly where), but its something to consider, as the base from which to build the expression of the relationships between the various entities being discussed. Being RDFifized (or even OWLified) could produce some interesting exposures to semantic web and other architectures, tools and technologies and kickstart XDI interest. Just a thought from an "active observer".. -Gabe __________________________________________________ gwachob@visa.com Chief Systems Architect Technology Strategies and Standards Visa International Phone: +1.650.432.3696 Fax: +1.650.554.6817 -----Original Message----- From: Loren West [mailto:loren.west@epok.net] Sent: Wednesday, May 19, 2004 8:59 AM To: xdi@lists.oasis-open.org Subject: RE: [xdi] Resource type representation If we had a 'type' attribute of the <resource>, it would need to contain an URI to the XSD of <resource> itself. It could be called 'xditype', but we would still have the problem of "many types" (or "sub types" as you've pointed out). You can (and probably will) still put the XSD type in the "type" attribute of the <data> element, and/or the sub-elements of <data> for efficient processing. XDI isn't as much for efficiency as expressiveness (IMO). Drummond is working on a proposal that has us putting ALL metadata about the <data> element within sub <resource> elements. That won't be highly efficient, but it will allow us to be highly expressive. Aside from addressing metadata, probably all metadata (including typing information) could be represented as <resource> elements within the enclosing <resource>. =Loren -----Original Message----- From: Barnhill William [mailto:barnhill_william@bah.com] Sent: Wednesday, May 19, 2004 7:09 AM To: xdi@lists.oasis-open.org Subject: Re: [xdi] Resource type representation I'd add... > 3) Where could it go? * A type attribute on the resource element, representing the type of the data itself. This would probably be mutually exclusive with having a datatype element under resource. The type attribute has an implementation advantage as attributes are generally faster, and much less parsing is needed to determine data type. It has the disadvantage of not allowing multiple data types, but a resource element can only hold one data element, so having this as a type attribute could make that restriction clearer. > 3) Examples > * As an XRI ...and as attribute <resource type="xri:@Epok/Schemas/BusinessCard"> <xri type="ename">=Loren/Cards/EpokCard</xri> <xri type="enumber">=:342.34/821.4</xri> <xri type="category">+work</xri> ... </resource> 4) This will be rushed as being called away..but.. subtype attribute, and narrow type to one of values defined in the xdi schema (xml, mime,...) Examples clarify: a) <resource type="xml" subtype="xri:@Epok/Schemas/BusinessCard"> <xri type="ename">=Loren/resume</xri> <xri type="enumber">=:342.34/821.5</xri> <xri type="category">+work</xri> ... </resource> b) <resource type="mime" subtype="xri:@w3c/mime/text/html"> <xri type="ename">=Loren/resume</xri> <xri type="enumber">=:342.34/821.5</xri> <xri type="category">+work</xri> ... </resource> Again apologies for not making the meeting, Bill ----- Original Message ----- From: "Loren West" <loren.west@epok.net> Date: Wednesday, May 19, 2004 9:34 am Subject: [xdi] Resource type representation > Discussion points of the use of "type" within XDI > > 1) A single <resource> has many types > > * Data type "what is the structure of this instance" > (Several: XSD type, ebXML type, Liberty type, XNS type, synonyms) > > * Category "what group does this instance belong in" > (Several: +home, +personal, +afterWork) > > 2) How is it represented? > > * As a URI to an XSD type? > * As an XRI? > * As an XRI representing an XSD <resource>? > (if so, could it be represented as XML <resource>) > > 3) Where could it go? > > * Not as an attribute <resource type=...> (can't have many) > * As an XRI (with a "type" attribute) > <xri type=datatype/category> > * As a <type> element? > * <datatype> element? > * <category> element? > > 3) Examples > > * As an XRI > <resource> > <xri type=ename>=Loren/Cards/EpokCard</xri> > <xri type=enumber>=:342.34/821.4</xri> > <xri type=datatype>" > target="l">http://example.com/BusinessCard.xsd</xri> <xri > type=datatype>@Epok/Schemas/BusinessCard</xri> <xri > type=category>+work</xri> ... > > * As an XML element > <resource> > <ename>=Loren/Cards/EpokCard</ename> > <enumber>=:342.34/821.4</enumber> > <datatype>" > target="l">http://example.com/BusinessCard.xsd</datatype> > <datatype>@Epok/Schemas/BusinessCard</datatype> > <category>+work</category> ... > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]