RE: Argumentation Markup

Pierre-Antoine,

I updated the Wiki documents again, expanding on the RDFa examples and adding an interesting HTML5 data-* attributes example.

https://www.w3.org/community/argumentation/wiki/Argumentation_Markup
https://www.w3.org/community/argumentation/wiki/Argumentation_Markup_(Further_Discussion)

It appears that, with a combination of document metadata and data-* attributes, real-time fact-checking and reasoning-checking can be achieved for HTML documents. There may be other ways of achieving the desired features and services for HTML documents.

Some new specification work may be needed to define how the specific document metadata values and specific data-* attributes interoperate, to provide a list of well-known document service types, and to describe possibilities for user interfaces (e.g. context menus for URI-addressable facts or claims).

Some well-known document service types are indicated in the wiki documents’ examples (metadata, provenance, fact-checking, reasoning supporting, reasoning opposing, reasoning supporting and opposing, reasoning-checking). Some user interface ideas are discussed in the new introduction section of the wiki document.


Updated RDFa Examples
<html>
  <head>
    <base href="https://www.example.org/document.xhtml" />
  </head>
  <body vocab="http://schema.org/">
    <span id="fact-123" about="#fact-123" typeof="Fact" property="text" datatype="rdf:XMLLiteral">...</span>
  </body>
</html>

<html>
  <head>
    <base href="https://www.example.org/document.xhtml" />
  </head>
  <body vocab="http://schema.org/">
  <span id="fact-123" about="#fact-123" typeof="Fact" property="meta" resource="https://www.example.org/external-proof-123.xhtml">
      <span property="text" datatype="rdf:XMLLiteral">...</span>
    </span>
  </body>
</html>

<html>
  <head>
    <base href="https://www.example.org/document.xhtml" />
    <script id="inline-proof-123" type="application/ld+json">...</script>
  </head>
  <body vocab="http://schema.org/">
    <span id="fact-123" about="#fact-123" typeof="Fact" property="meta" resource="#inline-proof-123">
      <span property="text" datatype="rdf:XMLLiteral">...</span>
    </span>
  </body>
</html>

<html>
  <head>
    <base href="https://www.example.org/document.xhtml" />
    <script id="inline-proof-123" type="application/ld+json">...</script>
  </head>
  <body vocab="http://schema.org/">
    <span id="fact-123" about="#fact-123" typeof="Fact">
      <link rel="fact-checking" href="https://www.wikidata.org/wiki/Special:FactCheck" />
      <link rel="reasoning" href="https://www.wikidata.org/wiki/Special:Reasoning" />
      <link rel="reasoning-checking" href="https://www.wikidata.org/wiki/Special:ReasoningCheck" />
      <span property="text" datatype="rdf:XMLLiteral">...</span>
    </span>
  </body>
</html>

data-* Example
<html>
  <head>
    <link rel="fact-checking-service-provider" href="https://www.wikidata.org/wiki/Special:FactCheck" />
    <base href="https://www.example.org/document.xhtml" />
  </head>
  <body>
    <span id="fact-123" role="fact">HTML and MathML content</span>
    <div id="fact-124" role="fact">HTML and MathML content</div>
    <math id="fact-125" role="fact" data-fact-checking="custom-service.php">MathML content</math>
  </body>
</html>


The data-* example, above, shows how the use-cases exceed RDFa expressiveness; there is a desired interplay between document metadata, per-element attributes, and users’ configurations and settings.


Best regards,
Adam

From: Adam Sobieski<mailto:adamsobieski@hotmail.com>
Sent: Friday, January 15, 2021 9:41 AM
To: Pierre-Antoine Champin<mailto:pierre-antoine.champin@ercim.eu>; www-math@w3.org<mailto:www-math@w3.org>; public-argumentation@w3.org<mailto:public-argumentation@w3.org>; semantic-web@w3.org<mailto:semantic-web@w3.org>
Subject: RE: Argumentation Markup

Pierre-Antoine,

Thank you. I updated the document at: https://www.w3.org/community/argumentation/wiki/Argumentation_Markup .

I also started a new Wiki page for noting and expanding upon topics raised in discussions: https://www.w3.org/community/argumentation/wiki/Argumentation_Markup_(Further_Discussion)  .

For consideration, some syntax examples:


New Element(s) for Facts and Claims

<html>

  <head>

    <base href="https://www.example.org/document.xhtml" />

    <script id="inline-proof-123" type="…">…</script>

  </head>

  <body>

    <fact id="fact-123" href="#inline-proof-123">…</fact>

  </body>

</html>



New Attribute for Metadata, Provenance, Mathematical Proof, and Argumentation

<html>

  <head>

   <base href="https://www.example.org/document.xhtml" />

    <script id="inline-proof-123" type="…">…</script>

  </head>

  <body>

    <span id="fact-123" role="fact" meta="#inline-proof-123">…</span>

    <div id="fact-124" role="fact" meta="…">…</div>

   <math id="fact-125" role="fact" meta="…">…</math>

  </body>

</html>



RDFa Syntax Example

<html>

  <head>

    <base href="https://www.example.org/document.xhtml" />

    <script id="inline-proof-123" type="application/ld+json">…</script>

  </head>

  <body vocab="http://schema.org/">

    <span id="fact-123" about="#fact-123" typeof="Fact" property="text" datatype="rdf:XMLLiteral">…</span>

  </body>

</html>

The datatype of rdf:XMLLiteral is used so that the fact or claim may contain MathML content.

The three examples, above, seem almost interchangeable for the scenario of providing inline metadata, provenance, mathematical proof, and/or argumentation for facts or claims in a HTML document. Where they start to differ is in referencing external resources or services.


<html>

  <body>

    <fact id="fact-123" href="external-proof-123.xhtml">…</fact>

  </body>

</html>


<html>

  <body>

    <span id="fact-123" meta="external-proof-123.xhtml">…</span>

    <div id="fact-124" meta="…">…</div>

    <math id="fact-125" meta="…">…</math>

  </body>

</html>



<html>

  <head>

    <base href="https://www.example.org/document.xhtml" />

  </head>

  <body vocab="http://schema.org/">

    <span id="fact-123" about="#fact-123" typeof="Fact" property="text" datatype="rdf:XMLLiteral">

      <link rel="meta" href="external-proof-123.xhtml" />

      …

    </span>

  </body>

</html>



Note: the parser at https://www.w3.org/2012/pyRdfa/Overview.html does not remove the <link> element from the XML contents of the <span> when processing with rdf:XMLLiteral, so the XML contents of the fact or claim include the markup for the <link> element which is placed there to attach the external resource. One could use a <script type="application/ld+json">…</script> element to add this content instead, however.



In addition to referencing external static documents for metadata, provenance, mathematical proof, and/or argumentation, one can consider referring to external services, e.g. utilizing the URI-addressable fact or claim as a URL parameter.



<html>

  <head>

    <base href="https://www.example.org/document.xhtml" />

  </head>

  <body>

    <fact id="fact-123" href="https://www.wikidata.org/wiki/Special:FactCheck?fact=https%3A%2F%2Fwww.example.org%2Fdocument.xhtml%23fact-123">…</fact>

    <fact id="fact-124" href="https://www.wikidata.org/wiki/Special:FactCheck?fact=https%3A%2F%2Fwww.example.org%2Fdocument.xhtml%23fact-124">…</fact>

    <fact id="fact-125" href="https://www.wikidata.org/wiki/Special:FactCheck?fact=https%3A%2F%2Fwww.example.org%2Fdocument.xhtml%23fact-125">…</fact>

  </body>

</html>



<html>

  <head>

    <base href="https://www.example.org/document.xhtml" />

  </head>

  <body>

    <span id="fact-123" role="fact" meta="https://www.wikidata.org/wiki/Special:FactCheck?fact=https%3A%2F%2Fwww.example.org%2Fdocument.xhtml%23fact-123">HTML and MathML content</span>

    <div id="fact-124" role="fact" meta="https://www.wikidata.org/wiki/Special:FactCheck?fact=https%3A%2F%2Fwww.example.org%2Fdocument.xhtml%23fact-124">HTML and MathML content</div>

    <math id="fact-125" role="fact" meta="https://www.wikidata.org/wiki/Special:FactCheck?fact=https%3A%2F%2Fwww.example.org%2Fdocument.xhtml%23fact-125">MathML content</math>

  </body>

</html>



Interestingly, one could utilize document metadata to avoid repetition.



<html>

  <head>

    <link rel="meta-service-endpoint" href="https://www.wikidata.org/wiki/Special:FactCheck" />

    <base href="https://www.example.org/document.xhtml" />

  </head>

  <body>

    <fact id="fact-123">…</span>

    <fact id="fact-124">…</span>

    <fact id="fact-125">…</span>

  </body>

</html>



<html>

  <head>

    <link rel="meta-service-endpoint" href="https://www.wikidata.org/wiki/Special:FactCheck" />

    <base href="https://www.example.org/document.xhtml" />

  </head>

  <body>

    <span id="fact-123" role="fact">…</span>

    <div id="fact-124" role="fact">…</div>

    <math id="fact-125" role="fact">…</math>

  </body>

</html>



Here, the goal is to use document metadata so that a document’s facts or claims can have default attribute values generated. Default values for the href or meta attributes for facts or claims could be automatically generated using a combination of the document URL, document metadata, and users’ configurations and settings. The desired result is that a document can indicate one or more services recommended by the document’s author for obtaining metadata, provenance, mathematical proof, and/or argumentation for documents’ URI-addressable facts and claims.



These topics are discussed in the updated version of the document: https://www.w3.org/community/argumentation/wiki/Argumentation_Markup .



Some areas where new markup elements or the new meta attribute exceed RDFa:



  1.  easily referencing external documents or services for metadata, provenance, mathematical proof, and/or argumentation
     *   this includes real-time fact-checking and reasoning-checking services
  2.  automatically generating default values for href or meta attributes for URI-addressable facts or claims
  3.  providing a means for obtaining and merging results from multiple services specified by documents’ authors and/or users’ configurations and settings
  4.  it could be that new element(s) or a new meta attribute could facilitate scenarios beyond those described thus far





Best regards,

Adam

From: Pierre-Antoine Champin<mailto:pierre-antoine.champin@ercim.eu>
Sent: Friday, January 15, 2021 4:30 AM
To: Adam Sobieski<mailto:adamsobieski@hotmail.com>; www-math@w3.org<mailto:www-math@w3.org>; public-argumentation@w3.org<mailto:public-argumentation@w3.org>; semantic-web@w3.org<mailto:semantic-web@w3.org>
Subject: Re: Argumentation Markup


Adam,

making claims URI-addressable is a cool idea, but why use new HTML tags and attributes, or a new format?

In the first section, you list a number of standard-compliant alternative (e.g. RDFa). How are they not fulfilling your use-cases?

And even if they are suboptimal, the cost-benefit ratio compared to extending HTML is likely to be better.

Anyway, that's my 2˘
On 13/01/2021 03:34, Adam Sobieski wrote:
Argumentation Community Group,
Math Working Group,
Semantic Web Interest Group,

Hello. I would like to share some new ideas for discussion.

HTML and MathML content could be wrapped in new markup elements (e.g. <fact> or <claim>) or could be adorned with new attributes (e.g. meta) to provide the means for automated reasoning technologies and/or users to traverse to metadata, provenance, mathematical proof, or argumentation about the contained HTML and MathML content.

These preliminary ideas are available online (https://www.w3.org/community/argumentation/wiki/Argumentation_Markup) and are also indicated below.

URI-addressable Facts and Claims

Some preliminary ideas for representing URI-addressable facts or claims in HTML documents include:
1.       new markup elements (e.g. <fact id="..."> or <claim id="...">)
2.       text fragments (https://wicg.github.io/scroll-to-text-fragment/)
3.       standardized class<https://html.spec.whatwg.org/multipage/dom.html#classes> names (e.g. <span id="..." class="w3c-fact">)
4.       the role<https://www.w3.org/TR/role-attribute/> attribute (e.g. <span id="..." role="fact">)
5.       custom elements (e.g. <fact-span id="...">)
6.       Web schema (see: http://schema.org<http://schema.org/>)
7.       RDFa or similar technologies
8.       embedding semantics in HTML documents via <script> elements to indicate which URI-addressable document elements are facts or claims
New Markup Elements

With new markup for facts or claims (e.g. <fact id="..."> or <claim id="...">), an “argument Web” could be composed where URI-addressable facts and claims in HTML documents could each reference their supporting and/or opposing argumentation, such argumentation referencing other facts or claims by URI.

<fact id="..." href="...">HTML and MathML content</fact>

<claim id="..." href="...">HTML and MathML content</claim>

In the above example, the href attribute is for referencing a resource which could include metadata, provenance data, mathematical proof, or argumentation supporting and/or opposing the fact or claim. The referenced resource could be text, XML, HTML, RDF, AIF, or another format.

Scenario: Inline Argumentation

For scenarios where it is desired to include metadata, provenance data, mathematical proof, or argumentation in the same HTML document which contains a fact or claim, one can use <script> elements with ID’s to provide inline resources.

<html>

  <head>

    <script id="inline-proof-123" type="...">...</script>

  </head>

  <body>

    <fact id="fact-123" href="#inline-proof-123">HTML and MathML content</fact>

  </body>

</html>

The content in such <script> elements can refer to URI-addressable facts or claims in containing documents as well as in other documents or resources.

A New Attribute

Understanding the meaning of the href attribute on a <fact> or <claim> element, we could rename that href attribute to, for example, meta which would mean that it could adorn existing HTML elements.

<html>

  <head>

    <script id="inline-proof-123" type="...">...</script>

    <script id="inline-proof-124" type="...">...</script>

  </head>

  <body>

    <span id="fact-123" role="fact" meta="#inline-proof-123">HTML and MathML content</span>

    <div id="fact-124" role="fact" meta="#inline-proof-124">HTML and MathML content</div>

  </body>

</html>

A New Format for Metadata, Provenance, Mathematical Proof, and Argumentation

A new format, model, or ontology could be of use for the machine-utilizable resources referenced by URI-addressable facts or claims, resources containing metadata, provenance, mathematical proof, or argumentation.

<html>

  <head>

    <script id="inline-proof-123" type="application/new-format">...</script>

    <script id="inline-proof-124" type="application/new-format">...</script>

  </head>

  <body>

    <span id="fact-123" role="fact" meta="#inline-proof-123">HTML and MathML content</span>

    <div id="fact-124" role="fact" meta="#inline-proof-124">HTML and MathML content</div>

    <span id="fact-125" role="fact" meta="https://www.example.org/automated-reasoning.php?fact=125"<https://www.example.org/automated-reasoning.php?fact=125>>HTML and MathML content</span>

  </body>

</html>

Embedding Metadata, Provenance, Mathematical Proof, and Argumentation in HTML Documents

Alternatively, resources could be (X)HTML and contain structured data for metadata, provenance, mathematical proof, or argumentation about a fact or claim. In this scenario, in addition to being machine-utilizable, resources would be human-readable.

<html>

  <body>

    <span id="fact-123" role="fact" meta="https://www.example.org/automated-reasoning/123.xhtml"<https://www.example.org/automated-reasoning/123.xhtml>>HTML and MathML content</span>

    <div id="fact-124" role="fact" meta="https://www.example.org/automated-reasoning/124.xhtml"<https://www.example.org/automated-reasoning/124.xhtml>>HTML and MathML content</div>

    <span id="fact-125" role="fact" meta="https://www.example.org/automated-reasoning/125.xhtml"<https://www.example.org/automated-reasoning/125.xhtml>>HTML and MathML content</span>

  </body>

</html>

The Link Element

For (X)HTML documents which are about a URI-addressable fact or claim, e.g. containing metadata, provenance, mathematical proof, or argumentation, we could use the <link> element, resembling:

<html>

  <head>

    <link rel="about" href="http://www.example.org/document.xhtml#fact-123"<http://www.example.org/document.xhtml#fact-123> />

  </head>

  <body>

    ...

  </body>

</html>



Best regards,
Adam Sobieski
http://www.phoster.com/

Received on Sunday, 17 January 2021 10:21:00 UTC