ISSUE-1 |
CLOSED |
|
2006-08-30 |
EMMA |
0 |
ISSUE-2 |
OPEN |
[long term] return to context attribute for derived from |
2006-09-12 |
EMMA |
0 |
ISSUE-3 |
CLOSED |
[long term] suggestion for emma:result from smartweb |
2006-09-12 |
EMMA |
0 |
ISSUE-4 |
CLOSED |
confidentiality of life cycle event data |
2006-09-16 |
MMI Architecture |
0 |
ISSUE-5 |
CLOSED |
Title test changed |
2006-09-18 |
All |
0 |
ISSUE-6 |
CLOSED |
Specify that the data model comes with the Interaction Manager |
2006-09-18 |
MMI Architecture |
0 |
ISSUE-7 |
CLOSED |
Specify security requirements for transport protocol |
2006-09-18 |
MMI Architecture |
0 |
ISSUE-8 |
CLOSED |
Presence for components |
2006-09-18 |
MMI Architecture |
0 |
ISSUE-9 |
CLOSED |
Aliases for send (for ease of authoring) |
2006-09-18 |
Authoring |
0 |
ISSUE-10 |
CLOSED |
Representing data events in SCXML |
2006-09-18 |
Authoring |
0 |
ISSUE-11 |
OPEN |
[long term] EMMA best practices document |
2006-09-26 |
EMMA |
0 |
ISSUE-12 |
CLOSED |
[cr] require contents of emma:info to be in any namespace but emma |
2006-09-26 |
EMMA |
0 |
ISSUE-13 |
CLOSED |
[cr] require emma:interpretation contain any namespace but emma: |
2006-09-26 |
EMMA |
0 |
ISSUE-14 |
CLOSED |
[cr] extend ir document with comment requirements |
2006-09-26 |
EMMA |
0 |
ISSUE-15 |
CLOSED |
[cr] require application namespace markup to appear only within emma:interpretation or emma:info tree |
2006-09-26 |
EMMA |
0 |
ISSUE-16 |
CLOSED |
[issue] schema constraints in IR document |
2006-09-26 |
EMMA |
0 |
ISSUE-17 |
CLOSED |
[issue] design template for vendor EMMA test reports |
2006-09-26 |
EMMA |
0 |
ISSUE-18 |
CLOSED |
clarify that |
2006-09-28 |
MMI Architecture |
0 |
ISSUE-19 |
CLOSED |
correct statement about \'context\' in section 6.2.5.1 |
2006-09-28 |
MMI Architecture |
0 |
ISSUE-20 |
CLOSED |
incorrect reference to |
2006-09-28 |
MMI Architecture |
0 |
ISSUE-21 |
CLOSED |
contents of Data field |
2006-09-28 |
MMI Architecture |
0 |
ISSUE-22 |
CLOSED |
Defining CR exit criteria |
2006-10-04 |
EMMA |
0 |
ISSUE-23 |
CLOSED |
Clarify policy of data submission |
2006-10-09 |
MMI Architecture |
0 |
ISSUE-24 |
OPEN |
Track changes in issues |
2006-10-16 |
Issue Tracker |
0 |
ISSUE-25 |
OPEN |
Some better notion of status or progress of an issue |
2006-10-16 |
Issue Tracker |
0 |
ISSUE-26 |
CLOSED |
timely event delivery |
2006-10-30 |
MMI Architecture |
0 |
ISSUE-27 |
CLOSED |
CR: status paragraph on at risk features for EMMA candidate draft |
2006-12-12 |
EMMA |
0 |
ISSUE-28 |
CLOSED |
CR: separation of emma:duration into new section section 4.2.10.3 |
2006-12-12 |
EMMA |
0 |
ISSUE-29 |
CLOSED |
how should audio visual speech recognition be annotated |
2006-12-12 |
EMMA |
0 |
ISSUE-30 |
CLOSED |
CR: change emma:mode values to align with VXML |
2006-12-12 |
EMMA |
0 |
ISSUE-31 |
CLOSED |
[cr] need to allow for emma:interpretation to be empty in case where emma:function= |
2006-12-12 |
EMMA |
0 |
ISSUE-32 |
CLOSED |
Create Request/Response events |
2007-01-15 |
MMI Architecture |
0 |
ISSUE-33 |
CLOSED |
Response to \"Start\" event from a component that\'s already started |
2007-02-19 |
MMI Architecture |
0 |
ISSUE-34 |
CLOSED |
Extra colon in emma namspace decl in examples |
2007-02-28 |
EMMA |
0 |
ISSUE-35 |
OPEN |
[longer term] EMMA should perhaps be easier to consume |
2007-02-28 |
EMMA |
0 |
ISSUE-36 |
OPEN |
No support for priorities for issues |
2007-03-19 |
Issue Tracker |
0 |
ISSUE-37 |
OPEN |
No way to group issues by topic/section of draft |
2007-03-19 |
Issue Tracker |
0 |
ISSUE-38 |
CLOSED |
Details of Media Stream handling in life cycle events |
2007-04-03 |
MMI Architecture |
0 |
ISSUE-39 |
CLOSED |
Allow open set of events with reserved event names |
2007-06-19 |
MMI Architecture |
0 |
ISSUE-40 |
CLOSED |
Define MMI profile for scxml as IM language |
2007-06-19 |
Authoring |
0 |
ISSUE-41 |
CLOSED |
add disconnect event |
2007-08-08 |
MMI Architecture |
0 |
ISSUE-42 keyboard modality |
CLOSED |
Keyboard as a basic modality |
2007-10-05 |
Authoring |
0 |
ISSUE-43 Timeouts |
CLOSED |
Adjusting timeouts for accessibility |
2007-10-05 |
Authoring |
0 |
ISSUE-44 Grammar as a resource |
OPEN |
Grammars should be available as a general resource |
2007-10-05 |
Authoring |
0 |
ISSUE-45 Events Addresses |
CLOSED |
Events must have address for routing by IM |
2007-10-08 |
MMI Architecture |
0 |
ISSUE-46 MC Description Registration |
CLOSED |
Modality Components need extensive registration and discovery facilities |
2007-10-08 |
MMI Architecture |
0 |
ISSUE-47 Ingmar |
CLOSED |
Additional MMI lifecycle events |
2007-11-09 |
MMI Architecture |
0 |
ISSUE-48 error handling |
CLOSED |
Structure for errors and error handlers |
2007-11-28 |
MMI Architecture |
0 |
ISSUE-49 Internationalization |
CLOSED |
Internationalizing MMI applications |
2007-11-28 |
Authoring |
0 |
ISSUE-50 |
CLOSED |
Representing user preferences |
2007-12-03 |
MMI Architecture |
0 |
ISSUE-51 |
CLOSED |
Clarify roles of interaction manager |
2007-12-03 |
Authoring |
0 |
ISSUE-52 kinesthetic input |
OPEN |
WAITING FOR VOLUNTEER: Medium Mode Overhaul, medium and mode for kinesthetic input to EMMA? |
2007-12-19 |
EMMA 1.1 |
0 |
ISSUE-53 layered interaction manager |
CLOSED |
Add layers of different functionality to the interaction manager |
2007-12-19 |
MMI Architecture |
0 |
ISSUE-54 |
CLOSED |
clarify prepare event sequence |
2008-01-21 |
MMI Architecture |
0 |
ISSUE-55 Frank_Ellermann |
OPEN |
Re: Request for review of InkML media type: application/inkml+xml |
2008-01-29 |
InkML-Media-Type |
0 |
ISSUE-56 Frank_Ellermann |
CLOSED |
Re: Request for review of InkML media type: application/inkml+xml |
2008-01-29 |
InkML-Media-Type |
0 |
ISSUE-57 Frank_Ellermann |
CLOSED |
Re: Request for review of InkML media type: application/inkml+xml |
2008-01-29 |
InkML-Media-Type |
0 |
ISSUE-58 Frank_Ellermann |
CLOSED |
Re: Request for review of InkML media type: application/inkml+xml |
2008-01-29 |
InkML-Media-Type |
0 |
ISSUE-59 Frank_Ellermann |
CLOSED |
Re: Request for review of InkML media type: application/inkml+xml |
2008-01-29 |
InkML-Media-Type |
0 |
ISSUE-60 |
CLOSED |
Example of tight coupling in MMI architecture |
2008-02-11 |
MMI Architecture |
0 |
ISSUE-61 Events |
CLOSED |
Short Description of Events Philosophy |
2008-02-18 |
MMI Architecture |
0 |
ISSUE-62 MMI Error Use Cases |
CLOSED |
Create MMI Error Use Cases |
2008-06-27 |
MMI Architecture |
0 |
ISSUE-63 MMI Error Matrix |
CLOSED |
Relate errors in Moshe's MMI error document to errors already in place in the draft MMI specification |
2008-06-27 |
MMI Architecture |
0 |
ISSUE-64 |
CLOSED |
How to do the negotiation of RTP? |
2008-10-21 |
MMI Architecture |
0 |
ISSUE-65 |
CLOSED |
Is there an existing language to describe capabilities? E.g., what about SDP as per Issue 46? |
2008-12-01 |
MMI Architecture |
0 |
ISSUE-66 |
CLOSED |
We need to distinguish between "status of component factory" vs. "status of individual component" |
2008-12-01 |
MMI Architecture |
0 |
ISSUE-67 brushes |
CLOSED |
how to handle channel and brushProperty |
2009-04-23 |
InkML |
0 |
ISSUE-68 |
CLOSED |
add source and target to all life cycle events |
2009-04-27 |
MMI Architecture |
0 |
ISSUE-69 |
CLOSED |
<bind> attributes can have invalid combinations |
2009-04-30 |
InkML |
0 |
ISSUE-70 |
CLOSED |
Specify default values for the vocabularies used, on document level |
2009-11-02 |
EmotionML |
0 |
ISSUE-71 |
CLOSED |
Version attribute for <emotionml>? |
2009-11-02 |
EmotionML |
0 |
ISSUE-72 |
CLOSED |
Require meaningful minimal emotion representation |
2009-11-02 |
EmotionML |
0 |
ISSUE-73 |
CLOSED |
<emotion> tag may need tag for definition of namespaces of custom vocabularies |
2009-11-02 |
EmotionML |
0 |
ISSUE-74 |
CLOSED |
Consensus on name of <emotion> element |
2009-11-02 |
EmotionML |
0 |
ISSUE-75 |
CLOSED |
"id" attribute for <emotion> |
2009-11-02 |
EmotionML |
0 |
ISSUE-76 |
CLOSED |
"set" attribute for <category> |
2009-11-02 |
EmotionML |
0 |
ISSUE-77 |
CLOSED |
"set" attribute for <dimensions> |
2009-11-02 |
EmotionML |
0 |
ISSUE-78 |
CLOSED |
Value range for dimensions |
2009-11-02 |
EmotionML |
0 |
ISSUE-79 |
CLOSED |
"set" attribute for <appraisals> |
2009-11-02 |
EmotionML |
0 |
ISSUE-80 |
CLOSED |
Value range for appraisals |
2009-11-02 |
EmotionML |
0 |
ISSUE-81 |
CLOSED |
"set" attribute for <action-tendencies> |
2009-11-02 |
EmotionML |
0 |
ISSUE-82 |
CLOSED |
Value range for action tendencies |
2009-11-02 |
EmotionML |
0 |
ISSUE-83 |
CLOSED |
Exaggerated confidence values? |
2009-11-02 |
EmotionML |
0 |
ISSUE-84 |
CLOSED |
Redundancy with emma:confidence? |
2009-11-02 |
EmotionML |
0 |
ISSUE-85 |
CLOSED |
"confidence" for metadata? |
2009-11-02 |
EmotionML |
0 |
ISSUE-86 |
CLOSED |
Standard values for "mode" and "medium" attributes of <modality> |
2009-11-02 |
EmotionML |
0 |
ISSUE-87 |
CLOSED |
Redundancy of <modality> with EMMA? |
2009-11-02 |
EmotionML |
0 |
ISSUE-88 |
CLOSED |
Multiple modalities |
2009-11-02 |
EmotionML |
0 |
ISSUE-89 |
CLOSED |
Multiple <modality> elements? |
2009-11-02 |
EmotionML |
0 |
ISSUE-90 |
CLOSED |
Reconsider content allowed in <metadata> element |
2009-11-02 |
EmotionML |
0 |
ISSUE-91 |
CLOSED |
Redundancy of <metadata> with <emma:info>? |
2009-11-02 |
EmotionML |
0 |
ISSUE-92 |
CLOSED |
<link> element: default values of "start" and "end" attributes? |
2009-11-02 |
EmotionML |
0 |
ISSUE-93 |
CLOSED |
Redundancy of <link> with <emma:source>? |
2009-11-02 |
EmotionML |
0 |
ISSUE-94 |
CLOSED |
Position on a timeline for externally linked objects |
2009-11-02 |
EmotionML |
0 |
ISSUE-95 |
CLOSED |
Consider making media type explicit in <link> |
2009-11-02 |
EmotionML |
0 |
ISSUE-96 |
CLOSED |
Redundancy of timestamps with EMMA? |
2009-11-02 |
EmotionML |
0 |
ISSUE-97 |
CLOSED |
Dates before Christ |
2009-11-02 |
EmotionML |
0 |
ISSUE-98 |
CLOSED |
SMIL or EMMA-like representation of time? |
2009-11-02 |
EmotionML |
0 |
ISSUE-99 |
CLOSED |
SMIL or EMMA-like representation of time? |
2009-11-02 |
EmotionML |
0 |
ISSUE-100 |
CLOSED |
Timing details: onset, hold, decay? |
2009-11-02 |
EmotionML |
0 |
ISSUE-101 |
CLOSED |
List of valid discrete scale values |
2009-11-02 |
EmotionML |
0 |
ISSUE-102 |
CLOSED |
Custom range of values for rating-scale type range? |
2009-11-02 |
EmotionML |
0 |
ISSUE-103 |
CLOSED |
Candidate for removal: discrete scale values |
2009-11-02 |
EmotionML |
0 |
ISSUE-104 |
CLOSED |
Candidate for removal: attribute "samples-confidence" |
2009-11-02 |
EmotionML |
0 |
ISSUE-105 |
CLOSED |
Mechanism for defining vocabularies for representing emotions |
2009-11-02 |
EmotionML |
0 |
ISSUE-106 |
CLOSED |
Meaningful sets of "recommended" emotion representations |
2009-11-02 |
EmotionML |
0 |
ISSUE-107 |
CLOSED |
Embed definition of custom vocabulary inside <emotionml> document? |
2009-11-02 |
EmotionML |
0 |
ISSUE-108 |
CLOSED |
Proper content for EmotionML namespace section |
2009-11-02 |
EmotionML |
0 |
ISSUE-109 |
CLOSED |
Proper content for section "Use with other Namespaces" |
2009-11-02 |
EmotionML |
0 |
ISSUE-110 |
CLOSED |
Schema language for validating EmotionML |
2009-11-02 |
EmotionML |
0 |
ISSUE-111 |
CLOSED |
How can user code know that the document is to be validated using XProc? |
2009-11-02 |
EmotionML |
0 |
ISSUE-112 |
CLOSED |
Details of absolute and relative timing information to be sorted out |
2009-11-02 |
EmotionML |
0 |
ISSUE-113 |
CLOSED |
Use of "id" attribute in EMMA and EmotionML |
2009-11-18 |
EmotionML |
0 |
ISSUE-114 |
RAISED |
We need to consider processing order so that we properly handle replacement of incremental recognition results |
2009-12-03 |
EMMA |
0 |
ISSUE-115 |
RAISED |
Need to fix namespace declaration in EMMA use cases note |
2009-12-03 |
EMMA 2.0 |
0 |
ISSUE-116 |
CLOSED |
Is the details field of a lifecycle event always optional? (independent of the value of status) |
2010-01-11 |
MMI Architecture |
0 |
ISSUE-117 |
CLOSED |
Add info to spec about subsequent StartRequests: a subsequent StartRequest implicitly cancels a previous process (triggered by a previous StartRequest). This implicit cancelation dues not lead to a cancelRequest (sent from the MC to the IM) |
2010-01-11 |
MMI Architecture |
0 |
ISSUE-118 |
CLOSED |
What does "empty" mean? |
2010-01-25 |
MMI Architecture |
0 |
ISSUE-119 |
CLOSED |
Next WD should have normative language |
2010-01-25 |
MMI Architecture |
0 |
ISSUE-120 |
CLOSED |
Change "one or more valid media types" to "zero or more" |
2010-01-25 |
MMI Architecture |
0 |
ISSUE-121 |
CLOSED |
Remove the word "valid" from the media type discussion |
2010-01-25 |
MMI Architecture |
0 |
ISSUE-122 |
CLOSED |
Should StatusInfo on failure be required to have further information? |
2010-01-25 |
MMI Architecture |
0 |
ISSUE-123 |
CLOSED |
Should we say "the NewContextResponse is sent by the IM and only by the IM"? |
2010-01-25 |
MMI Architecture |
0 |
ISSUE-124 |
CLOSED |
"must be able to contain" --> "MAY contain" |
2010-01-25 |
MMI Architecture |
0 |
ISSUE-125 Ingmar |
CLOSED |
Chapter 5.1.8.1, change "arbitrary" to "unique within the context" |
2010-02-01 |
MMI Architecture |
0 |
ISSUE-126 emotion registry |
CLOSED |
Should there be a registry for vocabularies? |
2010-02-03 |
EmotionML |
0 |
ISSUE-127 |
OPEN |
Emotion attributes for easier use with other markup languages, e.g. HTML 5 |
2010-02-03 |
EmotionML1.1 |
0 |
ISSUE-128 |
CLOSED |
Should user-defined strings be in attribute values rather than element names? |
2010-02-03 |
EmotionML |
0 |
ISSUE-129 |
CLOSED |
Add text to the spec, that a PrepareRequest, which is received after a StartRequest, should be ignored |
2010-02-15 |
MMI Architecture |
0 |
ISSUE-130 |
CLOSED |
Start and Prepare in any state |
2010-03-30 |
MMI Architecture |
0 |
ISSUE-131 |
CLOSED |
Emtpy Start Request |
2010-03-30 |
MMI Architecture |
0 |
ISSUE-132 |
OPEN |
FURTHER INVESTIGATION: An example showing use of Media fragment URI to refer to portions of a signal |
2010-04-08 |
EMMA 1.1 |
0 |
ISSUE-133 |
CLOSED |
ADD: The examples of EMMA process are pointing to actual documents, but we could make it explicit that we can use URI syntax to indicate type of process without actually pointing to an XML document |
2010-04-08 |
EMMA 1.1 |
0 |
ISSUE-134 |
CLOSED |
Should <emotion> have a confidence attribute? |
2010-04-14 |
EmotionML |
0 |
ISSUE-135 |
CLOSED |
What should the IM do if it gets an unknown context id? |
2010-04-26 |
MMI Architecture |
0 |
ISSUE-136 |
CLOSED |
In the vocabulary definition for unipolar vs. bipolar scales, is the neutral point on the scale always predictable from the type of scale? Think of some examples. |
2010-05-26 |
EmotionML |
0 |
ISSUE-137 |
CLOSED |
Ensure that all reasonable kickoff orders are supported by the MMI spec |
2010-06-14 |
MMI Architecture |
0 |
ISSUE-138 |
CLOSED |
clarify usage of default namespace in EMMA |
2010-06-15 |
EMMA 1.1 |
0 |
ISSUE-139 |
CLOSED |
allow inline content in <grammar> |
2010-06-15 |
EMMA 1.1 |
0 |
ISSUE-140 |
CLOSED |
grammar should be able to be child of other elements besides <emma> |
2010-06-15 |
EMMA 1.1 |
0 |
ISSUE-141 |
CLOSED |
ADD: need place to put a reference to the audio that was recognized - clarification text |
2010-06-15 |
EMMA 1.1 |
0 |
ISSUE-142 |
CLOSED |
ADD: annotation of information from human transcription |
2010-06-15 |
EMMA 1.1 |
0 |
ISSUE-143 |
CLOSED |
ADD: need a place to keep track of input parameters (process-parameters) |
2010-06-15 |
EMMA 1.1 |
0 |
ISSUE-144 |
OPEN |
VERY LOW INTEREST: the view of confidence in EMMA is incomplete and restrictive |
2010-06-15 |
EMMA 1.1 |
0 |
ISSUE-145 |
CLOSED |
hard to represent SRGS and SISR in EMMA and then go back to VXML |
2010-06-15 |
EMMA 1.1 |
0 |
ISSUE-146 |
CLOSED |
problems with derivations all needing to be direct children of emma:emma |
2010-06-15 |
EMMA 1.1 |
0 |
ISSUE-147 |
CLOSED |
FURTHER INVESTIGATION: 147: reference other EMMA documents from under sequence or group |
2010-06-15 |
EMMA 1.1 |
0 |
ISSUE-148 |
CLOSED |
The list of pre-defined values of modality needs to be extended and refined. |
2010-06-23 |
EmotionML |
0 |
ISSUE-149 |
CLOSED |
Emotion vocabularies: list and description are preliminary and incomplete |
2010-06-30 |
EmotionML |
0 |
ISSUE-150 |
CLOSED |
Sensor type by which a modality was observed cannot be annotated |
2010-06-30 |
EmotionML |
0 |
ISSUE-151 |
CLOSED |
Shortcut attributes for specifying e.g. gender, age (convapps issue 2, 7) |
2010-07-22 |
EMMA 1.1 |
0 |
ISSUE-152 |
CLOSED |
ADD: representation of complex NL semantics in EMMA (conv apps issue 13) |
2010-07-22 |
EMMA 1.1 |
0 |
ISSUE-153 |
CLOSED |
DEFER: Multi source input (convapps issue 9) |
2010-07-22 |
EMMA 1.1 |
0 |
ISSUE-154 |
CLOSED |
medium and mode do not capture the body part being used |
2010-07-22 |
EMMA 1.1 |
0 |
ISSUE-155 |
CLOSED |
clarification of non-redundancy of medium and mode |
2010-07-22 |
EMMA 1.1 |
0 |
ISSUE-156 |
CLOSED |
Is intensity to be included for all emotion description, or just for categories somehow? |
2010-09-01 |
EmotionML |
0 |
ISSUE-157 |
OPEN |
Define discrete emotion scales |
2010-10-18 |
EmotionML1.1 |
0 |
ISSUE-158 |
CLOSED |
Multiple categories in one emotion tag |
2010-10-18 |
EmotionML |
0 |
ISSUE-159 |
CLOSED |
Time stamps since program start |
2010-10-18 |
EmotionML |
0 |
ISSUE-160 |
CLOSED |
Represent an emotion's intensity but not it's nature |
2010-10-18 |
EmotionML |
0 |
ISSUE-161 |
RAISED |
Consider adding attributes on inertia and conscious-control to <emotion> |
2010-10-18 |
EmotionML1.1 |
0 |
ISSUE-162 |
OPEN |
Relations between emotions should be represented |
2010-10-18 |
EmotionML1.1 |
0 |
ISSUE-163 |
CLOSED |
Need to represent a consolidated emotion and the individual emotions upon which it is built |
2010-10-18 |
EmotionML |
0 |
ISSUE-164 |
CLOSED |
Represent a single time stamp rather than start+end |
2010-10-18 |
EmotionML |
0 |
ISSUE-165 |
CLOSED |
Requirement to record the identity of the annotator |
2010-10-18 |
EmotionML |
0 |
ISSUE-166 |
CLOSED |
Should the 'value' attribute of <appraisal> and <action-tendency> be optional? |
2010-10-27 |
EmotionML |
0 |
ISSUE-167 |
CLOSED |
What should be the status of the recommended vocabularies? |
2010-11-10 |
EmotionML |
0 |
ISSUE-168 |
CLOSED |
Should we develop a JSON serialization for the whole EMMA result |
2010-11-18 |
EMMA 1.1 |
0 |
ISSUE-169 |
CLOSED |
ADD: The intent in EMMA is to be able to cascade attributes, e.g. from "one-of" to child "interpretation" elements, but this needs to be clarified in the spec. |
2010-11-18 |
EMMA 1.1 |
0 |
ISSUE-170 |
OPEN |
FURTHER INVESTIGATION: To examine adding EMMA attributes to enable annotation of type information on components of a semantic representation, e.g. distinguishing numbers from strings when they are coming from, e.g. JSON |
2010-11-18 |
EMMA 1.1 |
0 |
ISSUE-171 |
CLOSED |
other semantic payloads in EMMA such as json |
2011-03-03 |
EMMA 1.1 |
0 |
ISSUE-172 |
CLOSED |
Should the reference from EmotionML spec to Vocabularies document be normative? If so, change Vocab doc into W3C Note |
2011-04-13 |
EmotionML |
0 |
ISSUE-173 |
CLOSED |
Dated or undated URI for vocabularies |
2011-04-13 |
EmotionML |
0 |
ISSUE-174 |
CLOSED |
Define a MIME type for EmotionML documents |
2011-04-13 |
EmotionML |
0 |
ISSUE-175 |
CLOSED |
Emotion vocabularies should not use custom mechanism |
2011-04-13 |
EmoLCC |
0 |
ISSUE-176 |
CLOSED |
syntactic error in appendix B |
2011-04-13 |
MMI Architecture |
0 |
ISSUE-177 |
CLOSED |
error in the sequence diagrams |
2011-04-13 |
MMI Architecture |
0 |
ISSUE-178 |
CLOSED |
Schema error about StatusResponse |
2011-04-18 |
MMI Architecture |
0 |
ISSUE-179 |
CLOSED |
Integration with SSML |
2011-04-26 |
EmoLCC |
0 |
ISSUE-180 Related to ISSUE-168 |
RAISED |
WAITING FOR MORE INFORMATION: Should there be an EMMA profile for HTML-Speech? |
2011-04-28 |
EMMA 1.1 |
0 |
ISSUE-181 |
CLOSED |
Schema for contentURL doesn't currently require namespaces on its attributes but it should |
2011-05-09 |
MMI Architecture |
0 |
ISSUE-182 |
CLOSED |
Mmi element is not required to have a namespace in the schema but it should |
2011-05-09 |
MMI Architecture |
0 |
ISSUE-183 |
OPEN |
FURTHER INVESTIGATION: Should we add a "device" attribute to EMMA? The problem is that there are many devices, and what to call them, but this would be useful. |
2011-05-19 |
EMMA 1.1 |
0 |
ISSUE-184 |
CLOSED |
Accessibility use cases for EmotionML |
2011-06-21 |
EmoLCC |
0 |
ISSUE-185 |
CLOSED |
Easier-to-use emotion markup using attributes |
2011-06-21 |
EmoLCC |
0 |
ISSUE-186 |
CLOSED |
Make explicit the relationship between different emotion vocabularies |
2011-06-21 |
EmoLCC |
0 |
ISSUE-187 |
CLOSED |
Public Comment 1 |
2011-06-21 |
MMIArchLLC |
0 |
ISSUE-188 |
CLOSED |
Public Comment 2 |
2011-06-21 |
MMIArchLLC |
0 |
ISSUE-189 |
CLOSED |
Public Comment 3 |
2011-06-21 |
MMIArchLLC |
0 |
ISSUE-190 |
CLOSED |
Public Comment 4 |
2011-06-21 |
MMIArchLLC |
0 |
ISSUE-191 |
CLOSED |
Wrong use of timestamps in EmotionML |
2011-06-22 |
EmoLCC |
0 |
ISSUE-192 |
CLOSED |
Suggestion to use XML Schema's DateTime instead milliseconds in EmotionML timestamps |
2011-06-22 |
EmoLCC |
0 |
ISSUE-193 |
CLOSED |
Should there be an "info-ref" capability so that you can refer to "info" elements elsewhere? It would need some kind of an id, but that should be optional (for backwards compatibility?) |
2011-06-30 |
EMMA 1.1 |
0 |
ISSUE-194 |
CLOSED |
ADD: Add <emma:process-model> with a ref attribute where you can have a URI describing or pointing to the particular model used for classification, object recognition etc > emma:process-model-ref |
2011-06-30 |
EMMA 1.1 |
0 |
ISSUE-195 |
CLOSED |
qualified vs unqualified attributes |
2011-07-05 |
MMIArchLLC |
0 |
ISSUE-196 |
CLOSED |
The medium and mode attributes should be reviewed and overhauled |
2011-09-08 |
|
0 |
ISSUE-197 |
OPEN |
ADD: Need to update schema to reflect the set of 1.1 changes |
2011-09-08 |
EMMA 1.1 |
0 |
ISSUE-198 |
CLOSED |
Review set of attributes on interpretation and see which should also apply to emma:annotation |
2011-11-10 |
EMMA 1.1 |
0 |
ISSUE-199 |
CLOSED |
Clarify what time attributes on annotation are for when the annotation is made rather than any time with respect to the input itself |
2011-11-10 |
EMMA 1.1 |
0 |
ISSUE-200 |
RAISED |
Review set of attributes on interpretation and see which should also apply to emma annotation |
2011-11-10 |
EMMA 1.1 |
0 |
ISSUE-201 |
CLOSED |
Add attr to annotation to mark which one if the annotation of the current top level interpretation |
2011-11-10 |
EMMA 1.1 |
0 |
ISSUE-202 |
CLOSED |
Discuss reference to vocabulary document. If additional explanation is needed regarding the mechanism for pointing to a vocabulary. |
2011-12-14 |
EmotionML |
0 |
ISSUE-203 |
CLOSED |
typos in XSD |
2012-06-25 |
MMIArchLLC |
0 |
ISSUE-204 |
CLOSED |
mc specific assertions for cancel |
2012-06-25 |
MMIArchLLC |
0 |
ISSUE-205 |
CLOSED |
modality component states |
2012-06-25 |
MMIArchLLC |
0 |
ISSUE-206 |
CLOSED |
Appendix A: Modality State Components |
2012-06-25 |
MMIArchLLC |
0 |
ISSUE-207 |
CLOSED |
Description of Done Notification |
2012-06-25 |
MMIArchLLC |
0 |
ISSUE-208 |
CLOSED |
Confidential Flag |
2012-06-25 |
MMIArchLLC |
0 |
ISSUE-209 |
CLOSED |
[active] FURTHER INVESTIGATION: We should consider if we should add location as metadata like time |
2012-06-28 |
EMMA 1.1 |
0 |
ISSUE-210 |
CLOSED |
How to provide both a lattice and nbest for the same input? |
2012-09-13 |
EMMA 1.1 |
0 |
ISSUE-211 |
RAISED |
[defer to next WD} What do we want to say about the formats of documents referred to by external URI's? |
2012-09-13 |
EMMA 1.1 |
0 |
ISSUE-212 |
CLOSED |
Should we add some kind of high res timestamp as in http://w3c-test.org/webperf/specs/HighResolutionTime/? |
2012-10-18 |
EMMA 1.1 |
0 |
ISSUE-213 |
OPEN |
[defer] JSON representation subset of EMMA for HTML Speech |
2012-11-01 |
EMMA 1.1 |
0 |
ISSUE-214 |
CLOSED |
Using SCXML for recording overall dialog structure |
2012-11-01 |
EMMA 1.1 |
0 |
ISSUE-215 |
CLOSED |
If we have doc-rec attribute with URI to refer to this exact document, doc-ref must be recognized as archival sense like this version URI in W3C specs |
2012-11-01 |
EMMA 1.1 |
0 |
ISSUE-216 |
RAISED |
We want to refer to fully fleshed version of the document rather than "this" vesion |
2012-11-01 |
EMMA 1.1 |
0 |
ISSUE-217 |
CLOSED |
Security permission notation for EMMA elements |
2012-11-01 |
EMMA 1.1 |
0 |
ISSUE-218 |
RAISED |
Big data and video stream using EMMA |
2012-11-01 |
EMMA 1.1 |
0 |
ISSUE-219 |
RAISED |
Semantic interpretation for mutlitmodal applications |
2012-11-01 |
Future Architecture |
0 |
ISSUE-220 |
RAISED |
Do we want to create a delta format for EMMA |
2012-11-01 |
EMMA 1.1 |
0 |
ISSUE-221 |
CLOSED |
There are a variety of ways to refer to other emma documents. The intended uses of these ways is not always clear. Further, there may be other reasons to refer to other emma documents, so perhaps we want a new element(s) with a type attribute to indicat |
2012-11-01 |
EMMA 1.1 |
0 |
ISSUE-222 |
CLOSED |
Should we have an "emma:partial" attribute to go along with "ref" to indicate that something more can be found on the server? |
2012-11-08 |
EMMA 1.1 |
0 |
ISSUE-223 |
RAISED |
How to identify which MC generated the emma fragment being referred to by prev-doc? maybe similar to emma:process |
2013-01-10 |
EMMA 1.1 |
0 |
ISSUE-224 |
RAISED |
For automotive purposes, a motion trajectory may be useful, could think about using inkML for actual trajectory, but would be xyz, rather than xy as in InkML |
2013-04-25 |
EMMA 1.1 |
0 |
ISSUE-225 |
RAISED |
What kind of functionality does the State Manager need in addition to data structures? For example, how much intelligence does it need? |
2013-06-03 |
Discovery and Registration |
0 |
ISSUE-226 |
RAISED |
Revisit time-keeping in EMMA, for example, how to deal with time zones |
2013-07-22 |
EMMA 1.1 |
0 |
ISSUE-227 |
RAISED |
How to handle biometric information in emma |
2013-08-01 |
EMMA 1.1 |
0 |
ISSUE-228 |
RAISED |
How to handle incrementality in emma |
2013-08-01 |
EMMA 1.1 |
0 |
ISSUE-229 |
CLOSED |
How to handle time zones in emma, currently we have only the absolute time in Unix time |
2013-08-01 |
EMMA 1.1 |
0 |
ISSUE-230 |
RAISED |
How to handle output in emma (see 2.0 use cases) |
2013-08-01 |
EMMA 1.1 |
0 |
ISSUE-231 |
RAISED |
How does the consumer of an emma output document quickly work out what's coming without having to navigate the whole structure |
2014-02-25 |
EMMA 2.0 |
0 |
ISSUE-232 |
RAISED |
What does emma:lang mean for output? in input it means the language of the input signal |
2014-02-25 |
EMMA 2.0 |
0 |
ISSUE-233 |
RAISED |
How to represent the uninterpreted part of a stream if we're making lists that have to line up with confidences and tokens? |
2014-03-20 |
|
0 |
ISSUE-234 |
RAISED |
Should the new discovery and registration events have their own namespace? |
2014-06-09 |
Discovery and Registration |
0 |
ISSUE-235 |
RAISED |
Should we have json examples? |
2014-06-09 |
Discovery and Registration |
0 |
ISSUE-236 |
RAISED |
Should we have a javascript api? |
2014-06-09 |
Discovery and Registration |
0 |
ISSUE-237 |
RAISED |
possible revision to section 1.1 |
2015-02-19 |
EMMA 2.0 |
0 |
ISSUE-238 |
RAISED |
work through issues of planned vs. actual output |
2015-02-19 |
EMMA 2.0 |
0 |
ISSUE-239 |
RAISED |
one-of for output example |
2015-02-19 |
EMMA 2.0 |
0 |
ISSUE-240 |
RAISED |
output example for group |
2015-02-19 |
EMMA 2.0 |
0 |
ISSUE-241 |
RAISED |
output example for sequence |
2015-02-19 |
EMMA 2.0 |
0 |
ISSUE-242 |
RAISED |
output derivation example |
2015-02-19 |
EMMA 2.0 |
0 |
ISSUE-243 |
RAISED |
emma:location on output |
2015-02-19 |
EMMA 2.0 |
0 |
ISSUE-244 |
RAISED |
add token-score and token-type to emma:interpretation, etc. |
2015-02-19 |
EMMA 2.0 |
0 |
ISSUE-245 |
RAISED |
example of output process for generation |
2015-02-19 |
EMMA 2.0 |
0 |
ISSUE-246 |
RAISED |
emma:lang on output |
2015-02-19 |
EMMA 2.0 |
0 |
ISSUE-247 |
RAISED |
emma:signal for output? |
2015-02-19 |
EMMA 2.0 |
0 |
ISSUE-248 |
RAISED |
emma:media-type for output? |
2015-02-19 |
EMMA 2.0 |
0 |
ISSUE-249 |
RAISED |
emma:confidence for output example |
2015-02-19 |
EMMA 2.0 |
0 |
ISSUE-250 |
RAISED |
emma:source for output |
2015-02-19 |
EMMA 2.0 |
0 |
ISSUE-251 |
RAISED |
output examples for medium/mode |
2015-02-19 |
EMMA 2.0 |
0 |
ISSUE-252 |
RAISED |
application of emma:cost to output |
2015-02-19 |
EMMA 2.0 |
0 |
ISSUE-253 |
RAISED |
output and emma:grammar-ref |
2015-02-19 |
EMMA 2.0 |
0 |
ISSUE-254 |
RAISED |
emma:model-ref for output |
2015-02-19 |
|
0 |
ISSUE-255 |
RAISED |
discuss emma:dialog-turn and output |
2015-02-19 |
|
0 |
ISSUE-256 |
RAISED |
example of emma:result-format for output |
2015-02-19 |
EMMA 2.0 |
0 |