VisualSchemas For papiNet

papiNet has standards for paper and forest industry. VisualSchema is pleased to announce the availability of Visual Schemas for papiNet XML Schema standards.

I am going to soon write up how exactly the Visual Schema are created in more detail later on. But the thing to note is that the UI is all pre-generated static html files. So, depending on the number of complex nodes and the various navigation paths, the number of these static files could be huge. So far, OAGIS™ used to be the most complex with several complex nodes for a few of the messages. papiNet has now over taken that complexity. The entire pre-generated html size is about 3 GB. Visual Schemas for OAGIS&trade Nouns on the other hand occupy only about 0.4 GB. papiNet would have occupied even more, but a few frequent and simple nodes have been deliberately excluded to reduce the storage requirements). This shouldn’t reduce the usability since the nodes that have been excluded are simple text fields and text fields with UOM.

A few reasons why some of the messages have several nodes is

1) Product definition is quite elaborate and recursive (packaging structure).
2) Paper & Wood, the key products of the papiNet standard have tolerances to their values with min and max values. One thing though, instead of defining a complexType of “value with UOM” and use it to define the value, range min and range max values, an alternate choice is to define a complexType that captures the value, UOM as well as range min and max values. In other words, instead of having to say

<Value UOM=”Inch”>20<Value>
<RangeMin UOM=”Inch”>18<RangeMin>
<RangeMax UOM=”Inch”>21<RangeMax>

saying

<Value UOM=”Inch” min=”18″ max=”21″>20<Value>

would have made the payload smaller.

Anyway, even though papiNet has overtaken OAGIS in terms of storage requirement for VisualSchemas, there is another open standard that has a single message that is probably the largest of all the standards. Because it’s very large, I haven’t published it yet. Need to think a bit more on how to reduce the storage requirement, perhaps changing the current architecture of VisualSchemas to suite a certain type of XML Schema that shares some of the papiNet message characteristics.

Advertisements

Visual Schemas For NewsML

NewsML is “an XML-based standard to represent and manage news throughout its lifecycle, including production, interchange, and consumer use”.

VisualSchema is pleased to announce Visual Schemas For NewsML.

WordPress Blog Sidebar Widgets Arrangement

I just changed the layout of this blog and it was quite a bit of dilemma as to how to organize the various widgets. Finally, came up with the following layout strategy.

WordPress Blog Sidebar Arrangement

The idea is, the widgets have been separated into two categories, one that present timeline of the blog posts and the other that presents the analytics of the blog posts. After observing this, it was an easy decision to place one category on one sidebar and the other category in the second sidebar. This feels like an optimal widget placing strategy.

Visual Schemas For eBay Web Services

eBay claims 5.7 billion web service calls a month! I wouldn’t be surprised that in the future, the number of total web service calls to be more than the number of manual page views.

While people visit the web and create the web traffic to mostly view content (including email which is a major contributor), using web services people can create creative and innovative applications that can be either online or on the desktop and provide facility to view and also create content. People making serious living out of eBay for example with hundreds or even thousands of listings would rather create their lists through a specialized tool that makes use of these web services than to do it online.

eBay has Shopping Web Services and Trading Web Services. They also have Research Web Services but I don’t see an XSD for this yet.

VisualSchema is pleased to release Visual Schemas for eBay Shopping Web Services and Visual Schemas for eBay Trading Web Services.

Visual Schemas For E-Government Standards

Who knew that even whitehouse had xml standards! At

http://www.whitehouse.gov/omb/egov/e-5-documents.html

I found

Exhibit 300 Schema, Version 3.02 (for FY08)

This document is used to describe and define the type of content including the entities, attributes, elements and notation used for the submission of Exhibit 300s for the FY08 budget cycle.”

The schema definition is published for every year’s budget cycle. VisualSchema.com is pleased to announce the availability of Visual Schemas For OMB (E-Government).

One interesting thing is that the namespace uri of the above schema is https://OMB300.gov a seemingly non-existent domain name and made me smile to see they are using https for the namespace uri. I mean, sure whitehouse has it’s own confidential documents, but using https in the target namespace uri sure isn’t going to keep them all that confidential. Or is it? :).

Visual Schemas For PBCore

The Public Broadcast Metadata Dictionary Project has a schema defined for exchanging the data related to the Public Broadcast industry. VisualSchema.com is pleased to offer Visual Schemas for PBCore.

Visual Schemas For EDGAR (SEC Filings)

EDGAR, which stands for Electronic Data Gathering, Analysis, and Retrieval, is from sec.gov and provides XML standards for the SEC filing documents.

VisualSchema is pleased to announce the availability of Visual Schemas for EDGAR SEC filing XML Schemas.

Unlike most standards published as Visual Schemas so far, each of the EDGAR schemas have a separate version. In addition, the same top-level element edgarSubmission and ownerDocument are used in different messages. Instead, the top level element names should have been the name of the Form such as FormTA-1.