#179 URIs in Segment, Type, and others

DAS2 (40)

The URI should be resolvable against the base URI. In
the biopackages DAS/2 some of the URIs are actually
created by slicing and dicing strings. This should
really not be done.


  • Brian O'Connor

    Brian O'Connor - 2006-08-15
    • priority: 5 --> 8
    • assigned_to: allenday --> boconnor
  • Allen Day

    Allen Day - 2006-08-15
    • priority: 8 --> 9
  • Brian O'Connor

    Brian O'Connor - 2006-08-15

    Logged In: YES

    Some notes:

    This is really talking about the filters in the DAS/2
    server. Currently, the filters use ids. But these really
    should be fully resolvable URIs i.e.


    rather than


    Apparently the following filters should be converted:
    sequence/region (all location based)

    A first pass on this would extract the correct value from a
    das.biopackages.net URL and then use that normally. In the
    future, it won't be possible to make assumptions about where
    the URIs point and what they resolve to.

  • Brian O'Connor

    Brian O'Connor - 2006-08-16

    Logged In: YES

    Some notes:

    After talking with Gregg and Allen about this one there are
    two "solutions". The first (not so flexible) solution is to
    mangle the URI and clip off the known ending and use that to
    produce a response by the server. The problem with this is
    it assumes the URI formats are all the same and that the
    local DAS/2 server is using the same build of the genome(s).
    The better solution is to use a mapping file based on
    Lincoln's official URIs in the wiki. That way everyone
    would use the same URI passed to, say, an overlaps query and
    the DAS/2 server would know how to map that URI to an
    internal ID used to locate and produce a response.

  • Brian O'Connor

    Brian O'Connor - 2006-08-19

    Logged In: YES

    OK... this is "fixed".

    The following need to use URIs:
    * xid
    * type
    * segment
    * coordinates

    These work but xid isn't supported in our server (but in the
    spec and needs to be implemented).

  • Brian O'Connor

    Brian O'Connor - 2006-08-19
    • status: open --> closed
  • Brian O'Connor

    Brian O'Connor - 2006-08-19
    • status: closed --> closed-fixed

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.

No, thanks