Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

HML Spec: For all elements that allow a URI attribute, do we need an additional 'format' or 'content' attribute to define what is at the URI endpoint? #15

Open
dvaliga opened this issue Sep 26, 2014 · 2 comments
Open

HML Spec: For all elements that allow a URI attribute, do we need an additional 'format' or 'content' attribute to define what is at the URI endpoint? #15

dvaliga opened this issue Sep 26, 2014 · 2 comments

Comments

@dvaliga
Copy link

dvaliga commented Sep 26, 2014

No description provided.

@mpresteg
Copy link

Related to issue #11

@ghost
Copy link

ghost commented Sep 27, 2014

For the the <raw-reads> element I think this might be necessary.

For <glstring> I think the use case is clear, and is ok with URIs-without-content-type, as those are used as identifiers by the gl-service.

For other URI properties, see nmdp-bioinformatics/hml#14

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dvaliga @mpresteg