Re: [xdi] $get operation helpers / enhancements

[Markus Sabadello <markus.sabadello@xdi.org>]

- I'm not sure if I fully understand the implications of distinguishing between binary and non-binary literals on the graph level. How do $add and $mod operations work with binaries?

- "Server MAY return $is$binary as literal value instead of binary" - Just a note on terminology here, $is$binary isn't a literal, it's an XRI. So speaking of $is$binary as a literal value is a bit confusing to me. Also, there might be ambiguous situations if somebody stores an actual $is$binary relational arc in the graph.

- $onelevel - I still don't understand why we can't use $level$1, $level$2, ...

- Filtering by arc types makes sense to me. Maybe this could also be done using the syntax for variables, instead of introducing special $ words.

- The filter _expression_ syntax looks pretty complicated, would need description to understand how it works. How does the syntax for variables fit into this? Have you looked at Giovanni's earlier work on XDI queries?

Markus

On Tue, May 22, 2012 at 7:31 PM, Michael Schwartz <mike@gluu.org> wrote:

XDI TC:

Continuing the discussion on filtering $get requests, please review the following proposals.

Any feedback ahead of time would also be appreciated.

- Mike




===================================
$get operation
===================================

1) Server MAY return $is$binary as literal value instead of binary


=====================================================
Filter by arc type $literal, $relational, $contextual
=====================================================

Types:

$literal, $contextual, $relational
Example 1 - returns ONLY literal xdi statements

@!1111$msg!e2bdc4de-f129-4d84-9009-3572c37b04d0$do/$get$literal/@!4444
Example 2 - returns relational and contextual xdi statements

@!1111$msg!e2bdc4de-f129-4d84-9009-3572c37b04d0$do/$get$relational$contextual/@!4444
Example 3 - NO sense filter because it returns all xdi statements, $get operation by default returns all xdi statements. Filter can be simply skipped.

@!1111$msg!e2bdc4de-f129-4d84-9009-3572c37b04d0$do/$get$relational$contextual$literal/@!4444

=======
$binary
=======

To force $get operation to return binaries.

Example:

@!1111$msg!e2bdc4de-f129-4d84-9009-3572c37b04d0$do/$get$binary/@!4444


=========
$onelevel
=========

$onelevel - returns only one level from target node of $get operation

If client wants to go deeper then 1 one level for example 2, then it should made 2 sequential calls.

Example:

@!1111$msg!e2bdc4de-f129-4d84-9009-3572c37b04d0$do/$get$onelevel/@!4444


==============================
Filter _expression_ / Evaluation
==============================

In evaluation filter only string operations can be used.

Example:

@!1111$msg!e2bdc4de-f129-4d84-9009-3572c37b04d0$do/$get($and(context=*friends*)(rel=*yuriy*))/@!4444


---------------------------------------------------------------------
To unsubscribe, e-mail: xdi-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: xdi-help@lists.oasis-open.org