xdi message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Re: [xdi] Groups - Comments about XDI versioning (Draft-Contrib-OASIS-XDI-versioning.pdf) uploaded
- From: "Markus Sabadello" <markus.sabadello@xdi.org>
- To: giovanni.bartolomeo@uniroma2.it
- Date: Thu, 21 Feb 2008 22:45:06 -0500
Heya Giovanni,
Since I already tried to implement the versioning described in the XDI RDF Model v8 doc, it's interesting for me to read your comments about this..
- Regarding the use of $num instead of ! to index things, I think it's mostly a matter of taste. Both would work fine I think. One thought I am having is that subsegments like !1, !2, !3 do exist in XRI resolution too. I.e. there are some authority resolution servers that use these number-like subsegments (and not ip address-like subsegments like !203.173.1276.1663)..
- Regarding the number of versions, can I ask you something?
Maybe you can take a quick look at this URL: http://graceland.parityinc.net/xdi-endpoint/hibernate-graph-ver/=drummond
As you can see there are the following two statements:
=drummond/$has/$v (this says that =drummond is versioned)
=drummond/$v/!5 (this says the current version is 5)
I'd like to understand how you would do it instead.
Would you say this?
=drummond/$has$num$5/$v
Or this?
=drummond/$has$5/$v
Just trying to understand it correctly.. I like the idea very much, it makes versioning a bit simpler and more consistent with other constructs..
Note to Drummond: We were talking about how to express multiple values of an attribute (e.g. =markus has multiple +email addresses). After reading Giovanni's comments, it appears to me that versioning may just be another instance of that same problem. I.e. there's no difference between saying =markus has 5 +email addresses, and saying that =drummond has 5 $v ersions. I agree with Giovanni that the same construct should be used in both cases.
- I don't understand why I would use the comparison operators like $greater in versioning.. What would be a practical use case for this? But in general I think these operators can be very useful..
Markus
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]