MHonArc v2.5.0b2 -->
emergency message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Re: [emergency] URN namespace for EDXL
Since these are internal fixed enumerations, seems like they're
already scoped by the namespacing of the schema... so making them
longer wouldn't seem to make them any more unique. That's as opposed
to the "external" vocabularies we're contemplating for other fields.
(And in that latter case I'm not sure we'll be able to enforce any
particular format on the various list managers, although presumably
identifying URNs and maybe URIs can be assigned to the lists as a
whole, which seems to amount to the same thing.)
I do, however, think we need to start using the OASIS URN for
namespacing our schemas... since a URI seems unavoidably to be
assumed to be a schema location.
- Art
On Jun 27, 2005, at 6/27/05 11:06 PM, Renato Iannella wrote:
> Hi all - two of the EDXL elements (Distribution Status,
> Distribution Type)
> define their own vocabulary of values (eg Actual, Exercise, System,
> Test - for Status).
>
> Should we utlise the formal URN mechanism (that other OASIS
> technical committees use)
> to give these all unique names instead?
>
> For example:
> urn:oasis:names:tc:em:edxl:status:actual
> urn:oasis:names:tc:em:edxl:status:exercise
>
> (not sure of the exact components for the URN - is there an OASIS
> document on that?)
>
> The main advantage is that we uniquely identify the source of the
> vocabulary, and later,
> we may wish to support other vocabularies.
>
>
> Cheers... Renato Iannella
> Project Leader, NICTA, Brisbane, QLD, AUSTRALIA
> P: +61 7 3000 0484 F: +61 7 3000 0480 M: +61 4 1313 2206
> E: renato@nicta.com.au W: http://nicta.com.au
>
>
> ----------------------------------------------------------------------
> ----
> This email and any attachments may be confidential. They may
> contain legally
> privileged information or copyright material. You should not read,
> copy,
> use or disclose them without authorisation. If you are not an intended
> recipient, please contact us at once by return email and then
> delete both
> messages. We do not accept liability in connection with computer
> virus,
> data corruption, delay, interruption, unauthorised access or
> unauthorised
> amendment. This notice should not be removed.
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail. You may a link to this group and 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]