RE: [xdi] Resource and Data

From
Loren West <>
Date
2004-08-18T22:50:53+00:00
ID
015d01c48575$c52f0f40$7101a8c0@TABLETPC
Thread
RE: [xdi] Resource and Data
Title: Message

Very 
interesting.  Stew on this:

 

<resource>

   <xri>...</xri>

   <instance>...(used to be 
<data>)</instance>

   <attributes>  (used to be 
<meta>?)

      
<resource><xri>+DataType</xri>...(isn't this the same as 
"class"?)

      
<resource><xri>+LinkContract</xri>...

      
<resource><xri>+Association</xri>...

       
...

   </attributes>

</resource>

 

Something to think about.   I think these terms are synonymous, 
so it doesn't change much.  Especially since you can have multiple nouns 
(synonyms) as soon as the data are represented within a 
resource.

 

=Loren

 

-----Original Message-----
From: Will St Germain IV 
[mailto:] 
Sent: Wednesday, August 18, 2004 3:34 
PM
To: Drummond Reed
Cc: 'Loren West'; 

Subject: RE: [xdi] Resource and 
Data

Drummon, 

The more we learn UML as a language to 
communicate, it seems reasonable to align to the same nouns when we talk about 
moving data from one persistence to another?  (note, as an observer I may 
be totally out of touch with the topic:) 

The nouns that come to mind are: 
Instance 
Class 
Attribute 
DataType 
Association 

Reference: 
 http://www.omg.org/technology/documents/formal/uml.htm 

Thanks,

Will St. Germain 
IV

Senior Transition and Information 
Architect,
303-924-1547

  
  

    "Drummond Reed" 
      <> 
      
08/18/2004 03:59 PM 

    
      
        
        

          
            
To

          "'Loren West'" 
            <>, <> 

        

          
            
cc

          
        

          
            
Subject

          RE: [xdi] Resource and 
            Data

      
        
        

          
          

Both Loren and Bill have brought up the potential need for a 
container
element for subresources (Resources contained by a parent Resource 
in the v5
metaschema). Both of them have good arguments for it, and I've 
shared with
them at least one good argument against it.

The net net is 
that it's a wonderful, meaty topic that we'll be diving into
on today's 
call.

=Drummond 

-----Original Message-----
From: Loren West 
[mailto:] 
Sent: Wednesday, August 18, 2004 2:46 PM
To: 

Subject: RE: [xdi] Resource and Data

Funny. 
 I read Gabe's request to mean the difference between <data>
and 
it's sibling <resource> elements.  Drummond read the request
as 
the difference between <data> and it's parent <resource>.

Now 
I'm more convinced than ever that we need a different name
for the 
<resource> elements that are siblings to <data> (or
at least 
group them under a <meta> tag).  They often times
get confused 
with the parent <resource> element.

=Loren

-----Original 
Message-----
From: Drummond Reed [mailto:] 

Sent: Wednesday, August 18, 2004 2:34 PM
To: 'Wachob, Gabe'; 

Subject: [xdi] Resource and Data

Gabe, 
it's a fine question. We've been working with the Resource/XRI/Data
element 
names for long enough now that no one has bothered to ask this 
basic
question.

I will give a very precise definition according to 
RFC2396bis and XRI 1.0.
An XDI "resource" is an entity that can be 
represented in an XDI document
and identified by an XRI. Period. It's 
abstract in the extreme.

XDI "data", by contrast, is any information that 
can be represented in an
XDI document that IS NOT identifiable by itself, but 
must be placed in the
context of one or more XRIs in order to become 
identifiable.

Example:

<data>43</data>

The 
value "43" in this XML element is XPath-addressable (in the scope of 
a
specific XML document) but not 
XRI-addressable.

<resource><xri>=Mary.Jones/(+age)</xri><data>43</data></resource>

Now 
this data has become identifiable - in both a local and global context -
with 
an XRI and thus now meets the RFC2396bis and XRI 1.0 definition of 
a
resource.

Of course, data does not have to be just a literal value. 
Complex data can
be a collection of resources. However, a collection of 
resources (each of
which itself is identifiable) needs to be put in the 
context of one or more
XRIs to be identifiable as a *collection*, so it still 
meets the definition
of data.

The next step beyond this simplest 
definition is to compare the XDI tuple
with the RDF tuple, and talk about 
Resource as Subject, XRI as Predicate,
and Data as Object. That was addressed 
in the powerpoint uploaded for the
last TC 
call
(http://www.oasis-open.org/committees/download.php/8454/How-XDI-Builds-On-RD
F-v1.ppt). 

With your knowledge of RDF, I would love your feedback on that view 
of
Resource and Data.

=Drummond 

-----Original 
Message-----
From: Wachob, Gabe [mailto:] 
Sent: 
Wednesday, August 18, 2004 11:27 AM
To: ; 

Subject: RE: [xdi] Groups - 
draft-xdi-metaschema-v5.xsd uploaded

Drummond-
      
          Can you explain in a sentence or two what the 
meaning of resource
vs. data is? This doesn't seem to be documented anywhere 
- you may have
discussed this on the phone calls, but I don't see explanation 
in the
minutes (not that I'd expect such content to be in minutes). 

                
Thanks

                
-Gabe

__________________________________________________ 


Chief Systems Architect
Technology Strategies and 
Standards
Visa International 
Phone: +1.650.432.3696   Fax: 
+1.650.554.6817

> -----Original Message-----
> From: 
 [mailto:]
> Sent: 
Tuesday, August 17, 2004 11:39 PM
> To: 
> 
Subject: [xdi] Groups - draft-xdi-metaschema-v5.xsd uploaded
> 
> 

> The document draft-xdi-metaschema-v5.xsd has been submitted 
> by 
Drummond Reed () to the OASIS 
> XRI Data 
Interchange (XDI) TC document repository.
> 
> Document 
Description:
> v5 Proposed XDI Metaschema (only change is Comment element 
eliminated)
> 
> Download Document:  
> 
http://www.oasis-open.org/apps/org/workgroup/xdi/download.php/
> 
8761/draft-xdi-metaschema-v5.xsd
> 
> View Document Details:
> 
http://www.oasis-open.org/apps/org/workgroup/xdi/document.php?
> 
document_id=8761
> 
> 
> PLEASE NOTE:  If the above links 
do not work for you, your 
> email application
> may 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.
> 

> 
>