Marked “Undefined Actions” section as possible to be removed in future …

…#105
w3c · Feb 14, 2017 · 6ef75d9 · 6ef75d9
1 parent 7726768
commit 6ef75d9
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 1 deletion.
diff --git a/model/config.js b/model/config.js
@@ -1,7 +1,7 @@
 var respecConfig = {
         specStatus: "ED",
         shortName:  "odrl-model",
-        publishDate:          "2017-02-13",
+        publishDate:          "2017-02-14",
         editors: [
             {   name:       "Renato Iannella",
                     url:        "https://au.linkedin.com/in/riannella",

diff --git a/model/index.html b/model/index.html
@@ -433,6 +433,11 @@ <h4>Policy Conflict</h4>
     <section id="undefined">
 <h4>Undefined Actions</h4>
 
+
+<div class="issue" data-number="105">
+    <p>The detection of undefined actions is viewed to be implementation-specific, and too vague to be part of the Information Model. This feature maybe removed in future versions.</p>
+</div>
+
 <p>The <code>undefined</code> attribute is used to indicate how to process unsupported Actions. That is, if an ODRL expression contains an Action that is not from a known (or supported) ODRL vocabulary, how should the Action be treated in the context of the whole ODRL Policy?</p>
 
  <p>The <code>undefined</code> attribute MUST take one of the following values:</p>