OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

xri message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [xri] <Title>


If someone needs xml:id they can just use it. I dont want us to  
require it and as an optional feature, it is already possible. I also  
think we are a long way before any meaningful need for CRUD apis.

EHL

On Sep 11, 2009, at 14:21, "Will Norris" <will@willnorris.com> wrote:

> since this discussion is generally about management of XRDs, it's
> worth noting that Joseph asked me some months ago about adding an
> xml:id to <Link>.  This is actually more useful when there is some API
> that would allow a service to modify entries in an XRD document,
> needing to refer to a specific Link by ID.  While that kind of API is
> still some ways off, and a <Title> element actually has application in
> the nearer term, I think it begs the question of how much management
> related elements would should be adding to the core spec.  While
> having the title embedded in the document directly is certainly
> convenient, it is by no means necessary (implementations could store
> it elsewhere).  Nor does it aid in any way the primary goal of XRD --
> to create a *machine-readable* format for describing resources.
>
> -will
>
> On Sep 11, 2009, at 7:32 AM, Eran Hammer-Lahav wrote:
>
>> Not sure what you mean but the point is to offer a general purpose
>> element that will work across rel types.
>>
>> EHL
>>
>> On Sep 11, 2009, at 2:07, "Nat Sakimura" <n-sakimura@nri.co.jp>  
>> wrote:
>>
>>> I had an impression that maintainer of <rel> uri will maintain the
>>> title
>>> etc. metadata for the uri so that one can resolve it for various
>>> language for its description somehow that UI can be built on it. If
>>> that
>>> is true, we should not need <Title>.
>>>
>>> =nat
>>>
>>> Joseph Anthony Pasquale Holsten wrote:
>>>> Maybe just pointing people to dublin core would be sufficient?
>>>> People
>>>> seem to use it enough with HTML.
>>>>
>>>> Also, has anyone noticed that XRD is becoming surprisingly close
>>>> to a
>>>> collection of XLink simple elements that's actually useful? The  
>>>> only
>>>> other stuff they have is xlink:show, for how to render the link,
>>>> notably useful for embedding; and xlink:actuate, for what sort of
>>>> event activates the link. These would only be useful for embedding
>>>> XRD
>>>> into rendered documents like HTML or ODF, say in a profile page or
>>>> resume. Totally not today's use cases, but maybe XRD 2.
>>>>
>>>> Also, +1 to xml:lang
>>>> ---
>>>> http://josephholsten.com
>>>>
>>>> On Sep 10, 2009, at 9:09 PM, Eran Hammer-Lahav wrote:
>>>>
>>>>> All the other link structures (header, element) provide a link-
>>>>> level
>>>>> title with language support. Should we add something like that to
>>>>> stay consistent? This is extremely useful in building UI for
>>>>> editing
>>>>> and presenting XRD documents to users, especially in the social
>>>>> space
>>>>> which is an important target for us. This came up in pretty much
>>>>> every place XRDS-Simple was discussed.
>>>>>
>>>>> It will look something like this:
>>>>>
>>>>> <Title lang='en-us'>A very special link</Title>
>>>>>
>>>>> Cardinality is 0 to any. 'lang' is optional and does not have a
>>>>> default value is omitted. It will use a standard languages code
>>>>> spec
>>>>> (whatever is the prevailing reference today).
>>>>>
>>>>> EHL
>>>>>
>>>>> ---
>>>>> ------------------------------------------------------------------
>>>>> To unsubscribe from this mail list, you must leave the OASIS TC
>>>>> that
>>>>> generates this mail.  Follow this link to all your TCs in OASIS  
>>>>> at:
>>>>> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>>>>
>>>>
>>>> --- 
>>>> ------------------------------------------------------------------
>>>> To unsubscribe from this mail list, you must leave the OASIS TC  
>>>> that
>>>> generates this mail.  Follow this link to all your TCs in OASIS at:
>>>> https://www.oasis-open.org/apps/org/workgroup/portal/
>>>> my_workgroups.php
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this mail list, you must leave the OASIS TC that
>> generates this mail.  Follow this link to all your TCs in OASIS at:
>> https://www.oasis-open.org/apps/org/workgroup/portal/ 
>> my_workgroups.php
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]