David R Newman | 27 Jan 2012 02:10
Picon
Favicon

Re: Adding things to the API

Hi Robert,

Not sure what the answer to the skinning question is, Don may have a 
better idea.  If there is stuff in the database, I am sure it can be 
exposed in the API.  How Taverna and other applications might be able to 
make use of this will need to be discussed further.

Semantic links in packs can be requested with a URL like the following: 
http://www.myexperiment.org/pack.xml?id=198&elements=relationships

This will return somthing like:

<pack uri="http://www.myexperiment.org/pack.xml?id=198" 
resource="http://www.myexperiment.org/packs/198">
<relationships>
<relationship uri="http://www.myexperiment.org/relationship.xml?id=6"/>
<relationship uri="http://www.myexperiment.org/relationship.xml?id=7"/>
</relationships>
</pack>

You can then do GET/POST/DELETE using relationship.xml URI.  See 
http://wiki.myexperiment.org/index.php/Developer:RelationshipsResource 
for more details.

Tags (taggings) for packs  have been available for some time, see 
http://wiki.myexperiment.org/index.php/Developer:TaggingsResource.  
Obviously, you'd change the subject of the tagging to a pack rather than 
a workflow as shown on the wiki page cited.

A comprehensive listing of what the API can currently do is available at 
(Continue reading)

robert Stevens | 27 Jan 2012 10:35
Picon
Favicon

Re: Adding things to the API

fab; many thanks

----- Original Message ----- 
From: "David R Newman" <drn@...>
To: "robert Stevens" <robert.stevens@...>
Cc: "myexperiment-discuss" <myexperiment-discuss@...>
Sent: Friday, January 27, 2012 1:10 AM
Subject: Re: [Myexperiment-discuss] Adding things to the API

> Hi Robert,
> 
> Not sure what the answer to the skinning question is, Don may have a 
> better idea.  If there is stuff in the database, I am sure it can be 
> exposed in the API.  How Taverna and other applications might be able to 
> make use of this will need to be discussed further.
> 
> Semantic links in packs can be requested with a URL like the following: 
> http://www.myexperiment.org/pack.xml?id=198&elements=relationships
> 
> This will return somthing like:
> 
> <pack uri="http://www.myexperiment.org/pack.xml?id=198" 
> resource="http://www.myexperiment.org/packs/198">
> <relationships>
> <relationship uri="http://www.myexperiment.org/relationship.xml?id=6"/>
> <relationship uri="http://www.myexperiment.org/relationship.xml?id=7"/>
> </relationships>
> </pack>
> 
> You can then do GET/POST/DELETE using relationship.xml URI.  See 
(Continue reading)

Alan R Williams | 27 Jan 2012 11:17
Picon
Picon

Re: Adding things to the API

I vaguely remember Finn saying that the available skins
were only known by looking in the file system i.e. it
is not stored in the database. (Finn can you confirm/deny?)
If that is correct, then it makes it difficult to expose the
available skins in the API.

Alan
Finn Bacall | 27 Jan 2012 11:32
Picon
Picon

Re: Adding things to the API

Yes, but the file is parsed when the server is started up, so all the 
layouts are already in memory.

The difficulty is in deciding which layouts are available for use, 
because this is determined by which groups the resource is shared with.

-Finn

On 27/01/12 10:17, Alan R Williams wrote:
> I vaguely remember Finn saying that the available skins
> were only known by looking in the file system i.e. it
> is not stored in the database. (Finn can you confirm/deny?)
> If that is correct, then it makes it difficult to expose the
> available skins in the API.
>
> Alan
>
> _______________________________________________
> Myexperiment-discuss mailing list
> Myexperiment-discuss@...
> https://lists.nongnu.org/mailman/listinfo/myexperiment-discuss

--

-- 
Finn Bacall
School of Computer Science
University of Manchester
http://www.myexperiment.org/

Gmane