{"action":"created","issue":{"url":"https://api.github.com/repos/cellml/libcellml/issues/15","labels_url":"https://api.github.com/repos/cellml/libcellml/issues/15/labels{/name}","comments_url":"https://api.github.com/repos/cellml/libcellml/issues/15/comments","events_url":"https://api.github.com/repos/cellml/libcellml/issues/15/events","html_url":"https://github.com/cellml/libcellml/issues/15","id":74494100,"number":15,"title":"Agree on the initial scope of libCellML","user":{"login":"nickerso","id":811244,"avatar_url":"https://avatars.githubusercontent.com/u/811244?v=3","gravatar_id":"","url":"https://api.github.com/users/nickerso","html_url":"https://github.com/nickerso","followers_url":"https://api.github.com/users/nickerso/followers","following_url":"https://api.github.com/users/nickerso/following{/other_user}","gists_url":"https://api.github.com/users/nickerso/gists{/gist_id}","starred_url":"https://api.github.com/users/nickerso/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nickerso/subscriptions","organizations_url":"https://api.github.com/users/nickerso/orgs","repos_url":"https://api.github.com/users/nickerso/repos","events_url":"https://api.github.com/users/nickerso/events{/privacy}","received_events_url":"https://api.github.com/users/nickerso/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-05-08T21:01:52Z","updated_at":"2015-05-10T13:59:37Z","closed_at":null,"body":"It would be good to document the intended scope of libCellML and this issue is to ensure there is agreement on the scope of the library. Obviously the scope may change over time, but this initial scope will guide the development of the project to address the initial set of use-cases.\r\n\r\nThe initial proposal is that the purpose of libCellML is to create, manipulate, serialise, deserialise, validate and instantiate CellML models. In the first instance, all serialising and deserialising will be to and from standard strings and using the CellML XML format. \r\n\r\nThe library should be lightweight and focused purely in dealing with CellML models. In achieving this, some of the convenience methods/objects that we might expect will not be part of libCellML. For example, in our current thoughts, libCellML would not be concerned with the actual mechanics of resolving and retrieving external resources - calling applications would be required to resolve and retrieve import URL's and provide the serialised documents to libCellML in the form of strings for instantiation as part of the CellML 1.1/1.2 hierarchical model description. \r\n\r\nExample code would be provided which demonstrates how such tasks can be achieved using standard tools, i.e., libcurl for C/C++ and maybe whatever PMR2 uses in Python to resolve and retrieve imported models. "},"comment":{"url":"https://api.github.com/repos/cellml/libcellml/issues/comments/100645561","html_url":"https://github.com/cellml/libcellml/issues/15#issuecomment-100645561","issue_url":"https://api.github.com/repos/cellml/libcellml/issues/15","id":100645561,"user":{"login":"jonc125","id":2032871,"avatar_url":"https://avatars.githubusercontent.com/u/2032871?v=3","gravatar_id":"","url":"https://api.github.com/users/jonc125","html_url":"https://github.com/jonc125","followers_url":"https://api.github.com/users/jonc125/followers","following_url":"https://api.github.com/users/jonc125/following{/other_user}","gists_url":"https://api.github.com/users/jonc125/gists{/gist_id}","starred_url":"https://api.github.com/users/jonc125/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jonc125/subscriptions","organizations_url":"https://api.github.com/users/jonc125/orgs","repos_url":"https://api.github.com/users/jonc125/repos","events_url":"https://api.github.com/users/jonc125/events{/privacy}","received_events_url":"https://api.github.com/users/jonc125/received_events","type":"User","site_admin":false},"created_at":"2015-05-10T13:59:37Z","updated_at":"2015-05-10T13:59:37Z","body":"I guess we can go with just example code initially, but I think this is a fairly useful feature to have in the core library eventually!"}}