[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Rough notes (I won't call them minutes just yet)
Greetings! The rough notes I took this morning are attached. Comments or suggestions are very welcome! Unlike the US Congress, we really can't add stuff that was not said, ;-), but if you think of something we need to add as being in agreement or a remaining issue, post a note to the list and we will get it mentioned next week. Hope everyone is having a great week! Patrick -- Patrick Durusau Patrick@Durusau.net Chair, V1 - Text Processing: Office and Publishing Systems Interface Co-Editor, ISO 13250, Topic Maps -- Reference Model Member, Text Encoding Initiative Board of Directors, 2003-2005 Topic Maps: Human, not artificial, intelligence at work!
Metadata SC meeting - 31 January 2007 Roll Call: *Bernd Bruce *Florian Gary *Patrick *Rob *Svante Svante has volunteered to do Brend's examples in N3 syntax. Passed unanimously selected. Understanding to Date: Using the RDF Model Storing RDF/XML in a file package May have multiple metadata files Registering such files with the 'application/rdf+xml' mediatype in the manifest In the metadata files: 1. properties should be encoded as elements 2. properties should generally be wrapped in a single resource node Use of metadata attributes in content Elements proposed to have metadata attributes: tables images equations fields paragraphs spans Question: Is this a complete list? Do we need to include table:table-cell for example? Open Questions: 1. object literals in content (may be split) 2. object URIs in content, where subject-object relations may be: i. local-global (document to something else; citations fit this) ii. global-global (talking about other stuff; John's use case) 3. Use of both path and global IRI in a manifest file 4. xml:id required? 5. Preservation of all metadata? Means content not understood must be preserved. 6. How to handle metadata in file plus metadata in separate file? If we want applications to honor the original storage of the metadata? (Florian) Need to say that applications must support both ways. 7. Bernd: Structured content, what about table content? Span would not work between rows. Svante: can use RDFa or XForms approach. Need metadata on row, column, and sets of rows and columns. 8. Bernd: To enable storage of files by document characteristics and retrieval by the same means rather than tree directory structures. An add-on value for ODF metadata. Perhaps a vocabulary that could be understood by all applications. Makes the document self-characterizing. 9. Svante: Patient medical record example - RDF statement about the doctor - someone wants all the documents where this doctor is taking care of this patient - vocabulary dependent - Search RDF only. 10. How do we cope with changes in content that have an impact on the validity of the associated metadata? In the manifest.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]