![]() Not a huge deal, but something that I can’t imagine would be an issue in a real app. I don’t know why, but the Fluid app occasionally messes up how the window should be displayed which doesn’t let me get to the progress tab of my bigger projects. Having a real desktop version that could sync data but let me enter it in realtime would be fabulous. It takes some seconds to load, sometimes takes a moment to let me check off a task, etc. Compared to applications that have native apps and sync (e.g., Evernote), my Fluid version of Asana is laggy. ![]() But this means that actually reviewing projects requires me to have internet access. That’s not a problem! My phone is for getting a quick overview of tasks for the day, checking things off, and adding new tasks on the go. I do most of my work on my laptop, not my phone, and the web interface is way better for viewing projects than the mobile app. Features that would be important in a real app include: ![]() Yes, I made my own version using Fluid, but it’s not the same thing. If so, the second key question is which mantra should drive status determinations in fluid conflicts: a “most protected status” approach or a “you are where you started” maxim.I’m chiming in to say I would really appreciate a native Asana app. A first key question is whether, when conflicting interpretations are possible, the analysis should rest on a broader theme or approach-a guiding principle of sorts-rather than a more iterative approach. Given the possibility of different interpretations for similarly-situated individuals, Part II then explores the underlying questions at the heart of the application of the Third Geneva Convention in fluid conflicts. The analysis focuses on the meaning of specific key terms in the Third Geneva Convention and how, in the circumstance of a fluid conflict, the meaning and interpretation of those provisions should determine the appropriate status of individuals. Part I of this chapter examines status determinations of persons in fluid conflicts under the Third Geneva Convention, whether in an IAC that becomes a NIAC or in a NIAC that transitions to an IAC. A deeper examination of the Convention, including the basis for the key applicable provisions, suggests that although the meaning and intent of the Third Geneva Convention are readily decipherable, if not explicit, the debate rests on the underlying “storyline” or theme that could or should drive interpretation in such situations. Although few if any adjudications or other formal pronouncements on these issues exist, understanding how the transitions in a fluid conflict can and should affect the status and treatment of persons is essential for effective operational planning and preparation. This chapter examines the application of the Third Geneva Convention in fluid conflicts, specifically with respect to the status of detainees and the obligation to release and repatriate. These “fluid conflicts,” that is, conflicts that morph from international to non-international or vice versa, perhaps even more than once, present a range of interesting questions of both law and policy. The usually straightforward determination during IAC that a captured enemy soldier is a prisoner of war (POW) becomes the much more difficult question of what authority the detaining party has and what treatment and disposition that soldier is owed when the conflict becomes a NIAC. However, where conflicts fluctuate between international and non-international based on the changing character of the parties involved or the involvement of additional parties, significant complexities arise. Where conflicts are distinguishable as either international or non-international, the law applicable to a given situation or issue is easily identifiable, even if the specific application or implementation of that legal rule may be complicated. ![]() The 1949 Geneva Conventions set forth a clear framework for for the identification and classification of armed conflicts and the applicable law in both international and non-international armed conflicts.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |