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

 


Help: OASIS Mailing Lists Help | MarkMail Help

bdxr-comment message

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


Subject: Question on the SMP identifiers


Dear BDXR technical committee,

We, at CEF eDelivery, have a question regarding the OASIS Service Metadata Publishing (SMP) Version 1.0 Committee Specification 03. It seems inconsistent with defining Identifiers' scheme emptiness.

The problem touches all 3 Identifiers used: ParticipantIdentifier, DocumentIdentifier, ProcessIdentifier – but we will focus on DocumentIdentifier to describe the issue clearly:

2.4.6 Document Identifier
2.4.6.1 Introduction

{rootNamespace}::{documentElementLocalName}[##{Subtype identifier}]
Where [ ] denotes an optional part of the identifier, and everything outside { } are string literals.
This implies that "rootNamespace" (which is called "scheme" in other places) is mandatory.
While few lines below:
 
2.4.6.2 XML Representation of Document Identifiers
Pseudo-scheme for DocumentIdentifier:
<DocumentIdentifier [scheme=xs:string]>xs:string</DocumentIdentifier>
 
This time "scheme" is defined as "optional".
 
We made some tests with official OASIS XSD, all these values pass XSD validation successfully:
<ParticipantIdentifier scheme="">string</ParticipantIdentifier>
<ParticipantIdentifier>string</ParticipantIdentifier>
<ParticipantIdentifier></ParticipantIdentifier>
<ParticipantIdentifier/>
 
There are 2 questions for which we need your help:
1.       Is "scheme" mandatory or not for each of 3 identifiers?
2.       If "scheme" is not mandatory, than what is their URL-representation?
::{IdentifierValue}
or this:
{IdentifierValue}

Best regards,

Adrien FERIAL
CEF eDelivery


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