Extension talk:Wiki Object Model

Jump to: navigation, search

About this board

By clicking "Add topic", you agree to our Terms of Use and agree to irrevocably release your text under the CC BY-SA 3.0 License and GFDL

Does this use the MW parser internally?

3
Dan Bolser (talkcontribs)

Or is it a totally new parser built independently of the MW parser? I'm curious for sustainability reasons. I've done something similar (less extensive) in Perl, and I'm wondering weather to abandon my work and switch to WOM.

Cheers,

Ning~mediawikiwiki (talkcontribs)

Sorry, this extension do not use MW parser.

WOM is targeting to parse wiki objects of wiki pages 'before rendering'.

  • it is designed to have an open development framework, to make wiki objects' parser/model easy to upgrade

Hope this can help.

Thanks,

This post was posted by Ning~mediawikiwiki, but signed as Ning.

Reply to "Does this use the MW parser internally?"
Dan Bolser (talkcontribs)

How come it can't work with or without SMW? Is listing SMW as a dep really correct? Cheers,

Ning~mediawikiwiki (talkcontribs)

SMW is optional.

  • WOM will test the wiki instance.
  • If SMW extension is deployed, 'Property' object model will thus be parsed, otherwise, the 'property object' parser will cancel its work.

Thanks,

This post was posted by Ning~mediawikiwiki, but signed as Ning.

Reply to "Is SMW really a dep?"
Zahara (talkcontribs)

I'm doing some development work on the RDFIO extension, which uses WOM. I've tried to access the links from the page to pages in http://wiking.vulcan.com/dev/index.php/Extension:Wiki_Object_Model, and got a message saying the site is having technical difficulties. Do you have any information on when this will be restored and/or if the content is hosted elsewhere?

Cheers,

Yaron Koren (talkcontribs)

Ooh... I don't have any firsthand knowledge of this, but I believe Vulcan has been out of the MediaWiki business since 2013, when Project Halo was canceled; so my guess is that you won't get an answer, and that the site will never come back up.

Kghbln (talkcontribs)

I too believe Yaron's assessment is correct. I have updated the extension's page to reflect this better and not to trigger too many expectations.

Zahara (talkcontribs)

Thanks - any idea if the content is cached somewhere? I was looking at possibly removing the WOM dependency, and if the documentation isn't available, that makes it a) more important b) more difficult. Current strategy without docs is to determine the functionality I'm looking to replace by experiment, which could be time-consuming!

Kghbln (talkcontribs)

Vulcan prevented the webpage in question from being crawled and archived via their "robots.txt" file. So the internet archive holds no information this. The only way I see is to approach Vulcan directly and ask if some or all of the documentation is still available somehow and may be provided.

Planetenxin (talkcontribs)

I send a message to Jesse asking to get the old documentation so I can update the extension page...

Reply to "WOM documentation site down"

'Download snapshot' gives a subversion error

2
81.86.161.240 (talkcontribs)

Subversion encountered an error: svn: Working copy '/mnt/upload6/private/ExtensionDistributor/mw-snapshot/trunk/extensions' locked svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)

111.191.116.88 (talkcontribs)

I had same with PrivatePageProtection extension. Got around it by downloading using SVN from command line:

svn checkout http://svn.wikimedia.org/svnroot/mediawiki/trunk/extensions/PrivatePageProtection
Reply to "'Download snapshot' gives a subversion error"

'Special Charaters' when querying template fields

1
Planetenxin (talkcontribs)

Hi,

I query a template field as follows:

api.php?action=womget&title=Alexander_Gesinn&xpath=//template[@name="Person_01_00"]/template_field[@key="Username"]

Template:

{{Person_01_00
|Username=Alex
}}

As a result I get:

<?xml version="1.0"?>
<api>
  <womget result="Success">
    <return>
      <id15 xml:space="preserve">Username=Alex
|</id15>
    </return>
  </womget>
</api>

Why do I get a \n| at the end of the returned value? When I remove the CRLF in the template I still get the Pipe symbol. Is this a bug?

MW 1.16.x, WOM r104210

Reply to "'Special Charaters' when querying template fields"
There are no older topics