WIF:Issues

From WikiSym

This page describes the open issues of the WSR 3 proposal. Please don't delete closed issues, they are a good documentation why things are as they are.

Issues are discussued according to IBAW (http://wiki.xam.de/2006-02-ibaw.html).

Single page issues

issue: Why not have full XHTML for the content?

idea: have a WIF-full-mode that allows XHTML, just makes conversion to WIkiSyntax much harder

issue: how to represent the distinction wikilink vs. external link

idea: microformats, class="wikilink"
- pro: easyto do
- con: hard to describe the semantics in any way
idea: use RDFa
- con: slightly more syntax
  - idea: doens't matter, it's just template generated
- pro: can describe semantics
- pro: universal
- pro: extensible
- ACTION: a proposal in WIF:Semantics

issue: how to handle "nowiki" schedules

idea: tag "pre" and "tt" sections

issue: nested tables are hard to render in wiki syntax (P1 and P3)

idea: nested tables are noz defined in WIF

issue: what are the different semantics of "nowikiw", "verbatim" and "pre"

issue: are headlines h1-h6 needed? why not just have "headline" that is nested?

issue: allow "pre" in "p" ?

issue: relation to WikiCreole?

idea: WikiCreole defines a wiki syntax in text that can be used on any wiki. WIF ignores the syntax that was used to created a wiki page and instead exports the semantics the user intended to create, e.g. a bulleted list or table.
idea: It's easier to agree on WIF than on WikiCreole, thus WIF can carry more information
idea: WIF is easier to be extend, can carry metadata
idea: WIF handles more elements, because it's easier to agree on elements than also on a syntax
idea: WIF/XML is easier than text parsing
idea: WIF/XML is easier to generate

issue: can WIF also export semantic wiki content?

idea: WIF has RDFa support and describes best practices how to use that to embed semantic wiki data
- ACTION: a proposal in WIF:Semantics

issue: how is metadata about the page stored? e.g. last changed date and author

idea: use RDFa
- pro: a single "Save as..." give the user all data
- ACTION: a proposal in WIF:Semantics
idea: use ATOM
- pro: defined way to do that, existing readers

issue: We should not use deprecated XHTML tags.

idea: check the XHTML 1 and XHTML 2 specs.
- TODO

issue: which format can be re-used?

idea: (X)HTML
- pro: all wikis generate HTML somehow, HTML represent thus what the user meant, that's what needs to be exchanged
- pro: XHTML captures the document semantics well
- pro: additional RDFA can capture annotations (e.g. which content is dynamic)
- con: we need to export: wiki link vs. external link AND Which content was generated from templates or queries?
  - idea: augment XHTML with RDFa @@add link
- con: HTML has to many features, it mixes content and styling
  - - idea: WIF supports only the structural elements, a subset
      - pro: current wikis generate a subset of HTML, it's already generated by wikis (Principle 4)
- ACTION: a proposal in WIF:Semantics

issue: how to annotate dynamic content?

idea: have static version as WIF and use RDFa to indicate dynamic source
- issue: agree on "ontology of plugins"
  - idea: many wikis use few extensions
    - there are simple and complex plugins

issue: How to handle wiki syntax that generates images as output?

E.g. consider a UML diagram generated from class A class B , imagine that indentation creates a subclass.

idea: store syntax used to create this particular chunk as well
- issue: P5

issue: how to handle links to unexisting pages (very common in wikis)

idea: an empty link <a href="" >text</a>

issue: one page should be sent as one file

idea: should be XML, because thats easy to manipulate in many prog. languages
idea: xhtml files that render in a browser
- pro: all wikis do (x)html anyways, so this is possible
- issue: how to distinguish wiki-links from external links?
  - idea: make relative links and use css class names (microformats approach)
- issue: how to embed RDF?
  - - pre-section with N3 or N-triples - with RDF being hidden in the stlye sheet
    - pro: easy to re-use existing RDF parser
    - con: how to make statements about parts of a page?
- issue: how to make statements about parts of the page?
  - idea: RDFa

issue: fall-back if WIF failed

idea: store full rendered HTML page as well
- pro: can be viewed if anything fails
- con: to much overhead, drop it
- ACTION: dropped.

More issues

issue: how to handle sets of pages?

issue: exchange format for many pages (Wiki Archive Format, WAF)

issue: attachments

issue: images

idea: have one "Images" directory in the WAF with all images
- pro: all pages can link to the same image, no waste of space

issue: where to store image metadata?

issue: transclusion

ACTION: how many wikis use it?
- note: WikiCreole defines transclusion

issue: templates

issue: WIF exchange protocol

idea: look into ATOM PP

issue: metadata per page

issue: metadata for the wiki as such

issue: user account migration?

issue: embedding arbitrary metadat, e.g. from semantic wikis

idea: use RDFa
- ACTION: a proposal in WIF:Semantics

issue: all wiki content should be sent as one file

idea: zip format like open office
- idea: unzip and browsing in the file system should work