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

 


Help: OASIS Mailing Lists Help | MarkMail Help

office-metadata message

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


Subject: Re: [office-metadata] Agreement on annotating content with RDF attributes



On Feb 9, 2007, at 2:57 PM, Svante Schubert wrote:

>> I want to stop right here and ask us to clarify this use case. What 
>> *exactly* is a user wanting to do here? Please explain in the 
>> language of a user; not an implementor.
> The user got from a different RDF application his VCard XML written in 
> RDF/XML document.
> As the user wants to sent VCard RDF data to some server, he decided to 
> use XForms technology ...

All of this I understand, and that's fine.

> ... to attach his VCard Data to the content the String "Schuster" in 
> our case. ;-)

This part is unclear to me. Why does the user need to "attach" the data 
to the string?

This is a serious question. If all we're talking about is editing via 
XForms, then that's fine, but that's different than the user just 
wanting to reference a patient, say, and for it to display a certain 
way.

To me the first one is outside this SCs scope. As I said before, great 
to see you want to use XForms for editing of this stuff, but there are 
many ways to do this. (Likely the best way is to use a domain-specific 
XML language, and convert it to RDF/XML using XSLT if you need to).

> But if you dislike XForms, just think of a paragraph, where he wrote 
> this string into.

Just to be clear, I have nothing against XForms. I just have something 
against *requiring* it to implement metadata support.

Bruce



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