RE: [xml-dev] xml:href, xml:rel and xml:type

["Toby Considine" <Toby.Considine@gmail.com>]

And then there is the issue of declaring special purpose XML lexicons. Just
as I need a mime type for traditional references, and one needs an
application type for, say, the "mailto" type link, there should, of ging
down this path, be a place to create/register additional
application-namespace types on the references.

In my recent work, I have wrestled with classes of calendar/schedule feeds,
and how links to them should be represented. If these are guides to service
end points, there should be some way to distinguish and select between a
list of them. The idea of a "mini-wsdl" for an array of xlinks w/I a larger
xml document, though, threatens to be like a monkfish, i.e. a relatively
small creature able to swallow a large goose. The monkfish is hideous.
After swallowing it has to lie on the bottom for a week or month to digest. 

tc


"If something is not worth doing, it`s not worth doing well" - Peter Drucker

Toby Considine
TC9, Inc
TC Chair: oBIX & WS-Calendar
TC Editor: EMIX, EnergyInterop
U.S. National Inst. of Standards and Tech. Smart Grid Architecture Committee

  
Email: Toby.Considine@gmail.com
Phone: (919)619-2104
http://www.tcnine.com/
blog: www.NewDaedalus.com



-----Original Message-----
From: Rushforth, Peter [mailto:Peter.Rushforth@NRCan-RNCan.gc.ca] 
Sent: Friday, April 13, 2012 9:18 AM
To: David Carlisle
Cc: xml-dev@lists.xml.org
Subject: RE: [xml-dev] xml:href, xml:rel and xml:type

> From: David Carlisle [mailto:davidc@nag.co.uk]
> Subject: Re: [xml-dev] xml:href, xml:rel and xml:type
> 
> On 13/04/2012 13:36, Rushforth, Peter wrote:
> > Hi there,
> >
> > @xml:href
> 
> As far as I understand your suggestion, having built in link semantics 
> was part of the original 3-part plan for XML (along with styling) but 
> that's xlink:href rather than xml:href. I can't see that adding 
> another standardised href attribute in addition to xlink's would be 
> that popular (especially given that xlink isn't exactly the most 
> successful part of xml)

XLink has a lot
of attributes the designer has to consider (its complicated), but none of
them really seem to support the "Web" IME.  I'm not thinking so much about
link semantics as I am about practical simple application of web
infrastructure in XML, along the lines of "what's the simplest thing that
could possibly work?".

For example, in scanning
http://www.w3.org/TR/2010/REC-xlink11-20100506/#linking-elements
I don't see anything about the media type of the resource which is linked
to, so there's no advertisement to the client what can be negotiated without
actually trying a link.

Also, I suppose you have to declare the xlink namespace in order to use
xlinks.  Something I was trying to avoid by going to the xml:
namespace.

But, you're correct, adding yet one more "standard" might not solve
anything.  Then again, it might catch on.

Cheers,
Peter
_______________________________________________________________________

XML-DEV is a publicly archived, unmoderated list hosted by OASIS to support
XML implementation and development. To minimize spam in the archives, you
must subscribe before posting.

[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
subscribe: xml-dev-subscribe@lists.xml.org List archive:
http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php