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: Elias' demo about an ODF calc document using metadata


Hi,

Last conf-call Elias showed us a demo of a calc document using metadata:
http://torrez.us/archives//2006/12/13/salsa/
In the demo the metadata was representing the salary of the US baseball 
teams of several cities.

Let us assume this demo is a real world example.
Most likely the data had existed before the calc document was written.
It might be reused/imported into the ODF document as a set or a single 
RDF XML files, created from database representations.

A RDF XML file might look like this:

<?xml version="1.0"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#";
    xmlns:dc="http://purl.org/dc/elements/1.1/";
    xmlns:ex="http://example.org/stuff/1.0/";>

  <rdf:Description
rdf:about="http://www.us-super-sports.com/teams-making-lot-of-money";
      dc:title="The US Baseball">

    <ex:Team rdf:about="ex:sport-team">
      <ex:name>Yankees</ex:name>
      <ex:salary>200000000</ex:salary>
      <ex:city>New York</ex:city>
      <ex:state>NY</ex:state>
    </ex:Team>

    <ex:Team rdf:about="ex:sport-team">
      <ex:name>Giants</ex:name>
      <ex:salary>90056419</ex:salary>
      <ex:city>San Francisco</ex:city>
      <ex:state>CA</ex:state>
    </ex:Team>

    <ex:Team rdf:about="ex:sport-team">
      <ex:name>Red Sox</ex:name>
      <ex:salary>Boston</ex:salary>
      <ex:city>121245900</ex:city>
      <ex:state>MA</ex:state>
    </ex:Team>

    <!-- Many more.... -->
  </rdf:Description>
</rdf:RDF>

Going on with this scenario, the user would now like to edit the RDF XML
literals in a calc document.

Most likely the user does not want to add metadata manually to each cell 
of the whole table, but wants to do it for the first row and let it 
repeat afterwards. By this he might even add rows, which are 
automatically related to metadata.
Possibly it is sufficient to save only this 'iteration pattern'?

Does this scenario sounds familiar to someone?
Although the repetition feature is yet not implemented this scenario is 
close related to a XForms scenario.

Also an upcoming feature of XForms are events. For example, I change the 
  content of a form (cell) and the data is being changed / an event is 
being triggered (by this a different spreadsheeet might be updated as
shown in the document).

Please take this example so far as a thought-provoking impulse..

Svante


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