Re: [xdi] Resource type representation

["Barnhill William" <barnhill_william@bah.com>]

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>  ...
> 
>