[jira] Created: (TIKA-61) Add namespaces to our metadata keys

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] Created: (TIKA-61) Add namespaces to our metadata keys

JIRA jira@apache.org
Add namespaces to our metadata keys
-----------------------------------

                 Key: TIKA-61
                 URL: https://issues.apache.org/jira/browse/TIKA-61
             Project: Tika
          Issue Type: Improvement
            Reporter: Bertrand Delacretaz
            Priority: Minor


To avoid collisions, we should namespace our metadata keys, using something like

// a) Set Dublin Core title
metadata.set("http://purl.org/dc/elements/1.1/", "title", title);

// b) Set OpenDocument keywords
metadata.set(
  "urn:oasis:names:tc:opendocument:xmlns:meta:1.0",
   "keywords", keywords);

Or also using the namespace prefix in the name:

// c)
metadata.set(
     "urn:oasis:names:tc:opendocument:xmlns:meta:1.0",
        "dc:keywords", keywords);

not sure what the implications of c) are. If the key is composed of the namespace URL and item name we should be fine, so for case a) I'd use

  http://purl.org/dc/elements/1.1/#title

for the key, and escape # if it is used in either the namespace URL or item name.


--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Updated: (TIKA-61) Add namespaces to our metadata keys

JIRA jira@apache.org

     [ https://issues.apache.org/jira/browse/TIKA-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris A. Mattmann updated TIKA-61:
----------------------------------

        Fix Version/s: 0.2-incubating
    Affects Version/s: 0.1-incubating

> Add namespaces to our metadata keys
> -----------------------------------
>
>                 Key: TIKA-61
>                 URL: https://issues.apache.org/jira/browse/TIKA-61
>             Project: Tika
>          Issue Type: Improvement
>          Components: metadata
>    Affects Versions: 0.1-incubating
>            Reporter: Bertrand Delacretaz
>            Assignee: Chris A. Mattmann
>            Priority: Minor
>             Fix For: 0.2-incubating
>
>
> To avoid collisions, we should namespace our metadata keys, using something like
> // a) Set Dublin Core title
> metadata.set("http://purl.org/dc/elements/1.1/", "title", title);
> // b) Set OpenDocument keywords
> metadata.set(
>   "urn:oasis:names:tc:opendocument:xmlns:meta:1.0",
>    "keywords", keywords);
> Or also using the namespace prefix in the name:
> // c)
> metadata.set(
>      "urn:oasis:names:tc:opendocument:xmlns:meta:1.0",
>         "dc:keywords", keywords);
> not sure what the implications of c) are. If the key is composed of the namespace URL and item name we should be fine, so for case a) I'd use
>   http://purl.org/dc/elements/1.1/#title
> for the key, and escape # if it is used in either the namespace URL or item name.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Assigned: (TIKA-61) Add namespaces to our metadata keys

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

     [ https://issues.apache.org/jira/browse/TIKA-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris A. Mattmann reassigned TIKA-61:
-------------------------------------

    Assignee: Chris A. Mattmann

> Add namespaces to our metadata keys
> -----------------------------------
>
>                 Key: TIKA-61
>                 URL: https://issues.apache.org/jira/browse/TIKA-61
>             Project: Tika
>          Issue Type: Improvement
>          Components: metadata
>    Affects Versions: 0.1-incubating
>            Reporter: Bertrand Delacretaz
>            Assignee: Chris A. Mattmann
>            Priority: Minor
>             Fix For: 0.2-incubating
>
>
> To avoid collisions, we should namespace our metadata keys, using something like
> // a) Set Dublin Core title
> metadata.set("http://purl.org/dc/elements/1.1/", "title", title);
> // b) Set OpenDocument keywords
> metadata.set(
>   "urn:oasis:names:tc:opendocument:xmlns:meta:1.0",
>    "keywords", keywords);
> Or also using the namespace prefix in the name:
> // c)
> metadata.set(
>      "urn:oasis:names:tc:opendocument:xmlns:meta:1.0",
>         "dc:keywords", keywords);
> not sure what the implications of c) are. If the key is composed of the namespace URL and item name we should be fine, so for case a) I'd use
>   http://purl.org/dc/elements/1.1/#title
> for the key, and escape # if it is used in either the namespace URL or item name.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Updated: (TIKA-61) Add namespaces to our metadata keys

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

     [ https://issues.apache.org/jira/browse/TIKA-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris A. Mattmann updated TIKA-61:
----------------------------------

    Component/s: metadata

> Add namespaces to our metadata keys
> -----------------------------------
>
>                 Key: TIKA-61
>                 URL: https://issues.apache.org/jira/browse/TIKA-61
>             Project: Tika
>          Issue Type: Improvement
>          Components: metadata
>    Affects Versions: 0.1-incubating
>            Reporter: Bertrand Delacretaz
>            Priority: Minor
>             Fix For: 0.2-incubating
>
>
> To avoid collisions, we should namespace our metadata keys, using something like
> // a) Set Dublin Core title
> metadata.set("http://purl.org/dc/elements/1.1/", "title", title);
> // b) Set OpenDocument keywords
> metadata.set(
>   "urn:oasis:names:tc:opendocument:xmlns:meta:1.0",
>    "keywords", keywords);
> Or also using the namespace prefix in the name:
> // c)
> metadata.set(
>      "urn:oasis:names:tc:opendocument:xmlns:meta:1.0",
>         "dc:keywords", keywords);
> not sure what the implications of c) are. If the key is composed of the namespace URL and item name we should be fine, so for case a) I'd use
>   http://purl.org/dc/elements/1.1/#title
> for the key, and escape # if it is used in either the namespace URL or item name.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.