W3C home > Mailing lists > Public > public-xmlhypermedia@w3.org > August 2012

RE: use cases

From: David Lee <David.Lee@marklogic.com>
Date: Mon, 20 Aug 2012 12:17:09 -0700
To: "Rushforth, Peter" <Peter.Rushforth@NRCan-RNCan.gc.ca>, "public-xmlhypermedia@w3.org" <public-xmlhypermedia@w3.org>
Message-ID: <EB42045A1F00224E93B82E949EC6675E16B04977C6@EXCHG-BE.marklogic.com>
Stepping back a few thousand feet.
I admit I am getting more, rather then less, confused about HyperMedia.
Are there any example apps or "Existing Works" which demonstrate the usefulness, feasibility etc of HyperMedia as proposed in this group ?
I am trying to get a handle on exactly what it is and still coming up short.
e.g. some questions.

Does it require HTTP ? 
What kind of application would be written using it ?
Does it require a different content-type ? 
Is it related to or compete with something like XForms ?	


-----------------------------------------------------------------------------
David Lee
Lead Engineer
MarkLogic Corporation
dlee@marklogic.com
Phone: +1 812-482-5224
Cell:  +1 812-630-7622
www.marklogic.com

This e-mail and any accompanying attachments are confidential. The information is intended solely for the use of the individual to whom it is addressed. Any review, disclosure, copying, distribution, or use of this e-mail communication by others is strictly prohibited. If you are not the intended recipient, please notify us immediately by returning this message to the sender and delete all copies. Thank you for your cooperation.

-----Original Message-----
From: Rushforth, Peter [mailto:Peter.Rushforth@NRCan-RNCan.gc.ca] 
Sent: Monday, August 20, 2012 1:48 PM
To: public-xmlhypermedia@w3.org
Cc: David Lee
Subject: RE: use cases


> >I would go first with using namespaces like most other 
> add-in vocabularies with XML do.
> 
> I agree that use case needs to be separately addressed, but 
> the no-namespace use case is important and so is called out 
> by a separately layered-on use case.  Maybe the layering is 
> not clear enough?  ie. the auto-namespaces use case could be 
> achieved with a regular namespace-based set of hypermedia 
> vowels, but to unlock the full benefit of hypermedia for the 
> general use case of xml, they would have to be in the xml namespace.

OK, I have completely separated the use case drawing on automatic namespaces
only to use an http://example.com -based namespace.

http://www.w3.org/community/xmlhypermedia/wiki/Distributed_extensibility_/_automatic_namespaces

I will work on the NeoXML use case example to clarify it a bit more.  If anyone
has any comments or issues, let me know.  Hopefully, it will reflect what this
community thinks.

Also, if anyone has any other use cases, especially which highlight the importance of any one or more
of the vowels or combination thereof, please bring it up on the list and we can potentially capture on the wiki.

Particular outliers right now are @hreflang, @method, @tref.

WRT @rel, I am thinking of that Achilles Heel of XML, the size of the document model post-parsing, as a use case justification for @rel="next".  What does the group think?

Cheers,
Peter
Received on Monday, 20 August 2012 19:17:36 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 20 August 2012 19:17:37 GMT