Nabble - w3.org - public-web-http-desc

wadl_documentation.xsl

2009-11-17T11:26:11Z

Hello. I haven’t been able to get any XSL on http://www.mnot.net/webdesc/ to transform any WADL, even the most simple WADL. I’ve used IE7, Firefox 3 and the suggested Saxon (Java version) utility.

If I use wadl_documentation-2006-10.xsl, I get an error “Namespace 'http://exslt.org/common' does not contain any functions.” The web site warned me about EXSLT node-set support and recommends Saxon. That complains as well. The browsers and Saxon take the other two xsl docs, wadl_documentation-2006-07.xsl and wadl_documentation.xsl, but give nearly empty, in Saxon’s case, or just echo back the XML doc, in the browsers.

I tried using wadl 1.0 from w3c as well as wadl referenced in the xsl, at http://research.sun.com/wadl/2006/10.

Am I missing something?

Thanks!

DISCLAIMER: This e-mail may contain information that is confidential, privileged or otherwise protected from disclosure. If you are not an intended recipient of this e-mail, do not duplicate or redistribute it by any means. Please delete it and any attachments and notify the sender that you have received it in error. Unintended recipients are prohibited from taking action on the basis of information in this e-mail.E-mail messages may contain computer viruses or other defects, may not be accurately replicated on other systems, or may be intercepted, deleted or interfered with without the knowledge of the sender or the intended recipient. If you are not comfortable with the risks associated with e-mail messages, you may decide not to use e-mail to communicate with IPC. IPC reserves the right, to the extent and under circumstances permitted by applicable law, to retain, monitor and intercept e-mail messages to and from its systems.

WADL grammars element and modularity

2009-10-19T14:47:30Z

This is a comment on WADL, and in particular on the recent W3C Submission [1].

I'd like to submit the idea for discussion, or for correction if my understanding is wrong.

Background
In WADL, it appears that there is one global <grammar> element containing schemas for XML request and response entity content, and that the only variation allowed on a per-resource or per-method basis is the root element name.

Request
We'd like to be able to specify grammar information for entity validation at a finer level of granularity.

Michael Sperberg-McQueen (among others) has discussed the importance of context in validation, for example here [2]:
"Validating the same document now with one, now with a different schema is perfectly legitimate."
"The process of schema validity assessment does not assign any more formal authority to the owner of the namespace than to the invoker of the validation process."

Finer granularity in schema specification in WADL would give this control over to the creator of the resources, rather than to the editor of the compendium document which is the WADL description.

Use Cases
A use case illustrating the context validation point above is in validation of entities for PUT and GET. We may want to reject PUT of entities containing an atom:published element with a value of before a certain time, yet certainly we must allow GET of existing entities containing publication dates even in the distant past. It's easy to imagine other similar constraints or variations in structure which differ between PUT and GET, and further to imagine that different schemas might apply to different resources sharing a similar XML element request or response entity.

A use case illustrating the finer granularity point is an application which allows access at to a variety of resources on the same system. Some resources will be present initially, and others may be made available through third-party APIs or other means at a later time. In such as system, control over element names may not be possible, and conflicts in names across resources will be inevitable, yet it should still be possible to generate a WADL document describing all the resources.

Related Issues
It may make sense for WADL to continue to abstract over certain required features, such as a root element name, because while ome schema languages (such as Relax NG) offer clear direction on root elements, others require a more complicated authoring style to force root element declaration. A different approach such as NVDL may offer a better path than ad hoc constraints such as element name.

Sincerely,
Leigh L. Klotz, Jr.
Senior Software Architect
Xerox Corp.

[1] http://www.w3.org/Submission/2009/SUBM-wadl-20090831/
[2] http://cmsmcq.com/2005/validity-marriage.html

WADL documentation stylesheets on github

2009-04-16T16:52:19Z

I've started a repository for the XSLT stylesheets on github, so that
others can contribute, fork, etc.;
http://github.com/mnot/wadl_stylesheets/

I'm pretty new to github, but if all goes well, their home will move
there permanently.

Cheers,

--
Mark Nottingham http://www.mnot.net/

Re: Issues in WADL stylesheet when referencing faults or methods

2009-04-06T17:45:11Z

I've applied the patch that Yves sent to me privately -- many thanks
(and sorry for the delay).

Cheers,

On 07/01/2009, at 4:03 AM, SAINTILLAN YVES wrote:

> Mark,
> Thanks a lot for fixing this, and best wishes for the new year!
>
> I have now a couple of other issues with the stylesheet:
>
> - When a WADL resource makes use of the 'type' attribute to refer to
> a resource_type element, the documentation does not display
> correctly the URI of the corresponding resource: only the base URI
> is displayed. For example, I have modified the previous WADL (see in
> attachment), so that the resource with path 'newsSearch' makes
> reference to a resource_type 'searchResourceType'; in the generated
> documentation (also attached), the relative path 'newsSearch' is
> missing from the resource URI.
>
> - My other issue is about the queryType attribute of a resource
> element (which is optional and defaults to application/x-www-form-
> urlencoded): it seems this attribute is ignored by the stylesheet
> and does not appear in the generated documentation; is there a
> particular reason for this ?
>
> Thanks and kind regards,
> Yves
>
> -----Original Message-----
> From: Mark Nottingham [mailto:mnot@...]
> Sent: mardi 9 décembre 2008 12:34
> To: SAINTILLAN YVES
> Cc: public-web-http-desc@...
> Subject: Re: Issues in WADL stylesheet when referencing faults or
> methods
>
> Fixed; some attributes weren't copied when expanding references. I
> may have missed some more, and there's hopefully a more elegant way
> to do it, but these problems should be gone, at least.
>
> Cheers,
>
>
> On 24/11/2008, at 10:13 PM, SAINTILLAN YVES wrote:
>
>> Dear Mark,
>>
>> Sure: please find attached a modified version of WADL for Yahoo
>> NewsSearch application, that allows to reproduce both issues. In the
>> WADL, the 'GET' method and 'SearchError' fault elements are both
>> defined as children of the application element.
>>
>> Included XSD files, and generated HTML output documentation are also
>> attached.
>>
>> Thanks,
>> Yves
>>
>> -----Original Message-----
>> From: Mark Nottingham [mailto:mnot@...]
>> Sent: samedi 22 novembre 2008 17:51
>> To: SAINTILLAN YVES
>> Cc: public-web-http-desc@...
>> Subject: Re: Issues in WADL stylesheet when referencing faults or
>> methods
>>
>> Could you provide sample input that triggers this?
>>
>> Thanks,
>>
>>
>> On 22/11/2008, at 4:26 AM, SAINTILLAN YVES wrote:
>>
>>> Hello,
>>>
>>> I am using the WADL XSL stylesheet and noticed a couple of issues
>>> when
>>
>>> referencing faults or methods in a WADL:
>>>
>>> - When making a reference (href) to a Fault, defined directly under
>>> the application element, the fault is not correctly displayed in the
>>> HTML output; in particular, the status of the fault (in the
>>> reference
>>> or in the definition) does not appear.
>>>
>>> - Similarly, when making reference to a method, defined directly
>>> under
>>
>>> the application element, the name of the method is not displayed in
>>> the HTML documentation.
>>>
>>> So it seems the XSL stylesheet handles well references to
>>> representations, but not faults or methods. Are you aware of these
>>> issues ?
>>>
>>> Thanks and kind regards,
>>> Yves
>>>
>>
>>
>> --
>> Mark Nottingham http://www.mnot.net/
>>

My Web Application

Resources
- http://api.search.yahoo.com/NewsSearchService/V1/
Representations
- A list of news items matching the query (application/xml - yn:ResultSet)
Faults
- Status Code 400 - application/xml (ya:Error)

Resources

Yahoo News Search Service

The Yahoo News Search service provides online searching of news stories from around the world.

Methods

GET

request query parameters

parameter	value	description
appid	string (required)	The application ID. See Application IDs for more information.
query	string (required)
type	string One of: `all` (default) `any` `phrase`	`all` (default) All query terms. `any` Any query terms. `phrase` Query terms as a phrase.
results	int Default: `10`
start	int Default: `1`
sort	string One of: `rank` (default) `date`
language	string
output	string One of: `xml` (default) `json` `php`	The format for the output. If json is requested, the results will be returned in JSON format. If php is requested, the results will be returned in Serialized PHP format.
callback	string	The name of the callback function to wrap around the JSON data. The following characters are allowed: A-Z a-z 0-9 . [] and _. If output=json has not been requested, this parameter has no effect. More information on the callback can be found in the Yahoo! Developer Network JSON Documentation.

available response representations:

A list of news items matching the query (application/xml - yn:ResultSet)

potential faults:

Status Code 400 - application/xml (ya:Error)

Representations

A list of news items matching the query (application/xml - yn:ResultSet)

XML Schema

Source: NewsSearchResponse.xsd

<xs:element name="ResultSet">
    <xs:complexType>
      <xs:sequence>
        <xs:element name="Result" type="ResultType" minOccurs="0" maxOccurs="50"/>
      </xs:sequence>
      <xs:attribute name="totalResultsAvailable" type="xs:integer"/>
      <xs:attribute name="totalResultsReturned" type="xs:integer"/>
      <xs:attribute name="firstResultPosition" type="xs:integer"/>
    </xs:complexType>
  </xs:element>

Faults

Status Code 400 - application/xml (ya:Error)

XML Schema

Source: NewsSearchError.xsd

<xs:element name="Error">
    <xs:complexType mixed="true">
      <xs:sequence>
        <xs:element name="Message"/>
      </xs:sequence>
    </xs:complexType>
  </xs:element>

--
Mark Nottingham http://www.mnot.net/

YahooSearch.wadl (6K) Download Attachment

wadl_documentation.xsl doesn't seem to handle resource type correctly

2009-03-13T15:16:43Z

Hi,

I've been playing with WADL for service description and I ran into
this bug with wadl_documentation.xsl. The stylesheet doesn't seem to
handle type attribute on a resource element if it doesn't have an id
attribute. The output omits the resource path in this case. Adding an
id to the resource seems to resolve the issue.

thanks,

Dave

<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="./wadl_documentation.xsl"?>
<application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://research.sun.com/wadl wadl.xsd"
xmlns:tns="urn:yahoo:yn"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:html="http://www.w3.org/1999/xhtml"
xmlns="http://research.sun.com/wadl/2006/10">

<resource_type id="testType">
<method name="GET" id="testMethod" />
</resource_type>

<resources base="http://example.org">
<resource path="hello" type="#testType"/>
</resources>
</application>

RE: WADL representation/@element in xmlns=""

2009-03-04T14:04:36Z

>From: Marc.Hadley@... [mailto:Marc.Hadley@...]
>Sent: Wednesday, March 04, 2009 11:11 AM
>To: Klotz, Leigh
>Cc: public-web-http-desc@...; Jurgielewicz, Mariusz
>Subject: Re: WADL representation/@element in xmlns=""
>
> On Feb 27, 2009, at 3:47 PM, Klotz, Leigh wrote:
>
> 2. What the spec says
>
> Not seeing much discussion on this list about namespaces or xmlns, I
> consulted the WADL paper to see how to express no-namespace @element
> values.
>
> The wadl20090202 WADL paper says that representation/element is
> defined as follows:
> For XML-based representations, specifies the qualified name of the
> root element as described within the grammars section - see section
> 2.3.
>
> It seems like a good idea to be more precise here.
>
>Would it be sufficient to say that if the value of representation/

@element does not contain a prefix then the element is in no namespace ?
>
>Marc.

That would make sense to me, since it makes definition of un-namespaced
elements trivial.
It's not what's implemented in the stylesheet, so the stylesheet would
need to change.
Similarly, it's possible binding tools (if any) have made decisions
already, so authors of tools should be on the lookout as well.

But your suggestion sound good to me.

Thank you,
Leigh.

Re: WADL representation/@element in xmlns=""

2009-03-04T11:11:04Z

On Feb 27, 2009, at 3:47 PM, Klotz, Leigh wrote:

>
> 2. What the spec says
>
> Not seeing much discussion on this list about namespaces or xmlns, I
> consulted the WADL paper to see how to express no-namespace @element
> values.
>
> The wadl20090202 WADL paper says that representation/element is
> defined
> as follows:
> For XML-based representations, specifies the qualified name of the
> root
> element as described within the grammars section - see section 2.3.
>
> It seems like a good idea to be more precise here.
>

Would it be sufficient to say that if the value of representation/
@element does not contain a prefix then the element is in no namespace ?

Marc.

WADL representation/@element in xmlns=""

2009-02-27T12:47:34Z

I am reporting a confusion I'm suffering about a WADL
representation/@element which refers to an element not in a namespace,
or in xmlns="" if you prefer to treat it that way. I've found what I
believe is ambiguity in the spec, and an error in the
wadl_description.xsl stylesheet.

1. The Issue

My colleague Mariusz Jurgielewicz has shown me a WADL file containing
<application xmlns="http://research.sun.com/wadl/2006/10">
...
<representation mediatype="application/xml" element="foo" />

He noted that wadl_description.xsl was unable to find the Schema for the
representation.

I changed the WADL as follows:
<w:application xmlns="" xmlns:w="http://research.sun.com/wadl/2006/10">
...
<wadl:representation mediatype="application/xml" element="foo" />
since it appears that wadl_description.xsl interprets the namespace of
unqualified attribute values of representation/@element as being in the
default namespace of the context.

However, it still doesn't work.

2. What the spec says

Not seeing much discussion on this list about namespaces or xmlns, I
consulted the WADL paper to see how to express no-namespace @element
values.

The wadl20090202 WADL paper says that representation/element is defined
as follows:
For XML-based representations, specifies the qualified name of the
root
element as described within the grammars section - see section 2.3.

It seems like a good idea to be more precise here.

Since XML doesn't define namespace rules for processing attribute value
content, so that's up to the application. CURIEs are one approach, but
since this specification is about XML elements themselves, it's not a
good match. XML Schema is more specific about it.
The exact XML Schema approach won't work in WADL, because WADL isn't
about exactly one namespace, but I think it points again in the
direction that more precision about unqualified attribute values is
required, either in prose, or in additional markup for the WADL document
itself.

A cautionary tale: XForms wasn't specific about the namespace of its
xf:bind/@type attribute, and some implementers chose it to default to
the XML Schema, while others chose it to be the host document. Finally
the WG decided to fix the problems, by making the XForms namespace by
default, and to preserve interoperability with those who had chosen XSD
as the default by including copies of the XSD types in that namespace.

3. What wadl_description.xsl does
As for wadl_description.xsl, I believe that if it is to be able to
render WADL representations with elements in xmlns="", the stylesheet
needs some adjustments.

I found that in wadl_documentation.xsl,
template/@match="wadl:representation|wadl:fault" calls
template/@name="get-element", which its qname argument to be qualified,
and cannot process unqualified element names.

<xsl:variable name="localname" select="substring-after($qname,
':')"/>

Certainly this could be changed to
<xsl:variable name="localname">
<xsl:choose>
<xsl:when test="substring-after($qname,
':')=''"><xsl:value-of select="$qname" /></xsl:when>
<xsl:otherwise><xsl:value-of select="substring-after($qname,
':')" /></xsl:otherwise>
</xsl:choose>
</xsl:variable>

But I suspect a more comprehensive fix is in order.

Leigh.

RE: Issues in WADL stylesheet when referencing faults or methods

2009-01-27T06:09:54Z

That helped tons; thanks. I actually figured that out myself from
reading the xslt file.

I'm having a different problem now, though, which I think may be related
to the way you copy referenced resource_types and methods. First, I was
using namespaces on my ids, which I don't think your xslt handles
because it's adding a namespace too. I removed them because the Yahoo
example doesn't have them. This hasn't solved my problem, though.

Given my example below, I would expect the documentation for the
"mytype" resource to show up three times, for the three different
resources that use it. Alternatively, I would expect those three
resources to link to a single instance of the documentation for mytype.
Neither of these happen; instead the first resource shows up with the
mytype documentation, and the other two resources don't appear at all. I
suspect this has to do with either the id mangling that you do when you
expand the resources, or a failure to handle nodesets instead of a
single node at some point.

Perhaps, rather than expanding references to resource types and methods,
it would be better to show references as links, and document the
referenced elements separately. This would mirror the structure of the
wadl file a lot more closely, which might be a good thing since it would
ensure that the doc elements show up where the programmer put them, and
the same number of times the programmer wrote them.

It'd make the xslt simpler too, I think.

Doug.

-----Original Message-----
From: Marc.Hadley@... [mailto:Marc.Hadley@...]
Sent: Tuesday, January 27, 2009 8:46 AM
To: Webb, Douglas
Cc: public-web-http-desc@...
Subject: Re: Issues in WADL stylesheet when referencing faults or
methods

The values of the type attributes are URIs, in the case below you need
type="#mytype" instead of type="mytype" - i.e. a fragment identifier
for a resource_type element in the same document.

Does that help ?

Marc.

On Jan 26, 2009, at 1:06 PM, Webb, Douglas wrote:

>
> I'm having the same problem, and if it helps I'll describe the use
> case
> I'm working with. One of my resource types allows resources to be
> identified under three different URI templates. I don't want to have
> to
> repeat the entire resource definition for each URI, so I'm using the
> same type attribute on three different resource elements, each of
> which
> has a different path attribute and different param children.
>
> eg:
>
> <resource path="root">
> <resource path="first/{firstcode}" type="mytype">
> <param name="firstcode" style="template"/>
> </resource>
> <resource path="second/{secondcode}" type="mytype">
> <param name="secondcode" style="template"/>
> </resource>
> <resource path="third/{thirdcode}" type="mytype">
> <param name="thirdcode" style="template"/>
> </resource>
> </resource>
>
> <resource_type id="mytype">
> ...
> </resource_type>
>
>
> This should allow a particular resource, whose type is "mytype", to be
> available under /root/first/abc, /root/second/123, and /root/third/
> xyz,
> assuming that the service understands that all three refer to the same
> resource. Other resources in my system will link to "mytype" resources
> using whichever URI is most convienient/available.
>
> Thanks for your help!
>
> Douglas Webb
>
>
>

---
Marc Hadley <marc.hadley at sun.com>
CTO Office, Sun Microsystems.

Re: Issues in WADL stylesheet when referencing faults or methods

2009-01-27T05:45:49Z

The values of the type attributes are URIs, in the case below you need
type="#mytype" instead of type="mytype" - i.e. a fragment identifier
for a resource_type element in the same document.

Does that help ?

Marc.

On Jan 26, 2009, at 1:06 PM, Webb, Douglas wrote:

---
Marc Hadley <marc.hadley at sun.com>
CTO Office, Sun Microsystems.

RE: Issues in WADL stylesheet when referencing faults or methods

2009-01-26T10:06:41Z

I'm having the same problem, and if it helps I'll describe the use case
I'm working with. One of my resource types allows resources to be
identified under three different URI templates. I don't want to have to
repeat the entire resource definition for each URI, so I'm using the
same type attribute on three different resource elements, each of which
has a different path attribute and different param children.

eg:

<resource path="root">
<resource path="first/{firstcode}" type="mytype">
<param name="firstcode" style="template"/>
</resource>
<resource path="second/{secondcode}" type="mytype">
<param name="secondcode" style="template"/>
</resource>
<resource path="third/{thirdcode}" type="mytype">
<param name="thirdcode" style="template"/>
</resource>
</resource>

<resource_type id="mytype">
...
</resource_type>

This should allow a particular resource, whose type is "mytype", to be
available under /root/first/abc, /root/second/123, and /root/third/xyz,
assuming that the service understands that all three refer to the same
resource. Other resources in my system will link to "mytype" resources
using whichever URI is most convienient/available.

Thanks for your help!

Douglas Webb

RE: Issues in WADL stylesheet when referencing faults or methods

2009-01-06T09:03:53Z

Mark,
Thanks a lot for fixing this, and best wishes for the new year!

I have now a couple of other issues with the stylesheet:

- When a WADL resource makes use of the 'type' attribute to refer to a resource_type element, the documentation does not display correctly the URI of the corresponding resource: only the base URI is displayed. For example, I have modified the previous WADL (see in attachment), so that the resource with path 'newsSearch' makes reference to a resource_type 'searchResourceType'; in the generated documentation (also attached), the relative path 'newsSearch' is missing from the resource URI.

- My other issue is about the queryType attribute of a resource element (which is optional and defaults to application/x-www-form-urlencoded): it seems this attribute is ignored by the stylesheet and does not appear in the generated documentation; is there a particular reason for this ?

Thanks and kind regards,
Yves

-----Original Message-----
From: Mark Nottingham [mailto:mnot@...]
Sent: mardi 9 décembre 2008 12:34
To: SAINTILLAN YVES
Cc: public-web-http-desc@...
Subject: Re: Issues in WADL stylesheet when referencing faults or methods

Fixed; some attributes weren't copied when expanding references. I may have missed some more, and there's hopefully a more elegant way to do it, but these problems should be gone, at least.

Cheers,

On 24/11/2008, at 10:13 PM, SAINTILLAN YVES wrote:

> Dear Mark,
>
> Sure: please find attached a modified version of WADL for Yahoo
> NewsSearch application, that allows to reproduce both issues. In the
> WADL, the 'GET' method and 'SearchError' fault elements are both
> defined as children of the application element.
>
> Included XSD files, and generated HTML output documentation are also
> attached.
>
> Thanks,
> Yves
>
> -----Original Message-----
> From: Mark Nottingham [mailto:mnot@...]
> Sent: samedi 22 novembre 2008 17:51
> To: SAINTILLAN YVES
> Cc: public-web-http-desc@...
> Subject: Re: Issues in WADL stylesheet when referencing faults or
> methods
>
> Could you provide sample input that triggers this?
>
> Thanks,
>
>
> On 22/11/2008, at 4:26 AM, SAINTILLAN YVES wrote:
>
>> Hello,
>>
>> I am using the WADL XSL stylesheet and noticed a couple of issues
>> when
>
>> referencing faults or methods in a WADL:
>>
>> - When making a reference (href) to a Fault, defined directly under
>> the application element, the fault is not correctly displayed in the
>> HTML output; in particular, the status of the fault (in the reference
>> or in the definition) does not appear.
>>
>> - Similarly, when making reference to a method, defined directly
>> under
>
>> the application element, the name of the method is not displayed in
>> the HTML documentation.
>>
>> So it seems the XSL stylesheet handles well references to
>> representations, but not faults or methods. Are you aware of these
>> issues ?
>>
>> Thanks and kind regards,
>> Yves
>>
>
>
> --
> Mark Nottingham http://www.mnot.net/
>

My Web Application

Resources
- http://api.search.yahoo.com/NewsSearchService/V1/
Representations
- A list of news items matching the query (application/xml - yn:ResultSet)
Faults
- Status Code 400 - application/xml (ya:Error)

Resources

Yahoo News Search Service

The Yahoo News Search service provides online searching of news stories from around the world.

Methods

GET

request query parameters

parameter	value	description
appid	string (required)	The application ID. See Application IDs for more information.
query	string (required)
type	string One of: `all` (default) `any` `phrase`	`all` (default) All query terms. `any` Any query terms. `phrase` Query terms as a phrase.
results	int Default: `10`
start	int Default: `1`
sort	string One of: `rank` (default) `date`
language	string
output	string One of: `xml` (default) `json` `php`	The format for the output. If json is requested, the results will be returned in JSON format. If php is requested, the results will be returned in Serialized PHP format.
callback	string	The name of the callback function to wrap around the JSON data. The following characters are allowed: A-Z a-z 0-9 . [] and _. If output=json has not been requested, this parameter has no effect. More information on the callback can be found in the Yahoo! Developer Network JSON Documentation.

available response representations:

A list of news items matching the query (application/xml - yn:ResultSet)

potential faults:

Status Code 400 - application/xml (ya:Error)

Representations

A list of news items matching the query (application/xml - yn:ResultSet)

XML Schema

Source: NewsSearchResponse.xsd

<xs:element name="ResultSet">
    <xs:complexType>
      <xs:sequence>
        <xs:element name="Result" type="ResultType" minOccurs="0" maxOccurs="50"/>
      </xs:sequence>
      <xs:attribute name="totalResultsAvailable" type="xs:integer"/>
      <xs:attribute name="totalResultsReturned" type="xs:integer"/>
      <xs:attribute name="firstResultPosition" type="xs:integer"/>
    </xs:complexType>
  </xs:element>

Faults

Status Code 400 - application/xml (ya:Error)

XML Schema

Source: NewsSearchError.xsd

<xs:element name="Error">
    <xs:complexType mixed="true">
      <xs:sequence>
        <xs:element name="Message"/>
      </xs:sequence>
    </xs:complexType>
  </xs:element>

YahooSearch.wadl (5K) Download Attachment

Re: Issues in WADL stylesheet when referencing faults or methods

2008-12-09T03:33:38Z

Fixed; some attributes weren't copied when expanding references. I may
have missed some more, and there's hopefully a more elegant way to do
it, but these problems should be gone, at least.

Cheers,

On 24/11/2008, at 10:13 PM, SAINTILLAN YVES wrote:

> Dear Mark,
>
> Sure: please find attached a modified version of WADL for Yahoo
> NewsSearch application, that allows to reproduce both issues. In the
> WADL, the 'GET' method and 'SearchError' fault elements are both
> defined
> as children of the application element.
>
> Included XSD files, and generated HTML output documentation are also
> attached.
>
> Thanks,
> Yves
>
> -----Original Message-----
> From: Mark Nottingham [mailto:mnot@...]
> Sent: samedi 22 novembre 2008 17:51
> To: SAINTILLAN YVES
> Cc: public-web-http-desc@...
> Subject: Re: Issues in WADL stylesheet when referencing faults or
> methods
>
> Could you provide sample input that triggers this?
>
> Thanks,
>
>
> On 22/11/2008, at 4:26 AM, SAINTILLAN YVES wrote:
>
>> Hello,
>>
>> I am using the WADL XSL stylesheet and noticed a couple of issues
>> when
>
>> referencing faults or methods in a WADL:
>>
>> - When making a reference (href) to a Fault, defined directly under
>> the application element, the fault is not correctly displayed in the
>> HTML output; in particular, the status of the fault (in the reference
>> or in the definition) does not appear.
>>
>> - Similarly, when making reference to a method, defined directly
>> under
>
>> the application element, the name of the method is not displayed in
>> the HTML documentation.
>>
>> So it seems the XSL stylesheet handles well references to
>> representations, but not faults or methods. Are you aware of these
>> issues ?
>>
>> Thanks and kind regards,
>> Yves
>>
>
>
> --
> Mark Nottingham http://www.mnot.net/
>

My Web Application

Resources
- http://api.search.yahoo.com/NewsSearchService/V1/newsSearch
Representations
- A list of news items matching the query (application/xml - yn:ResultSet)
Faults
- application/xml (ya:Error)

Resources

Yahoo News Search Service

The Yahoo News Search service provides online searching of news stories from around the world.

Methods

request query parameters

parameter	value	description
appid	string (required)	The application ID. See Application IDs for more information.
query	string (required)
type	string One of: `all` (default) `any` `phrase`	`all` (default) All query terms. `any` Any query terms. `phrase` Query terms as a phrase.
results	int Default: `10`
start	int Default: `1`
sort	string One of: `rank` (default) `date`
language	string
output	string One of: `xml` (default) `json` `php`	The format for the output. If json is requested, the results will be returned in JSON format. If php is requested, the results will be returned in Serialized PHP format.
callback	string	The name of the callback function to wrap around the JSON data. The following characters are allowed: A-Z a-z 0-9 . [] and _. If output=json has not been requested, this parameter has no effect. More information on the callback can be found in the Yahoo! Developer Network JSON Documentation.

available response representations:

A list of news items matching the query (application/xml - yn:ResultSet)

potential faults:

application/xml (ya:Error)

Representations

A list of news items matching the query (application/xml - yn:ResultSet)

XML Schema

Source: NewsSearchResponse.xsd

<xs:element name="ResultSet">
    <xs:complexType>
      <xs:sequence>
        <xs:element name="Result" type="ResultType" minOccurs="0" maxOccurs="50"/>
      </xs:sequence>
      <xs:attribute name="totalResultsAvailable" type="xs:integer"/>
      <xs:attribute name="totalResultsReturned" type="xs:integer"/>
      <xs:attribute name="firstResultPosition" type="xs:integer"/>
    </xs:complexType>
  </xs:element>

Faults

application/xml (ya:Error)

XML Schema

Source: NewsSearchError.xsd

<xs:element name="Error">
    <xs:complexType mixed="true">
      <xs:sequence>
        <xs:element name="Message"/>
      </xs:sequence>
    </xs:complexType>
  </xs:element>

--
Mark Nottingham http://www.mnot.net/

YahooSearch.wadl (6K) Download Attachment
NewsSearchError.xsd (748 bytes) Download Attachment
NewsSearchResponse.xsd (2K) Download Attachment

Help with the missing piece

2008-11-29T03:38:56Z

Hello,

After a lot of reading and a lot of experimenting and a lot of deep thought, I believe I grok the REST architecture fairly well. I understand that URIs identify resources (nouns) that HTTP methods (verbs) act upon. But I'm having a little trouble with representing resources.

The naive approach would be to represent resources by serializing them to XML/JSON/format-of-choice and be done, but that really doesn't feel RESTful to me. Vanilla XML is no better at representing state than vanilla HTML would be; they both require specific knowledge of the semantics of the representation to be able to make any sense of it. Machine consumability goes right out the window.

As far as I can tell, the "solution" to this problem is to associate data (via XML namespaces or RDF or DAML or whatever) with existing ontologies like Dublic Core, FOAF, DOAC, OWL, SKOS, RDFS, etc. Then the data will at least mean something to anything expecting to consume the same ontology, assuming that I'm not trying to shoehorn the data into an existing ontology just to make it fit somewhere (e.g., one service uses dc:title to represent a job title while another uses it to represent a book title, and now whatever association exists between them is going to be broken).

Am I understanding this all correctly? Is the best way to describe my data to pick and choose from a dozen different ontologies and then make up my own to fill in the missing pieces? It seems like that's what dbpedia.org has done. It feels like doing it this way really misses the point since services just end up defining their own data types. AWS has a concept of "movie" which is pretty much the same as the Netflix concept of "movie", but there's no correlation between them unless I as a developer step in and manually create the connection, which defeats the purpose of typing data at all.

What am I missing?

Thanks,

Erik

P.S. Really enjoyed the REST track at QCon. Thanks to all that presented.

RE: Issues in WADL stylesheet when referencing faults or methods

2008-11-24T03:13:38Z

Dear Mark,

Sure: please find attached a modified version of WADL for Yahoo
NewsSearch application, that allows to reproduce both issues. In the
WADL, the 'GET' method and 'SearchError' fault elements are both defined
as children of the application element.

Included XSD files, and generated HTML output documentation are also
attached.

Thanks,
Yves

-----Original Message-----
From: Mark Nottingham [mailto:mnot@...]
Sent: samedi 22 novembre 2008 17:51
To: SAINTILLAN YVES
Cc: public-web-http-desc@...
Subject: Re: Issues in WADL stylesheet when referencing faults or
methods

Could you provide sample input that triggers this?

Thanks,

On 22/11/2008, at 4:26 AM, SAINTILLAN YVES wrote:

> Hello,
>
> I am using the WADL XSL stylesheet and noticed a couple of issues when

> referencing faults or methods in a WADL:
>
> - When making a reference (href) to a Fault, defined directly under
> the application element, the fault is not correctly displayed in the
> HTML output; in particular, the status of the fault (in the reference
> or in the definition) does not appear.
>
> - Similarly, when making reference to a method, defined directly under

> the application element, the name of the method is not displayed in
> the HTML documentation.
>
> So it seems the XSL stylesheet handles well references to
> representations, but not faults or methods. Are you aware of these
> issues ?
>
> Thanks and kind regards,
> Yves
>

--
Mark Nottingham http://www.mnot.net/

My Web Application

My Web Application

Resources
- http://api.search.yahoo.com/NewsSearchService/V1/newsSearch
Representations
- A list of news items matching the query (application/xml - yn:ResultSet)
Faults
- application/xml (ya:Error)

Resources

Yahoo News Search Service

The Yahoo News Search service provides online searching of news stories from around the world.

Methods

request query parameters

parameter	value	description
appid	string (required)	The application ID. See Application IDs for more information.
query	string (required)
type	string One of: `all` (default) `any` `phrase`	`all` (default) All query terms. `any` Any query terms. `phrase` Query terms as a phrase.
results	int Default: `10`
start	int Default: `1`
sort	string One of: `rank` (default) `date`
language	string
output	string One of: `xml` (default) `json` `php`	The format for the output. If json is requested, the results will be returned in JSON format. If php is requested, the results will be returned in Serialized PHP format.
callback	string	The name of the callback function to wrap around the JSON data. The following characters are allowed: A-Z a-z 0-9 . [] and _. If output=json has not been requested, this parameter has no effect. More information on the callback can be found in the Yahoo! Developer Network JSON Documentation.

available response representations:

A list of news items matching the query (application/xml - yn:ResultSet)

potential faults:

application/xml (ya:Error)

Representations

A list of news items matching the query (application/xml - yn:ResultSet)

XML Schema

Source: NewsSearchResponse.xsd

<xs:element name="ResultSet">
    <xs:complexType>
      <xs:sequence>
        <xs:element name="Result" type="ResultType" minOccurs="0" maxOccurs="50"/>
      </xs:sequence>
      <xs:attribute name="totalResultsAvailable" type="xs:integer"/>
      <xs:attribute name="totalResultsReturned" type="xs:integer"/>
      <xs:attribute name="firstResultPosition" type="xs:integer"/>
    </xs:complexType>
  </xs:element>

Faults

application/xml (ya:Error)

XML Schema

Source: NewsSearchError.xsd

<xs:element name="Error">
    <xs:complexType mixed="true">
      <xs:sequence>
        <xs:element name="Message"/>
      </xs:sequence>
    </xs:complexType>
  </xs:element>

YahooSearch.wadl (5K) Download Attachment
NewsSearchError.xsd (998 bytes) Download Attachment
NewsSearchResponse.xsd (2K) Download Attachment

Re: Issues in WADL stylesheet when referencing faults or methods

2008-11-22T08:51:17Z

Could you provide sample input that triggers this?

Thanks,

On 22/11/2008, at 4:26 AM, SAINTILLAN YVES wrote:

> Hello,
>
> I am using the WADL XSL stylesheet and noticed a couple of issues
> when referencing faults or methods in a WADL:
>
> - When making a reference (href) to a Fault, defined directly under
> the application element, the fault is not correctly displayed in the
> HTML output; in particular, the status of the fault (in the
> reference or in the definition) does not appear.
>
> - Similarly, when making reference to a method, defined directly
> under the application element, the name of the method is not
> displayed in the HTML documentation.
>
> So it seems the XSL stylesheet handles well references to
> representations, but not faults or methods. Are you aware of these
> issues ?
>
> Thanks and kind regards,
> Yves
>

--
Mark Nottingham http://www.mnot.net/

Issues in WADL stylesheet when referencing faults or methods

2008-11-21T07:26:39Z

Issues in WADL stylesheet when referencing faults or methods

Hello,

I am using the WADL XSL stylesheet and noticed a couple of issues when referencing faults or methods in a WADL:

- When making a reference (href) to a Fault, defined directly under the application element, the fault is not correctly displayed in the HTML output; in particular, the status of the fault (in the reference or in the definition) does not appear.

- Similarly, when making reference to a method, defined directly under the application element, the name of the method is not displayed in the HTML documentation.

So it seems the XSL stylesheet handles well references to representations, but not faults or methods. Are you aware of these issues ?

Thanks and kind regards,
Yves

RE: WADL documentation stylesheet fails with Amazon item search example in WADL spec

2008-10-30T14:47:28Z

Marc/Mark,

Thanks for the quick response! The namespace was indeed the problem.
When I changed it to "10", then I was able to use Oxygen to create the
HTML documentation. Unfortunately, XMLSpy still fails, but the error it
generates (on line 173, "Error in function document, Could not find
external entity") is due to not finding the Amazon schema. Thanks again
for your help!

-- Matson

-----Original Message-----
From: Marc.Hadley@... [mailto:Marc.Hadley@...]
Sent: Thursday, October 30, 2008 5:21 AM
To: Mark Nottingham
Cc: Matson Wade; public-web-http-desc@...
Subject: Re: WADL documentation stylesheet fails with Amazon item search
example in WADL spec

My bad, it looks like I forgot to update the namespace declarations in
the examples in appendix A.

Marc.

On Oct 30, 2008, at 6:09 AM, Mark Nottingham wrote:

>
>
> On 30/10/2008, at 12:24 PM, Matson Wade wrote:
>
>> I'm considering using WADL, but only if I can generate reasonable
>> documentation. So as a test of the WADL-to-HTML documentation
>> stylesheet, I took the "Amazon Item Search" example from the
>> appendix of the WADL spec and tried to transform it using
>> "wadl_documentation.xls".
>
> What version of the stylesheet are you using? The Amazon example in
> the spec is uses the 07 namespace, but it appears to be using the 10
> syntax; Marc?
>
>
>> The transformation failed with both XMLSpy and Oxygen. The error I
>> received in XMLSpy is on line 169 of the XSLT: "Function not in
>> namespace, Error in XPath expression, Function not in namespace".
>
> What XSLT processor did you use? Oxygen, at least, can use a
> variety. The instructions clearly say that EXSLT support is required.
>
> If I change the namespace to 10 and run it with saxon against the 10
> stylesheet (the 07 stylesheet isn't supported any more), I get;
>
> ~> saxon amazon.xml

http://www.mnot.net/webdesc/wadl_tation-2006-10.xsl
> > amazon.html
> Warning: at xsl:stylesheet on line 40 of
http://www.mnot.net/webdesc/wadl_documentation-2006-10.xsl
> :
> Running an XSLT 1.0 stylesheet with an XSLT 2.0 processor
> Error on line 173 of
http://www.mnot.net/webdesc/wadl_documentation-2006-10.xsl

> :
> FODC0005: java.io.FileNotFoundException: AWSECommerceService.xsd
> (No such file or directory)
>
> The warning about XSLT 1.0 can be ignored; the error is because I
> haven't bothered to download Amazon's schema. The HTML it produces
> looks right, taking this into account.
>
>
>> Has this stylesheet been used at all beyond the Yahoo example?
>
> I'm aware of a fair number of people who use it to document
> services, both inside my company and outside.
>
>> Is it possible to fix the stylesheet so that it works with the
>> examples from the spec?
>
>
> I think it's more a matter of fixing the example, at least in this
> case.
>
>
> --
> Mark Nottingham mnot@...
>
>
>

---
Marc Hadley <marc.hadley at sun.com>
CTO Office, Sun Microsystems.

Re: WADL documentation stylesheet fails with Amazon item search example in WADL spec

2008-10-30T05:21:07Z

My bad, it looks like I forgot to update the namespace declarations in
the examples in appendix A.

Marc.

On Oct 30, 2008, at 6:09 AM, Mark Nottingham wrote:

>
>
> On 30/10/2008, at 12:24 PM, Matson Wade wrote:
>
>> I’m considering using WADL, but only if I can generate reasonable
>> documentation. So as a test of the WADL-to-HTML documentation
>> stylesheet, I took the “Amazon Item Search” example from the
>> appendix of the WADL spec and tried to transform it using
>> “wadl_documentation.xls”.
>
> What version of the stylesheet are you using? The Amazon example in
> the spec is uses the 07 namespace, but it appears to be using the 10
> syntax; Marc?
>
>
>> The transformation failed with both XMLSpy and Oxygen. The error I
>> received in XMLSpy is on line 169 of the XSLT: “Function not in
>> namespace, Error in XPath expression, Function not in namespace”.
>
> What XSLT processor did you use? Oxygen, at least, can use a
> variety. The instructions clearly say that EXSLT support is required.
>
> If I change the namespace to 10 and run it with saxon against the 10
> stylesheet (the 07 stylesheet isn't supported any more), I get;
>
> ~> saxon amazon.xml http://www.mnot.net/webdesc/wadl_tation-2006-10.xsl
> > amazon.html
> Warning: at xsl:stylesheet on line 40 of http://www.mnot.net/webdesc/wadl_documentation-2006-10.xsl
> :
> Running an XSLT 1.0 stylesheet with an XSLT 2.0 processor
> Error on line 173 of http://www.mnot.net/webdesc/wadl_documentation-2006-10.xsl
> :
> FODC0005: java.io.FileNotFoundException: AWSECommerceService.xsd
> (No such file or directory)
>
> The warning about XSLT 1.0 can be ignored; the error is because I
> haven't bothered to download Amazon's schema. The HTML it produces
> looks right, taking this into account.
>
>
>> Has this stylesheet been used at all beyond the Yahoo example?
>
> I'm aware of a fair number of people who use it to document
> services, both inside my company and outside.
>
>> Is it possible to fix the stylesheet so that it works with the
>> examples from the spec?
>
>
> I think it's more a matter of fixing the example, at least in this
> case.
>
>
> --
> Mark Nottingham mnot@...
>
>
>

---
Marc Hadley <marc.hadley at sun.com>
CTO Office, Sun Microsystems.

Re: WADL documentation stylesheet fails with Amazon item search example in WADL spec

2008-10-30T03:09:14Z

On 30/10/2008, at 12:24 PM, Matson Wade wrote:

> I’m considering using WADL, but only if I can generate reasonable
> documentation. So as a test of the WADL-to-HTML documentation
> stylesheet, I took the “Amazon Item Search” example from the
> appendix of the WADL spec and tried to transform it using
> “wadl_documentation.xls”.

What version of the stylesheet are you using? The Amazon example in
the spec is uses the 07 namespace, but it appears to be using the 10
syntax; Marc?

> The transformation failed with both XMLSpy and Oxygen. The error I
> received in XMLSpy is on line 169 of the XSLT: “Function not in
> namespace, Error in XPath expression, Function not in namespace”.

What XSLT processor did you use? Oxygen, at least, can use a variety.
The instructions clearly say that EXSLT support is required.

If I change the namespace to 10 and run it with saxon against the 10
stylesheet (the 07 stylesheet isn't supported any more), I get;

~> saxon amazon.xml http://www.mnot.net/webdesc/
wadl_tation-2006-10.xsl > amazon.html
Warning: at xsl:stylesheet on line 40 of http://www.mnot.net/webdesc/wadl_documentation-2006-10.xsl
:
Running an XSLT 1.0 stylesheet with an XSLT 2.0 processor
Error on line 173 of http://www.mnot.net/webdesc/wadl_documentation-2006-10.xsl
:
FODC0005: java.io.FileNotFoundException: AWSECommerceService.xsd
(No such file or directory)

The warning about XSLT 1.0 can be ignored; the error is because I
haven't bothered to download Amazon's schema. The HTML it produces
looks right, taking this into account.

> Has this stylesheet been used at all beyond the Yahoo example?

I'm aware of a fair number of people who use it to document services,
both inside my company and outside.

> Is it possible to fix the stylesheet so that it works with the
> examples from the spec?

I think it's more a matter of fixing the example, at least in this case.

--
Mark Nottingham mnot@...

WADL documentation stylesheet fails with Amazon item search example in WADL spec

2008-10-29T18:24:27Z

I’m considering using WADL, but only if I can generate reasonable documentation. So as a test of the WADL-to-HTML documentation stylesheet, I took the “Amazon Item Search” example from the appendix of the WADL spec and tried to transform it using “wadl_documentation.xls”. The transformation failed with both XMLSpy and Oxygen. The error I received in XMLSpy is on line 169 of the XSLT: “Function not in namespace, Error in XPath expression, Function not in namespace”. Has this stylesheet been used at all beyond the Yahoo example? Is it possible to fix the stylesheet so that it works with the examples from the spec?

-- Matson

Re: WADL - resource path attribute and "WADL to HTML documentation stylesheet".

2008-08-19T07:02:13Z

The algorithm in section 2.5.1 of the spec appends a '/' character to
the parent resource/resources URI if it doesn't end with one and then
appends the value of the path. It doesn't cope with a path that
contains a leading '/'. On the one hand this seems reasonable since a
leading '/' implies an absolute path rather than a relative one but
given the semantics of the path attribute a more accommodating
algorithm might be in order. Is there a reason you want to put in a
leading '/' in path values ?

Marc.

On Aug 19, 2008, at 12:14 AM, Mark Nottingham wrote:

>
> I'm happy to update it if that's the intent; frankly I haven't
> thought about WADL for a few months; Mark, what's your take?
> On 04/07/2008, at 7:20 PM, Thierry Boileau wrote:
>
>>
>> Hello all,
>>
>> I've a simple question about the "path" attribute. As written in
>> the specification, this attribute provides a relative URI template,
>> wich as far as I understand can either starts with a "/" character
>> or not. Having said that, I notice that the "WADL to HTML
>> documentation stylesheet" maintained by Mark Nottingham
>> systematically appends a leading "/" character to the resource path
>> atribute. And at the same time, it takes care of the "base"
>> attribute of the "Resources" item in order to remove the ending "/"
>> character.
>> Do I miss something? Is it possible to update the stylesheet in
>> order to appends the leading "/" character of the "path" attribute
>> only when required?
>>
>> Best regards,
>> Thierry Boileau
>>
>>
>
>
> --
> Mark Nottingham http://www.mnot.net/
>
>

---
Marc Hadley <marc.hadley at sun.com>
CTO Office, Sun Microsystems.

Re: WADL - resource path attribute and "WADL to HTML documentation stylesheet".

2008-08-18T21:14:10Z

I'm happy to update it if that's the intent; frankly I haven't thought
about WADL for a few months; Mark, what's your take?
On 04/07/2008, at 7:20 PM, Thierry Boileau wrote:

>
> Hello all,
>
> I've a simple question about the "path" attribute. As written in the
> specification, this attribute provides a relative URI template, wich
> as far as I understand can either starts with a "/" character or
> not. Having said that, I notice that the "WADL to HTML documentation
> stylesheet" maintained by Mark Nottingham systematically appends a
> leading "/" character to the resource path atribute. And at the same
> time, it takes care of the "base" attribute of the "Resources" item
> in order to remove the ending "/" character.
> Do I miss something? Is it possible to update the stylesheet in
> order to appends the leading "/" character of the "path" attribute
> only when required?
>
> Best regards,
> Thierry Boileau
>
>

--
Mark Nottingham http://www.mnot.net/

WADL - resource path attribute and "WADL to HTML documentation stylesheet".

2008-07-04T02:20:43Z

Hello all,

I've a simple question about the "path" attribute. As written in the
specification, this attribute provides a relative URI template, wich as
far as I understand can either starts with a "/" character or not.
Having said that, I notice that the "WADL to HTML documentation
stylesheet" maintained by Mark Nottingham systematically appends a
leading "/" character to the resource path atribute. And at the same
time, it takes care of the "base" attribute of the "Resources" item in
order to remove the ending "/" character.
Do I miss something? Is it possible to update the stylesheet in order to
appends the leading "/" character of the "path" attribute only when
required?

Best regards,
Thierry Boileau

Re: Google REST Describe first working Beta released

2008-04-12T09:18:15Z

GOOGLE

tHANKS

Dress up Games
- GIRLS GAMES
- Barbie Games
- Barbie

Re: snooze

2008-04-12T09:16:33Z

NOOR2 wrote:

tHANKS

Dress up Games
- GIRLS GAMES
- Barbie Games
- Barbie

Re: snooze

2008-04-12T09:14:55Z

tHANKS

Dress up Games
- GIRLS GAMES
- Barbie Games
- Barbie

Re: WADL documentation stylesheet updated

2007-12-26T08:39:47Z

Hi,
I can second that - but I heard, that they are working on it already. Well
lets see what 2008 brings.

Regards

Manuel Koch :: Webmaster http://www.cotono.com

Re: WADL documentation stylesheet updated

2007-12-04T11:00:34Z

Hey,

Unfortunately, FF's XSLT support is pretty primitive; they don't even
support the core spec very well, as I understand it. IIRC, this
should be fixed in the next major rev...

On 04/12/2007, at 8:37 AM, Marc Hadley wrote:

>
> Hi Mark,
>
> Any plan to get this to work with Firefox, currently I get an error
> due to call to an undefined extension function. It works great in
> Safari.
>
> Thanks,
> Marc.
>
> On Nov 1, 2007, at 8:48 PM, Mark Nottingham wrote:
>>
>> I've updated the WADL documentation stylesheet <http://
>> www.mnot.net/webdesc/>, primarily to;
>> * Fix a bug with finding and displaying XML Schema
>> * Make it compatible with xsltproc (and hopefully most other
>> XSLT1.0 processors that understand EXSLT)
>> * Generate valid XHTML
>>
>> Thanks to Dave Crawford (Yahoo! Media Group), Nathan Cantelmo
>> (Yahoo! Research Berkeley) and Gopalakrishnan S A (Yahoo!
>> Bangalore) for their bug reports, patches and patience.
>>
>> Cheers,
>>
>> --
>> Mark Nottingham mnot@...
>>
>>
>>
>
> ---
> Marc Hadley <marc.hadley at sun.com>
> CTO Office, Sun Microsystems.
>
>
>

--
Mark Nottingham http://www.mnot.net/

Re: WADL documentation stylesheet updated

2007-12-04T08:37:37Z

Hi Mark,

Any plan to get this to work with Firefox, currently I get an error
due to call to an undefined extension function. It works great in
Safari.

Thanks,
Marc.

On Nov 1, 2007, at 8:48 PM, Mark Nottingham wrote:

>
> I've updated the WADL documentation stylesheet <http://www.mnot.net/webdesc/
> >, primarily to;
> * Fix a bug with finding and displaying XML Schema
> * Make it compatible with xsltproc (and hopefully most other
> XSLT1.0 processors that understand EXSLT)
> * Generate valid XHTML
>
> Thanks to Dave Crawford (Yahoo! Media Group), Nathan Cantelmo
> (Yahoo! Research Berkeley) and Gopalakrishnan S A (Yahoo! Bangalore)
> for their bug reports, patches and patience.
>
> Cheers,
>
> --
> Mark Nottingham mnot@...
>
>
>

---
Marc Hadley <marc.hadley at sun.com>
CTO Office, Sun Microsystems.

WADL documentation stylesheet updated

2007-11-01T18:48:53Z

I've updated the WADL documentation stylesheet <http://www.mnot.net/
webdesc/>, primarily to;
* Fix a bug with finding and displaying XML Schema
* Make it compatible with xsltproc (and hopefully most other
XSLT1.0 processors that understand EXSLT)
* Generate valid XHTML

Thanks to Dave Crawford (Yahoo! Media Group), Nathan Cantelmo (Yahoo!
Research Berkeley) and Gopalakrishnan S A (Yahoo! Bangalore) for
their bug reports, patches and patience.

Cheers,

--
Mark Nottingham mnot@...

snooze

2007-09-24T15:13:40Z

Introduction

2007-09-08T07:30:31Z

Hi all,

I just subscribed to this list and wanted to introduce myself before posting. I'm Rob and coding and design is my hobby. So do nothing fancy but think I can learn a lot from all posts coming by in this W3C mailinglist.

I have a portal called Indelv.com (http://www.indelv.com/) and post some news on standards just to keep track of what is happening in the field. I know the site is not fully standardized, but I am working on it when I have free time.

So if you have some cool news or found a nice article, send me a note, I will repost some of it on Indelv, so I will not loose track of it. Hope I see nice tips passing by on this mailing list and in the future I might be a bit better and can even assist with answers.

Kind regards and have a good weekend

Rob

Marketing Online SEO and W3

2007-08-01T06:11:40Z

Is there any certification for Marketing Online SEO and W3

Marketing Online SEO

http://www.lososeans.info

Hotmail to go? Get your Hotmail, news, sports and much more! Check out the New MSN Mobile

Collaborative WADL directory

2007-08-01T02:50:19Z

I just learned about WADL and am very intrigued by it. We're running
an online service repository [1] which allows programmers to play with
services online [2]. Part of the information required to generate WADL
descriptions is already available. The idea is to generate these
partial descriptions and make them editable by users via the site.

I realize the global UDDI repositories were a big failure but on the
other hand it'd be nice for the adoption of WADL to have publicly
available WADL samples.

Looking forward to your feedback!

Mike

[1] http://www.webrpc.com
[2] http://www.webrpc.com/selectService.jsp?name=Geo%20Elevation